- From: Anil Saldhana <Anil.Saldhana@redhat.com>
- Date: Mon, 01 Oct 2007 17:40:01 -0500
- To: Ian Fette <ifette@google.com>
- CC: public-wsc-wg@w3.org
Last week is not counted. :( You will be relieved of potential scribing responsibilities at the f2f, if you show up there by 7am. I am already here in Austin and you can beat me up tomorrow. :) Ian Fette wrote: > Just as a small point, the scribe list is out of date (e.g. I scribed > last week, and the list shows me not having scribed since August). :-) > > -Ian > > On 10/1/07, * Mary Ellen Zurko* <Mary_Ellen_Zurko@notesdev.ibm.com > <mailto:Mary_Ellen_Zurko@notesdev.ibm.com>> wrote: > > > Removed Robustness - we covered it fine in the last distributed > meeting > > Web Security Context (WSC) WG Face-to-face #4 Agenda (v 1.0) > 2007-10-02 through 2007-10-03 > Austin, Texas, USA > http://www.w3.org/2006/WSC/Group/auslogistics > <http://www.w3.org/2006/WSC/Group/auslogistics> > > Phone number and IRC channel the same as usual, documented on WG > administrative home page > http://www.w3.org/2006/WSC/Group/ <http://www.w3.org/2006/WSC/Group/> > > Teleconference time and length information > 8:30 - 17:00 both days, local time (US Central timezone) > > Tuesday, 2007-10-02 - Chair, Mary Ellen Zurko > > (Coffee and juice provided) > > 1. Administrative details (8:30) 15 minutes > Including: > > 1a. Selection of scribes > http://www.w3.org/2006/WSC/scribes > <http://www.w3.org/2006/WSC/scribes> > > 1b. Brief roll call > Make sure you've already posted an introduction to yourself on our > list > > 2. Agenda bashing (8:45) 15 minutes > > 3. Ceremonies for secure data entry (9:00) 1 hour > http://www.w3.org/2006/WSC/drafts/rec/rewrite.html#ceremonies > Substantial progress may have been made on this section before our > f2f, based on discussions on our conference calls. > > 4. Mozilla demos (10:00) 30 minutes > Identity signal, page information, malware > Johnathan N leads > > Break (10:30) 30 minutes > > 5. Conformance labels (11:00) 1 hour > > Conformance labels for web content > http://www.w3.org/2006/WSC/drafts/rec/rewrite.html#clabels-content > > Conformance labels for web user agents > http://www.w3.org/2006/WSC/drafts/rec/rewrite.html#clabels-uagents > > Lunch (12:00) 1 hour > > 6. Lo-fi prototyping (13:00) 1 hour > Discussion of what we have, and what we need > Rachna D leads > > 7. Page security scoring (14:00) 30 minutes > Mike M leads > > Break (14:30) 30 minutes > Coffee/soda > > 8. Last call status for wsc-usecases (15:00) 30 minutes > If we have any outstanding issues, resolve them, so that > wsc-usecases is ready for last call now. > > 9. Publishing threats (15:30) 30 minutes > If we have any outstanding issues, resolve them, so that threats > is published. > > 10. Day one wrapup (16:00) > Any logistics, agenda changes for the next day, other actions, etc. > > Recess (17:00) > > Wednesday, 2007-10-03 - Chair, Mary Ellen Zurko > > (Coffee and juice provided) > > 1. Administrative details (8:30) 15 minutes > > 2. Agenda bashing (8:45) 15 minutes > > 3. Issues on our rec track document (9:00) all day > > We work through any and all issues on the rec track document that > need to be addressed so that it's ready for FPWD by the end of the > day > http://www.w3.org/2006/WSC/track/products/4 > > Here's what was there when this agenda was initially put together: > > logotype - SHOULD or MAY? > http://www.w3.org/2006/WSC/track/issues/96 > > logotypes tied to EV certs? > http://www.w3.org/2006/WSC/track/issues/97 > > What kind of logotype is preferred? > http://www.w3.org/2006/WSC/track/issues/98 > > What certificate fields in the identity signal? > http://www.w3.org/2006/WSC/track/issues/99 > > What should be our notion of EV certificates? > http://www.w3.org/2006/WSC/track/issues/102 > > Should unknown CAs and self-signed certificates be treated in the > same way? > http://www.w3.org/2006/WSC/track/issues/103 > > Some information in certificates is untrustworthy > http://www.w3.org/2006/WSC/track/issues/104 > <http://www.w3.org/2006/WSC/track/issues/104> > > What information should be communicated about client state? > http://www.w3.org/2006/WSC/track/issues/105 > > cert/URL matching > http://www.w3.org/2006/WSC/track/issues/106 > > Within the document itself: * > issueConformanceUsability* * > nonvisualmixing * * > issueChangeSSC* * > primaryToBeMerged* > > Break (10:30) 30 minutes > > Lunch (12:00) 1 hour > > Break (14:30) 30 minutes > Coffee/soda > > 4. Timeline/next steps (16:30) 30 minutes > > shortname for rec track document, and anything else > rec track document to FPWD > wsc-usescases to LC > threats to published > > Recess (17:00) > > -- Anil Saldhana Project/Technical Lead, JBoss Security & Identity Management JBoss, A division of Red Hat Inc. http://labs.jboss.com/portal/jbosssecurity/
Received on Monday, 1 October 2007 22:40:25 UTC