From 8a47a06ce8c8337f47f5ed86f33532146210d907 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Fri, 8 Nov 2019 13:02:07 -0500 Subject: [PATCH 1/3] Recommend replacing, not changing --- draft-ietf-quic-http.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index d9b71e5180..3d40918318 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -1485,8 +1485,9 @@ requirement and SHOULD be treated as an error. Extensions that could change the semantics of existing protocol components MUST be negotiated before being used. For example, an extension that changes the layout of the HEADERS frame cannot be used until the peer has given a positive -signal that this is acceptable. In this case, it could also be necessary to -coordinate when the revised layout comes into effect. +signal that this is acceptable. Coordinating when such a revised layout comes +into effect could prove complex. As such, allocating a new identifiers for +alternate versions of existing protocol elements is likely to be more effective. This document doesn't mandate a specific method for negotiating the use of an extension but notes that a setting ({{settings-parameters}}) could be used for From 36eba038a6b3e6216bd3532a2b3bc46e208c12f7 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Fri, 8 Nov 2019 13:32:16 -0500 Subject: [PATCH 2/3] Remove extra word --- draft-ietf-quic-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 3d40918318..b1e9f3f382 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -1486,7 +1486,7 @@ Extensions that could change the semantics of existing protocol components MUST be negotiated before being used. For example, an extension that changes the layout of the HEADERS frame cannot be used until the peer has given a positive signal that this is acceptable. Coordinating when such a revised layout comes -into effect could prove complex. As such, allocating a new identifiers for +into effect could prove complex. As such, allocating new identifiers for alternate versions of existing protocol elements is likely to be more effective. This document doesn't mandate a specific method for negotiating the use of an From 0b355bf7fd8387fd8cb722592c3e67531de7bc10 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Mon, 11 Nov 2019 10:02:33 -0500 Subject: [PATCH 3/3] Update draft-ietf-quic-http.md Co-Authored-By: Martin Thomson --- draft-ietf-quic-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index b1e9f3f382..d441f3d1d0 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -1487,7 +1487,7 @@ be negotiated before being used. For example, an extension that changes the layout of the HEADERS frame cannot be used until the peer has given a positive signal that this is acceptable. Coordinating when such a revised layout comes into effect could prove complex. As such, allocating new identifiers for -alternate versions of existing protocol elements is likely to be more effective. +new definitions of existing protocol elements is likely to be more effective. This document doesn't mandate a specific method for negotiating the use of an extension but notes that a setting ({{settings-parameters}}) could be used for