Definitions of Managed Objects for Network Address Translators (NATs)
RFC 7659
Yes
(Martin Stiemerling)
(Spencer Dawkins)
No Objection
(Alia Atlas)
(Alissa Cooper)
(Alvaro Retana)
(Barry Leiba)
(Ben Campbell)
(Brian Haberman)
(Deborah Brungard)
(Jari Arkko)
(Terry Manderson)
Note: This ballot was opened for revision 03 and is now closed.
Martin Stiemerling Former IESG member
Yes
Yes
(for -04)
Spencer Dawkins Former IESG member
Yes
Yes
(for -03)
Alia Atlas Former IESG member
No Objection
No Objection
(for -04)
Alissa Cooper Former IESG member
No Objection
No Objection
(for -04)
Alvaro Retana Former IESG member
No Objection
No Objection
(for -04)
Barry Leiba Former IESG member
No Objection
No Objection
(for -04)
Ben Campbell Former IESG member
No Objection
No Objection
(for -04)
Benoît Claise Former IESG member
No Objection
No Objection
(2015-06-09 for -04)
No objection to the publication of this document, but the Security Considerations boilerplate at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security has been changed a few months ago. Please update it before publication. There is a compilation warning related to InetAddress and InetAdressType The MIB doctors have been engaged, and the authors copied. Email subject = InetAddress and InetAdressType (draft-perrault-behave-natv2-mib-04 compilation). Let's follow the MIB doctors advice on this one.
Brian Haberman Former IESG member
No Objection
No Objection
(for -04)
Deborah Brungard Former IESG member
No Objection
No Objection
(for -04)
Jari Arkko Former IESG member
No Objection
No Objection
(for -04)
Joel Jaeggli Former IESG member
No Objection
No Objection
(2015-06-11 for -04)
Shen Jiang performed the opsdir review.
Kathleen Moriarty Former IESG member
No Objection
No Objection
(2015-06-09 for -04)
In the Security Considerations section, you have the following 2 tables called out for the possibility of revealing host information (both a security and possible privacy concern):
* entries in the natv2AddressMapTable;
* entries in the natv2PortMapTable.
Why are the 3.3.3 subscriber table and the 3.3.4 Individual NAT instances included in this list?
The text should also mention that there could be privacy concerns as well if this information were accessible. The protections already included cover both security and privacy already.
Thank you for addressing the SecDir review:
http://www.ietf.org/mail-archive/web/secdir/current/msg05651.html
Terry Manderson Former IESG member
No Objection
No Objection
(for -04)