From: Rick Jones <rick.jones2@hpe.com>
To: Tom Herbert <tom@herbertland.com>
Cc: Richard Weinberger <richard@nod.at>,
David Miller <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH net-next 0/8] tou: Transports over UDP - part I
Date: Fri, 24 Jun 2016 17:01:04 -0700 [thread overview]
Message-ID: <576DC9C0.4080102@hpe.com> (raw)
In-Reply-To: <CALx6S37e5uQ9RXzVaAmAD=rpeqpwDizRQML9G6XCjCf273Gr1A@mail.gmail.com>
On 06/24/2016 04:43 PM, Tom Herbert wrote:
> Here's Christoph's slides on TFO in the wild which presents a good
> summary of the middlebox problem. There is one significant difference
> in that ECN needs network support whereas TFO didn't. Given that
> experience, I'm doubtful other new features at L4 could ever be
> productively use (like EDO or maybe TCP-ENO).
>
> https://www.ietf.org/proceedings/94/slides/slides-94-tcpm-13.pdf
Perhaps I am being overly optimistic, but my takeaway from those slides
is Apple were able to come-up with ways to deal with the middleboxes and
so could indeed productively use TCP FastOpen.
"Overall, very good success-rate"
though tempered by
"But... middleboxes were a big issue in some ISPs..."
Though it doesn't get into how big (some connections, many, most, all?)
and how many ISPs.
rick jones
Just an anecdote... Not that I am a "power user" of my iPhone running
9.3.2 (13F69) nor that I know that anything I am using is the Apple
Service stated as using TFO (mostly Safari, Mail and Messages) but if it
is, I cannot say that any troubles under the covers have been noticed by me.
next prev parent reply other threads:[~2016-06-25 0:01 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 17:51 [PATCH net-next 0/8] tou: Transports over UDP - part I Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 1/8] net: Change SKB_GSO_DODGY to be a tx_flag Tom Herbert
2016-06-16 18:58 ` Alexander Duyck
2016-06-16 20:18 ` Tom Herbert
2016-06-16 20:33 ` Alexander Duyck
2016-06-17 22:33 ` Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 2/8] fou: Change ip_tunnel_encap to take net argument Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 3/8] tou: Base infrastructure for Transport over UDP Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 4/8] ipv4: Support TOU Tom Herbert
2016-06-16 17:51 ` [PATCH net-next 5/8] tcp: Support for TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 6/8] ipv6: Support TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 7/8] tcp6: Support for TOU Tom Herbert
2016-06-16 17:52 ` [PATCH net-next 8/8] tou: Support for GSO Tom Herbert
2016-06-16 18:10 ` [PATCH net-next 0/8] tou: Transports over UDP - part I Rick Jones
2016-06-16 23:15 ` Hannes Frederic Sowa
2016-06-17 16:51 ` Tom Herbert
2016-06-21 16:56 ` Hannes Frederic Sowa
2016-06-18 3:09 ` David Miller
2016-06-18 3:52 ` Tom Herbert
2016-06-19 20:15 ` Hajime Tazaki
2016-06-20 3:07 ` David Miller
2016-06-20 15:13 ` Tom Herbert
2016-06-21 8:29 ` David Miller
2016-06-22 3:42 ` Jerry Chu
2016-06-22 4:06 ` David Ahern
2016-06-22 19:24 ` David Miller
2016-06-22 17:40 ` Tom Herbert
2016-06-22 19:23 ` David Miller
2016-06-25 15:56 ` Tom Herbert
2016-06-21 17:11 ` Hannes Frederic Sowa
2016-06-21 17:23 ` Tom Herbert
2016-06-22 22:15 ` Richard Weinberger
2016-06-22 22:56 ` Tom Herbert
2016-06-23 7:40 ` David Miller
2016-06-23 7:50 ` Richard Weinberger
2016-06-24 21:12 ` Tom Herbert
2016-06-24 21:36 ` Rick Jones
2016-06-24 21:46 ` Tom Herbert
2016-06-24 22:06 ` Rick Jones
2016-06-24 23:43 ` Tom Herbert
2016-06-25 0:01 ` Rick Jones [this message]
2016-06-25 16:22 ` Tom Herbert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=576DC9C0.4080102@hpe.com \
--to=rick.jones2@hpe.com \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=richard@nod.at \
--cc=tom@herbertland.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;
as well as URLs for NNTP newsgroup(s).