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

Consequences of bad ECN markings #1626

Merged
merged 2 commits into from Aug 6, 2018
Merged

Consequences of bad ECN markings #1626

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
598dd85
Consequences of bad ECN markings
martinthomson Aug 1, 2018
716f89e
Agreed changes to ECN response text
martinthomson Aug 6, 2018
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: 4 additions & 3 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -1225,9 +1225,10 @@ rate, which is similar in effect to advertising reduced connection flow control
limits and so no advantage is gained by doing so.

Endpoints choose the congestion controller that they use. Though congestion
controllers ideally use reports of ECN markings as input, the exact response for
each controller could be different. Failure to correctly respond to information
about ECN markings is therefore difficult to detect.
controllers generally treat reports of ECN-CE markings as equivalent to loss
[RFC8311], the exact response for each controller could be different. Failure
to correctly respond to information about ECN markings is therefore difficult to
detect.


# IANA Considerations
Expand Down