(re)generate HTML

Author: mnot

specs/rfc2818.html

@@ -235,7 +235,7 @@
 
   </div>
 </nav><div class="container" id="top"><div class="row"><div class="col-lg-4 order-last d-none d-lg-block" id="sidebar" role="navigation"><div class="navbar"><div class="navbar-brand"><a href="#top"><strong>RFC </strong>9412</a></div><br clear="all"><div class=""><div class="toc "><ul><li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#problems">Introduction</a><ul><li><a href="#rfc.section.1.1">1.1.</a>&nbsp;&nbsp;&nbsp;<a href="#notational-conventions">Notational Conventions</a></li></ul></li><li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#frame-origin">The ORIGIN HTTP/3 Frame</a><ul><li><a href="#rfc.section.2.1">2.1.</a>&nbsp;&nbsp;&nbsp;<a href="#frame-layout">Frame Layout</a></li></ul></li><li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#security">Security Considerations</a></li><li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#iana">IANA Considerations</a></li><li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul><li><a href="#rfc.section.5.1">5.1.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Normative References</a></li><li><a href="#rfc.section.5.2">5.2.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.3">Informative References</a></li></ul></li><li><a href="#rfc.authors">Author's Address</a></li></ul></div></div></div></div><div class="col-lg-8 order-first main" role="main"><header><table class="table table-condensed header" id="rfc.headerblock"><tbody><tr><td class="text-left">Internet Engineering Task Force (IETF)</td><td class="text-right">M. Bishop</td></tr><tr><td class="text-left">Request for Comments: 9412</td><td class="text-right">Akamai</td></tr><tr><td class="text-left">Category: Standards Track</td><td class="text-right">June 2023</td></tr><tr><td class="text-left">ISSN: 2070-1721</td><td class="text-right"></td></tr></tbody></table><div id="rfc.title"><h1>The ORIGIN Extension in HTTP/3</h1></div></header><hr><h2 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h2><div class="lead"><div id="rfc.abstract.p.1"><p>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.</p></div></div><aside id="rfc.meta" class="alert alert-info"></aside><section id="rfc.status"><h2><a href="#rfc.status">Status of This Memo</a></h2><div id="rfc.boilerplate.1.p.1"><p>This is an Internet Standards Track document.</p></div><div id="rfc.boilerplate.1.p.2"><p>This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in <a href="https://www.rfc-editor.org/rfc/rfc7841.html#section-2">Section 2 of RFC 7841</a>.</p></div><div id="rfc.boilerplate.1.p.3"><p>Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at <a href="https://www.rfc-editor.org/info/rfc9412">https://www.rfc-editor.org/info/rfc9412</a>.</p></div></section><section id="rfc.copyrightnotice"><h2><a href="#rfc.copyrightnotice">Copyright Notice</a></h2><div id="rfc.boilerplate.2.p.1"><p>Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.</p></div><div id="rfc.boilerplate.2.p.2"><p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.</p></div></section><div class="toc d-lg-none"><ul><li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#problems">Introduction</a><ul><li><a href="#rfc.section.1.1">1.1.</a>&nbsp;&nbsp;&nbsp;<a href="#notational-conventions">Notational Conventions</a></li></ul></li><li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#frame-origin">The ORIGIN HTTP/3 Frame</a><ul><li><a href="#rfc.section.2.1">2.1.</a>&nbsp;&nbsp;&nbsp;<a href="#frame-layout">Frame Layout</a></li></ul></li><li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#security">Security Considerations</a></li><li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#iana">IANA Considerations</a></li><li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul><li><a href="#rfc.section.5.1">5.1.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Normative References</a></li><li><a href="#rfc.section.5.2">5.2.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.3">Informative References</a></li></ul></li><li><a href="#rfc.authors">Author's Address</a></li></ul></div><hr class="hidden-print"><section id="problems"><h2 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#problems">Introduction</a></h2><div id="rfc.section.1.p.1"><p>Existing RFCs define extensions to HTTP/2 <a href="#RFC9113"><cite title="HTTP/2">[HTTP/2]</cite></a> that remain useful in HTTP/3. <a href="https://www.rfc-editor.org/rfc/rfc9114.html#appendix-A.2">Appendix A.2</a> of <a href="#RFC9114"><cite title="HTTP/3">[HTTP/3]</cite></a> describes the required updates for HTTP/2 frames to be used with HTTP/3.</p></div><div id="rfc.section.1.p.2"><p><a href="#ORIGIN"><cite title="The ORIGIN HTTP/2 Frame">[ORIGIN]</cite></a> defines the HTTP/2 ORIGIN frame, which indicates what origins are available on a given connection. It defines a single HTTP/2 frame type.</p></div><section id="notational-conventions"><h3 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1.</a>&nbsp;<a href="#notational-conventions">Notational Conventions</a></h3><div id="rfc.section.1.1.p.1"><p>The key words "<em class="bcp14">MUST</em>", "<em class="bcp14">MUST NOT</em>", "<em class="bcp14">REQUIRED</em>", "<em class="bcp14">SHALL</em>", "<em class="bcp14">SHALL
