Translation of Structure of Management Information Version 2 (SMIv2) MIB Modules to YANG Modules
RFC 6643

Note: This ballot was opened for revision 05 and is now closed.

(Ron Bonica) Yes

(Benoît Claise) Yes

(Stewart Bryant) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

Comment (2012-04-25)
No email
send info
I found the text "config false" a bit out of context. Can you provide 
some explanation?

(Stephen Farrell) No Objection

Comment (2012-04-24)
No email
send info
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.

(Brian Haberman) No Objection

(Russ Housley) No Objection

Barry Leiba No Objection

(Pete Resnick) No Objection

Comment (2012-04-26)
No email
send info
The author has addressed my concerns about internationalization. Thanks.

(Robert Sparks) No Objection

(Martin Stiemerling) No Objection

(Sean Turner) No Objection

Comment (2012-04-25)
No email
send info
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?