From: "Eggert, Lars" <lars@netapp.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] if we're going to break middleboxes with TFO... why not go for more gusto?
Date: Mon, 14 Jan 2013 08:32:16 +0000 [thread overview]
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F61AF32@SACEXCMBX01-PRD.hq.netapp.com> (raw)
In-Reply-To: <CAA93jw61DB6rNFaDGBaAK8pn9zTTXvDEmSiXJ0kVuoeEnqm8LQ@mail.gmail.com>
Hi,
On Jan 12, 2013, at 20:45, Dave Taht <dave.taht@gmail.com> wrote:
> I got pointed at rfc6013 (TCPCT) recently which looked like it solved
> a raft of problems TFO doesn't solve.
also note that it is not an IETF standard but an independent submission to the RFC Editor. (That's not to say it's a bad proposal.)
IIRC, the author did not want to work on this in the IETF, the result is that TCPCT uses the experimental option numbers and must not be used over the wider Internet. Unless the author submits it to the TCPM WG, TCPCT is unlikely to get an option number assigned by IANA.
Lars
>
> Biggest problem it has though is that it eats all the remaining TCP
> option space. I wonder if anyone tried implementing something similar
> over UDP?
>
> More readable detail than the rfc here:
>
> http://static.usenix.org/publications/login/2009-12/openpdfs/metzger.pdf
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2013-01-14 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 19:45 [Cerowrt-devel] " Dave Taht
2013-01-14 8:32 ` Eggert, Lars [this message]
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D4D47BCFFE5A004F95D707546AC0D7E91F61AF32@SACEXCMBX01-PRD.hq.netapp.com \
--to=lars@netapp.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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