Updates to Network Address Translation (NAT) Behavioral Requirements
RFC 7857
Yes
No Objection
Note: This ballot was opened for revision 07 and is now closed.
Alvaro Retana No Objection
(Martin Stiemerling; former steering group member) Yes
(Spencer Dawkins; former steering group member) Yes
(Alia Atlas; former steering group member) No Objection
(Alissa Cooper; former steering group member) No Objection
(Barry Leiba; former steering group member) No Objection
(Ben Campbell; former steering group member) No Objection
Some very minor comments: - I echo Stephen's thanks to the shepherd for the details on the handling of the IPR disclosure. - 14, third paragraph: Please consider changing the "MUST...only" construction to either "MAY...only" or "MUST NOT...unless". I personally prefer the latter. (OTOH, isn't this already covered normatively in section 3? Perhaps it could be descriptive here.) -- Third paragraph from end: s/"Hosts which require..."/"Hosts that require..."
(Benoît Claise; former steering group member) No Objection
(Deborah Brungard; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Joel Jaeggli; former steering group member) No Objection
(Stephen Farrell; former steering group member) No Objection
- Thanks for the info about the IPR declaration in the write up. It's useful to know that. - intro: Phrases like "greatly advanced" always make me think I'm getting sales talk and make me wonder why. (In this case, there was no other sales talk though, and thanks for that:-) I think s/greatly advanced/documented/ would have been fine.
(Terry Manderson; former steering group member) No Objection