-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
message field registry migration needs to consider status "reserved" #273
Comments
|
Proposal 1: add a status "reserved" (and define the procedure for reserving field names) Proposal 2: move "close" to "permanent", but add a comment column in the registry and note what is special about that field name over there. cc @mnot |
|
Either is fine with me, but I lean towards (2). |
In instructions for IANA header field registry migration, consider "reserved" as well (#273)
|
Asked mailing list in https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/thread.html#msg103. EDIT: there was no feedback at all. |
Add "Comments" to HTTP field registry, and fix entry for "Close" to be "standard" with comment "(reserved)" (#273)
We have at least one entry in status "reserved" (for "close"). We need to define how it will show up in the new registry.
The text was updated successfully, but these errors were encountered: