Re: [quicwg/base-drafts] introduce a max_connection_ids transport parameter (#1998)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> -unused connection IDs.  While each endpoint independently chooses how many
-connection IDs to issue, endpoints SHOULD provide and maintain at least eight
-connection IDs.  The endpoint SHOULD do this by always supplying a new
-connection ID when a connection ID is retired by its peer or when the endpoint
-receives a packet with a previously unused connection ID.  Endpoints that
-initiate migration and require non-zero-length connection IDs SHOULD provide
-their peers with new connection IDs before migration, or risk the peer closing
-the connection.
+unused connection IDs. Endpoints store received connection IDs for future use.
+An endpoint uses a transport parameter to advertise the number of connection IDs
+it can store for future use. An endpoint SHOULD NOT provide more connection IDs
+than this limit. If an endpoint has provided its peer with the maximum number of
+connection IDs, it SHOULD only provide a new connection ID when the peer retires
+one. Endpoints that initiate migration and require non-zero-length connection
+IDs SHOULD provide their peers with new connection IDs before migration, or risk
+the peer closing the connection.

There are a lot of SHOULDs here, but it's a bit light on the associated justification.  I think that we'll need some more text about why an endpoint might choose not to follow this advice.  Having everything in the one paragraph will make that difficult.

> @@ -4106,6 +4102,12 @@ A client MUST NOT include an original connection ID, a stateless reset token, or
 a preferred address.  A server MUST treat receipt of any of these transport
 parameters as a connection error of type TRANSPORT_PARAMETER_ERROR.
 
+max_connection_ids (0x000e):
+
+: The maximum number of connection IDs that the peer is willing to store.
+  This value includes only connection IDs sent in NEW_CONNECTION_ID frames.
+  If this parameter is absent, a default of 0 is assumed.

I'd really like to be able to not send this.  Is 0 really the right answer?

-- 
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/1998#pullrequestreview-200906639