From cf4f420f68ab739f6149930c7d0111230bc032e6 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 17 May 2023 16:02:06 -0400 Subject: [PATCH 1/4] Initial AUTH48 changes from RFC Editor --- draft-ietf-httpbis-origin-h3.md | 55 ++++++++++++++++++++------------- 1 file changed, 34 insertions(+), 21 deletions(-) diff --git a/draft-ietf-httpbis-origin-h3.md b/draft-ietf-httpbis-origin-h3.md index b9ee03f31..ed44b39e1 100644 --- a/draft-ietf-httpbis-origin-h3.md +++ b/draft-ietf-httpbis-origin-h3.md @@ -1,6 +1,7 @@ --- title: The ORIGIN Extension in HTTP/3 abbrev: ORIGIN in HTTP/3 +number: 9412 docname: draft-ietf-httpbis-origin-h3-latest date: {DATE} category: std @@ -33,7 +34,7 @@ informative: --- abstract -The ORIGIN frame for HTTP/2 is equally applicable to HTTP/3, but +The ORIGIN frame for HTTP/2 is equally applicable to HTTP/3, but it needs to be separately registered. This document describes the ORIGIN frame for HTTP/3. @@ -41,7 +42,7 @@ frame for HTTP/3. # Introduction {#problems} -Existing RFCs define extensions to HTTP/2 {{HTTP2}} which remain useful in +Existing RFCs define extensions to HTTP/2 {{HTTP2}} that remain useful in HTTP/3. {{Section A.2.3 of HTTP3}} describes the required updates for HTTP/2 frames to be used with HTTP/3. @@ -53,21 +54,21 @@ type. {::boilerplate bcp14-tagged} -Frame diagrams in this document use the format defined in {{Section 1.3 of +The frame diagram in this document uses the format defined in {{Section 1.3 of QUIC-TRANSPORT}} to illustrate the order and size of fields. # The ORIGIN HTTP/3 Frame {#frame-origin} -The ORIGIN HTTP/3 frame allows a server to indicate what origin(s) -({{?RFC6454}}) the server would like the client to consider as members of the -Origin Set ({{Section 2.3 of ORIGIN}}) for the connection within which it +The ORIGIN HTTP/3 frame allows a server to indicate what origin or origins +{{?RFC6454}} the server would like the client to consider as one or more members +of the Origin Set ({{Section 2.3 of ORIGIN}}) for the connection within which it occurs. The semantics of the frame payload are identical to those of the HTTP/2 frame -defined in {{!ORIGIN}}. Where HTTP/2 reserves Stream 0 for frames related to the +defined in {{!ORIGIN}}. Where HTTP/2 reserves stream 0 for frames related to the state of the connection, HTTP/3 defines a pair of unidirectional streams called "control streams" for this purpose. Where {{ORIGIN}} indicates that the ORIGIN -frame should be sent on Stream 0, this should be interpreted to mean the HTTP/3 +frame should be sent on stream 0, this should be interpreted to mean the HTTP/3 control stream. The ORIGIN frame is sent from servers to clients on the server's control stream. @@ -77,9 +78,10 @@ mechanism for communicating such flags in HTTP/3. ## Frame Layout -The ORIGIN frame has a nearly identical layout to that used in HTTP/2, restated -here for clarity. The ORIGIN frame type is 0xc (decimal 12) as in HTTP/2. The -payload contains zero or more instances of the Origin-Entry field. +The ORIGIN frame has a frame layout that is nearly identical layout to the +layout used in HTTP/2; the information is restated here for clarity. The ORIGIN +frame type is 0x0c (decimal 12), as in HTTP/2. The payload contains zero or more +instances of the Origin-Entry field. ~~~~~ ascii-art HTTP/3 Origin-Entry { @@ -114,17 +116,28 @@ in {{!ORIGIN}} and {{HTTP3}}. # IANA Considerations {#iana} -This document registers a frame type in the "HTTP/3 Frame Type" -registry ({{HTTP3}}). +This document registers a frame type in the "HTTP/3 Frame Types" +registry {{HTTP3}}. -| ----- | ---------------- | --------- | ----------------- | -| Value | Frame Type | Status | Specification | -| :---: | ---------------- | --------- | ----------------- | -| 0xc | ORIGIN | permanent | {{frame-origin}} | -| ----- | ---------------- | --------- | ----------------- | -{: #iana-frame-table title="Registered HTTP/3 Frame Types"} +Value: +: 0x0c -This allocation lists a change controller of the IETF and a contact of the HTTP -working group (ietf-http-wg@w3.org). +Frame Type: +: ORIGIN + +Status: +: permanent + +Reference: +: {{frame-origin}} + +Date: +: 2023-03-14 + +Change Controller: +: IETF + +Contact: +: HTTP WG \ --- back From 77cb39067787b3a191b8c2f6dde12546c5e94bbd Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 17 May 2023 16:07:37 -0400 Subject: [PATCH 2/4] Proposed changes for ARTART and IANA --- draft-ietf-httpbis-origin-h3.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/draft-ietf-httpbis-origin-h3.md b/draft-ietf-httpbis-origin-h3.md index ed44b39e1..fb329515d 100644 --- a/draft-ietf-httpbis-origin-h3.md +++ b/draft-ietf-httpbis-origin-h3.md @@ -67,10 +67,11 @@ occurs. The semantics of the frame payload are identical to those of the HTTP/2 frame defined in {{!ORIGIN}}. Where HTTP/2 reserves stream 0 for frames related to the state of the connection, HTTP/3 defines a pair of unidirectional streams called -"control streams" for this purpose. Where {{ORIGIN}} indicates that the ORIGIN -frame should be sent on stream 0, this should be interpreted to mean the HTTP/3 -control stream. The ORIGIN frame is sent from servers to clients on the -server's control stream. +"control streams" for this purpose. + +Where {{ORIGIN}} indicates that the ORIGIN frame is sent on stream 0, this +should be interpreted to mean the appropriate HTTP/3 control stream: that is, +the ORIGIN frame is sent from servers to clients on the server's control stream. HTTP/3 does not define a Flags field in the generic frame layout. As no flags have been defined for the ORIGIN frame, this specification does not define a @@ -116,8 +117,9 @@ in {{!ORIGIN}} and {{HTTP3}}. # IANA Considerations {#iana} -This document registers a frame type in the "HTTP/3 Frame Types" -registry {{HTTP3}}. +This document registers a frame type in the "HTTP/3 Frame Types" registry +defined by {{HTTP3}}, located at +\. Value: : 0x0c From 018a5e8f29a20ca15988e781c80629c8be266f69 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 19 Jul 2023 16:22:25 -0400 Subject: [PATCH 3/4] Final AUTH48 changes --- draft-ietf-httpbis-origin-h3.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/draft-ietf-httpbis-origin-h3.md b/draft-ietf-httpbis-origin-h3.md index fb329515d..733b5b281 100644 --- a/draft-ietf-httpbis-origin-h3.md +++ b/draft-ietf-httpbis-origin-h3.md @@ -3,7 +3,7 @@ title: The ORIGIN Extension in HTTP/3 abbrev: ORIGIN in HTTP/3 number: 9412 docname: draft-ietf-httpbis-origin-h3-latest -date: {DATE} +date: 2023-06 category: std ipr: trust200902 @@ -22,10 +22,10 @@ author: email: mbishop@evequefou.be normative: - HTTP2: - RFC9113 - HTTP3: - RFC9114 + RFC9113: + display: HTTP/2 + RFC9114: + display: HTTP/3 informative: QUIC-TRANSPORT: @@ -42,8 +42,8 @@ frame for HTTP/3. # Introduction {#problems} -Existing RFCs define extensions to HTTP/2 {{HTTP2}} that remain useful in -HTTP/3. {{Section A.2.3 of HTTP3}} describes the required updates for HTTP/2 +Existing RFCs define extensions to HTTP/2 {{RFC9113}} that remain useful in +HTTP/3. {{Section A.2 of RFC9114}} describes the required updates for HTTP/2 frames to be used with HTTP/3. {{!ORIGIN=RFC8336}} defines the HTTP/2 ORIGIN frame, which indicates what @@ -70,7 +70,7 @@ state of the connection, HTTP/3 defines a pair of unidirectional streams called "control streams" for this purpose. Where {{ORIGIN}} indicates that the ORIGIN frame is sent on stream 0, this -should be interpreted to mean the appropriate HTTP/3 control stream: that is, +should be interpreted to mean the HTTP/3 control stream: that is, the ORIGIN frame is sent from servers to clients on the server's control stream. HTTP/3 does not define a Flags field in the generic frame layout. As no flags @@ -79,7 +79,7 @@ mechanism for communicating such flags in HTTP/3. ## Frame Layout -The ORIGIN frame has a frame layout that is nearly identical layout to the +The ORIGIN frame has a layout that is nearly identical to the layout used in HTTP/2; the information is restated here for clarity. The ORIGIN frame type is 0x0c (decimal 12), as in HTTP/2. The payload contains zero or more instances of the Origin-Entry field. @@ -113,13 +113,13 @@ ASCII-Origin: # Security Considerations {#security} This document introduces no new security considerations beyond those discussed -in {{!ORIGIN}} and {{HTTP3}}. +in {{!ORIGIN}} and {{RFC9114}}. # IANA Considerations {#iana} This document registers a frame type in the "HTTP/3 Frame Types" registry -defined by {{HTTP3}}, located at -\. +defined by {{RFC9114}}, located at +\. Value: : 0x0c From adff16529a45b9842af6f849cdbbdc6814e24d19 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 19 Jul 2023 16:24:46 -0400 Subject: [PATCH 4/4] Move file --- .../draft-ietf-httpbis-origin-h3.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename draft-ietf-httpbis-origin-h3.md => archive/draft-ietf-httpbis-origin-h3.md (100%) diff --git a/draft-ietf-httpbis-origin-h3.md b/archive/draft-ietf-httpbis-origin-h3.md similarity index 100% rename from draft-ietf-httpbis-origin-h3.md rename to archive/draft-ietf-httpbis-origin-h3.md