#71: Section 3.2 - "use" (Key Use) Parameter Changes (by [email protected]):
* status: new => closed * resolution: => fixed Old description: > A. What are the requirements for defining a new use string. Is there a > registry for this, are they supposed to be collision resistant? > > * FIXED: A registry now exists for this field. > > B. Use of member is OPTIONAL does not convey sufficient information. For > whom is it optional? > > C. What happens if use is absent is not covered in the document. > > D. John Bradley made a big deal at the Berlin meeting about the fact that > this needs to be a single value rather than a multi-value field. The > reasoning behind this was that allowing for multiple values was an evil > thing. This would imply that this is not an optional field but is, at a > minimum a SHOULD field with heavy language about when one would not > specify a value. all uses (absent) is worse than some usages (multi) is > worse than one usage (single). New description: A. What are the requirements for defining a new use string. Is there a registry for this, are they supposed to be collision resistant? * FIXED: A registry now exists for this field. B. Use of member is OPTIONAL does not convey sufficient information. For whom is it optional? * FIXED - no longer optional field C. What happens if use is absent is not covered in the document. * WON'T FIX - probably implicit that all uses are allowed D. John Bradley made a big deal at the Berlin meeting about the fact that this needs to be a single value rather than a multi-value field. The reasoning behind this was that allowing for multiple values was an evil thing. This would imply that this is not an optional field but is, at a minimum a SHOULD field with heavy language about when one would not specify a value. all uses (absent) is worse than some usages (multi) is worse than one usage (single). * FIXED - it is not a should so it meets minimum requirements -- -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-jose-json-web- [email protected] | [email protected] Type: defect | Status: closed Priority: major | Milestone: Component: json-web- | Version: key | Resolution: fixed Severity: - | Keywords: | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/71#comment:2> jose <http://tools.ietf.org/jose/> _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
