Subject: Re: MPLS TE MIB

From: Adrian Farrel <[email-masked]>
Date: Fri, 7 Jan 2000 13:54:10 -0000

Tom,

A further thought...

The CR-LDP ER-Hop TLV can be of type LSPID to allow an LSP to be "tunneled"
down another LSP for the next hop.

This is not currently reflected in the MIB.

I think you need to modify as follows.

MplsTunnelHopEntry ::= SEQUENCE {
      mplsTunnelHopIndex              Integer32,
      mplsTunnelHopAddrType           INTEGER,
      mplsTunnelHopIpv4Addr           IpAddress,
      mplsTunnelHopIpv4PrefixLen      INTEGER,
      mplsTunnelHopIpv6Addr           Ipv6Address,
      mplsTunnelHopIpv6PrefixLen      INTEGER,
      mplsTunnelHopAsNumber           INTEGER,
      mplsTunnelHopLspId              INTEGER,
      mplsTunnelHopStrictOrLoose      INTEGER,
      mplsTunnelHopRowStatus          RowStatus
   }

mplsTunnelHopAddrType OBJECT-TYPE
   SYNTAX        INTEGER { 
           ipV4(1),
           ipV6(2),
           asNumber(3),
           lspId(4)
      }
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "Address type of this hop."
   DEFVAL        { ipV4 }
   ::= { mplsTunnelHopEntry 2 }

mplsTunnelHopLspId OBJECT-TYPE
   SYNTAX        OCTET STRING (SIZE(6))
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
       "If mplsTunnelHopAddrType is lspId(4), the LSPID
        over which to route this hop.  This is encoded as
        two bytes of Local LSPID followed by four bytes of
        Ingress LSR Router ID.
        This object is not significant otherwise and should
        return a value of 0."
   ::= { mplsTunnelHopEntry 8 }

What do you think?

Regards,
Adrian
--
Adrian Farrel  mailto:[email-masked]
ATM, MPLS and Telecoms Development Group
Data Connection Ltd., Chester, UK
http://www.datcon.co.uk/
Tel: +44 (0) 1244 313440  Fax: +44 (0) 1244 312422