19:58:50 <RRSAgent> RRSAgent has joined #crypto
19:58:50 <RRSAgent> logging to http://www.w3.org/2013/08/05-crypto-irc
19:58:53 <kodonog> kodonog has joined #crypto
19:58:59 <nvdbleek> zakim, code?
19:59:00 <Zakim> sorry, nvdbleek, I don't know what conference this is
19:59:07 <rsleevi> Zakim, this is crypto
19:59:07 <Zakim> sorry, rsleevi, I do not see a conference named 'crypto' in progress or scheduled at this time
19:59:42 <nvdbleek> trackbot, start meeting
19:59:45 <trackbot> RRSAgent, make logs public
19:59:47 <trackbot> Zakim, this will be SEC_WebCryp
19:59:47 <Zakim> ok, trackbot, I see SEC_WebCryp()4:00PM already started
19:59:48 <trackbot> Meeting: Web Cryptography Working Group Teleconference
19:59:48 <trackbot> Date: 05 August 2013
20:00:00 <karen> karen has joined #crypto
20:00:02 <hhalpin> hhalpin has joined #crypto
20:00:06 <nvdbleek> zakim, code
20:00:07 <Zakim> I don't understand 'code', nvdbleek
20:00:11 <nvdbleek> zakim, code?
20:00:11 <Zakim> the conference code is 27978 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), nvdbleek
20:00:14 <hhalpin> trackbot, start meeting
20:00:17 <trackbot> RRSAgent, make logs public
20:00:19 <trackbot> Zakim, this will be SEC_WebCryp
20:00:19 <Zakim> ok, trackbot, I see SEC_WebCryp()4:00PM already started
20:00:20 <trackbot> Meeting: Web Cryptography Working Group Teleconference
20:00:20 <trackbot> Date: 05 August 2013
20:01:00 <Zakim> +[IPcaller]
20:01:07 <hhalpin> Zakim, [IPcaller] is hhalpin
20:01:07 <Zakim> +hhalpin; got it
20:01:35 <hhalpin> topic: start meeting
20:01:38 <hhalpin> chair: hhalpin
20:01:54 <Zakim> +kodonog
20:02:07 <hhalpin> Zakim, pick a scribe
20:02:07 <Zakim> Not knowing who is chairing or who scribed recently, I propose rsleevi
20:02:14 <hhalpin> Zakim, pick a scribe
20:02:14 <Zakim> Not knowing who is chairing or who scribed recently, I propose hhalpin
20:02:16 <hhalpin> Zakim, pick a scribe
20:02:16 <Zakim> Not knowing who is chairing or who scribed recently, I propose hhalpin
20:02:18 <hhalpin> Zakim, pick a scribe
20:02:18 <Zakim> Not knowing who is chairing or who scribed recently, I propose kodonog
20:02:21 <hhalpin> Zakim, pick a scribe
20:02:21 <Zakim> Not knowing who is chairing or who scribed recently, I propose rsleevi
20:02:23 <hhalpin> Zakim, pick a scribe
20:02:23 <Zakim> Not knowing who is chairing or who scribed recently, I propose rsleevi
20:02:25 <hhalpin> Zakim, pick a scribe
20:02:25 <Zakim> Not knowing who is chairing or who scribed recently, I propose hhalpin
20:02:28 <karen> aaaa is Karen
20:02:47 <hhalpin> Zakim, who's on the phone?
20:02:47 <Zakim> On the phone I see google, Karen, hhalpin, kodonog
20:02:48 <Zakim> google has rsleevi
20:02:49 <bryaneyler> bryaneyler has joined #crypto
20:02:51 <Zakim> +MichaelH
20:02:58 <Zakim> +Wendy
20:03:21 <kodonog> i can report on ietf, but I'm in a starbucks
20:03:34 <MichaelH> MichaelH has joined #crypto
20:03:41 <Zakim> + +31.61.877.aabb
20:03:45 <wseltzer> scribenick: wseltzer
20:03:57 <nvdbleek> zakim, I am +31.61.877.aabb
20:03:57 <Zakim> +nvdbleek; got it
20:04:27 <hhalpin> scribe: wseltzer
20:04:37 <wseltzer> ack karen
20:04:38 <hhalpin> topic: IETF
20:04:41 <nvdbleek> zakim, mute me
20:04:41 <Zakim> nvdbleek should now be muted
20:05:21 <wseltzer> karen: Reporting from IETF
20:06:19 <wseltzer> ... JOSE WG issue-tracker shows many issues closed
20:06:27 <wseltzer> ... starting bi-weekly calls 19 Aug
20:06:36 <wseltzer> ... hope to resolve open issues for WG last call next month
20:06:44 <wseltzer> ... use cases ready for IESG
20:06:56 <wseltzer> ... other 4 docs close; we've asked everyone to get issues on the table
20:07:10 <wseltzer> ... Jim has specific issues to follow-up with webcrypto
20:07:30 <rsleevi> q+
20:07:35 <hhalpin> ack rsleevi
20:07:35 <wseltzer> JOSE: https://datatracker.ietf.org/wg/jose/
20:08:16 <wseltzer> rsleevi: a few places JOSE said it wouldn't take on WebCrypto work, we'll need to work out
20:08:32 <wseltzer> ... JWK, array or single-value, and exportable/extractable
20:08:45 <hhalpin> those sound quite serious re usage of JWK
20:08:47 <wseltzer> ... if it's not in the JOSE spec, we'll need an IANA registry
20:09:02 <wseltzer> ... so questions for our timing and deliverables
20:09:16 <wseltzer> ... respecting Netflix-desired features around wrap/unwrap
20:09:56 <wseltzer> topic: Publication of Use Cases
20:10:12 <hhalpin> Just checking on it, it seems not have gone out again
20:10:33 <hhalpin> ACTION: hhalpin and wseltzer to ping systeam to push Use-cases and Key Discovery out
20:10:33 <trackbot> Created ACTION-113 - And wseltzer to ping systeam to push Use-cases and Key Discovery out [on Harry Halpin - due 2013-08-12].
20:10:43 <hhalpin> topic: Promises
20:11:12 <wseltzer> hhalpin: any open issues on Promises?
20:11:28 <wseltzer> rsleevi: Issue raised by Israel. I've attempted to resolve in push this AM
20:11:51 <wseltzer> ISSUE-86?
20:11:51 <trackbot> ISSUE-86 does not exist.
20:11:55 <wseltzer> ISSUE-84?
20:11:55 <trackbot> ISSUE-84 does not exist.
20:12:10 <wseltzer> ... how do we process streams of data efficiently?
20:12:47 <wseltzer> ... WebApps, other WGs considering; MS streams proposal
20:13:08 <wseltzer> ... better not to try to introduce yet another streaming mechanism
20:13:15 <wseltzer> ... under active discussion in other WGs
20:13:53 <wseltzer> ... Netflix says this isn't critical; MS may propose extensions
20:14:07 <wseltzer> ... we don't yet have good solution for multi-part, committing to work on it.
20:14:31 <rsleevi> ISSUE-49?
20:14:31 <trackbot> ISSUE-49 -- Using Streams or something similar to support Multi-part on WebCrypto APIs -- raised
20:14:31 <trackbot> http://www.w3.org/2012/webcrypto/track/issues/49
20:15:12 <wseltzer> rsleevi: we've always understood this to be at-risk
20:15:32 <hhalpin> no problem with that being open as we go into CR
20:15:39 <hhalpin> re implementations
20:16:00 <MichaelH> q+
20:16:03 <wseltzer> s/other WGs/script-coord/
20:16:05 <rsleevi> original issue was ISSUE-18
20:16:10 <hhalpin> topic: PING review
20:16:14 <hhalpin> August 22nd
20:16:21 <rsleevi> ISSUE-18?
20:16:21 <trackbot> ISSUE-18 -- Should it be possible to perform CryptoOperations as a 'streaming' operation with URI semantics? -- closed
20:16:21 <trackbot> http://www.w3.org/2012/webcrypto/track/issues/18
20:16:23 <hhalpin> ack Michael
20:16:38 <wseltzer> MichaelH: Re Promises, wasn't there an outstanding issue on error reporting?
20:16:50 <wseltzer> rsleevi: resolved on our prior call
20:16:58 <wseltzer> ... exceptions, in WebIDL
20:17:04 <wseltzer> ... discussion on script-coord
20:17:58 <wseltzer> ... the only thing outstanding is to identify errors that are usefully distinguished
20:18:30 <wseltzer> MichaelH: editorial note on the document
20:19:04 <wseltzer> ... awaiting input on DOM errors that would be meaningful
20:19:11 <hhalpin> q?
20:19:12 <wseltzer> rsleevi: if no feedback, will remove the note
20:19:20 <hhalpin> topic: PING review
20:19:28 <hhalpin> August 22nd
20:20:33 <hhalpin> date and time work for folks in WG?
20:21:21 <rsleevi> q+
20:21:25 <rsleevi> https://dvcs.w3.org/hg/webcrypto-api/
20:21:30 <hhalpin> ack rsleevi
20:21:37 <hhalpin> topic: wrapping up
20:21:42 <wseltzer> [PING: http://www.w3.org/Privacy/ ]
20:21:48 <rsleevi> https://dvcs.w3.org/hg/webcrypto-api/shortlog
20:22:09 <wseltzer> rsleevi: fixing a bug in RSA-PKCS1
20:22:23 <wseltzer> ... quick overview of supported algorithms
20:22:28 <wseltzer> ... non-normative
20:23:12 <wseltzer> ... I've kept deriveKey, added vgb's proposed deriveBits
20:23:27 <wseltzer> ... handle KDF use cases and secret agreement
20:23:47 <Zakim> -kodonog
20:23:57 <wseltzer> ... deriveBits will let you polyfill
20:24:06 <hhalpin> as opposed to deriveKey
20:24:08 <wseltzer> ... Issue 49 taken out
20:24:35 <wseltzer> ... Issue 46
20:25:28 <wseltzer> ... see the full list and diffs, https://dvcs.w3.org/hg/webcrypto-api/shortlog
20:25:41 <MichaelH> q+
20:25:45 <hhalpin> ack Michael
20:26:05 <wseltzer> MichaelH: deadline on import key / export key gets filled out
20:26:11 <wseltzer> s/out/out?/
20:26:24 <wseltzer> rsleevi: JOSE decided not to take on these items, thread is ongoing
20:26:37 <wseltzer> ... with markw. My goal is to clarify key types
20:26:51 <wseltzer> ... JOSE use case remains in limbo
20:28:35 <wseltzer> rsleevi: biggest issue, progress on attributes of keys; JOSE hasn't taken that on
20:28:59 <wseltzer> ... what happens if we register uses in conflict with JOSE
20:29:40 <wseltzer> ... we need to understand what JWK attribute should look like
20:31:40 <Zakim> -google
20:31:43 <karen> karen has left #crypto
20:31:45 <wseltzer> rrsagent, make minutes
20:31:45 <RRSAgent> I have made the request to generate http://www.w3.org/2013/08/05-crypto-minutes.html wseltzer
20:31:46 <hhalpin> RRSAgent, draft minutes
20:31:46 <RRSAgent> I have made the request to generate http://www.w3.org/2013/08/05-crypto-minutes.html hhalpin
20:31:48 <Zakim> -nvdbleek
20:31:51 <wseltzer> trackbot, end teleconf
20:31:51 <trackbot> Zakim, list attendees
20:31:51 <Zakim> As of this point the attendees have been +1.512.257.aaaa, hhalpin, rsleevi, kodonog, Karen, MichaelH, Wendy, +31.61.877.aabb, nvdbleek
20:31:51 <hhalpin> trackbot, end meeting
20:31:53 <Zakim> -Karen
20:31:57 <Zakim> -Wendy
20:31:59 <trackbot> RRSAgent, please draft minutes
20:31:59 <RRSAgent> I have made the request to generate http://www.w3.org/2013/08/05-crypto-minutes.html trackbot
20:32:00 <trackbot> RRSAgent, bye
20:32:00 <RRSAgent> I see 1 open action item saved in http://www.w3.org/2013/08/05-crypto-actions.rdf :
20:32:00 <RRSAgent> ACTION: hhalpin and wseltzer to ping systeam to push Use-cases and Key Discovery out [1]
20:32:00 <RRSAgent>   recorded in http://www.w3.org/2013/08/05-crypto-irc#T20-10-33
20:32:00 <trackbot> Zakim, list attendees
20:32:00 <Zakim> As of this point the attendees have been +1.512.257.aaaa, hhalpin, rsleevi, kodonog, Karen, MichaelH, Wendy, +31.61.877.aabb, nvdbleek