Re: [quicwg/base-drafts] Gorry's ECN rewrite (#4059)

[ianswett <[e-mail]>]

@ianswett commented on this pull request.



>  
-Note that supporting ECN requires being able to set and read the ECN codepoints
-in the IP headers of datagrams carrying QUIC packets. On platforms where
- this is not possible, QUIC cannot support ECN.
-
-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 does not support ECN if ECN marked packets get dropped or ECN markings are
-rewritten on the path. An endpoint validates the use of ECN on the path, both
-during connection establishment and when migrating to a new path
-({{migration}}).
+To enable ECN, a sending QUIC endpoint first determines whether a path supports
+ECN marking and whether the peer reports the ECN values in received IP headers;
+see {{ecn-validation}}.
 
 
 ### ECN Counts

```suggestion
### Reporting ECN Counts
```

-- 
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/4059#pullrequestreview-487010467