From 0c8c6eee66c20a2c6e52f06ff68b714a5da68e64 Mon Sep 17 00:00:00 2001 From: Kazu Yamamoto Date: Tue, 17 Nov 2020 15:13:23 +0900 Subject: [PATCH] s/endpoint/client/ because only a server can send NEW_TOKEN. --- draft-ietf-quic-transport.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 73bb26813a..27891ff90f 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -5739,15 +5739,15 @@ Token Length: Token: : An opaque blob that the client may use with a future Initial packet. The token - MUST NOT be empty. An endpoint MUST treat receipt of a NEW_TOKEN frame with + MUST NOT be empty. A client MUST treat receipt of a NEW_TOKEN frame with an empty Token field as a connection error of type FRAME_ENCODING_ERROR. -An endpoint might receive multiple NEW_TOKEN frames that contain the same token +A client might receive multiple NEW_TOKEN frames that contain the same token value if packets containing the frame are incorrectly determined to be lost. -Endpoints are responsible for discarding duplicate values, which might be used +Clients are responsible for discarding duplicate values, which might be used to link connection attempts; see {{validate-future}}. -Clients MUST NOT send NEW_TOKEN frames. Servers MUST treat receipt of a +Clients MUST NOT send NEW_TOKEN frames. A server MUST treat receipt of a NEW_TOKEN frame as a connection error of type PROTOCOL_VIOLATION.