Translation of Structure of Management Information Version 2 (SMIv2) MIB Modules to YANG Modules
RFC 6643
Yes
No Objection
Note: This ballot was opened for revision 05 and is now closed.
(Benoît Claise; former steering group member) Yes
(Ron Bonica; former steering group member) Yes
(Adrian Farrel; former steering group member) No Objection
I found the text "config false" a bit out of context. Can you provide some explanation?
(Barry Leiba; former steering group member) No Objection
(Brian Haberman; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection
(Pete Resnick; former steering group member) No Objection
The author has addressed my concerns about internationalization. Thanks.
(Robert Sparks; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Sean Turner; former steering group member) No Objection
s4.2: Is it worth having a default yang statement added to all converted MIBs that says this module was converted from SMIv2 to YANG using RFC X? Maybe it's called conversion?
(Stephen Farrell; former steering group member) No Objection
Just wanna check two things, they're probably ok already though... 1. An ASN.1 INTEGER can be multi-precision (e.g. 2048 bits). Not sure if that's allowed in SMIv2 but if so, worth a mention? Section 2 implies 32 bits is enough. 2. OID arcs can similarly be >32 bits long so if those were just mapped to 32 bit values that'd be bad.
(Stewart Bryant; former steering group member) No Objection
(Wesley Eddy; former steering group member) No Objection