Move registry creation to sfbis

Fixes #2356.
httpwg · Jan 27, 2023 · b90e32a · b90e32a
1 parent 62a67d0
commit b90e32a
Show file tree

Hide file tree

Showing 2 changed files with 37 additions and 25 deletions.
diff --git a/draft-ietf-httpbis-retrofit.md b/draft-ietf-httpbis-retrofit.md
@@ -14,6 +14,9 @@ stand_alone: yes
 smart_quotes: no
 pi: [toc, tocindent, sortrefs, symrefs, strict, compact, comments, inline]
 
+entity:
+  SELF: "RFC nnnn"
+
 venue:
   group: HTTP
   type: Working Group
@@ -325,13 +328,8 @@ SF-Cookie: ("SID" "31d4d96e407aad42"), ("lang" "en-US")
 
 Please add the following note to the "Hypertext Transfer Protocol (HTTP) Field Name Registry":
 
-> The "Structured Type" column indicates the type of the field (per RFC8941), if any, and may be
-> "Dictionary", "List" or "Item". A prefix of "*" indicates that it is a retrofit type (i.e., not
-> natively Structured); see \[this specification].
->
-> Note that field names beginning with characters other than ALPHA or "*" will not be able to be
-> represented as a Structured Fields Token, and therefore may be incompatible with being mapped into
-> fields that refer to it; see \[this specification].
+> A prefix of "*" in the Structured Type column indicates that it is a retrofit type (i.e., not
+> natively Structured); see {{&SELF}}.
 
 Then, add a new column, "Structured Type", with the values from {{compatible}} assigned to the nominated registrations, prefixing each with "*" to indicate that it is a retrofit type.
 
@@ -355,22 +353,6 @@ Then, add the field names in {{new-fields}}, with the corresponding Structured T
 | SF-Set-Cookie          | List            |
 {:id="new-fields" title="New Fields"}
 
-Then, add the indicated Structured Type for each existing registry entry listed in {{existing-fields}}.
-
-| Field Name                                | Structured Type |
-|-------------------------------------------|-----------------|
-| Accept-CH                                 | List            |
-| Cache-Status                              | List            |
-| CDN-Cache-Control                         | Dictionary      |
-| Cross-Origin-Embedder-Policy              | Item            |
-| Cross-Origin-Embedder-Policy-Report-Only  | Item            |
-| Cross-Origin-Opener-Policy                | Item            |
-| Cross-Origin-Opener-Policy-Report-Only    | Item            |
-| Origin-Agent-Cluster                      | Item            |
-| Priority                                  | Dictionary      |
-| Proxy-Status                              | List            |
-{:id="existing-fields" title="Existing Fields"}
-
 Finally, add a new column to the "Cookie Attribute Registry" established by {{COOKIES}} with the title "Structured Type", using information from {{cookie-params}}.
 
 

diff --git a/draft-ietf-httpbis-sfbis.md b/draft-ietf-httpbis-sfbis.md
@@ -13,6 +13,9 @@ stand_alone: yes
 smart_quotes: no
 pi: [toc, tocindent, sortrefs, symrefs, strict, compact, comments, inline]
 
+entity:
+  SELF: "RFC nnnn"
+
 author:
  -
     ins: M. Nottingham
@@ -914,9 +917,35 @@ Given an ASCII string as input_string, return a Date. input_string is modified t
 5. Return output_date.
 
 
-# IANA Considerations
+# IANA Considerations {#iana}
+
+Please add the following note to the "Hypertext Transfer Protocol (HTTP) Field Name Registry":
+
+> The "Structured Type" column indicates the type of the field (per {{&SELF}}), if any, and may be
+> "Dictionary", "List" or "Item".
+>
+> Note that field names beginning with characters other than ALPHA or "*" will not be able to be
+> represented as a Structured Fields Token, and therefore may be incompatible with being mapped into
+> fields that refer to it.
+
+Then, add a new column, "Structured Type".
+
+Then, add the indicated Structured Type for each existing registry entry listed in {{existing-fields}}.
+
+| Field Name                                | Structured Type |
+|-------------------------------------------|-----------------|
+| Accept-CH                                 | List            |
+| Cache-Status                              | List            |
+| CDN-Cache-Control                         | Dictionary      |
+| Cross-Origin-Embedder-Policy              | Item            |
+| Cross-Origin-Embedder-Policy-Report-Only  | Item            |
+| Cross-Origin-Opener-Policy                | Item            |
+| Cross-Origin-Opener-Policy-Report-Only    | Item            |
+| Origin-Agent-Cluster                      | Item            |
+| Priority                                  | Dictionary      |
+| Proxy-Status                              | List            |
+{:id="existing-fields" title="Existing Fields"}
 
-This document has no IANA actions.
 
 # Security Considerations
 
@@ -1020,6 +1049,7 @@ This revision of the Structured Field Values for HTTP specification has made the
 * Added the Date structured type. ({{date}})
 * Stopped encouraging use of ABNF in definitions of new structured fields. ({{specify}})
 * Moved ABNF to an informative appendix. ({{abnf}})
+* Added a "Structured Type" column to the HTTP Field Name Registry. ({{iana}})
 
 
 # Acknowledgements