From abebe52fbabd9b184ef481fe17afc77d46883549 Mon Sep 17 00:00:00 2001 From: Lars Eggert <200328+larseggert@users.noreply.github.com> Date: Mon, 24 Aug 2020 11:00:54 +0300 Subject: [PATCH] Update draft-ietf-quic-transport.md Co-authored-by: Martin Thomson --- draft-ietf-quic-transport.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index ae97d53ac6..d5cf30ab3e 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1076,7 +1076,7 @@ A zero-length connection ID can be used when a connection ID is not needed to route to the correct endpoint. However, multiplexing connections on the same local IP address and port while using zero-length connection IDs will cause failures in the presence of peer connection migration, NAT rebinding, and client -port reuse. An endpoint MUST NOT use an IP address and port pair for multiple +port reuse. An endpoint MUST NOT use the same IP address and port for multiple connections with zero-length connection IDs, unless it is certain that those protocol features are not in use.