#103: Rename "alg" to avoid future collision problems In order to support the use case of using key management and MAC computation, I would like to re-name alg to be "int" (integrity) or something similar (I would equally be happy to re-name "alg" in the encryption document to "kmgt" (key management))
In the future there will be a need to do MAC computations on object with key management, the group has decided that this is not an immediate priority and this not to revisit that issue. However, in the future when this is added, all of the key management algorithms from both the JWS and JWE drafts should be placed in the same header parameter member according to the rules of header parameter (if they have the same name then they should have the same usage). This will also facility a reasonable restriction that an algorithm can occur only for a single member and not in multiple members. If it can occur in both alg (for JWE) and kmgt (for JWS) then the rules for using alg as a determination get broken. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-jose-json-web- [email protected] | [email protected] Type: defect | Status: new Priority: major | Milestone: Component: json-web- | Version: signature | Keywords: Severity: - | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/103> jose <http://tools.ietf.org/jose/> _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
