From 9eee3ebec69c4aea0577718f0c751bc861f065b7 Mon Sep 17 00:00:00 2001 From: Dmitri Tikhonov Date: Wed, 29 Jan 2020 11:08:07 -0500 Subject: [PATCH] Add forward references to packet number spaces Fixes issue #2334 --- draft-ietf-quic-transport.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index d9d026910c..9a4ace38bd 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -199,8 +199,8 @@ Ack-eliciting Packet: Out-of-order packet: : A packet that does not increase the largest received packet number for its - packet number space by exactly one. A packet can arrive out of order - if it is delayed or if earlier packets are lost or delayed. + packet number space ({{packet-numbers}}) by exactly one. A packet can arrive + out of order if it is delayed or if earlier packets are lost or delayed. Endpoint: @@ -1339,9 +1339,10 @@ properties: An endpoint can verify support for Explicit Congestion Notification (ECN) in the first packets it sends, as described in {{ecn-validation}}. -The CRYPTO frame can be sent in different packet number spaces. The sequence -numbers used by CRYPTO frames to ensure ordered delivery of cryptographic -handshake data start from zero in each packet number space. +The CRYPTO frame can be sent in different packet number spaces +({{packet-numbers}}). The sequence numbers used by CRYPTO frames to ensure +ordered delivery of cryptographic handshake data start from zero in each +packet number space. Endpoints MUST explicitly negotiate an application protocol. This avoids situations where there is a disagreement about the protocol that is in use.