MIB review guidelines open issues list

["C. M. Heard" <heard@pobox.com>]

Howdy,

I've attached a list of open issues for
<draft-ietf-ops-mib-review-guidelines-00.txt>

I think it covers everything that's been 
discussed on the mreview list so far.  Please
let me know if I missed anything.

It would be nice if we could get the bulk of
these resolved in time to post an updated
draft well before the IETF-56 blackout date
of March 3rd.

Thanks,

Mike

Issue                     Section  Status  Comments

More specific security    3.6      Open    Text proposed by Bert & Mike;
instructions are needed                    additions requested by dbh.

Importing items used in   4.4      Open    Text proposed to change from
compliance statements &                    MAY to RECOMMENDED; call for
capabilities statements                    consensus issued.

Gauge32 as an index       4.6.1.1  Ready   s/appropriate/acceptable/ in
                                           paragraph on Gauge32 as index

Counter Discontinuity     4.6.1.2  Open    Adding ifCounterDiscontinuityTime
Indicators                                 as an example is proposed;
                                           awaiting feedback.

One houe rule             4.6.1.2  Open    Editor has proposed text to
                                           rescind the one-hour rule as
                                           obsolete;  awaiting feedback.

Non-contiguous BITS       4.6.1.6  Open    Current text says they are not
enumerations                               allowed;  RFC 2578 allows them
                                           only in revisions;  awaiting
                                           feedback on whether any form
                                           of ban is a CLR that should be
                                           done away with.

Should it be explicitly   4.6.4    Open    Editor has agreed to add such
statted that objects                       text if there is feedback
SHOULD NOT be registered                   requesting it.
beneath groups, MCs, ACs

Should it be mandated     4.6.5    Open    This was suggested on the list
that overall index size                    when we discussed the APM-MIB;
limit be spelled out in                    awaiting feedback.
tables where SIZE clauses
do not enforce the 128
sub-identifier limit

Should guidelines say     4.6.x    Open    Editor has requested that the
something about not                        proponents explain why IMPLIED
unsing IMPLIED                             is a bad idea.

Should index objects      4.7      Open    This was not mentioned because
in notifications be                        most index objects these days
NOT RECOMMENDED                            are inaccessible, and so are
                                           not eligible in the first place.
                                           Editor will add such text if it
                                           is requested;  awaiting feedback.

Typos in 4.9 para 4       4.9      Ready   s/implemantations/implementations/
                                           s/descriptions/descriptors/

Does SMICng include    Appendix C  Open    The include file in Appendix C
file need to be updated                    was built for book version 2.2.07