[quicwg/base-drafts] When to send the SETTINGS frame (#2945)

[Kazuho Oku <[e-mail]>]

It seems that there are disagreement among the implementors, regarding when the SETTINGS frame need to be sent.

Some argue that it needs to be sent right after the handshake, even if the SETTINGS frame would contain no parameters. Some argue that it can be delayed, until the need to send something on the control stream arises.

I think we should clarify the expected behavior.

FWIW, existing text that refers to the topic are:
[section 3.3](https://quicwg.org/base-drafts/draft-ietf-quic-http.html#rfc.section.3.3):
> After the QUIC connection is established, a SETTINGS frame (Section 7.2.5) MUST be sent by each endpoint as the initial frame of their respective HTTP control stream (see Section 6.2.1)

[section 6.2.1](https://quicwg.org/base-drafts/draft-ietf-quic-http.html#rfc.section.6.2.1):
> Each side MUST initiate a single control stream at the beginning of the connection and send its SETTINGS frame as the first frame on this stream.

[section 7.2.5](https://quicwg.org/base-drafts/draft-ietf-quic-http.html#rfc.section.7.2.5):
> SETTINGS frames always apply to a connection, never a single stream. A SETTINGS frame MUST be sent as the first frame of each control stream (see Section 6.2.1) by each peer, and MUST NOT be sent subsequently.

cc @DavidSchinazi @LPardue @rmarx 

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