The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: Addressing PE/ CE Links - 2547
Hi Thamir, The point-to-point interfaces are assigned by the provider, using private address space. The provider would manage the assignment across all their interfaces regardless of which VPN the interface would exist in. For internet connecting VPNs, the addresses assigned would be registered Internet numbers to ensure traceroutes / path MTU discovery work. Route Distinguishers applied to routes advertised in the SP would prevent overlap issues in the core. Customer networks are free to advertise any routes they wish to use, except for the addresses assigned to their PE-CE links. Cheers, Truman On 21/05/2005, at 10:51 PM, Thamir M.Al Hammad wrote: > > Hi Truman, > > If they are using private IP addresses, how they can guarantee no > overlap in the addresses between the customers is happened? > > > Best regards, > > Thamir M Alhammad > > -----Original Message----- > From: Truman Boyes [mailto:truman@suspicious.org] > Sent: Friday, May 20, 2005 1:37 AM > To: mpls_buchaill@zen.co.uk > Cc: mpls-ops@mplsrc.com > Subject: Re: [MPLS-OPS]: Addressing PE/ CE Links - 2547 > > On 20/05/2005, at 2:26 AM, MPLS Buchaill wrote: > > >> Hi Guys, >> >> >> >> There seems to be mixed opinion on what addressing should be >> applied to PE-CE links for MPLS VPN. I know Jim Guichard >> highlighted a lot of the common issues in his draft in 2003 but was >> wondering what practical experience has shown? >> >> >> >> Just wondering what is the general experience and common practice >> on a large scale, RFC1918, customer or registered? >> >> >> >> D >> > Many large carriers that I have worked with use private addressing > for PE-CE links in MPLS VPNs. If the VPN is to provide internet > connectivity, they will generally number the links with allocated and > registered address space. > > As long as there is communication between the carrier and the > customer and service recommendations are given, the odds of address > conflict on various /31 prefixes is quite low. > > Truman > > ------- > The MPLS-OPS Mailing List > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > MPLScon 2005 - May 16-19, NYC, NY > http://www.mplscon.com/ > > > DiscalimerThe information in this email and in any files > transmitted with it, > is intended only for the addressee and may contain confidential and/ > or privileged material. > Access to this email by anyone else is unauthorized. If you receive > this in error, > please contact the sender immediately and delete the material from > any computer. > If you are not the intended recipient, any disclosure, copying, > distribution or > any action taken or omitted to be taken in reliance on it, is > strictly prohibited. > Statement and opinions expressed in this e-mail are those of the > sender, and do not > necessarily reflect those of STC. > > ------- > The MPLS-OPS Mailing List > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
|
|