The MPLS WG Archive

[Anouk Rocher <anouk@ureach.com>]

David, 

Let me clarify with a more specific example. Lets say we want
to deploy one of the l2 vpn mechanisms - say the one in draft-maritini-*
The inner label there is negotiated between the ingress and egress
LSRs via LDP (sort of multi-hop). The inner label is negotiated (say)
via RSVP-TE.

I don't see a reason why LDP and RSVP-TE be forced to use the same
label space in this case. (I am sure there are similar cases while
using wavelengths as labels.)

Am I missing something obvious?

Anouk.


________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag


---- On Tue, 10 Jul 2001, David Charlap (david.charlap@marconi.com) wrote:

> Anouk Rocher wrote:
> > 
> > RFC 3031 in section 3.14 says (in the penultimate paragraph)
> > 
> >   "In MPLS, there is no notion of
> >    having a different label space for different levels of the
> >    hierarchy; when interpreting a label, the level of the label is
> >    irrelevant."
> > 
> > Does this mean that while doing label stacking, it is neccessary to
> > allocate labels from a single label space?
> 
> Yes.
> 
> > Isn't this a bit too restrictive for the cases where the inner
> > label represents customer traffic transiting a provider and the
> > outer label represents a path through the provider?
> 
> What's your alternative?  When a data packet arrives, how are you going
> to know what label space the top label should belong to?
> 
> -- David
> 
>