Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Jul 2011 10:42:50 +0300
From:      Catalin Nicutar <catalin.nicutar@gmail.com>
To:        soc-status@freebsd.org
Subject:   TCP UTO - Weekly Report 6
Message-ID:  <CADgY63u44PObXK8m8zc-42xMkH2CArfTUuQ1Ay8pOHOuKDtMWQ@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
Hello!

This is the sixth 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
   * Retransmits are being sent at regular intervals (TCPTV_REXMTMAX)
   until the timeout runs out. This will probably be adjusted as sending
   data continuously to a possibly uninterested peer should be avoided
   * I have added two captures on the wiki page, showing the behavior
   with and without UTO (see link above)

* My goals for for this week
   * Write tests for tools/regression and look for possible boundary cases
   * Add more examples to the wiki page (including a scenario with a
   very short timeout)
   * Try to get the Linux patch by Hagen Paul Pfeifer and test it with
   the current FreeBSD implementation
   * Consider adjusting the API so it's similar to the Linux patch (it
   will help adoption by more applications)
   * I will start changing tcp.4 as the API is becoming stable


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

Catalin Nicutar



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADgY63u44PObXK8m8zc-42xMkH2CArfTUuQ1Ay8pOHOuKDtMWQ>