Skip to content

Commit

Permalink
Change references to 3168 to be normative
Browse files Browse the repository at this point in the history
I'm not sure if all of them need to be normative or not?
  • Loading branch information
ianswett committed Oct 12, 2020
1 parent 606b7d2 commit f61b2d0
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions draft-ietf-quic-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -795,7 +795,7 @@ is sent on a PTO timer expiration (see {{pto}}) or when entering recovery

## Explicit Congestion Notification {#congestion-ecn}

If a path has been validated to support ECN ({{?RFC3168}}, {{?RFC8311}}), QUIC
If a path has been validated to support ECN ({{!RFC3168}}, {{?RFC8311}}), QUIC
treats a Congestion Experienced (CE) codepoint in the IP header as a signal of
congestion. This document specifies an endpoint's response when the
peer-reported ECN-CE count increases; see Section 13.4.2 of {{QUIC-TRANSPORT}}.
Expand Down Expand Up @@ -1123,15 +1123,15 @@ A sender can detect suppression of reports by marking occasional packets that it
sends with an ECN-CE marking. If a packet sent with an ECN-CE marking is not
reported as having been CE marked when the packet is acknowledged, then the
sender can disable ECN for that path by not setting ECT codepoints in subsequent
packets sent on that path {{?RFC3168}}.
packets sent on that path {{!RFC3168}}.

Reporting additional ECN-CE markings will cause a sender to reduce their sending
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. Congestion controllers
respond to reports of ECN-CE by reducing their rate, but the response may vary.
Markings can be treated as equivalent to loss ({{?RFC3168}}), but other
Markings can be treated as equivalent to loss ({{!RFC3168}}), but other
responses can be specified, such as ({{?RFC8511}}) or ({{?RFC8311}}).


Expand Down

0 comments on commit f61b2d0

Please sign in to comment.