-NOT</em>", "<em class="bcp14">SHOULD</em>", "<em class="bcp14">SHOULD NOT</em>", "<em class="bcp14">RECOMMENDED</em>", "<em class="bcp14">NOT RECOMMENDED</em>", "<em class="bcp14">MAY</em>", and "<em class="bcp14">OPTIONAL</em>" in this document are to be interpreted as described in BCP&nbsp;14 <a href="#RFC2119"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a> <a href="#RFC8174"><cite title="Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words">[RFC8174]</cite></a> when, and only when, they appear in all capitals, as shown here.</p></div><div id="rfc.section.1.1.p.2"><p>The frame diagram in this document uses the format defined in <a href="https://www.rfc-editor.org/rfc/rfc9000.html#section-1.3">Section 1.3</a> of <a href="#QUIC-TRANSPORT"><cite title="QUIC: A UDP-Based Multiplexed and Secure Transport">[QUIC-TRANSPORT]</cite></a> to illustrate the order and size of fields.</p></div></section></section><hr class="hidden-print"><section id="frame-origin"><h2 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#frame-origin">The ORIGIN HTTP/3 Frame</a></h2><div id="rfc.section.2.p.1"><p>The ORIGIN HTTP/3 frame allows a server to indicate what origin or origins <a href="#RFC6454"><cite title="The Web Origin Concept">[RFC6454]</cite></a> the server would like the client to consider as one or more members of the Origin Set (<a href="https://www.rfc-editor.org/rfc/rfc8336.html#section-2.3">Section 2.3</a> of <a href="#ORIGIN"><cite title="The ORIGIN HTTP/2 Frame">[ORIGIN]</cite></a>) for the connection within which it occurs.</p></div><div id="rfc.section.2.p.2"><p>The semantics of the frame payload are identical to those of the HTTP/2 frame defined in <a href="#ORIGIN"><cite title="The ORIGIN HTTP/2 Frame">[ORIGIN]</cite></a>. 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.</p></div><div id="rfc.section.2.p.3"><p>Where <a href="#ORIGIN"><cite title="The ORIGIN HTTP/2 Frame">[ORIGIN]</cite></a> indicates that the ORIGIN frame is sent on stream 0, this 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.</p></div><div id="rfc.section.2.p.4"><p>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 mechanism for communicating such flags in HTTP/3.</p></div><section id="frame-layout"><h3 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1.</a>&nbsp;<a href="#frame-layout">Frame Layout</a></h3><div id="rfc.section.2.1.p.1"><p>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.</p></div><div id="rfc.figure.1"><div><pre>
+NOT</em>", "<em class="bcp14">SHOULD</em>", "<em class="bcp14">SHOULD NOT</em>", "<em class="bcp14">RECOMMENDED</em>", "<em class="bcp14">NOT RECOMMENDED</em>", "<em class="bcp14">MAY</em>", and "<em class="bcp14">OPTIONAL</em>" in this document are to be interpreted as described in <span class="nobr">BCP 14</span> <a href="#RFC2119"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a> <a href="#RFC8174"><cite title="Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words">[RFC8174]</cite></a> when, and only when, they appear in all capitals, as shown here.</p></div><div id="rfc.section.1.1.p.2"><p>The frame diagram in this document uses the format defined in <a href="https://www.rfc-editor.org/rfc/rfc9000.html#section-1.3">Section 1.3</a> of <a href="#QUIC-TRANSPORT"><cite title="QUIC: A UDP-Based Multiplexed and Secure Transport">[QUIC-TRANSPORT]</cite></a> to illustrate the order and size of fields.</p></div></section></section><hr class="hidden-print"><section id="frame-origin"><h2 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#frame-origin">The ORIGIN HTTP/3 Frame</a></h2><div id="rfc.section.2.p.1"><p>The ORIGIN HTTP/3 frame allows a server to indicate what origin or origins <a href="#RFC6454"><cite title="The Web Origin Concept">[RFC6454]</cite></a> the server would like the client to consider as one or more members of the Origin Set (<a href="https://www.rfc-editor.org/rfc/rfc8336.html#section-2.3">Section 2.3</a> of <a href="#ORIGIN"><cite title="The ORIGIN HTTP/2 Frame">[ORIGIN]</cite></a>) for the connection within which it occurs.</p></div><div id="rfc.section.2.p.2"><p>The semantics of the frame payload are identical to those of the HTTP/2 frame defined in <a href="#ORIGIN"><cite title="The ORIGIN HTTP/2 Frame">[ORIGIN]</cite></a>. 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.</p></div><div id="rfc.section.2.p.3"><p>Where <a href="#ORIGIN"><cite title="The ORIGIN HTTP/2 Frame">[ORIGIN]</cite></a> indicates that the ORIGIN frame is sent on stream 0, this 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.</p></div><div id="rfc.section.2.p.4"><p>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 mechanism for communicating such flags in HTTP/3.</p></div><section id="frame-layout"><h3 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1.</a>&nbsp;<a href="#frame-layout">Frame Layout</a></h3><div id="rfc.section.2.1.p.1"><p>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.</p></div><div id="rfc.figure.1"><div><pre>
 HTTP/3 Origin-Entry {
   Origin-Len (16),
   ASCII-Origin (..),