Skip to content
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

Closed
reschke opened this issue Jan 9, 2020 · 3 comments
Closed
Assignees

Comments

@reschke
Copy link
Contributor

reschke commented Jan 9, 2020

We have at least one entry in status "reserved" (for "close"). We need to define how it will show up in the new registry.

@reschke
Copy link
Contributor Author

reschke commented Feb 2, 2020

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

@mnot
Copy link
Member

mnot commented Feb 3, 2020

Either is fine with me, but I lean towards (2).

reschke added a commit that referenced this issue Feb 3, 2020
reschke added a commit that referenced this issue Feb 4, 2020
In instructions for IANA header field registry migration, consider "reserved" as well (#273)
@reschke
Copy link
Contributor Author

reschke commented Feb 4, 2020

Asked mailing list in https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/thread.html#msg103.

EDIT: there was no feedback at all.

royfielding added a commit that referenced this issue Jun 3, 2020
Add "Comments" to HTTP field registry, and fix entry for "Close" to be "standard" with comment "(reserved)" (#273)
@mnot mnot closed this as completed Jul 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants