19:32:49 <RRSAgent> RRSAgent has joined #crypto
19:32:49 <RRSAgent> logging to http://www.w3.org/2013/10/14-crypto-irc
19:32:51 <trackbot> RRSAgent, make logs public
19:32:51 <Zakim> Zakim has joined #crypto
19:32:53 <trackbot> Zakim, this will be SEC_WebCryp
19:32:53 <Zakim> ok, trackbot; I see SEC_WebCryp()4:00PM scheduled to start in 28 minutes
19:32:54 <trackbot> Meeting: Web Cryptography Working Group Teleconference
19:32:54 <trackbot> Date: 14 October 2013
19:38:57 <Jyates> Jyates has joined #Crypto
19:43:47 <mete> mete has joined #crypto
19:46:41 <ale> ale has joined #crypto
19:46:43 <sangrae> sangrae has joined #crypto
19:50:22 <Jyates> Jyates has joined #Crypto
19:52:13 <Zakim> SEC_WebCryp()4:00PM has now started
19:52:14 <Zakim> + +90533302aaaa
19:52:19 <mete> mete has joined #crypto
19:52:23 <Zakim> - +90533302aaaa
19:52:25 <Zakim> SEC_WebCryp()4:00PM has ended
19:52:25 <Zakim> Attendees were +90533302aaaa
19:53:10 <Zakim> SEC_WebCryp()4:00PM has now started
19:53:11 <Zakim> + +90533302aaaa
19:57:09 <hhalpin> Zakim, what's the code?
19:57:09 <Zakim> the conference code is 27978 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), hhalpin
19:57:39 <Zakim> +[IPcaller]
19:57:41 <Zakim> -[IPcaller]
19:57:41 <Zakim> +[IPcaller]
19:57:46 <hhalpin> Zakim, [IPcaller] is hhalpin
19:57:47 <Zakim> +hhalpin; got it
19:57:54 <Zakim> +Michael_Hutchinson
19:57:55 <Zakim> +[GVoice]
19:58:18 <bryaneyler> bryaneyler has joined #crypto
19:58:53 <arunranga> arunranga has joined #crypto
19:58:54 <Zakim> +JYates
19:59:12 <Zakim> +[IPcaller]
19:59:47 <MichaelH> MichaelH has joined #crypto
19:59:57 <hhalpin> Zakim, who's on the phone?
19:59:57 <Zakim> On the phone I see mete, hhalpin, Michael_Hutchinson, [GVoice], JYates, [IPcaller]
20:00:05 <hhalpin> Who is GVoice and IPcaller?
20:00:15 <Zakim> +arunranga
20:00:46 <arunranga> Zakim, who is on the phone?
20:00:46 <Zakim> On the phone I see mete, hhalpin, Michael_Hutchinson, [GVoice], JYates, [IPcaller], arunranga
20:00:55 <arunranga> Zakim, mute
20:00:55 <Zakim> I don't understand 'mute', arunranga
20:01:01 <arunranga> Zakim, mute me
20:01:01 <Zakim> arunranga should now be muted
20:01:02 <hhalpin> Zakim, GVoice is bryaneyler
20:01:02 <Zakim> +bryaneyler; got it
20:01:16 <sangrae> this is sangrae calling from Skype
20:01:39 <jimsch> jimsch has joined #crypto
20:02:24 <hhalpin> topic: Web Certficate API and Future of the WG
20:02:33 <hhalpin> mountie, want to introduce?
20:02:58 <hhalpin> http://mountielee.github.io/webcertapi/webcertapi_draft.html
20:03:04 <MichaelH> W3C Editor’s Draft 11 October 2013
20:03:09 <hhalpin> Oct 11trh?
20:03:17 <hhalpin> Which API?
20:03:18 <Zakim> +[IPcaller.a]
20:03:22 <hhalpin> has the link?
20:03:26 <hhalpin> Zakim, pick a scribe?
20:03:26 <Zakim> I don't understand your question, hhalpin.
20:03:35 <jimsch> Zakim, [IPcller] is jimsch
20:03:35 <Zakim> sorry, jimsch, I do not recognize a party named '[IPcller]'
20:03:37 <hhalpin> Zakim, pick a scribe
20:03:37 <Zakim> Not knowing who is chairing or who scribed recently, I propose [IPcaller]
20:03:51 <hhalpin> Zakim, IPcaller is jimsch
20:03:51 <Zakim> +jimsch; got it
20:03:54 <hhalpin> Zakim, IPcaller is jimsch
20:03:54 <Zakim> sorry, hhalpin, I do not recognize a party named 'IPcaller'
20:03:57 <hhalpin> Zakim, pick a scribe
20:03:57 <Zakim> Not knowing who is chairing or who scribed recently, I propose bryaneyler
20:04:02 <jimsch> Zakim, [IPCaller] is jimsch
20:04:02 <Zakim> sorry, jimsch, I do not recognize a party named '[IPCaller]'
20:04:20 <jimsch> Zakim, [IPCaller.a] is jimsch
20:04:20 <Zakim> +jimsch; got it
20:05:01 <nvdbleek> nvdbleek has joined #crypto
20:05:16 <nvdbleek> zakim, code?
20:05:16 <Zakim> the conference code is 27978 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), nvdbleek
20:05:21 <bryaneyler> [missed name]: presenting webcert API; latest version not on web yet
20:06:13 <hhalpin> s/[missed name]/sangrae
20:06:33 <bryaneyler> sangrae: Latest update changes use cases ...
20:07:02 <Zakim> + +1.650.214.aabb
20:07:02 <tantek> tantek has joined #crypto
20:07:11 <bryaneyler> ... previous, focus on certs for Korean banking, but violates same origin policies.  ...
20:07:58 <rsleevi> rsleevi has joined #crypto
20:08:00 <bryaneyler> ... New focus on cert mgmt instead of usage; doesn't violate same origin.  ...
20:08:36 <bryaneyler> ... Can revoke cert when not desired to use.
20:08:52 <jimsch> bryan, can you mute?
20:09:03 <bryaneyler> I believe I'm muted.
20:09:28 <rsleevi> Zakim, mute bryaneyler
20:09:28 <Zakim> bryaneyler should now be muted
20:09:33 <rsleevi> Zakim, who is making noise
20:09:33 <Zakim> I don't understand 'who is making noise', rsleevi
20:09:39 <arunranga> Zakim, who is noisy?
20:09:51 <Zakim> arunranga, listening for 10 seconds I heard sound from the following: hhalpin (74%), jimsch (75%)
20:09:59 <rsleevi> Zakim, mute hhalpin
20:09:59 <Zakim> hhalpin should now be muted
20:10:07 <rsleevi> :)
20:10:08 <arunranga> :-)
20:10:14 <rsleevi> Zakim, unmute bryaneyler
20:10:14 <Zakim> bryaneyler should no longer be muted
20:10:34 <Zakim> +nvdbleek
20:10:49 <arunranga> zakim, who is noisy?
20:11:02 <Zakim> arunranga, listening for 12 seconds I heard sound from the following: jimsch (78%)
20:11:45 <bryaneyler> sangrae:  When user wants to use cert, can issue request to CA; CA returns cert and UA sends notification to CA to use cert.  ...
20:11:55 <nvdbleek> zakim, pointer?
20:11:55 <Zakim> I don't understand your question, nvdbleek.
20:12:17 <trackbot> Sorry, rsleevi, I don't understand 'trackbot, pointer'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.
20:12:44 <nvdbleek> nvdbleek has joined #crypto
20:12:46 <bryaneyler> ... 3.6: First 3 methods to request cert, plus generating and revoking methods.  ...
20:13:54 <bryaneyler> ... Currently working on API specs.  ...
20:14:10 <bryaneyler> ... will be ready for F2F.
20:14:21 <MichaelH> q+
20:14:23 <hhalpin> Zakim, unmute me
20:14:23 <Zakim> hhalpin should no longer be muted
20:14:27 <hhalpin> q?
20:14:30 <jimsch> q+
20:14:31 <hhalpin> ack MichaelH
20:15:01 <bryaneyler> Michael:  What are we standardizing?  Call to web-based CA?  Or generic CA?  Or supposed to standardize all CAs?
20:15:17 <bryaneyler> sangrae: Trying to standardize all CAs.
20:15:34 <bryaneyler> ... mainly focus on RFC 4210
20:15:50 <bryaneyler> ... PKCS#10 req msgs
20:15:52 <Zakim> +[Microsoft]
20:15:53 <israelh> israelh has joined #Crypto
20:16:10 <bryaneyler> ... more about UA being about to request from any CA using those protocols.
20:16:26 <rsleevi> q+
20:16:28 <bryaneyler> Michael: UA communicates with all RFC 4210 CAs?
20:16:29 <hhalpin> Now in W3C space
20:16:29 <hhalpin> http://www.w3.org/2012/webcrypto/WebCertAPI/webcertapi.html
20:16:33 <bryaneyler> sangrae: Yes
20:16:42 <hhalpin> Zakim, unmute jimsch
20:16:42 <Zakim> jimsch.a was not muted, hhalpin
20:16:48 <hhalpin> Zakim, ack jimsch
20:16:48 <Zakim> I see rsleevi on the speaker queue
20:16:52 <hhalpin> jim?
20:17:48 <bryaneyler> Jim: 3 different cert mgmt protocols: CNC, CMP, PKCS10.  Why choose to standardize one?
20:17:52 <hhalpin> q+
20:17:56 <bryaneyler> ... no mention of PKCS10 in doc.
20:18:33 <bryaneyler> sangrae: API will incorporate PKCS10.  In Korea, typically use CMP.
20:19:49 <bryaneyler> ... anyone with knowledge of CNC; can incorporate.  Still basic API types: response and confirm.
20:20:30 <jimsch> rsleevi, Yes I did finally find it
20:20:42 <MichaelH> enum ReqType { 	// RFC 4210 Certificate Management Protocol. 	"cmp", 	// PKCS#10 type Certificate signing request. 	"pkcs10", };
20:21:03 <bryaneyler> Ryan: PKCS10 is referenced in draft.  Need to identify what capabilities are needed that cannot be handled at the moment.
20:21:29 <bryaneyler> ... can implement these protocols fully within JS.
20:21:53 <bryaneyler> ... need to bring down to 1st principles.  Take a look at work products and identify features needed for use case.
20:21:54 <jimsch> +1 to making this in JavaScript for the current period of time
20:22:14 <bryaneyler> ... to make progress, need the problem space.
20:22:49 <nvdbleek> nvdbleek has joined #crypto
20:22:53 <bryaneyler> ... don't understand the root set of problems that cannot be addressed in JS.
20:23:30 <bryaneyler> ... already apps that handle problem.
20:24:32 <bryaneyler> Sangrae: Trying to expand cert request to cert mgmt.
20:24:42 <bryaneyler> ... can handle issuing, updating, revoking.
20:24:45 <hhalpin> Here's one version of the banking use-case: http://www.w3.org/TR/2013/WD-webcrypto-usecases-20130108/#banking
20:24:46 <Jyates> Jyates has joined #Crypto
20:25:04 <bryaneyler> ... PKCS#10 doesn't have mgmt protocol capabilities.
20:25:33 <hhalpin> That's why I referenced the earlier paragraph, as I think sangrae needs to go through
20:25:38 <MichaelH> q+
20:25:44 <hhalpin> and tighten his case, thta text seems to be a decent starting place
20:25:48 <bryaneyler> ... cert mgmt deals with public key pairs; cannot handle the keys in JS because it's insecure.
20:26:26 <Zakim> +karen_oDonoghue
20:26:31 <bryaneyler> Ryan: Only discussing use case; need problem.
20:26:32 <hhalpin> Agree the use-case needs work, but I don't really understand the details of banking use-case
20:26:41 <hhalpin> it seems like they want a certficate management library
20:26:59 <Zakim> -nvdbleek
20:27:01 <bryaneyler> ... how secure should keys be?
20:27:10 <kodonog> kodonog has joined #crypto
20:27:27 <Zakim> +nvdbleek
20:27:29 <bryaneyler> ... if wrote an app using current API, what are points that cannot be used to write it?
20:27:50 <bryaneyler> ... if no problems, need better documentation.  If problems exist, need to understand where.
20:28:18 <bryaneyler> Sangrae: Will provide problem statement.
20:29:12 <bryaneyler> Harry: Need more detail in problem and why cannot use current API.
20:29:37 <bryaneyler> ... is Sangrae going to make it to F2F?
20:29:41 <bryaneyler> Sangrae: Yes
20:29:45 <hhalpin> ack MichaelH
20:29:49 <hhalpin> ack hhalpin
20:30:04 <rsleevi> did we lose Michael?
20:30:38 <arunranga> Zakim, mute hhalpin
20:30:38 <Zakim> hhalpin should now be muted
20:30:45 <bryaneyler> Michael: Why is UA involved in process?  What is it adding to the application?
20:31:06 <bryaneyler> Sangrae: In previous Korean banking use cases, cert is used in web apps.
20:31:41 <bryaneyler> ... if cert mgmt is in UA, then don't need extra plugins to handle cert.
20:31:51 <bryaneyler> ... currently causing security problem in Korea.
20:31:56 <arunranga> ACTION: Arun to bug-fix use cases document with removed banking use case.
20:31:56 <trackbot> Created ACTION-116 - Bug-fix use cases document with removed banking use case. [on Arun Ranganathan - due 2013-10-21].
20:32:00 <bryaneyler> ... main reason for standardizing.
20:32:09 <hhalpin> q?
20:32:22 <jimsch> It is not clear to me if the problem is how to deal with certificates, or if the problem is how to deal with single origin
20:32:27 <Jyates> Jyates has joined #Crypto
20:32:35 <bryaneyler> Harry: Need to revisit in F2F.
20:32:45 <bryaneyler> ... believe trying to fix same origin problem.
20:33:09 <bryaneyler> ... want to keep working group running beyond current charter?
20:33:28 <bryaneyler> ... some groups that have ending point, some that continue to put out new versions.
20:33:56 <bryaneyler> ... Would people want to discuss the future?
20:35:01 <israelh> q+
20:35:06 <bryaneyler> Harry: How do we close issues like set of algorithms?
20:35:06 <hhalpin> ack israelh
20:35:08 <rsleevi> I'd like to see us not take on any *new* items until we get to actual shipping and site experience. I think it's unreasonable to suggest "This can't be done" until people have tried
20:35:23 <hhalpin> well, MS has started shipping :)
20:35:32 <bryaneyler> Israel: Instead of going indefinitely, set achievements for different versions.
20:35:37 <hhalpin> but agreed, however, we need to figure out how to close some open issues
20:35:46 <hhalpin> and either we put them in a "roadmap" document
20:35:48 <hhalpin> and close them
20:35:52 <bryaneyler> ... important to address certificates since people will be asking about them.
20:35:57 <hhalpin> or we say "we're likely to go on with a new charter"
20:36:12 <rsleevi> q+
20:36:24 <hhalpin> ack rsleevi
20:36:25 <bryaneyler> Harry?: Can close this out in F2F.
20:36:50 <bryaneyler> Ryan: Charter extremely broad.  Like to close up, then can look at secondary deliverables.
20:37:06 <bryaneyler> ... Should focus on immediate deliverables and have threads for side-issues.
20:37:20 <bryaneyler> ... instead of indefinite group, use charter to prioritize issues
20:37:24 <ale> ale has joined #crypto
20:37:42 <bryaneyler> ... lots missing from problem statement, but prioritize broad and narrow problems.
20:38:14 <bryaneyler> Harry: Going back to closing out issues on current API, what needs to be closed before last call?
20:38:26 <bryaneyler> ... do you have time to close them out?  Any discussion on specific issues?
20:39:10 <bryaneyler> Ryan: Want to go into F2F with issues closed.  Some issues don't fit API.
20:39:31 <tantek> tantek has joined #crypto
20:39:39 <bryaneyler> ... some issues: want more algorithms, need registry point for some algorithms
20:40:00 <bryaneyler> Harry: Nice to close out Dan's issues before F2F.
20:40:05 <hhalpin> oct 28th?
20:40:06 <bryaneyler> ... on call of 28th.
20:40:15 <hhalpin> That call to close out all of Dan's 28th.
20:40:33 <bryaneyler> Ryan: All can be closed.
20:40:40 <bryaneyler> ... just need to add some notes
20:40:51 <jimsch> rsleevi; +1 from my memory from the call that most of them could be closed out
20:40:55 <bryaneyler> ... already supported or addressed, just need rewording.
20:41:26 <bryaneyler> Harry: If somebody doesn't understand, good indicator that web devs won't understand as well.
20:41:47 <hhalpin> Lot of it was informative notes
20:41:50 <bryaneyler> Ryan: Everything is questioning choice of algorithms or wording; no action
20:42:02 <bryaneyler> ... should data and key be separate?
20:42:14 <bryaneyler> ... for something like encrypt, does not make appropriate API.
20:42:29 <bryaneyler> ... from API design point, proposal is incorrect; should close
20:42:43 <bryaneyler> ... that's the only issue that would require lots of change.
20:43:01 <bryaneyler> ... others: ECC: additional curves (could add additional curves)
20:43:13 <bryaneyler> ... no guarantees of entropy
20:43:34 <bryaneyler> ... bigger problems than WebCrypto
20:43:52 <bryaneyler> ... Overall, issues can be closed out, just need communication to ensure they're being addressed.
20:44:08 <bryaneyler> Harry: Respond to original email?
20:44:17 <bryaneyler> Ryan: Will do.
20:44:25 <rsleevi> ACTION: rsleevi to respond to Dr. Boneh's issues email
20:44:26 <trackbot> Created ACTION-117 - Respond to dr. boneh's issues email [on Ryan Sleevi - due 2013-10-21].
20:44:50 <bryaneyler> Harry: What issues should be addressed in F2F?  Need a draft agenda.
20:45:32 <bryaneyler> Ryan: Put together finalized doc.  Should skip in favour of putting together new draft before F2F to give enough time to review.
20:45:49 <bryaneyler> ... people should have time to review before F2F
20:45:55 <hhalpin> I think the issues that need to be added are the draft solution re key wrapping
20:46:00 <bryaneyler> ... need to get draft in final review
20:46:15 <bryaneyler> ... during implementation on Chrome side, issues brought up
20:46:23 <bryaneyler> ... need to understand Microsoft implementation
20:46:32 <bryaneyler> ... any broad or concerning text?
20:46:37 <hhalpin> Anyone from Mozilla on phone?
20:46:43 <bryaneyler> ... call or review?  Prefer review.
20:46:54 <bryaneyler> Harry: Purpose of call to remind to review.
20:47:05 <arunranga> Zakim, unmute me
20:47:05 <Zakim> arunranga should no longer be muted
20:47:06 <bryaneyler> ... need to also request review from Mozilla
20:47:20 <arunranga> q+
20:47:22 <bryaneyler> ... anybody from Mozilla handling API?
20:47:28 <hhalpin> ack arunranga
20:47:29 <rsleevi> we can hear you
20:47:40 <hhalpin> ddahl has left Mozilla
20:47:45 <bryaneyler> Arun: Currently no implemention since David left.
20:47:54 <bryaneyler> ... won't be able to attend F2F
20:48:04 <bryaneyler> ... can still review and interact with implementers
20:48:10 <israelh> q+
20:48:16 <hhalpin> ack israelh
20:48:35 <bryaneyler> Israel: Trying to figure out how promises maps to long-term strategy.
20:48:41 <bryaneyler> ... when can implement it
20:48:59 <bryaneyler> ... mapping to current spec
20:49:29 <bryaneyler> Harry: Main thing to do: implementation experience section to walk through common problems.
20:49:36 <bryaneyler> ... like to get new version before F2F
20:49:53 <bryaneyler> ... have people from W3C to do reviews after last call
20:50:03 <bryaneyler> ... Graham Steel's group will be available
20:50:09 <MichaelH> What % of spec has been implemented so far?
20:50:18 <bryaneyler> ... any major open issues?
20:50:30 <bryaneyler> ... Promises is outside of WebCrypto scope.
20:50:43 <bryaneyler> Arun: No objection, just timeframe.
20:50:49 <hhalpin> s/Arun/Israelh
20:50:59 <bryaneyler> ... when can bake it into platform
20:51:21 <bryaneyler> ... need feedback on overall implementation before sending to group
20:51:46 <bryaneyler> Harry: Anything else to cover in F2F?
20:52:06 <bryaneyler> Ryan: Have a number of members representing non-UA.
20:52:57 <bryaneyler> ... during review, instead of implementation concerns, like to see members representing smart cards, etc. putting together problem statements
20:53:14 <bryaneyler> ... so we can merge interests to look for next steps.
20:53:39 <hhalpin> 2. Session on use-cases from non-implementers
20:53:43 <bryaneyler> ... any common themes in problems
20:53:46 <hhalpin> ideally with problem statements/docs emailed out beforehand
20:54:16 <bryaneyler> Israel?: Great example is work that Netflix has done
20:54:36 <bryaneyler> ... Netlfix has real-world experience using API, so would be interesting to share that info
20:54:45 <rsleevi> +1 to Israel's comments
20:54:50 <hhalpin> q?
20:54:52 <MichaelH> Is Mark Watson going to F2F?
20:55:11 <bryaneyler> Harry: Will check on anybody from Netflix going.
20:55:28 <hhalpin> We're meeting for two days :)
20:55:31 <bryaneyler> ... 1st day: implementation concerns.  2nd day: problems missing solutions currently?
20:55:50 <MichaelH> How about Wednesday?
20:55:51 <bryaneyler> Ryan: Should interleave the issues to allow more discussion.
20:55:57 <arunranga> hhalpin, if possible, a dial-in for some of the sessions would be great if feasible.
20:55:59 <hhalpin> Wednesday will be quite busy with AC
20:56:02 <bryaneyler> ... mixing would be productive and refreshing.
20:56:27 <bryaneyler> Harry: Challenge is to get use cases emailed out ahead of time to form agenda.
20:56:39 <bryaneyler> ... Will put a call out for putting forward the use cases.
20:57:15 <bryaneyler> Israel: Possible to have Netflix do a demo at EOD 1
20:57:16 <hhalpin> Netflix demo on day 1
20:57:26 <bryaneyler> ... for good example of how to use
20:57:54 <bryaneyler> Harry: Will send call out
20:58:10 <bryaneyler> ... Time to close the call?
20:58:12 <MichaelH> q+
20:58:32 <bryaneyler> Michael: Hoping somebody else could contribute to key discovery implementation
20:58:34 <hhalpin> ACTION: hhalpin to send out call for use-cases for Crypto API
20:58:35 <trackbot> Created ACTION-118 - Send out call for use-cases for crypto api [on Harry Halpin - due 2013-10-21].
20:58:36 <bryaneyler> ... over email is fine
20:59:06 <bryaneyler> [unknown]: Anybody from Brazil involved in key management?
20:59:19 <arunranga> s/[unknown]/IsraelH
20:59:51 <bryaneyler> Harry: W3C office in Brazil, but not sure what's going on
21:00:12 <bryaneyler> Israel: Will do more research to find specific person
21:00:22 <bryaneyler> Harry: Can send the email, just need to know to whom.
21:00:33 <Zakim> - +1.650.214.aabb
21:00:34 <Zakim> -nvdbleek
21:00:34 <Zakim> -karen_oDonoghue
21:00:35 <Zakim> -JYates
21:00:36 <Zakim> -jimsch.a
21:00:40 <Zakim> -sangrae
21:00:41 <Zakim> -mete
21:00:42 <Zakim> -bryaneyler
21:00:51 <Zakim> -[Microsoft]
21:01:04 <Zakim> -hhalpin
21:01:12 <hhalpin> Zakim, draft minutes
21:01:12 <Zakim> I don't understand 'draft minutes', hhalpin
21:01:17 <hhalpin> trackbot, end meeting
21:01:17 <trackbot> Zakim, list attendees
21:01:17 <Zakim> As of this point the attendees have been +90533302aaaa, mete, hhalpin, Michael_Hutchinson, JYates, arunranga, bryaneyler, +1.650.214.aabb, nvdbleek, sangrae, [Microsoft],
21:01:20 <Zakim> ... karen_oDonoghue
21:01:25 <trackbot> RRSAgent, please draft minutes
21:01:25 <RRSAgent> I have made the request to generate http://www.w3.org/2013/10/14-crypto-minutes.html trackbot
21:01:26 <trackbot> RRSAgent, bye
21:01:26 <RRSAgent> I see 3 open action items saved in http://www.w3.org/2013/10/14-crypto-actions.rdf :
21:01:26 <RRSAgent> ACTION: Arun to bug-fix use cases document with removed banking use case. [1]
21:01:26 <RRSAgent>   recorded in http://www.w3.org/2013/10/14-crypto-irc#T20-31-56
21:01:26 <RRSAgent> ACTION: rsleevi to respond to Dr. Boneh's issues email [2]
21:01:26 <RRSAgent>   recorded in http://www.w3.org/2013/10/14-crypto-irc#T20-44-25
21:01:26 <RRSAgent> ACTION: hhalpin to send out call for use-cases for Crypto API [3]
21:01:26 <RRSAgent>   recorded in http://www.w3.org/2013/10/14-crypto-irc#T20-58-34