Re: MPLS VPN: Why two lables?

From: Paul Negron <negron.paul_at_gmail.com>
Date: Sun, 03 Jul 2011 11:47:11 -0600

It's just like the ATM days. You need one label to represent the Virtual
Path and one label to represent the Virtual Connection.

A Tunnel within a Tunnel.

It's like asking why we use 2 encapsulations for QinQ.

Paul

-- 
Paul Negron
CCIE# 14856 CCSI# 22752
Senior Technical Instructor
www.micronicstraining.com
> From: marc abel <marcabel_at_gmail.com>
> Reply-To: marc abel <marcabel_at_gmail.com>
> Date: Sun, 3 Jul 2011 12:13:49 -0500
> To: Vladimir Osipenko <tiffolk_at_gmail.com>
> Cc: <ccielab_at_groupstudy.com>
> Subject: Re: MPLS VPN: Why two lables?
> 
> The biggest efficiency with the labels might be that P routers don't
> have to speak BGP, they just need to know the routes to the BGP
> speaking PE routers.
> 
> On Sun, Jul 3, 2011 at 11:44 AM, Vladimir Osipenko <tiffolk_at_gmail.com> wrote:
>> Hi, Guys!
>> 
>> Despite reading books and articles, I simply don't get it: why we must
>> use two lables for MPLS VPN instead of using one label, but without
>> PHP?
>> 
>> Is it because every P router will need to know customer routes? Any
>> other reasons?
>> 
>> 
>> Blogs and organic groups at http://www.ccie.net
>> 
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
> 
> 
> Blogs and organic groups at http://www.ccie.net
> 
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Sun Jul 03 2011 - 11:47:11 ART

This archive was generated by hypermail 2.2.0 : Mon Aug 01 2011 - 06:30:05 ART