Re: [quicwg/base-drafts] Send complete SETTINGS (#2972)

[Kazuho Oku <[e-mail]>]

@MikeBishop 
> I think this is ultimately intractable. You can't tell the difference between the control stream having a delay due to packet loss vs. the server simply not sending the settings until it has something else to send, or even not sending it at all.

I disagree. If we are to require endpoints to send SETTINGS frame right after the connection is established, not sending anything until receiving the SETTINGS frame is a totally acceptable behavior (even though it might be less performant in some cases). It is no different than waiting for a Handshake packet before becoming possible to process a 1-RTT packet.

I think we should clarify if an endpoint can be implemented that way, because we have seen interop issues due to some doing that, and because that is the way H2 is designed. Maybe something like https://github.com/quicwg/base-drafts/commit/5fadbbbff7a5e566a2c951376be7999aca2c7edb.

-- 
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/pull/2972#issuecomment-522808046