The MPLS WG Archive

["Manikantan S" <manis@future.futsoft.com>]

Hello Joan, Thomas

I have an another observation/suggestion with respect to the
CRLSP support. 

This is with respect to the ER Hop that is configured to be of
type LSPID. Currently we have support to configure the LSPID
value via the MIB object "mplsTunnelHopLspId" and the
have the MIB object "mplsTunnelHopAddrType" set to value "lspid".

For a ER Hop Type of LSPID, the Ingress LSR Router ID value is
also required. 

Can we add an object to facilitate this configuration?
(We have added this to our enterprises MIB to support LSPID ER hop
types).

The SMI for the object can be as follows.

mplsTunnelHopIngressRouterId MplsLsrId

mplsTunnelHopIngressRouterId OBJECT-TYPE
   SYNTAX        MplsLsrId
   MAX-ACCESS    read-create
   STATUS        current
   DESCRIPTION
          "If mplsTunnelHopAddrType is set to lspid(4), then
           this value will contain the IPv4 address of the
           Ingress Router ID of the Tunnel. This object is 
           otherwise insignificant and should contain a 
           value of 0."
  
NOTE: The suggestion made is for IPv4 Address alone here, since
the LSPID TLV currently supports IPv4 address type only.

Thanks in advance
with best regards
mani
-----------------------------------------
S.Manikantan
Future Software Limited
480-481, Anna Salai, 
Nandanam, Chennai, India.
Zip (PIN CODE) : 600 035
Phone          : 91-44-4330550
Fax            : 91-44-4344157
email          : manis@future.futsoft.com
-----------------------------------------