Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add handling of all packets marked as CE #3455

Closed
wants to merge 4 commits into from
Closed

Add handling of all packets marked as CE #3455

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a5241b6
Add handling of all packets marked as CE
mirjak Feb 13, 2020
4112f50
Update draft-ietf-quic-transport.md
mirjak Feb 14, 2020
d6ca8a8
Update draft-ietf-quic-transport.md
mirjak Feb 14, 2020
4886482
Update draft-ietf-quic-transport.md
mirjak Feb 17, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 7 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3517,6 +3517,13 @@ use the following steps on receiving an ACK frame to validate ECN.
corresponding ECT codepoint that are newly acknowledged in this ACK frame.
This step detects any erroneous network remarking from ECT(0) to ECT(1) (or
vice versa).

Another special case is when all packets are marked ECN-CE, independent of the
marking used, including Not-ECT.If this is caused by a network element
erroneously overwriting the ECN code point field, it will also conceal actual
congestion information. Therefore, if a peer indicates that all received packets
are ECN-CE marked, endpoints MAY treat this as an ECN validation failure and
ignore any ECN-CE counts in acknowledgments.

Processing ECN counts out of order can result in validation failure. An
endpoint SHOULD NOT perform this validation if this ACK frame does not advance
Expand Down