- From: Richard Barnes <rbarnes@bbn.com>
- Date: Mon, 4 Mar 2013 14:55:09 -0500
- To: Mark Watson <watsonm@netflix.com>
- Cc: GALINDO Virginie <Virginie.GALINDO@gemalto.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>, Wendy Seltzer <wseltzer@w3.org>, Harry Halpin <hhalpin@w3.org>
Please note that the JOSE WG will be discussing key wrapping at their meeting next week: <http://tools.ietf.org/wg/jose/agenda?item=agenda-86-jose.html> You are all welcome to tune in and contribute to the discussion. There will be remote participation via audio streaming and jabber, if you're not going to be at the IETF meeting. The hope is that the result of this discussion will be consensus around a coherent approach to JOSE keys -- public/private/symmetric, wrapped/unwrapped. On Mar 4, 2013, at 2:40 PM, Mark Watson <watsonm@netflix.com> wrote: > Virginie, all, > > I have updated the Key Wrap/Unwrap proposal here: http://www.w3.org/2012/webcrypto/wiki/KeyWrap_Proposal > > It now follows Vijay's suggestion of focussing on JWE-protected JWK objects according to http://tools.ietf.org/html/draft-miller-jose-jwe-protected-jwk > > Mark > > On Mar 4, 2013, at 2:36 AM, GALINDO Virginie wrote: > >> Dear all, >> >> Here is a proposed agenda for our next call monday @20 UTC, feel free to suggest additional items, on the basis of the recent discussions over the mailing list. >> >> Bridge and irc are the usual ones >> +1.617.761.6200, 27978# (CRYPT) >> IRC irc.w3.org:6665 #crypto >> >> Regards, >> Virginie >> Gemalto >> >> ---------agenda proposal for 04th of March ------ >> >> 1- Welcome - 5 >> - attendees list >> - pick a scribe - (scribe guide https://www.w3.org/2008/xmlsec/Group/Scribe-Instructions.html or http://www.w3.org/2008/04/scribe.html ) >> - agenda approval >> - minutes approval from previous meeting http://www.w3.org/2013/02/04-crypto-minutes.html >> >> 2- Web Crypto API 20 >> - W3C office discussion about IANA registry : call for action >> - We will be discussing proposal from editors to close the following issues >> PROPOSAL: Close ISSUE-37 - Method Naming >> PROPOSAL: Close ISSUE-33 - Clarify text in section 5.1 with respect to how key tainting is handled with multi-origin scenario >> PROPOSAL: Close ISSUE-32 - API should mention the use of secure elements in the context of key security >> PROPOSAL: Close ISSUE-31 - Problems with keys attribute of the Crypto interface >> PROPOSAL: Close ISSUE-29 - Handling of block encryption modes and padding >> PROPOSAL: Close ISSUE-17 - Define the scope and API for custom key attributes >> PROPOSAL: Close ISSUE-9 what will be the mean to integrate in the API the fact that key usage may need user consent ? >> θ Editors please add any other proposal you think are mature enough to be voted by the WG. >> >> 3- High Level API 10 >> Discussion on the technical merits of the high level API >> >> 4- Secondary feature discussion 5 >> Call for comment and contribution to make progressing the certificate management secondary features >> >> 5- Group Life 5 >> - Charter extension >> - Our next F2F exact location : eBay/PayPal headquarters, 2211 North First Street, San Jose, CA, USA >> Book tickets and suggest topics you would like to discuss at that time. >> >> 6- AOB 1 >> News from 3GPP http://lists.w3.org/Archives/Public/public-webcrypto/2012Nov/0096.html >> >> >
Received on Monday, 4 March 2013 19:55:42 UTC