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

Make the ECN requirements match the the discussion in #2156. Fixes #2156 #2201

Merged
merged 4 commits into from
Dec 18, 2018
Merged

Make the ECN requirements match the the discussion in #2156. Fixes #2156 #2201

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9d20ea5
Make the ECN requirements match the the discussion in #2156. Fixes #2156
ekr Dec 15, 2018
029d729
SHOULD ECN
martinthomson Dec 18, 2018
81997cf
Merge branch 'master' into ecn_reqs
martinthomson Dec 18, 2018
2941ecc
editorial nit
janaiyengar Dec 18, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3017,7 +3017,7 @@ the 1-RTT packet number space will be increased by two.
Each endpoint independently verifies and enables use of ECN by setting the IP
header ECN codepoint to ECN Capable Transport (ECT) for the path from it to the
other peer. Even if not setting ECN codepoints on packets it transmits, the
endpoint MAY provide feedback about ECN markings received (if accessible).
endpoint SHOULD provide feedback about ECN markings received (if accessible).

To verify both that a path supports ECN and the peer can provide ECN feedback,
an endpoint sets the ECT(0) codepoint in the IP header of all outgoing
Expand Down