The MPLS-OPS Archive

[Rajiv Asati <rajiva@cisco.com>]

Devendra,

> > customer service provider's POPs or regional networks. If all of the 
> customer
> > service provider's sites have the same AS number, then the BGP/MPLS VPN 
> transit
> > service provider delivers a carrier-of-carriers service.

Yup.

> > If the customer service
> > provider's sites have different AS numbers, then the BGP/MPLS VPN transit
> > service provider supports multi-AS operations."
> > AFAIK, this refers to multi-carrier , interprovider(inter-AS?) MPLS/BGP 
> VPN's .....

Not necessarily. If the motive is to provide the transport service, then 
CsC is still the way to go.
Whether the ASN values are the same or not usually has no relevance to the 
above conclusion.

And this is no different from the usual VPN service. Think of it as the 
following -
  1) If the VPN customer has the same ASN in all the sites, then the SP 
need to use "as-override"
      to facilitate the CE routes being accepted at the other CEs.
  2) If the VPN customer has unique ASN in each site, then the SP doesn't 
need to use
      any special knob, since BGP (at the CE) would accept the remote site 
routes just fine.



> >
> > so a service provider x in india can tie up with service provider y in 
> malaysia
> > ----and a customer can get an end to service thru these 2 service 
> providers
> > using the BGP/MPLS VPN model.

Now, the motive has changed. You want to service the same VPN customer 
which has sites spread across two SPs and want seamless VPN connectivity. 
Hence the need for Inter-AS, in which two SPs peer with each other at one 
or two locations. Of course, this requires agreements regarding number of 
VPN routes, amount of traffic, SLA, QoS etc to be negotiated.

Important to note that we are referring to "tie-up" -> Partnership here.

But keep in mind that if the same VPN customer is already serviced by two 
different SPs, then Inter-AS is only way to provide seamless VPN 
connectivity. CsC helps to provide the transport service to another (baby) 
SP, hence the VPN customer of baby SP will not be able to talk to the VPN 
customer of parent SP (without some heavy lifting and hair loss).

Hope this helps.

Cheers,
Rajiv

At 10:47 PM 1/21/2005, Maher Adib wrote:

>Thanks for the info. Perhaps this is what you are looking for?
>
>http://www.cisco.com/warp/public/105/interasvpn.html
>
>http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/interas.htm
>
>regards,
>
>maher
>
>Devendra.Vyas@relianceinfo.com wrote:
> > cut and pate from the net
> >
> > "hierarchical and recursive BGP/MPLS VPNs are described in RFC 2547bis. As
> > BGP/MPLS VPNs are deployed in the Internet, it is possible that the 
> customer of
> > a BGP/MPLS VPN service provider is another service provider rather than an
> > enterprise customer. For this scenario, the customer service provider 
> depends on
> > the BGP/MPLS VPN service provider to deliver a transport service 
> between the
> > customer service provider's POPs or regional networks. If all of the 
> customer
> > service provider's sites have the same AS number, then the BGP/MPLS VPN 
> transit
> > service provider delivers a carrier-of-carriers service. If the 
> customer service
> > provider's sites have different AS numbers, then the BGP/MPLS VPN transit
> > service provider supports multi-AS operations."
> >
> >
> > AFAIK,
> >
> > this refers to multi-carrier , interprovider(inter-AS?) MPLS/BGP VPN's 
> .....
> >
> > so a service provider x in india can tie up with service provider y in 
> malaysia
> > ----and a customer can get an end to service thru these 2 service 
> providers
> > using the BGP/MPLS VPN model.
> >
> >
> > others- correct me if im wrong
> >
> >
> > Thanks & Regards,
> >
> > Devendra Vyas
> >
> > Inactive hide details for Maher Adib <maher@pd.jaring.my>Maher Adib
> > <maher@pd.jaring.my>
> >
> >
> >
> >
> >
> >                         *Maher Adib <maher@pd.jaring.my>*
> >
> >                         01/21/2005 06:55 PM
> >
> >
> >
> > To: Devendra.Vyas@relianceinfo.com
> > cc: mpls-ops@mplsrc.com
> > Subject: Re: [MPLS-OPS]: Re: MPLS on Interface/ recursive VPNS
> >
> >
> >
> > Hi there,
> >
> > I personally do not know what is Recursive VPN's. Can you please
> > elobrate more about it.
> >
> > Thanks.
> >
> > maher
> >
> > Devendra.Vyas@relianceinfo.com wrote:
> >  > the second someone to be read as someplace....................
> >  >
> >  > secondly can someone point me to someone(SOMEPLACE:-))LOL) where i 
> can get the
> >  > aroma of wots cooking on the Recursive VPN's front in the industry. 
> ------- 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

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml