Add a (temporary) note to IANA regarding section references

httpwg · Sep 3, 2021 · 1abd87e · 1abd87e
1 parent e2b4149
commit 1abd87e
Showing 1 changed file with 10 additions and 5 deletions.
diff --git a/draft-ietf-httpbis-http2bis.xml b/draft-ietf-httpbis-http2bis.xml
@@ -328,7 +328,7 @@
           protocol that does not use TLS.
         </t>
         <t>
-          Once TLS negotiation is complete, both the client and the server MUST send a <xref target="ConnectionHeader">connection preface</xref>.
+          Once TLS negotiation is complete, both the client and the server MUST send a <xref target="preface">connection preface</xref>.
         </t>
       </section>
       <section anchor="known-http">
@@ -339,14 +339,14 @@
         </t>
         <t>
           A client that knows that a server supports HTTP/2 can establish a TCP connection and send
-          the <xref target="ConnectionHeader">connection preface</xref> followed by HTTP/2 frames.
+          the <xref target="preface">connection preface</xref> followed by HTTP/2 frames.
           Servers can identify these connections by the presence of the connection preface. This
           only affects the establishment of HTTP/2 connections over cleartext TCP; HTTP/2 connections
           over TLS MUST use <xref target="TLS-ALPN">protocol negotiation in
           TLS</xref>.
         </t>
         <t>
-          Likewise, the server MUST send a <xref target="ConnectionHeader">connection preface</xref>.
+          Likewise, the server MUST send a <xref target="preface">connection preface</xref>.
         </t>
         <t>
           Without additional information, prior support for HTTP/2 is not a strong signal that a
@@ -355,7 +355,7 @@
           clustered servers, or for network conditions to change.
         </t>
       </section>
-      <section anchor="ConnectionHeader">
+      <section anchor="preface">
         <name>HTTP/2 Connection Preface</name>
         <t>
           In HTTP/2, each endpoint is required to send a connection preface as a final confirmation
@@ -3718,7 +3718,7 @@ cookie: e=f
         </t>
         <t>
           The cleartext version of HTTP/2 has minimal protection against cross-protocol attacks.
-          The <xref target="ConnectionHeader">connection preface</xref> contains a string that is
+          The <xref target="preface">connection preface</xref> contains a string that is
           designed to confuse HTTP/1.1 servers, but no special protection is offered for other
           protocols.
         </t>
@@ -4008,6 +4008,11 @@ cookie: e=f
         for frame types, settings, and error codes.  These registrations and registries apply to
         HTTP/2, but are not redefined in this document.
       </t>
+      <t>
+        [RFC Editor: please remove this paragraph.]  IANA is requested to update references in these
+        registries to refer to this document.  The registration of the <tt>PRI</tt> method needs to
+        be updated to refer to <xref target="preface"/>; all other section numbers have not changed.
+      </t>
       <section anchor="HTTP2-Settings">
         <name>HTTP2-Settings Header Field Registration</name>
         <t>