16:50:27 RRSAgent has joined #websec 16:50:27 logging to http://www.w3.org/2014/01/21-websec-irc 16:51:15 Zakim has joined #websec 16:51:32 Zakim, what conference do you see ? 16:51:32 I don't understand your question, virginie. 16:51:44 dom has joined #websec 16:53:10 Zakim, this will be WSIG 16:53:10 I do not see a conference matching that name scheduled within the next hour, dom 16:53:34 Zakim, list conferences 16:53:34 I see XML_ET-TF()11:00AM, WAI_WCAG()11:00AM, Team_(eme)16:00Z, HTML_WG()11:00AM active 16:53:36 also scheduled at this time are VB_VBWG()10:00AM, RWC_WebEven()11:00AM, T&S_DNTC()12:00PM, RWC_PEWG()11:00AM, SW_HCLS()11:00AM, SEC_(PUSHAPIPAG)11:00AM 16:53:38 zakim, this is WSIG 16:53:40 sorry, wseltzer, I do not see a conference named 'WSIG' in progress or scheduled at this time 16:53:49 zakim, call for 15 at 1200? 16:53:49 I don't understand your question, wseltzer. 16:53:54 zakim, space for 15 at 1200? 16:53:56 ok, wseltzer; conference Team_(websec)17:00Z scheduled with code 26634 (CONF4) at 12:00 for 60 minutes until 1800Z 16:54:09 zakim, make this code WSIG 16:54:09 I don't understand 'make this code WSIG', wseltzer 16:54:30 zakim, code? 16:54:30 the conference code is 26634 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), wseltzer 16:54:49 virginie, I guess today's code will be 26634 16:55:00 npdoty has joined #websec 16:55:02 ok, i'll send it on the mailing list 16:57:06 kodonog has joined #websec 16:57:24 sftcd has joined #websec 16:58:19 Team_(websec)17:00Z has now started 16:58:26 + +1.512.257.aaaa 16:58:36 +karen_oDonoghue 16:58:57 fan has joined #websec 16:59:09 hi all, the conf call code is 26634# 17:00:10 + +3531896aabb 17:00:18 +Masinter 17:00:26 + +861381144aacc 17:00:37 Zakim, code? 17:00:37 the conference code is 26634 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), npdoty 17:01:01 zakim, call wendy-mobile 17:01:01 ok, wseltzer; the call is being made 17:01:03 +Wendy 17:01:07 Zakim, call dom-home 17:01:07 ok, dom; the call is being made 17:01:09 +Dom 17:01:25 Zakim, mute me 17:01:25 Dom should now be muted 17:01:25 zakim, who is on the phone ? 17:01:26 On the phone I see +1.512.257.aaaa, karen_oDonoghue, +3531896aabb, Masinter, +861381144aacc, Wendy, Dom (muted) 17:01:39 zakim, aabb is sftcd 17:01:39 +sftcd; got it 17:01:47 zakim, aaaa is virginie 17:01:47 +virginie; got it 17:01:51 thanks wendy 17:02:22 agenda+ welcome 17:02:35 agenda+ ietf liaison 17:02:42 AndyF has joined #websec 17:03:00 agenda+ W3C TAG security discussions 17:03:33 agenda+ IG priorities and task force leaders 17:03:51 agenda+ AOB 17:04:11 <_JeffH> _JeffH has joined #websec 17:04:56 zakim, who is on the phone ? 17:04:56 On the phone I see virginie, karen_oDonoghue, sftcd, Masinter, +861381144aacc, Wendy, Dom (muted) 17:04:58 <_JeffH> what is the code for the bridge? i tried 9744# and am told it is invalid? 17:05:17 _JeffH, 26634 17:05:20 aacc is fan 17:05:25 zakim, aacc is fan 17:05:25 +fan; got it 17:05:30 sorry for that the code is 26634# 17:05:32 +[IPcaller] 17:05:42 <_JeffH> ok, that worked thx 17:05:48 <_JeffH> ok, need to update wiki ? 17:05:50 zakim, +[IPC is JeffH 17:05:50 sorry, wseltzer, I do not recognize a party named '+[IPC' 17:05:54 zakim, +IPC is JeffH 17:05:54 sorry, wseltzer, I do not recognize a party named '+IPC' 17:06:04 zakim, IPcaller is JeffH 17:06:04 +JeffH; got it 17:06:05 <_JeffH> I'm covering for BHill who had a conflict 17:06:25 -JeffH 17:06:29 <_JeffH> oops 17:06:38 done 17:07:35 +[IPcaller] 17:07:41 I will today... 17:07:43 zakim, IPcaller is JeffH 17:07:43 +JeffH; got it 17:07:56 + +1.425.214.aadd 17:07:57 zakim, who is on the phone ? 17:07:58 On the phone I see virginie, karen_oDonoghue, sftcd, Masinter, fan, Wendy, Dom (muted), JeffH, +1.425.214.aadd 17:08:50 scribenick kodonog 17:09:09 +terri 17:09:19 s/scribenick kodonog/scribenick: kodonog/ 17:09:24 Introductions 17:09:46 <_JeffH> i don't see masinter in the irc ? 17:10:00 Zakim, unmute me 17:10:00 Dom should no longer be muted 17:10:05 <_JeffH> oh it's "larry" 17:10:29 Zakim, mute me 17:10:29 Dom should now be muted 17:10:36 Virginie, Karen O'Donoghue, Stephen Farrell, Larry Masinter, Dom, Wendy Seltzer, Jeff Hodges 17:11:20 terri has joined #websec 17:11:26 agenda? 17:11:50 Terri (Intel), Nick Doty 17:11:57 <_JeffH> someone is scribing ? 17:12:50 zakim, who is here? 17:12:50 On the phone I see virginie, karen_oDonoghue, sftcd, Masinter, fan, Wendy, Dom (muted), JeffH, +1.425.214.aadd, terri 17:12:52 Hannes Tschonfeig 17:12:53 On IRC I see terri, _JeffH, AndyF, fan, sftcd, kodonog, npdoty, dom, Zakim, RRSAgent, virginie, Larry, wseltzer 17:12:55 zakim, aadd is Hannes 17:12:55 +Hannes; got it 17:13:07 Virginie address the plan for the meeting. 17:13:35 <_JeffH> which is coord between IETF, esp security, with overlapping areas in W3C 17:13:52 First agenda item, Stephen Farrell, IETF work and STRINT workshop 17:14:16 want an active liaison and conserve resources 17:14:45 W3C is interested in IETF security review process as we are considering doing the same 17:15:01 <_JeffH> where "we" == ietf ? 17:15:13 Stephen Farrell: folks on call already know a lot about the IETF 17:15:17 we= W3C 17:15:25 <_JeffH> k 17:15:53 … main working groups relevant to the W3C, httpbis, httpauth, 17:16:33 . . . oauth 17:16:54 … in ops area also the wpkops wg 17:17:59 UTA Using TLS in Applications 17:18:03 ,,, in the applications area relevant was include websec and uta (using tls in applications) 17:18:16 websec? 17:18:27 <_JeffH> yes, websec in apps area is impt 17:18:49 STRINT workshop 28 Feb / 1 Mar before IETF 89 in London 17:19:00 <_JeffH> got 62 submissions (closed today) 17:19:20 idea is to continue the discussion started in Vancouver to address pervasive monitoring 17:19:32 <_JeffH> https://www.w3.org/2014/strint/ 17:20:11 WGLC on IETF document definiting pervasive monitoring as an attack 17:20:25 <_JeffH> strint is aimed to figure out actual mitigations to pervasive monitoring 17:20:27 workshop CFP deadline has passed 17:21:05 regarding IETF security review, there are various directorates in the IETF including the Security Directorate 17:21:35 every document that is coming up for approval in the IESG gets some security review in the Security Directorate 17:21:39 <_JeffH> directorates are a means for collecting a review board, and parselling out specs for review 17:21:51 <_JeffH> have about 40 folks in Sec Dir 17:21:51 reviews allocated in a round robin basis, 80% hit rate 17:22:07 each reviewer tends to get one review every few months 17:22:07 <_JeffH> each reviewer gets a doc to review about every couple months 17:22:33 Security Area Director uses review during the IESG processing of the document 17:23:09 useful as an educational tool for people working in the IETF - get exposure to lots of other work in the IETF 17:23:43 facilitated by a tool with someone to help manage the tool, inputs reviews, allocates reviews, inputs results 17:24:12 Virginie: description indicates you have quite an infrastructure to support security reviews 17:25:02 q+ 17:25:05 Stephen: have regular liaison calls with Wendy and Mark Nottingham, issues could be raised to that forum, or send direct mail 17:25:15 Stephen: happy to help as we can 17:25:54 Larry: concerned about things that have fallen out of websec and not appeared in W3C (missed specific examples) 17:26:43 Stephen: mime sniffing was really an apps thing so you would be better off talking to them. Believe there wasn't a clear consensus and volunteers to support the work. 17:27:04 origin is an RFC 17:27:37 Virginie: W3C and IETF are currently well coordinated, 17:28:13 <_JeffH> https://tools.ietf.org/search/rfc6454 The Web Origin Concept 17:28:13 need to monitor output of the STRINT workshop to see if there is some W3C websec work to pursue 17:28:46 ? agenda 17:28:58 what i remember reading was that the Origin RFC is wrong and they are just abandoning it 17:29:04 (scribe has forgotten how to switch agenda items…) 17:29:10 zakim, next agenda 17:29:10 agendum 1. "welcome" taken up [from virginie] 17:29:15 zakim, drop agendum 1 17:29:15 agendum 1, welcome, dropped 17:29:17 <_JeffH> larry: really? that on whatwg list? 17:29:18 zakim, next agenda 17:29:18 agendum 2. "ietf liaison" taken up [from virginie] 17:29:20 @larry - don't whatwg think *everything* is wrong? 17:29:26 zakim, take up agendum 3 17:29:26 agendum 3. "W3C TAG security discussions" taken up [from virginie] 17:29:46 i'll have to find this 17:30:01 W3C TAG security discussions - need to make some effort to build a community of experts 17:30:13 I did hear something about whatwg and SOP messing a few months ago 17:30:14 there are some security topics of interest but possibly not enough contributors 17:30:34 two things from the TAG discussions: 17:30:59 TAG members were not that excited by systematic reviews of W3C recommendations 17:31:13 possibly the implementation reports are sufficient to address this. 17:31:25 need to consider if we really need these reviews 17:31:51 https://github.com/w3ctag/secure-the-web 17:32:26 There is now a TAG effort to secure the web. 17:32:35 This may overlap with activity in the interest group 17:33:04 TAG concerned that there are a lack of security contributors in the W3C 17:33:12 need to recruit additional participants 17:33:40 Virginie will share her slides to the TAG on the wiki 17:34:01 just to note that PFS for TLS under HTTP is on the charter for the new UTA wg in the IETF 17:34:08 zakim, next agenda 17:34:08 I see a speaker queue remaining and respectfully decline to close this agendum, kodonog 17:34:19 q? 17:34:28 ack 17:34:30 q- Larry 17:34:32 ack 17:34:34 q- 17:34:38 zakim, next agenda 17:34:38 agendum 2. "ietf liaison" taken up [from virginie] 17:34:39 zakim, next agendum 17:34:39 agendum 2 was just opened, wseltzer 17:34:45 zakim, take up agendum 4 17:34:45 agendum 4. "IG priorities and task force leaders" taken up [from virginie] 17:34:49 zakim, drop agendum 2 17:34:49 agendum 2, ietf liaison, dropped 17:34:49 @larry: the general question of HTML5 not referencing RFCs is a good liaison topic for w3c/ieft calls , pete resnick is the right AD for that I think 17:34:59 http://www.w3.org/Security/wiki/IG 17:35:11 review the wiki to discuss W3C work 17:35:55 http://www.w3.org/Security/wiki/IG/W3C_spec_review 17:36:09 + +1.703.948.aaee 17:36:25 http://www.w3.org/Security/wiki/IG/web_security_model 17:36:28 virginie has updated the page related to spec review 17:37:26 http://www.w3.org/Security/wiki/IG/Mobile_Security_analysis 17:38:10 http://www.w3.org/Security/wiki/IG/W3C_security_roadmap 17:39:15 virginie is stepping through the current material on the wiki to help develop a work plan for the interest group 17:39:31 http://www.w3.org/Security/wiki/IG/press_news 17:40:06 looking for people for the IG to contribute to the various topics 17:40:21 q+ 17:40:23 ++ 17:40:28 Zakim, unmute me 17:40:28 Dom should no longer be muted 17:40:44 q+ to ask about 'cloud security' standards and if there's some liaison possibilities 17:40:46 zakim, aaee may be AndyF 17:40:46 +AndyF?; got it 17:40:56 <_JeffH> sorry, I am overbooked and can't commit to anything new at this time, tho we can see, over the next several months, if we can have someone contribute (no promises tho) 17:41:07 Dom: for the mobile topic, would like to collaborate with security experts 17:41:12 q? 17:41:16 ack me 17:41:59 http://www.w3.org/Security/wiki/IG/Mobile_Security_analysis 17:42:59 no one on the call from Nokia, perhaps we could contact them 17:43:12 Zakim, mute me 17:43:12 Dom should now be muted 17:44:07 ack me 17:44:07 Larry, you wanted to ask about 'cloud security' standards and if there's some liaison possibilities 17:44:08 Larry: see a lot of activity related to cloud 17:44:09 i'm done 17:44:34 there are possible liaisons to facilitate this work 17:44:45 I'm trying to sort it out, so i'd rather not display my ignorance 17:44:46 Virginie: are you talking about the Cloud Security Alliance 17:44:59 they have issued some guidance that is quite vague 17:45:25 operational procedures, etc. 17:45:46 bring back additional references or recommendations for cloud security work 17:45:59 I can help with that 17:46:01 asks Larry to provide any additional references for analysis 17:46:10 q? 17:47:50 beginning to announce the existence of the IG and the ability to do security reviews 17:48:06 need to recruit members in order to execute on these reviews 17:48:47 all of the 'ongoing issues' in http://www.w3.org/Security/wiki/Main_Page#Ongoing_issues ... 17:48:51 q+ 17:49:27 Larry: Ongoing issues , documents are 2009 and 2010, nothing that has been published recently 17:50:00 [that's an old wiki -- we're working from http://www.w3.org/Security/wiki/IG ] 17:50:05 -Dom 17:50:20 [thanks Larry, we'll work to clean up that "Main Page"] 17:50:46 http://www.w3.org/Security/wiki/IG/web_security_model 17:51:04 what about guidelines for W3C working groups about how to do security analysis of their specs? 17:51:05 Virginie: this is an older wiki and we are working to update the material on the new wiki 17:51:08 gotta drop off the call - thanks for listening and if we can help just shoot a mail to me stephen.farrell@cs.tcd.ie 17:51:18 -sftcd 17:51:37 next steps: each person think about a potential activity that they could lead 17:51:52 http://www.w3.org/Security/wiki/IG/W3C_security_roadmap 17:51:58 understanding the web security model is important 17:52:35 +1 to monthly calls 17:53:03 proposing a monthly call for the websec IG 17:53:29 q? 17:53:29 no consensus for a monthly call 17:53:35 ack Larry 17:53:47 continue discussions over the mailing list and if interest increases schedule a clal 17:54:16 <_JeffH> ok thx bye now 17:54:20 -Masinter 17:54:24 tx 17:54:27 -JeffH 17:54:38 -Wendy 17:54:39 -AndyF? 17:54:39 -Hannes 17:54:41 -virginie 17:54:41 -fan 17:54:50 -terri 17:57:48 rrsagent, create minutes 17:57:48 I have made the request to generate http://www.w3.org/2014/01/21-websec-minutes.html virginie 18:05:01 disconnecting the lone participant, karen_oDonoghue, in Team_(websec)17:00Z 18:05:03 Team_(websec)17:00Z has ended 18:05:03 Attendees were +1.512.257.aaaa, karen_oDonoghue, +3531896aabb, Masinter, +861381144aacc, Wendy, Dom, sftcd, virginie, fan, JeffH, +1.425.214.aadd, terri, Hannes, +1.703.948.aaee, 18:05:03 ... AndyF? 18:55:10 terri has joined #websec 19:26:35 rrsagent, set logs public 19:26:41 rrsagent, make minutes 19:26:41 I have made the request to generate http://www.w3.org/2014/01/21-websec-minutes.html wseltzer 19:26:55 chair: Virginie 19:27:20 Meeting: Web Security Interest Group 19:27:22 rrsagent, make minutes 19:27:22 I have made the request to generate http://www.w3.org/2014/01/21-websec-minutes.html wseltzer 21:53:15 terri has joined #websec 22:26:35 npdoty has joined #websec 22:58:34 npdoty has joined #websec