See also: IRC log
engelke: Working on deriveBits,
deriveKeys
... Jim is doing import and export
... then all that is left wrap
hhalpin: vacation plans?
engelke: It was nice if there were feedback
focus the next meeting on getting the browser vendors to go through your pull requests
engelke: One way to do this,
submitted bug reports to chrome
... worked on all of them
... so they agreed with those
... Shockingly little
... mostly wrong errors from the older spec
... No padding errors, they are just passing in it
through
... There is one thing
... 192 bit AES
... Google does
<hhalpin_> then by strict process, we'd have drop 192 bits AES-CTR
<hhalpin_> we really do want notes areas across ALL browsers
<hhalpin_> any places where it doesn't, we do want note that
<hhalpin_> between chrome and mozilla 192 bit
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: hhalpin Inferring Scribes: hhalpin WARNING: No "Topic:" lines found. WARNING: No "Present: ... " found! Possibly Present: engelke hhalpin hhalpin_ You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 27 Jun 2016 Guessing minutes URL: http://www.w3.org/2016/06/27-crypto-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]