Entity MIB (Version 4)
draft-ietf-eman-rfc4133bis-06

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

(Benoit Claise) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

(Stephen Farrell) No Objection

Comment (2013-02-18)
I'm glad to see you've recognised the potential security issue
with the new UUID objects and that you do allow the value to be
empty. However, I guess these (and other similar objects) could
also cause potential privacy problems, so would suggest maybe
making the following changes to section 5 (if you want, I'm not
insisting):

OLD: 

Their mis-configuration or disclosure may reveal sensitive
information on assets or perturb the management of entities.  

NEW:

Their mis-configuration or disclosure may reveal sensitive
information on assets or perturb the management of entities,
or could cause privacy issues if they allow tracking of 
values that are personally identifying.  

OLD:

These objects expose information about the physical entities
within a managed system, which may be used to identify the
vendor, model, and version information of each system
component.

NEW:

These objects expose information about the physical entities
within a managed system, which may be used to identify the
vendor, model, version and specific device identification
information of each system component.

(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) No Objection