Re: Suggestions on high-level API - perhaps a meeting next week?

On Oct 9, 2012, at 5:21 PM, David Dahl wrote:

> ----- Original Message -----
>> From: "Ryan Sleevi" <sleevi@google.com>
>> To: "David Dahl" <ddahl@mozilla.com>
>> Cc: "Jim Burrows" <brons@eldacur.com>, "Harry Halpin" <hhalpin@w3.org>, "Emily Stark" <estark@mit.edu>, "Wan-Teh
>> Chang" <wtc@google.com>, public-webcrypto@w3.org, "GALINDO Virginie" <Virginie.GALINDO@gemalto.com>, "Mountie Lee"
>> <mountie.lee@mw2.or.kr>
>> Sent: Tuesday, October 9, 2012 3:54:25 PM
>> Subject: Re: Suggestions on high-level API - perhaps a meeting next week?
>> 
>> On Tue, Oct 9, 2012 at 8:33 AM, David Dahl <ddahl@mozilla.com> wrote:
>>> Jim:
>>> I have been tinkering with a high-level design over here:
>>> https://github.com/daviddahl/web-crypto-ideas/blob/master/high-level-api.js
>>> 
>>> The simplest possible API is what I am going for: encryptAndSign(),
>>> verifyAndDecrypt() (as well as sign(), verify(), hash() and
>>> mac()), see:
>>> https://github.com/daviddahl/web-crypto-ideas/blob/master/high-level-api.idl
>> 
>> I thought previous discussions established the preferred form as "an
>> API for JOSE"
>> 
>> (Note that I have no especially strong feelings about this, other
>> than
>> I think it's the right choice because JOSE has made the algorithm
>> trade-offs already)
> 
> Indeed, we discussed that after I drafted these ideas. I am a fan of JOSE for this.

Just to note: JOSE has *not* made algorithm choices.  There was consensus at the last IETF meeting to make JOSE algorithm-agnostic, for the same reasons that we discussed at the WebCrypto F2F in Mountain View.

--Richard

Received on Tuesday, 9 October 2012 22:16:22 UTC