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

Hi everyone,

Glad to see this draft reaching WGLC so quickly!  I am looking forward to
implementing the Early-Data/425 Too Early mechanism.

I've already reviewed this draft in the past, and it has not changed much
conceptually, so this is mostly editorial nits.

"early data is concatenated with other application to form a single stream"
--
do you mean "other *application* data"?

"If HTTP/2 is selected after early data is rejected, a client sends another
connection preface" -- this feels somewhat redundant given what's already
said
in the paragraph.

"A gateway that is uncertain about whether an origin server supports the
Early-Data header field SHOULD disable early data." -- this sounds weird. Is
there an implicit assumption that the gateway only serves a single origin?

"Implementations MUST either ensure that any early data that is delivered
late
is either discarded or consistently identified and processed." -- I am not
quite sure what exactly this means.  Is that (re)statement of the
requirement
that the early data status is not changed in the middle of processing?


On Thu, Nov 23, 2017 at 9:43 PM, Patrick McManus <mcmanus@ducksong.com>
wrote:

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