Skip to content

Commit

Permalink
Small improvements
Browse files Browse the repository at this point in the history
Co-authored-by: Jana Iyengar <jri.ietf@gmail.com>
  • Loading branch information
martinthomson and janaiyengar authored Jun 19, 2020
1 parent 7ed7007 commit 56370b0
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -3816,11 +3816,12 @@ validation using ECT(1) counts.

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

Erroneous application of markings in the network can result in ECN marking
providing bad information. Before using ECN counts, an endpoint validates the
ECN counts by comparing the counts in each ACK frame it processes against the
last ACK frame that was successfully processed. The increase in ECN counts is
validated based on the markings that were applied to packets that are newly
Erroneous application of ECN marks in the network can result in degraded
connection performance. An endpoint that receives an ACK frame with ECN
counts therefore validates the counts before using them. An endpoint validates
these counts by comparing newly received counts against those from the last
successfully processed ACK frame. Any increase in ECN counts is validated
based on the markings that were applied to packets that are newly
acknowledged in the ACK frame.

If an ACK frame newly acknowledges a packet that the endpoint sent with either
Expand Down Expand Up @@ -3848,7 +3849,7 @@ validation when a non-zero count for the corresponding marking is received.
This check can detect when packets are marked ECT(0) or ECT(1) in the network.

Processing ECN counts out of order can result in validation failure. An
endpoint SHOULD skip ECN validation when an ACK frame does not increase the
endpoint SHOULD skip ECN validation on an ACK frame that does not increase the
largest acknowledged packet number.


Expand Down

0 comments on commit 56370b0

Please sign in to comment.