[quicwg/base-drafts] Allow connections to share a port by adding restrictions on zero-length connection IDs (#2851)

[David Schinazi <[e-mail]>]

In the current spec, zero-length connection IDs can be used when a host wants to route connections on the 4-tuple (remote IP/port, local IP/port). However, doing this prevents your peer from multiplexing connections on a single port. This PR restricts zero-length connection IDs to only be used when a host can route connection on the local 2-tuple (IP/port).

The current spec does not allow clients to share a local port ever, because at the time they start their connection they cannot know if a given server will want to route on the 4-tuple. Additionally, some clients might even be forced to perform this multiplexing because they are going through a proxy. Slightly restricting the use of zero-length connection IDs gives value to client connection IDs.

Fixes #2844.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/2851

-- Commit Summary --

  * Allow connections to share a port by adding restrictions on zero-length connection IDs

-- File Changes --

    M draft-ietf-quic-transport.md (41)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/2851.patch
https://github.com/quicwg/base-drafts/pull/2851.diff

-- 
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/2851