#84: Section 7.1 JSON Web Key Parameters Registry A. This section is missing any mention of criteria by which an expert is to determine if the registration makes any sense.
B. I have a problem with the word reserved. To me this is not the same as "reserved word" used in computer languages. To me this implies something that is set aside for future use. This is not consistent with how the word is used in this content. In the case of the first sentence it can just be deleted. You have a registry for JWK parameter names. C. Is it permissible for a "private" field to be registered without a public specification attached to it? It would appear not, but this may be desirable behavior in the future. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-jose-json-web- [email protected] | [email protected] Type: defect | Status: new Priority: major | Milestone: Component: json-web- | Version: key | Keywords: Severity: - | -------------------------+------------------------------------------------- Ticket URL: <https://grenache.tools.ietf.org/wg/jose/trac/ticket/84> jose <http://tools.ietf.org/jose/> _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
