Subject: FW: Revision to draft-ietf-mpls-lsr-mib-00.txt

From: Hywel Jones <[email-masked]>
Date: Mon, 22 Nov 1999 16:37:11 -0000

As previously discussed on the MPLS list, there are a number of issues with
the current wording of section 7 of the LSR MIB document,
draft-ietf-mpls-lsr-mib-00.txt, which gives an example setup of an LSP with
an in-segment, an out-segment, along with cross connect entries. 

In order to move this forward I have attached some suggested text below.
Does anyone have any issues with it?  Can we incorporate it into the next
version of the draft?

In summary, my changes are

- fix the incorrect reference to bi-directional LSP
- clarify the setup of the cross connect by specifying a single entry in the
mplsXCTable

Regards
Hywel

----------------------------------------------------------
Hywel Jones
Software Engineer, ATM, MPLS and Telecoms Development Group
Data Connection Ltd
Tel:  +44 1244 313440	Fax:  +44 1244 312422
Email:  [email-masked]	Web:  http://www.datcon.co.uk
-----------------------------------------------------------

This text to completely replace the existing section 7 of 
draft-ietf-mpls-lsr-mib-00.txt
                             
7. Specifying the Segments of an LSP
                             
   Suppose that we want to manually create a best-effort uni-
   directional LSP, consisting of an in-segment and an out-segment on
   an LSR (with no label stack beneath the top label on the outgoing
   labeled packets). The following rows and corresponding objects
   need to be created to do this.

   First, the in-segment and the out-segment are created with the
   appropriate traffic parameters.

   In mplsInSegmentTable:
   {
      mplsInSegmentIfIndex = i1,
      mplsInSegmentLabel = l1,
      mplsInSegmentNPop = 1,
      mplsInSegmentTSpecIndex = 0,
      mplsInSegmentRowStatus = createAndGo(3)
   }

   In mplsOutSegmentTable:
   {
      mplsOutSegmentIndex = o,
      mplsOutSegmentIfIndex = i2,
      mplsOutSegmentPushTopLabel = true(1),
      mplsOutSegmentTopLabel = l2,
      mplsOutSegmentTSpecIndex = 0,
      mplsOutSegmentRowStatus = createAndGo(3)
   }

   Next, a single cross-connect entry associating these two segments
   is created.

   In mplsXCTable:
   {
      mplsXCIndex = x,
      mplsInSegmentIfIndex = i1,
      mplsInSegmentLabel = l1,
      mplsOutSegmentIndex = o,
      mplsLabelStackIndex = 0,
      mplsXCRowStatus = createAndGo(3)
   }

   Note that the objects mplsInSegmentXCIndex and
   mplsOutSegmentXCIndex automatically get populated with the
   value "x" when these segments are referred to from the
   cross-connect entry.