W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2017

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

From: Willy Tarreau <w@1wt.eu>
Date: Fri, 24 Nov 2017 05:07:11 +0100
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>, mnot <mnot@mnot.net>, Martin Thomson <martin.thomson@gmail.com>
Message-ID: <20171124040711.GA12820@1wt.eu>
On Fri, Nov 24, 2017 at 12:57:33PM +0900, Kazuho Oku wrote:
> Hi Willy,
> 
> 2017-11-24 12:48 GMT+09:00 Willy Tarreau <w@1wt.eu>:
> 
> > Hi Kazuho,
> >
> > On Fri, Nov 24, 2017 at 12:27:59PM +0900, Kazuho Oku wrote:
> > > Section 4 has the following paragraph.
> > >
> > > > An intermediary MUST NOT use early data when forwarding a request
> > unless
> > > early data was used on a previous hop, or it knows that the request can
> > be
> > > retried safely without consequences (typically, using out-of-band
> > > configuration).  Absent better information, that means that an
> > intermediary
> > > can only use early data if the request either arrived in early data or
> > > arrived with the "Early-Data" header field set to "1" (see Section 5.1).
> > >
> > >
> > > Could I ask why an intermediary is allowed to forward early data if it
> > "was
> > > used on a previous hop"?
> >
> > It's simply because there is a guarantee that either an intermediary before
> > it or the client will be able to deal with 425 if one such happens.
> >
> 
> Thank you very much for the clarification. Now I understand.
> 
> 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.

Yes, and if I remember well, you were the first one requesting to allow
this as it was not covered by the initial proposal :-)

Willy
Received on Friday, 24 November 2017 04:07:40 UTC

This archive was generated by hypermail 2.3.1 : Friday, 24 November 2017 04:07:44 UTC