19:58:08 <RRSAgent> RRSAgent has joined #crypto
19:58:08 <RRSAgent> logging to http://www.w3.org/2016/03/21-crypto-irc
19:58:10 <trackbot> RRSAgent, make logs public
19:58:12 <trackbot> Zakim, this will be CRYPT
19:58:12 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
19:58:13 <trackbot> Meeting: Web Cryptography Working Group Teleconference
19:58:13 <trackbot> Date: 21 March 2016
19:58:22 <wseltzer> zakim, code?
19:58:22 <Zakim> I have been told this is +1-617-324-0000 Access Code: 643 244 026 WebEx
20:01:07 <jyates> Two of us are on the phone
20:02:43 <hhalpin> Just to note, the W3C AC meeting that both Virginie and Wendy are currently at is ongoing, and so I suspect they may be late. wseltzer?
20:03:24 <wseltzer> the AC meeting is about to hit a break, but Virginie is on a panel right after the break
20:03:37 <wseltzer> I believe she was not planning to join
20:03:47 <hhalpin> OK, I am happy to chair as stated on the phone.
20:05:30 <RobTrace> RobTrace has joined #crypto
20:05:37 <wseltzer> hhalpin: review quickly with implementors, implementation schedule
20:06:08 <wseltzer> present+ hhalpin
20:06:11 <wseltzer> present+ wseltzer
20:06:14 <wseltzer> present+ RobTrace
20:06:15 <jimsc> Jim Schaad on the phone
20:06:20 <hhalpin> present+ RobTrace
20:06:22 <wseltzer> present+ jimsc
20:06:30 <wseltzer> present+ jyates
20:06:35 <wseltzer> present+ ttaubert
20:06:41 <wseltzer> regrets+ Virginie
20:06:46 <wseltzer> regrets+ markw
20:07:00 <hhalpin> topic: Updated schedule
20:07:18 <wseltzer> hhalpin: WebCrypto charter was renewed for a 6mo extension
20:07:58 <wseltzer> ... check in on scheduling
20:08:16 <wseltzer> ... To get to Recommendation, we need to move from CR to PR, Rec
20:08:27 <wseltzer> ... show that we have two interoperable implementations of each feature
20:08:40 <wseltzer> ... So we need to gather implementation status over the next 2 weeks
20:08:56 <wseltzer> ... 2-3 weeks of work on tests
20:09:21 <wseltzer> ... ~ May, review status of test suite and test results
20:09:36 <wseltzer> ... end of May, determine whehter to keep/cancel each feature
20:09:46 <wseltzer> ... June/July, CfC to Proposed Rec
20:10:00 <wseltzer> -> https://lists.w3.org/Archives/Public/public-webcrypto/2016Mar/0048.html Virginie's email re schedul
20:10:05 <wseltzer> s/schedul/schedule/
20:10:50 <wseltzer> RobTrace: When we talk about features and cutting features
20:11:04 <wseltzer> ... that doesn't account for an implementor who wants features but doesn't have current resources for them
20:11:07 <wseltzer> q+
20:11:30 <wseltzer> hhalpin: that's a scheduel proposed by Virginie
20:11:31 <wseltzer> q+
20:11:48 <wseltzer> RobTrace: Do we have to change the schedule, or if all algorithms are listed as optional,
20:12:09 <wseltzer> ... with algorithms that can be implement, can we finalize without having 2 implementations of each
20:12:12 <wseltzer> q+
20:12:23 <wseltzer> hhalpin: there are different kinds of features
20:13:01 <wseltzer> q+
20:13:04 <wseltzer> q+
20:13:06 <wseltzer> q+
20:15:57 <wseltzer> wseltzer: we need to be able to move forward; we could do that by showing progress, by doing extensions, or by cutting
20:16:11 <wseltzer> RobTrace: lookng at media, codecs, we had some options, let the market decide
20:16:37 <wseltzer> ... we had some items that we didn't implement at first, then when the market showed interes
20:17:26 <hhalpin> q+
20:17:50 <wseltzer> q-
20:18:01 <wseltzer> s/interes/interest, implemented later/
20:18:33 <wseltzer> wseltzer: are you asking for extension points, where we finalize the core, and then extend?
20:18:36 <wseltzer> hhalpin: @@
20:19:02 <wseltzer> RobTrace: RSA-PSS is the example we'd ask for
20:19:16 <wseltzer> hhalpin: that will remain in the final spec, Firefox implemented
20:19:56 <wseltzer> ... the resolution we had to stabilize the specwas to put removed algorithms into a "proposed" status, then move them to the spec when implemented
20:20:16 <hhalpin> RSA-PSS will be kept
20:20:35 <hhalpin> The implementation report needs to be updated to take into account Firefox's latest work
20:21:05 <hhalpin> Microsoft will not change, but wants to keep RSA-PSS
20:21:07 <wseltzer> RobTrace: MS implementation won't change in next 6mo, but we have desire to implement
20:21:20 <hhalpin> I believe Chrome wants to keep RSA-PSS
20:21:29 <wseltzer> ... we want to complete implementation, support; just can't at the moment
20:21:36 <ale> ale has joined #crypto
20:22:03 <wseltzer> RobTrace: Are we making everything mandatory?
20:22:09 <wseltzer> hhalpin: No. nothing is mandatory
20:22:21 <ttaubert> RSA-PSS is currently available in Firefox Beta
20:22:39 <wseltzer> ... but we could note in test suite, "browser profile" what algorithms are implemented everywhere
20:22:58 <wseltzer> ... not cutting things out for the sake of process, but recognizing what has actual interop
20:23:09 <ale> ale has joined #crypto
20:23:42 <wseltzer> ... others that are specd but not implemnted stick around for potential later use.
20:24:11 <wseltzer> ... So everyone -> "browser profile"
20:24:18 <wseltzer> ... 2 implementations stay in the spec
20:24:32 <wseltzer> ... one or no implementations, go into "proposed" for later Rec
20:24:57 <hhalpin> AES-CMAC, AES-CFB, CONCAT, DH are the ones at risk to be moving in a different section.
20:25:16 <wseltzer> hhalpin: other issues, key format, service workers
20:25:24 <jimsc> CONCAT has already been killed from the spec
20:25:40 <hhalpin> Sorry missed that jimsc
20:25:45 <wseltzer> ttaubert: I'm working on getting webcrypto supported in workers
20:25:53 <wseltzer> ... going to turn to service workers afgter
20:25:58 <wseltzer> s/afgter/after/
20:26:11 <wseltzer> RobTrace: I don't know that we've fully internalized SW crypto
20:26:17 <wseltzer> ... no official roadmap
20:26:29 <wseltzer> hhalpin: I think it's in chrome
20:26:40 <wseltzer> ... so we can keep that part of the spec
20:26:48 <wseltzer> ... Then key format issues remain
20:27:11 <wseltzer> ... everyone agrees JWKs work fine, but cross-browser and in-browser issues with other formats
20:27:21 <wseltzer> ... there's desire from users to have PKCS
20:27:43 <wseltzer> jimsc: 2 ways to deal with asn1 imports
20:27:52 <wseltzer> ... no longer tie algorithms hard to keys
20:28:03 <wseltzer> ... pretty simple in current spec
20:28:17 <wseltzer> ... versus getting people to implement what's in current spec is hard, not doable in time-frame
20:28:50 <wseltzer> RobTrace: Not something we've had deep discussions on
20:28:52 <wseltzer> ttaubert: same
20:29:07 <wseltzer> ... can someone summarize on ml the problems iwth key imports
20:29:17 <wseltzer> jimsc: I'll send something on the ML
20:29:51 <wseltzer> hhalpin: concenrn that dealing with asn1 lots of work
20:29:57 <wseltzer> ... markw willing to do the work
20:30:56 <wseltzer> hhalpin: testing training, 11 am Friday re TTWF
20:31:02 <jimsc> This is still a clear time for me
20:31:08 <Karen> Karen has joined #crypto
20:31:20 <wseltzer> RobTrace: I could track that
20:31:36 <wseltzer> ttaubert: I couldn't participate Friday night
20:31:43 <wseltzer> ... but would track ML
20:32:04 <wseltzer> [calendar syncing]
20:33:03 <wseltzer> hhalpin: one training, with Mike Smith, then work moving forward
20:33:39 <wseltzer> ttaubert: this Friday doesn't work for me
20:33:39 <jimsc> Harry, we should try and record it since it is on web crypto
20:33:45 <jimsc> s/web crypt/webex/
20:34:15 <wseltzer> hhalpin: I'll share the info
20:34:29 <wseltzer> ... any other questions?
20:34:42 <jimsc> q+
20:34:47 <wseltzer> rrsagent, draft minutes
20:34:47 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/21-crypto-minutes.html wseltzer
20:34:50 <wseltzer> ack jimsc
20:34:51 <hhalpin> ack hhalpin
20:34:54 <hhalpin> http://testthewebforward.org/
20:35:03 <hhalpin> We'll go through this agenda
20:35:21 <wseltzer> jimsc: note, IETF meeting in 2 weeks, I can't attend then
20:35:32 <wseltzer> hhalpin: I'll check with Virginie
20:36:04 <wseltzer> ... Rob and Tim, how much time do you want for review of Jim's proposal
20:36:24 <wseltzer> ttaubert: propose 3 weeks
20:37:07 <wseltzer> hhalpin: I'll follow up with Virginie
20:37:15 <wseltzer> [adjourned]
20:37:20 <wseltzer> rrsagent, make minutes
20:37:20 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/21-crypto-minutes.html wseltzer
20:37:23 <hhalpin> trackbot, end meeting
20:37:23 <trackbot> Zakim, list attendees
20:37:23 <Zakim> As of this point the attendees have been wseltzer, virginie, hhalpin, jyates, Charles_Engelke, jimsch, timeless, kodonog, markw, jmann, ttaubert, RobTrace
20:37:31 <trackbot> RRSAgent, please draft minutes
20:37:31 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/21-crypto-minutes.html trackbot
20:37:32 <trackbot> RRSAgent, bye
20:37:32 <RRSAgent> I see no action items
20:43:41 <RRSAgent> RRSAgent has joined #crypto
20:43:41 <RRSAgent> logging to http://www.w3.org/2016/03/21-crypto-irc
20:43:42 <wseltzer> rrsagent, make logs public
20:43:52 <wseltzer> rrsagent, make minutes
20:43:52 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/21-crypto-minutes.html wseltzer
20:44:09 <wseltzer> rrsagent, bye
20:44:09 <RRSAgent> I see no action items
20:45:02 <RRSAgent> RRSAgent has joined #crypto
20:45:02 <RRSAgent> logging to http://www.w3.org/2016/03/21-crypto-irc
20:45:24 <wseltzer> present: hhalpin, wseltzer, jyates, jimsc, ttaubert, RobTrace
20:45:30 <wseltzer> rrsagent, make minutes
20:45:30 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/21-crypto-minutes.html wseltzer