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

ECN probing needs to imply that you stop #3669

Merged
merged 2 commits into from Jun 9, 2020
Merged

ECN probing needs to imply that you stop #3669

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d95b49f
ECN probing needs to imply that you stop
martinthomson May 19, 2020
c93cddb
>>
martinthomson May 19, 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
6 changes: 3 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3733,9 +3733,9 @@ packets on a new path to a peer:
lost {{QUIC-RECOVERY}}, validation is deemed to have failed.

To reduce the chances of misinterpreting congestive loss as packets dropped by a
faulty network element, an endpoint could set the ECT(0) codepoint in the first
ten outgoing packets on a path, or for a period of three RTTs, whichever occurs
first.
faulty network element, an endpoint could set the ECT(0) codepoint for only the
first ten outgoing packets on a path, or for a period of three RTTs, whichever
occurs first.

Implementations MAY experiment with and use other strategies for use of ECN.
Other methods of probing paths for ECN support are possible, as are different
Expand Down