Removing IANA consideration sections for HTTP headers #7274
Comments
annevk
added
the
meta
|
I'm skeptical that the existence of a GitHub repository will cause the IETF to process registration requests any more quickly than they did with a mailing list. I.e. changing the technology doesn't seem like it'd help with the human factors. But indeed, removing the IANA boilerplate and fleshing out the definitions where appropriate seems nice. |
|
It took a day without issue for the first registration I tried (see issue 1 there), so I'm optimistic. |
|
Indeed things seem to be moving quickly now! It looks like @mikewest registered Cross-Origin-* using the iana.html URLs per https://www.iana.org/assignments/http-fields/http-fields.xhtml ; see e.g. protocol-registries/http-fields#18 . So we'd need to take some care to get those updated... |
This concludes moving away from using IANA templates to define HTTP headers. It takes care of Last-Event-ID, Ping-From, Ping-To, Refresh, and X-Frame-Options. It also adds an index to ensure these headers are still easy to find. And finally it corrects the casing of several index sections. This helps with #7274 (kept open to update the IANA registry) and fixes #7355.
This concludes moving away from using IANA templates to define HTTP headers. It takes care of Last-Event-ID, Ping-From, Ping-To, Refresh, and X-Frame-Options. It also adds an index to ensure these headers are still easy to find. And finally it corrects the casing of several index sections. This helps with #7274 (kept open to update the IANA registry) and fixes #7355.
|
The HTML Standard has been updated. IANA tickets have been submitted:
I'll leave this open for now. |
|
They all succeeded. \o/ |
This is the first step towards addressing whatwg#7274. It takes care of Cross-Origin-Embedder-Policy, Cross-Origin-Embedder-Policy-Report-Only, Cross-Origin-Opener-Policy, Cross-Origin-Opener-Policy-Report-Only, and Origin-Agent-Cluster. Closes whatwg#7325.
This is the first step towards addressing whatwg#7274. It takes care of Cross-Origin-Embedder-Policy, Cross-Origin-Embedder-Policy-Report-Only, Cross-Origin-Opener-Policy, Cross-Origin-Opener-Policy-Report-Only, and Origin-Agent-Cluster. Closes whatwg#7325.
This concludes moving away from using IANA templates to define HTTP headers. It takes care of Last-Event-ID, Ping-From, Ping-To, Refresh, and X-Frame-Options. It also adds an index to ensure these headers are still easy to find. And finally it corrects the casing of several index sections. This helps with whatwg#7274 (kept open to update the IANA registry) and fixes whatwg#7355.
Now that https://github.com/protocol-registries/http-fields exists it seems we can register most of these with ease.
Cross-Origin-*: these have dedicated sections already so that is relatively straightforward. We should consider giving the "The headers" sections better IDs though.Origin-Agent-Cluster: same.Ping-FromandPing-To: I suggest we add a short section after "Hyperlink auditing" (same level?) that defines these.Refresh: a section parallel to "TheX-Frame-Optionsheader" that is mainly a pointer to the http-equiv state?Last-Event-ID: a section after "Processing model" within the overallEventSourcesection?X-Frame-Options: already has a section. It's also already registered as https://datatracker.ietf.org/doc/html/rfc7034 so we might not be successful in getting this updated. There's a similar situation withOriginand I asked mnot for input.Thoughts?
The text was updated successfully, but these errors were encountered: