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

Header Field Registry #42

Closed
mnot opened this issue Nov 23, 2017 · 6 comments
Closed

Header Field Registry #42

mnot opened this issue Nov 23, 2017 · 6 comments

Comments

@mnot
Copy link
Member

mnot commented Nov 23, 2017

... is currently interleaved with News and SMTP, which is less than ideal.

See:
https://mnot.github.io/I-D/httpbis-header-registry/

@mnot mnot added the semantics label Nov 23, 2017
@mnot mnot added the discuss label Jul 4, 2018
@mnot
Copy link
Member Author

mnot commented Jul 18, 2018

Discussed in Montreal; take it to the list, talk to DISPATCH.

@royfielding
Copy link
Member

Strictly speaking, it's an IANA instruction, but those instructions are in some other RFC. I think we would need the responsible list to agree first, which I guess means dispatch.

@mnot
Copy link
Member Author

mnot commented Jul 19, 2018

Yes. I'm talking to Alexey about it.

@mnot mnot removed the discuss label Oct 22, 2018
@mnot
Copy link
Member Author

mnot commented Nov 5, 2018

Discussed in DISPATCH Bangkok, no problem from them.

I've updated and submitted my draft, see:
https://tools.ietf.org/html/draft-nottingham-httpbis-header-registry-00

@mnot mnot added the discuss label Nov 5, 2018
@reschke reschke changed the title Header registry Header Field Registry Nov 6, 2018
@mcmanus
Copy link

mcmanus commented Nov 6, 2018

in bkk: make it so

@mnot mnot removed the discuss label Nov 12, 2018
@mnot mnot self-assigned this Nov 12, 2018
mnot added a commit that referenced this issue Nov 29, 2018
@mnot mnot closed this as completed Dec 2, 2018
reschke added a commit that referenced this issue Dec 2, 2018
reschke added a commit that referenced this issue Dec 2, 2018
@mnot
Copy link
Member Author

mnot commented Mar 12, 2019

As per discussion in #188, re-opening to remind us to remove this:

Entries with a status of 'deprecated' are to have a status of 'obsoleted'.

@mnot mnot reopened this Mar 12, 2019
@mnot mnot closed this as completed in 371a7f8 Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants