From 02ce4ae6f1074600ae3d6327df8ad9d1d5ede81d Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Wed, 9 Aug 2017 17:54:38 -0700 Subject: [PATCH] editorial nits --- 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 16b98417b9..7903541975 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1202,11 +1202,11 @@ based on the value of the supported_versions list. When an endpoint accepts multiple QUIC versions, it can potentially interpret transport parameters as they are defined by any of the QUIC versions it supports. The version field in the QUIC packet header is authenticated using -the transport parameters. The position and the format of the version fields in +transport parameters. The position and the format of the version fields in transport parameters MUST either be identical across different QUIC versions, or -be unambiguously different to ensure no for confusion about their -interpretation. One way that a new format could be introduced is to define a -TLS extension with a different codepoint. +be unambiguously different to ensure no confusion about their interpretation. +One way that a new format could be introduced is to define a TLS extension with +a different codepoint. ## Stateless Retries {#stateless-retry}