The MPLS-OPS Archive

["M.V. Padmini" <padmini@genie.iitd.ernet.in>]

Well, the debate may not end so soon after all!!

First of all, when i meant unique labels - i meant it for a complete LSR
and among all LSRs not confinig to the ingress.

Philosophically or from the design perspective, the idea is to keep all
edges of the graph unique.  This should eliminate the need of label space.
 But this will lead to exhausting the labels very soon.  If u look at it
carefully, you may need to keep the labels unique only between two
adjacent sets of labels.  Never the less, by putting in the label space,
you are trying to build a heirarchical structure of labels.

Does that make sense?

> Hi,
>
> I feel label-space will be important even if u assign unique labels to
> FECs at the ingress LSR. Imagine thie scenario wherein,
>
> FECs A, B, C are assigned labels (1,2,3) uniquely by the ingress...
>
> At the next LSR, these labels are swapped (1,2,3)->(2,2,3), then in
> this case the information provided by the label-space would be
> important for swapping at the next LSR. (althou i am not really sure
> whether the swapping (1,2,3)->(2,2,3) is really valid !!)
>
> --Sundeep.
>
>
> On Fri, 17 Sep 2004, M.V. Padmini wrote:
>
>> Hi sudeep,
>>
>> Well, we are talking of a static routing scenario here.  When we
>> alreadly know the LSR, where where is the need to use the label space
>> info?  (well pardon me since i have still not read the doc.
>> completely!).  Since the labels on the LSRs are unique, there is no
>> question of messing up.  Well, as far as the simple routing is
>> concerned, unique label for every FEC should work fine.  May be its
>> required in some other cases i.e. Tunnel etc.  Am not sure.  The other
>> reason could be not to run out of labels!!
>>
>> - Padmini
>>



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