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 validation nits #3747

Merged
merged 2 commits into from
Jun 9, 2020
Merged

ECN validation nits #3747

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
85a58f1
ECN validation nits
martinthomson Jun 9, 2020
ac51483
QUIC packets
martinthomson Jun 9, 2020
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
15 changes: 8 additions & 7 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3717,9 +3717,10 @@ subsequent ACK frames; see {{generating-acks}} and {{frame-ack}}. Note that
this requires being able to read the ECN codepoints from the enclosing IP
packet, which is not possible on all platforms.

A packet detected by a receiver as a duplicate does not affect the receiver's
local ECN codepoint counts; see ({{security-ecn}}) for relevant security
concerns.
An IP packet that results in no QUIC packets being processed does not increase
ECN counts. A QUIC packet detected by a receiver as a duplicate does not
affect the receiver's local ECN codepoint counts; see {{security-ecn}} for
relevant security concerns.

If an endpoint receives a QUIC packet without an ECT or CE codepoint in the IP
packet header, it responds per {{generating-acks}} with an ACK frame without
Expand All @@ -3728,7 +3729,7 @@ support or does not have access to received ECN codepoints, it does not increase
ECN counts.

Coalesced packets (see {{packet-coalesce}}) mean that several packets can share
the same IP header. The ECN counter for the ECN codepoint received in the
the same IP header. The ECN counts for the ECN codepoint received in the
associated IP header are incremented once for each QUIC packet, not per
enclosing IP packet or UDP datagram.

Expand Down Expand Up @@ -3773,10 +3774,10 @@ 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.

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
marking strategies. Implementations can also use the ECT(1) codepoint, as
specified in {{?RFC8311}}.
marking strategies. Implementations MAY use other methods defined in RFCs; see
{{?RFC8311}}. Implementations that use the ECT(1) codepoint need to perform ECN
validation using ECT(1) counts.


#### Receiving ACK Frames {#ecn-ack}
Expand Down