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

Question: does SEMANTICS obsolete/update RFC3864 aka BCP90 ? #515

Closed
ioggstream opened this issue Nov 18, 2020 · 4 comments
Closed

Question: does SEMANTICS obsolete/update RFC3864 aka BCP90 ? #515

ioggstream opened this issue Nov 18, 2020 · 4 comments

Comments

@ioggstream
Copy link
Contributor

ioggstream commented Nov 18, 2020

Question

IIUC httpbis-semantics changes the field name registry, thus obsoleting updating BCP 90 / RFC3684.

Is that correct?
Should httpbis-semantics mention that?

@reschke

@reschke
Copy link
Contributor

reschke commented Nov 18, 2020

"obsoletes": no, because BCP 90 is also for email. "updates": yes, I think so. @mnot?

@mnot
Copy link
Member

mnot commented Nov 19, 2020

Hm; I suppose so, given that it's taking some of 3684's turf away.

@mnot mnot added the semantics label Nov 19, 2020
@reschke reschke changed the title Question: does SEMANTICS obsolete/update RFC3684 aka BCP90 ? Question: does SEMANTICS obsolete/update RFC3864 aka BCP90 ? Nov 19, 2020
@reschke
Copy link
Contributor

reschke commented Nov 19, 2020

Now does that make SEMANTICS part of BCP90?

@mnot
Copy link
Member

mnot commented Nov 19, 2020

I'm inclined to say no -- it modifies the scope of BCP90 to exclude HTTP header fields. Worth discussing more broadly, though.

royfielding added a commit that referenced this issue Nov 19, 2020
note that we are updating RFC 3864 (for #515)
@reschke reschke closed this as completed Nov 19, 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

3 participants