Date: Mon, 27 Jun 2011 19:56:02 +0300 From: Catalin Nicutar <catalin.nicutar@gmail.com> To: soc-status@freebsd.org Subject: TCP UTO - Weekly Report 5 Message-ID: <BANLkTikTAGEF-mrL-0sTXeAyXE2uQa0mDA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
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@FreeBSD.org.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTikTAGEF-mrL-0sTXeAyXE2uQa0mDA>