QPACK references

rfc9204.md

@@ -40,11 +40,13 @@ author:
 
 normative:
 
-  HTTP3:
+  RFC9114:
+    display: HTTP/3
     title: "Hypertext Transfer Protocol Version 3 (HTTP/3)"
-    date: {DATE}
+    date: 1970-01-01
     seriesinfo:
-      Internet-Draft: draft-ietf-quic-http-latest
+      RFC: 9114
+      DOI: 10.17487/RFC9114
     author:
       -
           ins: M. Bishop
@@ -57,6 +59,25 @@ normative:
 
 informative:
 
+  RFC9113:
+    display: HTTP/2
+    title: "HTTP/2"
+    date: 1970-01-01
+    seriesinfo:
+      RFC: 9113
+      DOI: 10.17487/RFC9113
+    author:
+      -
+          ins: M. Thomson
+          name: Martin Thomson
+          org: Mozilla
+          role: editor
+      -
+          ins: C. Benfield
+          name: Cory Benfield
+          org: Apple Inc.
+          role: editor
+
   CRIME:
     target: http://en.wikipedia.org/w/index.php?title=CRIME&oldid=660948120
     title: "CRIME"
@@ -93,8 +114,8 @@ HPACK compression that seeks to reduce head-of-line blocking.
 
 The QUIC transport protocol ({{!QUIC-TRANSPORT=RFC9000}}) is designed to support
 HTTP semantics, and its design subsumes many of the features of HTTP/2
-({{?RFC7540}}). HTTP/2 uses HPACK ({{!RFC7541}}) for compression of the header
-and trailer sections.  If HPACK were used for HTTP/3 ({{HTTP3}}), it would
+({{?RFC9113}}). HTTP/2 uses HPACK ({{!RFC7541}}) for compression of the header
+and trailer sections.  If HPACK were used for HTTP/3 ({{RFC9114}}), it would
 induce head-of-line blocking for field sections due to built-in assumptions of a
 total ordering across frames on all streams.
 
@@ -1420,14 +1441,14 @@ or decoder stream.
 # IANA Considerations
 
 This document makes multiple registrations in the registries defined by
-{{HTTP3}}. The allocations created by this document are all assigned permanent
+{{RFC9113}}. The allocations created by this document are all assigned permanent
 status and list a change controller of the IETF and a contact of the HTTP
 working group (ietf-http-wg@w3.org).
 
 ## Settings Registration
 
 This document specifies two settings. The entries in the following table are
-registered in the "HTTP/3 Settings" registry established in {{HTTP3}}.
+registered in the "HTTP/3 Settings" registry established in {{RFC9113}}.
 
 |------------------------------|--------|---------------------------| ------- |
 | Setting Name                 |  Code  | Specification             | Default |
@@ -1443,7 +1464,7 @@ For formatting reasons, the setting names here are abbreviated by removing the
 ## Stream Type Registration
 
 This document specifies two stream types. The entries in the following table are
-registered in the "HTTP/3 Stream Types" registry established in {{HTTP3}}.
+registered in the "HTTP/3 Stream Types" registry established in {{RFC9113}}.
 
 | ---------------------------- | ------ | ------------------------- | ------ |
 | Stream Type                  |  Code  | Specification             | Sender |
@@ -1456,7 +1477,7 @@ registered in the "HTTP/3 Stream Types" registry established in {{HTTP3}}.
 ## Error Code Registration
 
 This document specifies three error codes. The entries in the following table
-are registered in the "HTTP/3 Error Codes" registry established in {{HTTP3}}.
+are registered in the "HTTP/3 Error Codes" registry established in {{RFC9113}}.
 
 | --------------------------------- | ------ | ---------------------------------------- | ---------------------- |
 | Name                              | Code   | Description                              | Specification          |