I agree that ISSUE-15 has been addressed in -11. On a related note: As I recall, there was consensus at the interim to add something in the "jku" section to the following effect:
NEW: """ If a "jku" URI refers to a JWK Set containing more than one key, then the JWE MUST also contain a "kid" attribute identifying the key to be used for this object. In general, a JWE containing a "jku" URI SHOULD also contain a "kid" for this purpose. """ I don't see anything like that in -11. On Tue, Jun 25, 2013 at 8:31 PM, Mike Jones <[email protected]>wrote: > Please add these issues to the agenda: #5, #14, and #15. Suggested > agenda text follows.**** > > ** ** > > Issue #5 - Unclear instructions for key management**** > > Discuss closing this issue as “fixed”, as text addressing > it was added in the -09 drafts**** > > ** ** > > Issue #14 - Support longer wrapped keys than OAEP allows**** > > Discuss closing this issue as “won’t fix”, as it will not > occur in practice**** > > ** ** > > Issue #15 - At least one key indicator should be mandatory**** > > Discuss closing this issue as “fixed”, as text addressing > it was added in -11, as proposed by the WG in Denver**** > > ** ** > > Thanks,*** > * > > -- Mike*** > * > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On Behalf > Of *Jim Schaad > *Sent:* Tuesday, June 25, 2013 9:51 AM > *To:* [email protected] > *Subject:* [jose] Teleconference July 1 Agenda**** > > ** ** > > Agenda has been posted > http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/agenda-interim-2013-jose-3 > **** > > ** ** > > _______________________________________________ > jose mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/jose > >
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
