NAT Behavioral Requirements for TCP
draft-ietf-behave-tcp-08
Yes
(Cullen Jennings)
(Jari Arkko)
(Magnus Westerlund)
No Objection
(Chris Newman)
(Dan Romascanu)
(David Ward)
(Jon Peterson)
(Lisa Dusseault)
(Mark Townsley)
(Ron Bonica)
(Ross Callon)
(Russ Housley)
(Tim Polk)
Note: This ballot was opened for revision 08 and is now closed.
Cullen Jennings Former IESG member
(was Discuss)
Yes
Yes
()
Unknown
Jari Arkko Former IESG member
Yes
Yes
()
Unknown
Lars Eggert Former IESG member
(was Discuss)
Yes
Yes
(2007-04-16)
Unknown
[Editing nits emailed to authors directly.]
Magnus Westerlund Former IESG member
Yes
Yes
()
Unknown
Chris Newman Former IESG member
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
David Ward Former IESG member
No Objection
No Objection
()
Unknown
Jon Peterson Former IESG member
No Objection
No Objection
()
Unknown
Lisa Dusseault Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Sam Hartman Former IESG member
No Objection
No Objection
(2007-04-17)
Unknown
I'm not making this a discuss, but I consider it a significant limitation that this document does not consider the implications of an external address being used both for local traffic to the NAT and for translated traffic. I think the requirements for handling internal SYNs are very challenging to deal with in this situation and guidance would almost certainly improve implementation quality here. I've seen significant problems with NATs getting issues like this wrong for UDP.
Tim Polk Former IESG member
No Objection
No Objection
()
Unknown