Definition of Managed Objects for the Neighborhood Discovery Protocol
RFC 6779

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

(Adrian Farrel) Yes

(Stewart Bryant) No Objection

Comment (2012-05-23 for -13)
No email
send info
I am voting no objection on the basis that other members of the IESG who are more knowledgeable on MIBS will have reviewed this.

(Gonzalo Camarillo) No Objection

(Benoît Claise) (was Discuss) No Objection

Comment (2012-09-10)
No email
send info
Thank you for your good work, which addresses my DISCUSS/COMMENT

Note regarding the applicability statement: This is solved, as we discussed, but I'll keep this little sentence in one 
corner of my head "A fuller discussion of MANET network management use cases 
and challenges will be provided elsewhere."

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Stephen Farrell) No Objection

Comment (2012-05-21 for -13)
No email
send info
I agree with Sean's discuss. DES just isn't up to this these
days.

p60 - I think you mean confidentiality and not privacy?

(Brian Haberman) No Objection

(Russ Housley) No Objection

Barry Leiba No Objection

(Pete Resnick) No Objection

(Robert Sparks) No Objection

(Martin Stiemerling) No Objection

(Sean Turner) (was Discuss) No Objection

(Ron Bonica) Abstain

Comment (2012-06-04 for -14)
No email
send info
This document fails to provide use cases. Because it doesn't provide use cases, it is not clear that any/all of its objects are useful.

While this comment might be leveled concerning regarding MIB, it is particularly applicable in this case because we have so little operational experience with ad hoc networks. Will the ad hoc network include a NOC? What policy will that NOC attempt to enforce? What information/control will the NOC need to enforce that policy.