#77: Section 3.7 "x5c" (X.509 Certificate Chain) Parameter Description changed by [email protected]:
Old description: > A. Why are these base64 encoded and not base64url encoded? This would > appear to break the Mike Jones rule that there be only one way to do > things. I.e. you should not have two base64 encoding algorithms. > > B. What happens if the chain is out of order? > > C. What happens if this is not a complete chain? > > D. Eliminate the word "bare" as it is not useful. > > E. There are additional requirements imposed on the representation of > members in the JWK and the contents of the certificate. For example the > use and alg need to be compatible. > > F. There is a violation of the one way to do things rule here - x5u > produces a PEM encoded item while this is an array of things. Does this > need to be resolved/explained? New description: A. Why are these base64 encoded and not base64url encoded? This would appear to break the Mike Jones rule that there be only one way to do things. I.e. you should not have two base64 encoding algorithms. * WON'T FIX - it is life B. What happens if the chain is out of order? * WON'T FIX - it just doesn't work if the client is not smart. C. What happens if this is not a complete chain? * WON'T FIX - it just doesn't work if the client is not smart. D. Eliminate the word "bare" as it is not useful. * FIXED E. There are additional requirements imposed on the representation of members in the JWK and the contents of the certificate. For example the use and alg need to be compatible. F. There is a violation of the one way to do things rule here - x5u produces a PEM encoded item while this is an array of things. Does this need to be resolved/explained? * WON'T FIX - JSON vs ASN.1 -- -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-jose-json-web- [email protected] | [email protected] Type: defect | Status: new Priority: Editorial | Milestone: Component: json-web- | Version: key | Resolution: Severity: - | Keywords: | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/77#comment:1> jose <http://tools.ietf.org/jose/> _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
