TCP UTO - Weekly Report 5

Catalin Nicutar catalin.nicutar at gmail.com
Mon Jun 27 16:56:23 UTC 2011


Hello!

This is the fifth report for TCP UTO.

* Short TCP UTO description
UTO stands for User Timeout Option (it is described in RFC5482). TCP UTO
specifies a peer should be allowed to advertise its chosen `User Timeout'
for a connection.
The wiki page for this project: http://wiki.freebsd.org/CatalinNicutar/TCPUTO


* Work completed last week
    * The options weren't correctly inherited from a listening socket
    * When using UTO, no keepalives are sent (RFC 5482 4.2)
    * The connection was dropped whenever TCP_MAXRXTSHIFT retransmits had
    been performed. Now (if using UTO) it is reset if the USER_TIMEOUT is
    exceeded.

* My goals for for this week
    * Consider the implications of changing the retransmit timer and
    stopping the keepalive timer (RFC 5482 only specified that a timeout
    > USER_TIMEOUT must be chosen)
    * Consider performing retransmits beyond TCP_MAXRXTSHIFT when in UTO
    * When waiting in UTO, ICMP destination unreachable messages must be
    ignored

If you have questions, suggestions or advices drop me an email to
cnicutar at FreeBSD.org.


More information about the soc-status mailing list