NAT64 Deployment Options and Experience
RFC 7269

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

(Joel Jaeggli) Yes

(Sean Turner) Yes

(Jari Arkko) (was Discuss) No Objection

(Richard Barnes) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Benoît Claise) No Objection

Comment (2014-02-19 for -09)
No email
send info
A minor editorial improvement would make the draft easier to read (when looking at the HTML version, http://tools.ietf.org/html/draft-ietf-v6ops-nat64-experience-09). Some references don't mention the RFC title and don't have an embedded link.
I had to open a new window, and google the RFC number.
Examples:
    - [RFC6036] reports at least 30% of operators plan to run some kind of translator (presumably NAT64/DNS64).
    - ... while it has to be coordinated with A+P[RFC6346]
    - For example, the value of the "established connection idle-timeout" for TCP sessions must not be less than 2 hours 4 minutes[RFC5382] and 5 minutes for UDP sessions[RFC4787].

(Spencer Dawkins) No Objection

(Adrian Farrel) No Objection

(Brian Haberman) No Objection

Barry Leiba No Objection

(Ted Lemon) No Objection

Comment (2014-02-20 for -09)
No email
send info
I support the publication of this document in theory, but I think it really needs an editorial pass to make the language clearer.

(Martin Stiemerling) No Objection

Comment (2014-02-20 for -09)
No email
send info
Some nits:

6.2.  Resource Reservation

   Session status normally is managed by a static timer.  For example,
   the value of the "established connection idle-timeout" for TCP
   sessions must not be less than 2 hours 4 minutes[RFC5382] and 5
   minutes for UDP sessions[RFC4787].

This text isn't exactly clear about who is supposed to handle the timers and also the 5 minutes for UDP is not 'less than 5 minutes' but it is RECOMMENDED to be 5  minutes and 'MUST NOT expire in less than two minutes'.

A text change proposal to get it correct:

   The session status at the NAT normally is managed by a static timer.
   For example, the value of the "established connection idle-timeout"
   for TCP sessions must not be less than 2 hours 4 minutes[RFC5382].
   For UDP sessions the timer must not be less than 2 minutes
   [RFC4787],  but the recommended value is 5 minutes.