Repository navigation
message field registry migration needs to consider status "reserved" #273
Description
We have at least one entry in status "reserved" (for "close"). We need to define how it will show up in the new registry.
{{ message }}
We have at least one entry in status "reserved" (for "close"). We need to define how it will show up in the new registry.
Activity
reschke commentedon 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 commentedon Feb 3, 2020
Either is fine with me, but I lean towards (2).
In instructions for IANA header field registry migration, consider "r…
Merge pull request #293 from httpwg/reschke-273
reschke commentedon 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.
Merge pull request #376 from httpwg/reschke-273