The MPLS WG Archive

["Thomas D. Nadeau" <tnadeau@cisco.com>]

         Hi Tim,


>       1) The syntax for mplsXCIndex is Integer32(0..2147483647), it
>          should be Integer32(1..2147483647).

         You are right. We will fix this in a rev. that we
will publish on Wednesday. We will wait until then in case
we get other comments from folks. We encourage all interested
parties to please read over the current draft and submit
any errors you might find ASAP. 8)

>       2) In the descriptions of both mplsInterfaceTotalBandwidth and
>          mplsInterfaceAvailableBandwidth, it says "kilobits per second
>          (Kbps/sec)". It should be "kilobits per second (Kbps)".
>
>       3) In the descriptions of both mplsTrafficParamMaxRate and
>          mplsTrafficParamMeanRate it says "rate in bits/second". It
>          should be "rate in kilobits/second".

         We will fix these in the next revision. Dang typos.

>       4) The syntax for mplsInSegmentNPop is Integer32(1..2147483647).
>          Zero should be a valid value. Also, it was previously agreed
>          that INTEGER(0..255) was a better syntax for this object.

         The top most label must always be popped, so the default
value of this is set to 1, and the range correctly begins at
1. A value of 0 does not make sense.

>       5) For consistency, mplsMaxLabelStackDepth should also have a
>          syntax of INTEGER(1..255).

         The motivation was that the framework document did not
preclude the use of label stacks greater than 255, although we
couldn't determine why anyone would ever want to do this.

         --Tom