Re: [quicwg/base-drafts] Clarify use of the term "supports ECN" (#1631)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> -
-To verify that both a path and the peer support ECN, an endpoint MUST set one of
-the ECN Capable Transport (ECT) codepoints -- ECT(0) or ECT(1) -- in the IP
-header {{!RFC8311}} of all outgoing packets.
+To use ECN, QUIC endpoints first determine whether a path supports ECN
+marking and the peer is able to access the ECN codepoint in the IP header. 
+A network path regarded as not supporting ECN if ECN marked packets get dropped
+or ECN marking are rewritten on the path.
+An endpoint verifies the path, both during connection establishment 
+and when migrating to a new path (see {{migration}}).
+
+Each endpoint independently verifies and enables use of ECN by setting the IP
+header ECN codepoint to ECN Capable Transport (ECT) for the path from it to the
+other peer. Even if ECN is not used on the path to the peer, the endpoint MUST
+provide ECN feedback information if the receive of a non-zero ECN IP codepoint
+is observed.

Grammar here could be improved: "an endpoint MUST provide ECN feedback information if it receives packets with non-zero ECN markings." ?

-- 
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/1631#pullrequestreview-142724553