From 5294b4053075e2c58e3ae33e165116a89f1a24f9 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 15 Jan 2020 10:26:53 +1100 Subject: [PATCH] Fix references to -tls Closes #3328. --- draft-ietf-quic-recovery.md | 6 +++--- draft-ietf-quic-transport.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md index 1a73f1c778..9f0ab34b19 100644 --- a/draft-ietf-quic-recovery.md +++ b/draft-ietf-quic-recovery.md @@ -618,8 +618,8 @@ initial RTT estimate. ## Discarding Keys and Packet State {#discarding-packets} -When packet protection keys are discarded (see Section 4.9 of {{QUIC-TLS}}), all -packets that were sent with those keys can no longer be acknowledged because +When packet protection keys are discarded (see Section 4.10 of {{QUIC-TLS}}), +all packets that were sent with those keys can no longer be acknowledged because their acknowledgements cannot be processed anymore. The sender MUST discard all recovery state associated with those packets and MUST remove them from the count of bytes in flight. @@ -637,7 +637,7 @@ is expected to be infrequent. It is expected that keys are discarded after packets encrypted with them would be acknowledged or declared lost. Initial secrets however might be destroyed -sooner, as soon as handshake keys are available (see Section 4.9.1 of +sooner, as soon as handshake keys are available (see Section 4.10.1 of {{QUIC-TLS}}). # Congestion Control {#congestion-control} diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index b78daff02f..284273e17a 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -4069,7 +4069,7 @@ first Handshake packet. A server stops sending and processing Initial packets when it receives its first Handshake packet. Though packets might still be in flight or awaiting acknowledgment, no further Initial packets need to be exchanged beyond this point. Initial packet protection keys are discarded (see -Section 4.9.1 of {{QUIC-TLS}}) along with any loss recovery and congestion +Section 4.10.1 of {{QUIC-TLS}}) along with any loss recovery and congestion control state (see Section 6.5 of {{QUIC-RECOVERY}}). Any data in CRYPTO frames is discarded - and no longer retransmitted - when