Checking duplicate TPs is onerous #2689
Labels
-transport
design
An issue that affects the design of the protocol; resolution requires consensus.
has-consensus
An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Unlike HTTP/3 settings, receipt of duplicated transport parameters must be treated as an error:
Why the inconsistency?
The checks for duplicated transport (or settings) parameters are expensive, because one has to maintain an arbitrarily-sized set of possibly large numbers.
I propose we switch the duplicate transport parameters enforcement to "MAY treat as error."
The text was updated successfully, but these errors were encountered: