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.

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

Add handling of all packets marked as CE #3455

Closed
wants to merge 4 commits into from
Closed
Changes from 1 commit
Commits
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
12 changes: 6 additions & 6 deletions draft-ietf-quic-transport.md
Expand Up @@ -3518,12 +3518,12 @@ use the following steps on receiving an ACK frame to validate ECN.
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. In this case
it could be a network element overwriting the ECN field of all packets and
thereby potentially concealing actual congestion information. Especially,
when it is recognized that Not-ECT packets get remarked to CE, ECN marking
should be disabled and any received CE feedback should be treated with caution.
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