From f77ee20808e88e9b92e35c8d9f94a075547b775f Mon Sep 17 00:00:00 2001 From: EKR Date: Wed, 24 Jul 2019 06:30:08 -0700 Subject: [PATCH 1/2] Minor clarification. Fixes #2084 --- draft-ietf-quic-transport.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index e429fee772..d20dde95e9 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -902,10 +902,11 @@ connection IDs using an implementation-specific (and perhaps deployment-specific) method which will allow packets with that connection ID to be routed back to the endpoint and identified by the endpoint upon receipt. -Connection IDs MUST NOT contain any information that can be used by an external -observer to correlate them with other connection IDs for the same connection. -As a trivial example, this means the same connection ID MUST NOT be issued more -than once on the same connection. +Connection IDs MUST NOT contain any information that can be used by an +external observer (i.e., one which is not affiliated with the issuer) +to correlate them with other connection IDs for the same connection. +As a trivial example, this means the same connection ID MUST NOT be +issued more than once on the same connection. Packets with long headers include Source Connection ID and Destination Connection ID fields. These fields are used to set the connection IDs for new From e73037faf71f5140a941a1f29cf4dd84e0cd6830 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Tue, 30 Jul 2019 09:13:35 +1000 Subject: [PATCH 2/2] Rewrap, clarify affiliation to mean cooperation --- draft-ietf-quic-transport.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index d20dde95e9..8da2c39ab8 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -902,11 +902,11 @@ connection IDs using an implementation-specific (and perhaps deployment-specific) method which will allow packets with that connection ID to be routed back to the endpoint and identified by the endpoint upon receipt. -Connection IDs MUST NOT contain any information that can be used by an -external observer (i.e., one which is not affiliated with the issuer) -to correlate them with other connection IDs for the same connection. -As a trivial example, this means the same connection ID MUST NOT be -issued more than once on the same connection. +Connection IDs MUST NOT contain any information that can be used by an external +observer (that is, one that does not cooperate with the issuer) to correlate +them with other connection IDs for the same connection. As a trivial example, +this means the same connection ID MUST NOT be issued more than once on the same +connection. Packets with long headers include Source Connection ID and Destination Connection ID fields. These fields are used to set the connection IDs for new