Translation of Structure of Management Information Version 2 (SMIv2) MIB Modules to YANG Modules
draft-ietf-netmod-smi-yang-05
Yes
(Benoît Claise)
(Ron Bonica)
No Objection
(Barry Leiba)
(Brian Haberman)
(Martin Stiemerling)
(Robert Sparks)
(Russ Housley)
(Stewart Bryant)
(Wesley Eddy)
Note: This ballot was opened for revision 05 and is now closed.
Benoît Claise Former IESG member
Yes
Yes
()
Unknown
Ron Bonica Former IESG member
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
(2012-04-25)
Unknown
I found the text "config false" a bit out of context. Can you provide some explanation?
Barry Leiba Former IESG member
No Objection
No Objection
()
Unknown
Brian Haberman Former IESG member
No Objection
No Objection
()
Unknown
Martin Stiemerling Former IESG member
No Objection
No Objection
()
Unknown
Pete Resnick Former IESG member
No Objection
No Objection
(2012-04-26)
Unknown
The author has addressed my concerns about internationalization. Thanks.
Robert Sparks Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Sean Turner Former IESG member
No Objection
No Objection
(2012-04-25)
Unknown
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 IESG member
No Objection
No Objection
(2012-04-24)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown
Wesley Eddy Former IESG member
No Objection
No Objection
()
Unknown