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

I've been trying to think about the cases when that would be useful, but
I'm drawing a blank here.  Even if those exist, I am not sure how one
would analyze those.  I for some reason thought that those cases were
disallowed as a consequence of consistency requirements.

Do you have a good use case in mind for processing 0-RTT in manner other
than "identical to 1-RTT, buffer or 425"?

On Sun, Dec 3, 2017 at 8:09 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On Mon, Dec 4, 2017 at 12:07 PM, Victor Vasiliev <vasilvv@google.com>
> wrote:
> > Are we talking about the "scenarios in the middle" when a request is
> > processed
> > differently on 0-RTT and 1-RTT, but the 0-RTT processing is actually
> > meaningful
> > (not 425 or buffering)?  Because if you process request same regardless
> of
> > whether it's 0-RTT or 1-RTT, you're consistent.
>
> Yeah, it's the cases where you might do meaningful processing on 0-RTT
> and that processing might have side effects.
>