From: Justin McCann <jneilm@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Hsiao-keng Jerry Chu <hkchu@google.com>,
bloat-devel@lists.bufferbloat.net,
Yuchung Cheng <ycheng@google.com>
Subject: Re: tcp fast open?
Date: Thu, 23 Feb 2012 13:20:12 -0500 [thread overview]
Message-ID: <CAFkTFa_MCbjgaOnNJZc3eX3RcVtZW-1mhAwKEDNToMDso_7gvQ@mail.gmail.com> (raw)
In-Reply-To: <4F43E192.7060100@hp.com>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
On Tue, Feb 21, 2012 at 1:25 PM, Rick Jones <rick.jones2@hp.com> wrote:
> On 02/20/2012 01:40 PM, Dan McDonald wrote:
>
>> On Fri, Feb 17, 2012 at 07:24:32AM -0800, Yuchung Cheng wrote:
>>
>> <SNIP!>
>>
>> At this moment, we do have a working patch under testing it
>>> internally. The handshake code is the most complicated and critical
>>> piece in TCP. One important test is the fail over if routers drop or
>>> act weirdly on SYN/SYN-ACK with payload and/or experimental TCP
>>> options. If things go well we will upstream it to Linux netdev in
>>> April and I'll CC you.
>>>
>>
>> Do you have a paper spec (Internet Draft or other such documentation) so
>> other platforms can port this?
>>
>
> http://tools.ietf.org/html/**draft-cheng-tcpm-fastopen-02<http://tools.ietf.org/html/draft-cheng-tcpm-fastopen-02>
>
>
>
You might also want to check out their CoNEXT paper (probably sent around
already). It's more of the why and supporting evidence than a spec:
overview: http://research.google.com/pubs/pub37517.html
pdf: http://research.google.com/pubs/archive/37517.pdf
Justin
[-- Attachment #2: Type: text/html, Size: 1951 bytes --]
next prev parent reply other threads:[~2012-02-23 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 14:38 Dave Taht
2012-02-17 15:24 ` Yuchung Cheng
2012-02-20 21:40 ` Dan McDonald
2012-02-21 7:30 ` Jerry Chu
2012-02-21 18:25 ` Rick Jones
2012-02-23 18:20 ` Justin McCann [this message]
2012-02-20 22:55 ` Juliusz Chroboczek
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=CAFkTFa_MCbjgaOnNJZc3eX3RcVtZW-1mhAwKEDNToMDso_7gvQ@mail.gmail.com \
--to=jneilm@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=hkchu@google.com \
--cc=rick.jones2@hp.com \
--cc=ycheng@google.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