The MPLS WG Archive

[Adrian Farrel <AF@datcon.co.uk>]

Tom, Thanks.

>>>>3. LSPId explicit hop type 
>>>>Is there any reason to prevent configuration of an explicit hop 
>>>>of type LSPId?  I suggested some ASN.1 for this in an email to 
>>>>Tom on 7th Jan. 

>>>If ldp is chosen to route the tunnel then we'll add this as 
>>>a choice for the hop type. 

>>I'm not quite sure what your answer means.  I think you're
>>saying you'll add the hop type but only allow it if the 
>>signaling protocol is flagged as [CR-]LDP.  This would be
>>great.

>        Perhaps I was confused about this. Now that Arun and I 
>have discussed this, we now recall that we agreed to add this.
>Here is a description of the object type. We have also added the
>LSP ID to the hop entry as well.
>
>mplsTunnelHopAddrType OBJECT-TYPE
>SYNTAX        INTEGER {ipV4(1), 
>                       ipV6(2), 
>                       asNumber(3), 
>                       lspid(4) 
>                      }

Great.  Thanks, that's just what I wanted.  You'll also need to add another
object to express a hop of this type as I suggested in January, viz.

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

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 }


>>>>6. MPLS Tunnel Resource Table 
[Lots of pruning!]

OK.  I think we now have the same understanding on most of this.
We have...
- mplsTunnelResourceTable is configured and not updated by 
  the protocol code
- mplsTrafficParamTable reflects the actual reservations made
- if two rows in the mplsTunnelTable reference the same row in
  the mplsTunnelResourceTable and the protocol is RSVP then
  the LSPs have the same TSpec
- if two rows in the mplsIn/OutSegmentTable reference the same
  row in the mplsTrafficParamTable then the segments share the 
  same reserved resources

Adrian
--
Adrian Farrel  mailto:af@datcon.co.uk
Network Convergence Group
Data Connection Ltd., Chester, UK
http://www.datcon.co.uk/
Tel: +44 (0) 1244 313440  Fax: +44 (0) 1244 312422