Re: [jose] #16: URI identifying a specific key in a JWK set

+1

Would be good to have a MUST here to clarify.

On Mon, Mar 25, 2013 at 8:31 AM, Brian Campbell
<bcampbell@pingidentity.com>wrote:

> I'd always just assumed that, short of some other means of figuring it
> out, a kid header would accompany a jku to identify the specific key in the
> set.
>
>
> On Sun, Mar 24, 2013 at 6:40 PM, jose issue tracker <
> trac+jose@trac.tools.ietf.org> wrote:
>
>> #16: URI identifying a specific key in a JWK set
>>
>>  When a public key is required to process a JOSE message, providing a URI
>>  for the key is a useful alternative to providing the actual key or a
>>  certificate. The URI needs to identify the specific individual public key
>>  required for the specific JOSE message. A URI that merely identifies a
>> set
>>  of keys (one of which is the correct one) is not sufficient.
>>
>>  Given that a "jku" field holds a URI pointing to a set of keys, we need
>> to
>>  define how to use the fragment part of those URIs to identify a specific
>>  key in the set.
>>
>>  Using the "kid" (key id) in the fragment would be a sensible choice.
>>
>> --
>>
>> -------------------------+-------------------------------------------------
>>  Reporter:               |      Owner:  draft-ietf-jose-json-web-
>>   james@manger.com.au    |  key@tools.ietf.org
>>      Type:  defect       |     Status:  new
>>  Priority:  major        |  Milestone:
>> Component:  json-web-    |    Version:
>>   key                    |   Keywords:
>>  Severity:  -            |
>>
>> -------------------------+-------------------------------------------------
>>
>> Ticket URL: <https://tools.ietf.org/wg/jose/trac/ticket/16>
>> jose <http://tools.ietf.org/jose/>
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>