* Fw: [Bug 93901] New: TCP Fast Open uses
@ 2015-02-26 16:07 Stephen Hemminger
2015-02-26 16:13 ` Eric Dumazet
0 siblings, 1 reply; 4+ messages in thread
From: Stephen Hemminger @ 2015-02-26 16:07 UTC (permalink / raw)
To: netdev
Begin forwarded message:
Date: Thu, 26 Feb 2015 15:43:45 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 93901] New: TCP Fast Open uses
https://bugzilla.kernel.org/show_bug.cgi?id=93901
Bug ID: 93901
Summary: TCP Fast Open uses
Product: Networking
Version: 2.5
Kernel Version: 4.0-rc1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: rueth@comsys.rwth-aachen.de
Regression: No
TCP Fast Open still uses the TCP Experimental Option even though RFC7413
advises not to use the experimental options field anymore but rather use IANA
assigned option number 34 (https://tools.ietf.org/html/rfc7413#section-9).
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fw: [Bug 93901] New: TCP Fast Open uses
2015-02-26 16:07 Fw: [Bug 93901] New: TCP Fast Open uses Stephen Hemminger
@ 2015-02-26 16:13 ` Eric Dumazet
2015-02-26 17:58 ` Rick Jones
0 siblings, 1 reply; 4+ messages in thread
From: Eric Dumazet @ 2015-02-26 16:13 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: netdev, Yuchung Cheng, rueth
On Thu, 2015-02-26 at 08:07 -0800, Stephen Hemminger wrote:
>
> Begin forwarded message:
>
> Date: Thu, 26 Feb 2015 15:43:45 +0000
> From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
> To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
> Subject: [Bug 93901] New: TCP Fast Open uses
>
>
> https://bugzilla.kernel.org/show_bug.cgi?id=93901
>
> Bug ID: 93901
> Summary: TCP Fast Open uses
> Product: Networking
> Version: 2.5
> Kernel Version: 4.0-rc1
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: low
> Priority: P1
> Component: IPV4
> Assignee: shemminger@linux-foundation.org
> Reporter: rueth@comsys.rwth-aachen.de
> Regression: No
>
> TCP Fast Open still uses the TCP Experimental Option even though RFC7413
> advises not to use the experimental options field anymore but rather use IANA
> assigned option number 34 (https://tools.ietf.org/html/rfc7413#section-9).
This is work in progress at Google, of course.
Classic chicken and egg problem ;)
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fw: [Bug 93901] New: TCP Fast Open uses
2015-02-26 16:13 ` Eric Dumazet
@ 2015-02-26 17:58 ` Rick Jones
2015-02-26 19:10 ` Eric Dumazet
0 siblings, 1 reply; 4+ messages in thread
From: Rick Jones @ 2015-02-26 17:58 UTC (permalink / raw)
To: Eric Dumazet, Stephen Hemminger; +Cc: netdev, Yuchung Cheng, rueth
On 02/26/2015 08:13 AM, Eric Dumazet wrote:
> This is work in progress at Google, of course.
>
> Classic chicken and egg problem ;)
Does it need to be any more complicated than a sysctl which enables
accepting an alternate (the experimental) option value in addition to
the assigned, to be enabled (perhaps by default for a release or three)
for the server side, and then just switching the active connection
establishment side to the assigned number?
If the server is "old" and using the experimental version, the only
thing that will happen is the clients using the standardized version
will end-up falling back on the classic three-way handshake. That
doesn't seem so bad. Particularly since that option value was
"experimental" after all and presumably then not really meant for
"production" purposes :)
rick jones
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fw: [Bug 93901] New: TCP Fast Open uses
2015-02-26 17:58 ` Rick Jones
@ 2015-02-26 19:10 ` Eric Dumazet
0 siblings, 0 replies; 4+ messages in thread
From: Eric Dumazet @ 2015-02-26 19:10 UTC (permalink / raw)
To: Rick Jones; +Cc: Stephen Hemminger, netdev, Yuchung Cheng, rueth
On Thu, 2015-02-26 at 09:58 -0800, Rick Jones wrote:
> On 02/26/2015 08:13 AM, Eric Dumazet wrote:
> > This is work in progress at Google, of course.
> >
> > Classic chicken and egg problem ;)
>
> Does it need to be any more complicated than a sysctl which enables
> accepting an alternate (the experimental) option value in addition to
> the assigned, to be enabled (perhaps by default for a release or three)
> for the server side, and then just switching the active connection
> establishment side to the assigned number?
>
> If the server is "old" and using the experimental version, the only
> thing that will happen is the clients using the standardized version
> will end-up falling back on the classic three-way handshake. That
> doesn't seem so bad. Particularly since that option value was
> "experimental" after all and presumably then not really meant for
> "production" purposes :)
Really, if you are eager to see this coming, you could send a patch.
Or simply wait for the work being done by a Googler ;)
<quote Google-Bug-Id: 19264158 >
Add support to use RFC7413 option (34) for TCP Fast open while
supporting the old/current experimental option format. The idea is
a new client will request fast open cookie using option 34
if the SYN-ACK contains TFO cookie with option 34. everything works out.
otherwise, the client retries the cookie request with the exp option in
the subsequent TFO connection attempt. if the server grants the cookie,
records the destination is an old server for the next (30?) days.
a new server will respond TFO cookie based on the option number used in
cookie request.
</quote>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-02-26 19:10 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-26 16:07 Fw: [Bug 93901] New: TCP Fast Open uses Stephen Hemminger
2015-02-26 16:13 ` Eric Dumazet
2015-02-26 17:58 ` Rick Jones
2015-02-26 19:10 ` Eric Dumazet
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.