General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Ketan Kulkarni <ketkulka@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, cerowrt-devel@lists.bufferbloat.net
Subject: [Bloat] TCP TFO client behaviour
Date: Tue, 11 Dec 2012 22:18:00 +0530	[thread overview]
Message-ID: <CAD6NSj6et8TQ=5VVHZsjTW6DumnsMXyOz2za+Nsz3CX3-sCMww@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

Hi,
I am testing tcp tfo behavior with httping client and polipo server.

One observation from my TFO testing  -If for a connection server sends a
cookie to client, client always does TFO for subsequent connections. This
is ok.

If for some reason, server stops supporting TFO (either because server got
restarted without TFO support (in my case) or because path changed and the
nw node is dropping packet with unknown syn option or stripping the
option), client does not clear up its cookie cache. It always sends data in
syn and server never acks the syn-data and client retransmits.

As per kernel code -if syn-data is not acked it is retransmitted
immediately - with the assumption first syn was dropped (but the assumption
server stopped supporting TFO might not have been considered)

My opinion is to flush the cookie for this server and re-attempt the cookie
"negotiation" on subsequent connection.

Your thoughts?

Thanks,
Ketan

[-- Attachment #2: Type: text/html, Size: 997 bytes --]

             reply	other threads:[~2012-12-11 16:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 16:48 Ketan Kulkarni [this message]
2012-12-11 16:59 ` Eric Dumazet
2012-12-11 17:52   ` Dave Taht
2012-12-11 18:41     ` Rick Jones
2012-12-11 20:00       ` Dave Taht
2012-12-11 20:52         ` Rick Jones
2012-12-12  9:01     ` Ketan Kulkarni
2012-12-12 19:17   ` Jan Ceuleers
2012-12-12 10:45 ` Eggert, Lars

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAD6NSj6et8TQ=5VVHZsjTW6DumnsMXyOz2za+Nsz3CX3-sCMww@mail.gmail.com' \
    --to=ketkulka@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox