Script updating gh-pages from eee42a3. [ci skip]

h3qp_auth48/rfc9114.html

@@ -2031,19 +2031,20 @@ <h3 id="name-http-fields">
 <p id="section-4.2-1">HTTP messages carry metadata as a series of key-value pairs called "HTTP
 fields"; see Sections <a href="https://rfc-editor.org/rfc/rfc9110#section-6.3" class="relref">6.3</a> and <a href="https://rfc-editor.org/rfc/rfc9110#section-6.5" class="relref">6.5</a> of <span>[<a href="#RFC9110" class="xref">HTTP</a>]</span>. For a listing of registered
 HTTP fields, see the "Hypertext Transfer Protocol (HTTP) Field Name Registry"
-maintained at <span>&lt;<a href="https://www.iana.org/assignments/http-fields/">https://www.iana.org/assignments/http-fields/</a>&gt;</span>.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
+maintained at <span>&lt;<a href="https://www.iana.org/assignments/http-fields/">https://www.iana.org/assignments/http-fields/</a>&gt;</span>.  Like HTTP/2, HTTP/3 has additional considerations related to
+the use of characters in field names, the Connection header field, and
+pseudo-header fields.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
 <p id="section-4.2-2">Field names are strings containing a subset of ASCII characters. Properties of
-HTTP field names and values are discussed in more detail in <span><a href="https://rfc-editor.org/rfc/rfc9110#section-5.1" class="relref">Section 5.1</a> of [<a href="#RFC9110" class="xref">HTTP</a>]</span>. As in HTTP/2, characters in field names          <span class="bcp14">MUST</span>
- be converted to
-lowercase prior to their encoding. A request or response containing uppercase
-characters in field names          <span class="bcp14">MUST</span>
+HTTP field names and values are discussed in more detail in <span><a href="https://rfc-editor.org/rfc/rfc9110#section-5.1" class="relref">Section 5.1</a> of [<a href="#RFC9110" class="xref">HTTP</a>]</span>. Characters in field names          <span class="bcp14">MUST</span>
+ be converted to lowercase prior to
+their encoding. A request or response containing uppercase characters in field
+names          <span class="bcp14">MUST</span>
  be treated as <a href="#malformed" class="xref">malformed</a><span id="iref-malformed-56" class="iref"></span>.<a href="#section-4.2-2" class="pilcrow">¶</a></p>
-<p id="section-4.2-3">Like HTTP/2, HTTP/3 does not use the Connection header field to indicate
-connection-specific fields; in this protocol, connection-specific metadata is
-conveyed by other means.  An endpoint          <span class="bcp14">MUST NOT</span>
- generate an HTTP/3 field section
-containing connection-specific fields; any message containing
-connection-specific fields          <span class="bcp14">MUST</span>
+<p id="section-4.2-3">HTTP/3 does not use the Connection header field to indicate connection-specific
+fields; in this protocol, connection-specific metadata is conveyed by other
+means.  An endpoint          <span class="bcp14">MUST NOT</span>
+ generate an HTTP/3 field section containing
+connection-specific fields; any message containing connection-specific fields          <span class="bcp14">MUST</span>
  be treated as <a href="#malformed" class="xref">malformed</a><span id="iref-malformed-57" class="iref"></span>.<a href="#section-4.2-3" class="pilcrow">¶</a></p>
 <p id="section-4.2-4">The only exception to this is the TE header field, which          <span class="bcp14">MAY</span>
  be present in an
@@ -3269,7 +3270,7 @@ <h4 id="name-push_promise">
 <a href="#section-7.2.5" class="section-number selfRef">7.2.5. </a><a href="#name-push_promise" class="section-name selfRef">PUSH_PROMISE</a>
           </h4>
 <p id="section-7.2.5-1">The <a href="#frame-push-promise" class="xref">PUSH_PROMISE</a><span id="iref-push_promise-305" class="iref"></span> frame (type=0x05) is used to carry a promised request header
-section from server to client on a <a href="#request-streams" class="xref">request stream</a><span id="iref-request-stream-306" class="iref"></span>, as in HTTP/2.<a href="#section-7.2.5-1" class="pilcrow">¶</a></p>
+section from server to client on a <a href="#request-streams" class="xref">request stream</a><span id="iref-request-stream-306" class="iref"></span>.<a href="#section-7.2.5-1" class="pilcrow">¶</a></p>
 <span id="name-push_promise-frame"></span><figure id="figure-8">
             <div class="alignLeft art-ascii-art art-text artwork" id="section-7.2.5-2.1">
 <pre>
@@ -4238,8 +4239,8 @@ <h4 id="name-settings-parameters">
             </tbody>
           </table>
 </div>
-<p id="section-11.2.2-7">For fomatting reasons, setting names can be abbreviated by removing the
-'SETTING_' prefix.<a href="#section-11.2.2-7" class="pilcrow">¶</a></p>
+<p id="section-11.2.2-7">For formatting reasons, setting names can be abbreviated by removing the
+'SETTINGS_' prefix.<a href="#section-11.2.2-7" class="pilcrow">¶</a></p>
 <p id="section-11.2.2-8">Each code of the format <code>0x1f * N + 0x21</code> for non-negative integer values of <code>N</code>
 (that is, 0x21, 0x40, ..., through 0x3ffffffffffffffe)            <span class="bcp14">MUST NOT</span>
  be assigned by
@@ -4679,10 +4680,10 @@ <h2 id="name-considerations-for-transiti">
 <p id="appendix-A-2">HTTP/3 begins from the premise that similarity to HTTP/2 is preferable, but not
 a hard requirement.  HTTP/3 departs from HTTP/2 where QUIC differs from TCP,
 either to take advantage of QUIC features (like streams) or to accommodate
-important shortcomings (such as a lack of total ordering). These differences
-make HTTP/3 similar to HTTP/2 in key aspects, such as the relationship of
-requests and responses to streams. However, the details of the HTTP/3 design are
-substantially different from HTTP/2.<a href="#appendix-A-2" class="pilcrow">¶</a></p>
+important shortcomings (such as a lack of total ordering). While HTTP/3 is
+similar to HTTP/2 in key aspects, such as the relationship of requests and
+responses to streams, the details of the HTTP/3 design are substantially
+different from HTTP/2.<a href="#appendix-A-2" class="pilcrow">¶</a></p>
 <p id="appendix-A-3">Some important departures are noted in this section.<a href="#appendix-A-3" class="pilcrow">¶</a></p>
 <div id="h2-streams">
 <section id="appendix-A.1">

h3qp_auth48/rfc9114.txt

@@ -4,7 +4,7 @@
 
 Internet Engineering Task Force (IETF)                    M. Bishop, Ed.
 Request for Comments: 9114                                        Akamai
-Category: Standards Track                                  25 April 2022
+Category: Standards Track                                  26 April 2022
 ISSN: 2070-1721
 
 
@@ -667,22 +667,24 @@ Table of Contents
    "HTTP fields"; see Sections 6.3 and 6.5 of [HTTP].  For a listing of
    registered HTTP fields, see the "Hypertext Transfer Protocol (HTTP)
    Field Name Registry" maintained at <https://www.iana.org/assignments/
-   http-fields/>.
+   http-fields/>.  Like HTTP/2, HTTP/3 has additional considerations
+   related to the use of characters in field names, the Connection
+   header field, and pseudo-header fields.
 
    Field names are strings containing a subset of ASCII characters.
    Properties of HTTP field names and values are discussed in more
-   detail in Section 5.1 of [HTTP].  As in HTTP/2, characters in field
-   names MUST be converted to lowercase prior to their encoding.  A
-   request or response containing uppercase characters in field names
-   MUST be treated as malformed.
-
-   Like HTTP/2, HTTP/3 does not use the Connection header field to
-   indicate connection-specific fields; in this protocol, connection-
-   specific metadata is conveyed by other means.  An endpoint MUST NOT
-   generate an HTTP/3 field section containing connection-specific
-   fields; any message containing connection-specific fields MUST be
+   detail in Section 5.1 of [HTTP].  Characters in field names MUST be
+   converted to lowercase prior to their encoding.  A request or
+   response containing uppercase characters in field names MUST be
    treated as malformed.
 
