The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Feb> msg00077



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

Question on Draft IETF MPLS LSR MIB 07: Segment and XC tables indexes

  • From: "Dave Danenberg" <dave_danenberg@litchfieldcomm.com>
  • Date: Mon, 12 Feb 2001 08:59:19 -0500
  • Cc: "Thomas D. Nadeau" <tnadeau@cisco.com>
  • Thread-Index: AcCU+/53ki08BD1DQgGudVjHAyI1hQ==
  • Thread-Topic: Question on Draft IETF MPLS LSR MIB 07: Segment and XC tables indexes
  • X-MIME-Autoconverted: from quoted-printable to 8bit by cell.onecall.net id JAA12354

I just noticed that Section 8 "Example of LSP Setup" and the MIB objects
conflict. The example shows the XCTable referencing entries in the
segmentTables, but the segment entries do not reference the XC table
entry. then looking at the actual MIB you see the opposite: the in and
out segment entries each reference the XC entry, but the XC entry does
not reference the segments.
 
I would think it would be useful for the XC entry to reference the
segments as shown in the example. Starting from a tunnel entry, you can
get to the XC entry, but then you can not get to the cross-connect
segments. I would think that you would especially need the inSegment
indexes for obtaining the inbound label. 
 
Is this something, that has been noted already? Will the Example vs MIB
conflict be resolved? Will the segment indexes be added to the XC table?
 
Thanx,
Dave