[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ID-nits



Mike wrotes and asked:
> > - Appendix A
> >   - add a bullet to do a general/overall check on ID-NITs
> >     with ptr to it of course
> 
> OK.  How about the following:
> 
>    10.) Other issues -- check for any issues mentioned in
>    http://www.ietf.org/ID-nits.html that are not covered above.
> 
> The technical content bullet would then become #11.
> 
Good

> While I have your attention:  one of the promised fixes
> to http://www.ietf.org/ID-nits.html is incompletely
> implemented.  It now says:
> 
>      * All MIBs must compile cleanly using "smilint -m -s -l 9 -i
>        namelength-32"
> 
> and this is still not quite right: ``must'' needs to
> be changed to ``should'', otherwise ID-nits and the
> guidelines doc will be out-of-sync.

So did I screw that up? Possibly. Don't worry, I take the blame.
I will try and get it fixed. 
As you may have noticed, changes to those pages do 
not go easy, let alone quickly.

> I'd like to
> suggest a formatting change too, so that it would read:
> 
>      * All MIBs should compile cleanly using
>        "smilint -m -s -l 9 -i namelength-32"
> 
I did tell them to reformat right after it got posted
in the (in my view screwed up) format. It seems I need
to keep micro-managing/guiding that till it is actually
correct. Oh well... that's why I get the big bucks I guess.

> The other fix (regarding the IANA considerations section) is
> also formatted rather poorly, and I request that
> 
>      * Required if the document requires IANA to assign or update values
>        in an IANA registry before RFC publication. Note that for the
>        assignment of just an OID for a MIB or PIB Module, no IANA
>        Considerations section is required; it is sufficient to request
>        such via a MIB/SMI or PIB/SPPI comment line, aka: ::= 
> { mib-2 xxx
>        } -- xxx to be assigned by IANA
> 
> be changed to
> 
>      * Required if the document requires IANA to assign or update values
>        in an IANA registry before RFC publication. Note that for the
>        assignment of just an OID for a MIB or PIB Module, no IANA
>        Considerations section is required; it is sufficient to request
>        such via a MIB/SMI or PIB/SPPI comment line, aka:
>        ::= { mib-2 xxx } -- xxx to be assigned by IANA
> 
> (Note that only the layout is requested to be changed in the above)
> 
Same story... sigh.

I will follow up again.
If it is still in shambles a week from now, pls do alert me again

Bert
Thanks,
Bert