* I'm just wondering if the stated goal be achieved by exposing a well-known HTTP path endpoint that clients can use to query congestion param data for the current connection?
Wouldn’t that require a separate endpoint for potential every/many clients? * The client can inspect the information provided by the server, but there is no guarantee that the server will provide congestion param cookies that do not uniquely identify the client. The server can already do that in the address validation token which is opaque to the client.
