From 211844a95c6f746fdef571c6bbee15212b4455ec Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 24 Sep 2020 11:18:33 +1000 Subject: [PATCH] ECN is validated ...not verified. Consistency in terms helps. Closes #4146. --- draft-ietf-quic-recovery.md | 2 +- draft-ietf-quic-transport.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md index 675db01b3a..b1fab77395 100644 --- a/draft-ietf-quic-recovery.md +++ b/draft-ietf-quic-recovery.md @@ -795,7 +795,7 @@ is sent on a PTO timer expiration (see {{pto}}) or when entering recovery ## Explicit Congestion Notification {#congestion-ecn} -If a path has been verified to support ECN ({{?RFC3168}}, {{?RFC8311}}), QUIC +If a path has been validated to support ECN ({{?RFC3168}}, {{?RFC8311}}), QUIC treats a Congestion Experienced (CE) codepoint in the IP header as a signal of congestion. This document specifies an endpoint's response when its peer receives packets with the ECN-CE codepoint. diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index c3b1d22028..c355728b57 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1496,7 +1496,7 @@ Handshake (CRYPTO) ~~~ {: #fig-hs title="Simplified QUIC Handshake"} -An endpoint verifies support for Explicit Congestion Notification (ECN) by +An endpoint validates support for Explicit Congestion Notification (ECN) by observing whether the ACK frames acknowledging the first packets it sends carry ECN counts, as described in {{ecn-validation}}. @@ -2329,7 +2329,7 @@ rate. Therefore, the endpoint resets its congestion controller and RTT estimate, as described in {{migration-cc}}. The new path might not have the same ECN capability. Therefore, the endpoint -verifies ECN capability as described in {{ecn}}. +validates ECN capability as described in {{ecn}}. ## Responding to Connection Migration {#migration-response}