The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Jan> msg00154



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

mpls lsr mib

  • From: francis.arts@alcatel.be
  • Date: Thu, 24 Jan 2002 15:54:24 +0100
  • Cc: mpls@UU.NET
  • X-MIMETrack: Serialize by Router on BEMAIL06/BE/ALCATEL(Release 5.0.8 |June 18, 2001) at01/24/2002 15:54:31,Serialize complete at 01/24/2002 15:54:31


Tom,

> First, how can you use two different label spaces to advertise over
> the same interface?  I have never heard of this behavior before. One
> assigns a per-interface label range that is unique for that interface
> only, no?


The idea is to split the label range in 2 partitions that are mutually exclusive -1 partition for the per interface label space and 1 partition for the global label range. My understanding is that this behavior is also supported in the mpls lsr mib where the mplsInterfaceLabelParticipationType obejct has then both its perPlatform and perInterface set for each ifIndex /= 0.

For example:
* For a static LSP we will use a label from the per interface label space.
* For an LDP established LSP we will use a global label (==> so for LDP we will only advertise the global label space).


But the point that this not clear to me, is how the mplsInterfaceLabelMinIn object in the mpls lsr mib should be set in the above approach.

Best regards,

        Francis.

-----------------------------------



"Thomas D. Nadeau" <tnadeau@cisco.com>

24/01/2002 15:29

       
        To:        Francis ARTS/BE/ALCATEL@ALCATEL
        cc:        mpls@UU.NET
        Subject:        Re: mpls lsr mib





>Hello Tom et all,
>
>I have a question on the mplsInterfaceConfTable in the mpls lsr mib.
>IAssume that we consider the following:
>* Per interface label space used for RSVP signalled LSPs and static LSPs.
>* Global label space used for LDP signalled LSPs.

        First, how can you use two different label spaces to advertise over
the same interface?  I have never heard of this behavior before. One
assigns a per-interface label range that is unique for that interface
only, no?

        --Tom


>Which value should we then give to the mplsInterfaceLabelMinIn:
>* The min label value of the per interface label space (that is, the min
>label value from the RSVP signalled LSPs and the static LSPs)?
>* The min label value of the RSVP signalled LSPs.
>* The min label value of all LSPs on the interface (=min of all LDP
>signalled, RSVP signalled and static LSPs).
>
>I would appreciate any help you can give me.
>
>Kind regards,
>
>         Francis.
>
>--------------------------------
>
>mplsInterfaceLabelMinIn OBJECT-TYPE
>    SYNTAX        MplsLabel
>    MAX-ACCESS    read-only
>    STATUS        current
>    DESCRIPTION
>        "This is the minimum value of an MPLS label that this
>         LSR is willing to receive on this interface."
>    ::= { mplsInterfaceConfEntry 2 }



------------------------------------------------------------------------
Mathematics is the supreme nostalgia of our time.