Re: Key IDs take 2, plus public key as an (JWK) array buffer

----- Original Message -----
> From: "Vijay Bharadwaj" <Vijay.Bharadwaj@microsoft.com>
> To: "David Dahl" <ddahl@mozilla.com>, "Ryan Sleevi" <sleevi@google.com>
> Cc: public-webcrypto@w3.org
> Sent: Saturday, June 30, 2012 2:08:31 AM
> Subject: RE: Key IDs take 2, plus public key as an (JWK) array buffer

> You make a good point about the need for some metadata that can be
> used as a "friendly name" for the key in various UI contexts.
> However, I wonder if we should be depending on the app to display
> such metadata correctly, especially given the discussion about an
> app accessing keys created outside the app. Perhaps it would be
> better to have a model where such metadata can be written at key
> creation time and later used by apps for key selection, but is
> displayed by the user agent?

Agreed. I was thinking that it would be helpful to keep the domain info, but, in many cases like this we should defer to the application. 

Regards,

David

Received on Saturday, 30 June 2012 13:38:30 UTC