Fill out IANA section #29
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bemasc
reviewed
Jun 12, 2024
draft-ietf-tls-wkech.xml
Outdated
| </t> | ||
| </section> | ||
|
|
||
| <section title="JSON HTTP Origin Information"> | ||
|
|
||
| <t>If approved, this specification requests the creation of an IANA | ||
| registry named "JSON HTTP Origin Info" with a Standards Action |
There was a problem hiding this comment.
If we don't expect extensions here, we might not need a registry at all. For example, we aren't asking for a registry for the inner object ("alias", "target", etc.).
There was a problem hiding this comment.
I dunno, I would think #14 might add things?
There was a problem hiding this comment.
I think that's just another SvcParamKey.
There was a problem hiding this comment.
Well, we might move regeninterval to the top-level :)
Closed
|
And I added the registry entry for the top-level |
Closed
bemasc
approved these changes
Jun 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I filled in the text for the IANA Considerations section.
I am not sure if "standards action" is appropriate, but can live with it if you agree. Expert review seems better, and similar to what other JSON registries do. Thoughts?
I deleted the comment about I18N because I'm not sure it matters, since it's just JSON. Was that wrong to do?