07-04-2012 01:47 AM
I have a customer who requires a private MPLS infrastructure to support his separate businesses. The use of private addresses and AS numbers for the formation of Route Distinguishers is ‘strongly discouraged’ in RFC 4364 (and arrangements for a connection to an Internet Service Provider have yet to be defined).
The question is whether the RFC recommendation should still apply when implemented outside the Internet; where there is no requirement to be globally unique?
Solved! Go to Solution.
07-04-2012 02:01 AM
It all depends, if in future you don't want to do the any nni or csc with any of the SP, in that case private is ok but if you have any plans to go global, I would suggest you to go with public AS + Public Loop back addresses.
regards
Shivlu Jain
07-04-2012 02:01 AM
It all depends, if in future you don't want to do the any nni or csc with any of the SP, in that case private is ok but if you have any plans to go global, I would suggest you to go with public AS + Public Loop back addresses.
regards
Shivlu Jain
07-09-2012 04:53 AM
Many thanks Shivlu, and I appreciate the clarification regarding NNI. Will be checking this thougherly with the client
kind regards, Dave Gabb
07-09-2012 05:10 AM
Hi
Please close the thread it it answer your question. If any mor ehelp is required, please let me know.
regards
shivlu jain
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: