search

quicwg / multipath

In-progress version of draft-ietf-quic-multipath
Other
53 stars 20 forks source link

First proposal to "remove" single packet number space option #149

Closed mirjak closed 1 year ago

mirjak commented 2 years ago

This PR removes the use of a single packet number space on multiple paths as a fully supported option. However, it currently doesn't remove it entirely. Specifically, it moves the respective text for now into the appendix but still allows the reception of packets without a Connection ID on multiple validated paths, similarly as path migration is not strictly forbidden without connection ID.

mirjak commented 2 years ago

@huitema yes I also opened issue #152 for discussion!

mirjak commented 1 year ago

I updated the PR and removed the appendix for SPNP. Further this PR threats the use of the multipath extension without CID as an error new text is the following:

If the parameter is set to 1, both endpoints MUST use non-zero connection
IDs. If an enable_multipath parameter set to 1 is received and the carrying packet
does not contain a non-zero legnth connection, the receiver MUST treat this as a connection error of type
TRANSPORT_PARAMETER_ERROR (specified in {{Section 20.1 of QUIC-TRANSPORT}})
and close the connection.