+   HTTP/3 does not use the Connection header field to indicate
+   connection-specific fields; in this protocol, connection-specific
+   metadata is conveyed by other means.  An endpoint MUST NOT generate
+   an HTTP/3 field section containing connection-specific fields; any
+   message containing connection-specific fields MUST be treated as
+   malformed.
+
    The only exception to this is the TE header field, which MAY be
    present in an HTTP/3 request header; when it is, it MUST NOT contain
    any value other than "trailers".
@@ -1687,8 +1689,7 @@ Table of Contents
 7.2.5.  PUSH_PROMISE
 
    The PUSH_PROMISE frame (type=0x05) is used to carry a promised
-   request header section from server to client on a request stream, as
-   in HTTP/2.
+   request header section from server to client on a request stream.
 
    PUSH_PROMISE Frame {
      Type (i) = 0x05,
@@ -2370,8 +2371,8 @@ Table of Contents
 
                      Table 3: Initial HTTP/3 Settings
 
-   For fomatting reasons, setting names can be abbreviated by removing
-   the 'SETTING_' prefix.
+   For formatting reasons, setting names can be abbreviated by removing
+   the 'SETTINGS_' prefix.
 
    Each code of the format 0x1f * N + 0x21 for non-negative integer
    values of N (that is, 0x21, 0x40, ..., through 0x3ffffffffffffffe)
@@ -2650,10 +2651,10 @@ Appendix A.  Considerations for Transitioning from HTTP/2
    preferable, but not a hard requirement.  HTTP/3 departs from HTTP/2
    where QUIC differs from TCP, either to take advantage of QUIC
    features (like streams) or to accommodate important shortcomings
-   (such as a lack of total ordering).  These differences make HTTP/3
-   similar to HTTP/2 in key aspects, such as the relationship of
-   requests and responses to streams.  However, the details of the
-   HTTP/3 design are substantially different from HTTP/2.
+   (such as a lack of total ordering).  While HTTP/3 is similar to
+   HTTP/2 in key aspects, such as the relationship of requests and
+   responses to streams, the details of the HTTP/3 design are
+   substantially different from HTTP/2.
 
    Some important departures are noted in this section.
 
@@ -3035,24 +3036,24 @@ Index
             Section 7.2.6, Paragraph 5; Section 7.2.7, Paragraph 2;
             Section 7.2.7, Paragraph 3; Section 7.2.7, Paragraph 6;
             Section 7.2.8, Paragraph 3; Section 8, Paragraph 2;
-            Section 8, Paragraph 4; Section 10.5, Paragraph 7
+            Section 8, Paragraph 4; Section 10.5, Paragraph 7;
+            Appendix A.4.1, Paragraph 4
          control stream  Section 2, Paragraph 3; Section 3.2, Paragraph
-            4; Section 6.2, Paragraph 5; Section 6.2, Paragraph 6;
-            Section 6.2.1, Paragraph 1; Section 6.2.1, Paragraph 2;
+            4; Section 6.2, Paragraph 3; Section 6.2, Paragraph 5;
+            Section 6.2, Paragraph 6; Section 6.2.1, Paragraph 1;
             Section 6.2.1, Paragraph 2; Section 6.2.1, Paragraph 2;
             Section 6.2.1, Paragraph 2; Section 6.2.1, Paragraph 2;
             Section 6.2.1, Paragraph 2; Section 6.2.1, Paragraph 2;
-            Section 6.2.1, Paragraph 3; Section 6.2.1, Paragraph 3;
-            Section 7, Paragraph 1; Section 7.2.1, Paragraph 2;
-            Section 7.2.2, Paragraph 3; Section 7.2.3, Paragraph 5;
-            Section 7.2.3, Paragraph 5; Section 7.2.4, Paragraph 2;
-            Section 7.2.4, Paragraph 2; Section 7.2.4, Paragraph 3;
-            Section 7.2.5, Paragraph 8; Section 7.2.6, Paragraph 3;
-            Section 7.2.6, Paragraph 5; Section 7.2.7, Paragraph 2;
-            Section 8.1, Paragraph 2.22.1; Section 9, Paragraph 4;
-            Appendix A.2.4, Paragraph 3; Appendix A.3, Paragraph 1
-         control streams
-            control streams  Section 6.2, Paragraph 3
+            Section 6.2.1, Paragraph 2; Section 6.2.1, Paragraph 3;
+            Section 6.2.1, Paragraph 3; Section 7, Paragraph 1;
+            Section 7.2.1, Paragraph 2; Section 7.2.2, Paragraph 3;
+            Section 7.2.3, Paragraph 5; Section 7.2.3, Paragraph 5;
+            Section 7.2.4, Paragraph 2; Section 7.2.4, Paragraph 2;
+            Section 7.2.4, Paragraph 3; Section 7.2.5, Paragraph 8;
+            Section 7.2.6, Paragraph 3; Section 7.2.6, Paragraph 5;
+            Section 7.2.7, Paragraph 2; Section 8.1, Paragraph 2.22.1;
+            Section 9, Paragraph 4; Appendix A.2.4, Paragraph 3;
+            Appendix A.3, Paragraph 1
 
       D
 
@@ -3217,22 +3218,21 @@ Index
             Section 7.2.7, Paragraph 6; Section 8.1, Paragraph 2.18.1;
             Appendix A.2.5, Paragraph 1.12.1; Appendix A.2.5, Paragraph
             1.16.1
-         push stream  Section 4.1, Paragraph 9; Section 4.6, Paragraph
-            3; Section 4.6, Paragraph 5; Section 4.6, Paragraph 5;
+         push stream  Section 4.1, Paragraph 8; Section 4.1, Paragraph
+            9; Section 4.6, Paragraph 3; Section 4.6, Paragraph 5;
+            Section 4.6, Paragraph 5; Section 4.6, Paragraph 13;
             Section 4.6, Paragraph 13; Section 4.6, Paragraph 13;
-            Section 6.2.2, Paragraph 2; Section 6.2.2, Paragraph 3;
-            Section 6.2.2, Paragraph 5; Section 6.2.2, Paragraph 5;
+            Section 6.2, Paragraph 3; Section 6.2.2, Paragraph 2;
+            Section 6.2.2, Paragraph 3; Section 6.2.2, Paragraph 5;
+            Section 6.2.2, Paragraph 5; Section 6.2.2, Paragraph 6;
             Section 6.2.2, Paragraph 6; Section 6.2.2, Paragraph 6;
-            Section 6.2.2, Paragraph 6; Section 7, Paragraph 1;
+            Section 7, Paragraph 1; Section 7.2.2, Paragraph 3;
             Section 7.2.3, Paragraph 1; Section 7.2.3, Paragraph 2;
             Section 7.2.3, Paragraph 2; Section 7.2.3, Paragraph 2;
             Section 7.2.3, Paragraph 2; Section 7.2.3, Paragraph 3;
             Section 7.2.3, Paragraph 4; Section 7.2.3, Paragraph 4;
-            Section 7.2.5, Paragraph 4.2.1; Appendix A.2.5, Paragraph
-            1.12.1
-         push streams  Section 4.1, Paragraph 8; Section 4.6, Paragraph
-            13; Section 6.2, Paragraph 3; Section 7.2.2, Paragraph 3;
-            Section 7.2.3, Paragraph 4; Section 7.2.7, Paragraph 1
+            Section 7.2.3, Paragraph 4; Section 7.2.5, Paragraph 4.2.1;
+            Section 7.2.7, Paragraph 1; Appendix A.2.5, Paragraph 1.12.1
 
       R
 
@@ -3276,8 +3276,9 @@ Index
             Paragraph 4.12.1
          stream error  Section 2.2; Section 4.1.2, Paragraph 4;
             Section 4.4, Paragraph 10; Section 8, Paragraph 1;
-            Section 8, Paragraph 4; Appendix A.4.1, Paragraph 3;
-            Appendix A.4.1, Paragraph 3
+            Section 8, Paragraph 2; Section 8, Paragraph 4;
+            Appendix A.4.1, Paragraph 3; Appendix A.4.1, Paragraph 3;
+            Appendix A.4.1, Paragraph 4
 
 Author's Address