Re: Working Group Last Call for Using Early Data in HTTP

• From: Martin Thomson <martin.thomson@gmail.com>
• Date: Fri, 24 Nov 2017 16:49:14 +1100
• To: Kazuho Oku <kazuhooku@gmail.com>
• Cc: Willy Tarreau <w@1wt.eu>, Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>, mnot <mnot@mnot.net>
• Message-ID: <CABkgnnVu3qMxx9RBP+hyubzqNQ6RqwLzekb1bR_SQ6mJ-n8FDg@mail.gmail.com>

On Fri, Nov 24, 2017 at 2:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:
> The assumption I missed is that by enabling the intermediary to reconnect
> with 0-RTT (through the use of EarlyDataIndication is NewSessionTicket
> message) the origin server is opting-in to use early data.

:) Oddly enough, the server accepting early data actually makes this a
tiny bit safer.  If the intermediary accepts early data and forwards
the request to a server on a connection that doesn't allow 0-RTT, then
the intermediary has to hope, guess or somehow know that the server
will look at the Early-Data header field.  This way, it knows that the
server will know about Early-Data.

Received on Friday, 24 November 2017 05:49:39 UTC