Re: MPLS-LSR-STD-MIB (RFC 3813) errata

[Keith McCloghrie <kzm@cisco.com>]

As I recall, that appendix was written by Dave, and so perhaps he
can answer your question.

Keith.

> On Sun, 13 Feb 2005, Michael Kirkham wrote:
> > [MPLS-LSR-STD-MIB:mplsLsrModuleReadOnlyCompliance:MPLS-LSR-STD-MIB:mplsInSegmentNPop]
> > : error : Invalid size/range subspecification '1..1' -- must be '1'.
> > 
> > The following variation is not legal:
> s/variation/refinement/
> > 
> >     OBJECT       mplsInSegmentNPop
> >     SYNTAX       Integer32 (1..1)
> >     MIN-ACCESS   read-only
> >     DESCRIPTION "Write access is not required.  This object
> >                  SHOULD be set to 1 if it is read-only.
> > 
> > It must be:
> > 
> >     OBJECT       mplsInSegmentNPop
> >     SYNTAX       Integer32 (1)
> >     MIN-ACCESS   read-only
> >     DESCRIPTION "Write access is not required.  This object
> >                  SHOULD be set to 1 if it is read-only.
> > 
> > Ref: RFC 2578, section 11.1:
> > 
> >                  - when a pair of values is specified, the first value
> >                    must be less than the second value.
> 
> Interesting.  One wonders why RFC 2578 was written in such a restrictive
> way.  However, the language is quite clear, and the cited construct in
> the MIB module violates it.  So I would have to agree that this should
> be written up as an RFC Erratum.
> 
> I note that neither smilint (current version) nor SMICng (book
> version) catches this particular error.
> 
> Mike Heard
>