Re: [quicwg/base-drafts] Congestion feedback for rejected 0-RTT (#762)

[ekr <[e-mail]>]

On Wed, Sep 13, 2017 at 6:12 AM, mirjak <[e-mail]> wrote:

> So even if the rejected packets where not ack'ed, the server could still
> indicate to the client in the TLS handshake that the 0-RTT data was
> rejected and potentially even tell the client how many packets where
> rejected.
>

Well, you can say it was rejected, though you don't know how many packets
were rejected at this point.

-Ekr


> That might be all you need to know for congestion control purposes because
> if some or all of the 0-RTT packets were lost you might want to reduce the
> congestion window even below the initial window (assuming the initial
> window was larger than the minimum window).
>
> However, just resending the 1-RTT with the initial window is probably
> easier and should be fine in most cases, or in the worse case just delay
> your congestion control reaction by one RTT.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/762#issuecomment-329163257>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1ob9bnui6cixnkJe0lewa1uMH0NSNks5sh9TGgaJpZM4PNta6>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/762#issuecomment-329303874