TCP User Timeout Option
RFC 5482

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

Lars Eggert Recuse

(Magnus Westerlund; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Chris Newman; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Cullen Jennings; former steering group member) No Objection

No Objection (2008-12-17 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I think this is great (as long as it works through firewalls and nats - and support that part of Pasi discuss) but I think that it has to be exposed to apps and support that parts of Chris' discuss.

(Dan Romascanu; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Lisa Dusseault; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Mark Townsley; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Pasi Eronen; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Ron Bonica; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Ross Callon; former steering group member) No Objection

No Objection (2008-12-18 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
In the security considerations section, where the document mentions MD5, it should also mention TCP-AO as another option (with an informative reference to TCP-AO).

(Russ Housley; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Tim Polk; former steering group member) No Objection

No Objection (2008-12-17 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I support Chris's and Pasi's discusses.  The failure rate with middleboxes could present a significant problem unless the TCP stack is clever enough to establish new connections
without using uto after failure.  The onus is clearly on the TCP stack to adjust since the
"communication of timeout information between the TCP stack and application software
has been so poor in the past" to quote Chris's discuss.