search

quicwg / multipath

In-progress version of draft-ietf-quic-multipath
Other
49 stars 18 forks source link

probably stale statement regarding "no connection ID exposed in the QUIC header" #224

Closed kazuho closed 1 year ago

kazuho commented 1 year ago

In section 3, we state that

If the parameter is set to 1, both endpoints MUST use non-zero connection IDs.

but also state that

For the QUIC multipath extension this limit even applies when no connection ID is exposed in the QUIC header.

I believe the latter is a leftover from when we allowed zero-length connection IDs to be used?