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

Hi,

I'd like to thank the authors for working on the draft. H2O already
implements this draft, and I am looking forward to see this becoming a
standard soon.

That said, I have one question.

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"?


Shouldn't an intermediary wait for the handshake completion or send 425 in
case it is unsure if the request can be retried safely?


My understanding is that the intent of the draft it to make use of
early-data an opt-in feature from server's perspective. This guidance for
the intermediary seems to contradict with the principle.



2017-11-24 11:43 GMT+09:00 Patrick McManus <mcmanus@ducksong.com>:

> Hi All - When we met in Singapore we discussed a couple final details of
> the Early Data / Replay draft and indicated we would start WGLC after a
> final(?) update. The authors have made that update and we're ready for the
> LC now.
>
> Please have a look at:
> https://tools.ietf.org/html/draft-ietf-httpbis-replay-02
>
> Raise any issues either on the mailing list or in the issues list.
> Statements of support, implementation, or intent to implement to the list
> would also be helpful.
>
> We'll run this for a touch over two weeks, ending the WGLC on December 10,
> 2017. We look forward to your comments :)
>
> -Patrick
>
>


-- 
Kazuho Oku