public-wsc-wg@w3.org from April 2007 by date

Monday, 30 April 2007

• RE: DNSSEC indicator michael.mccormick@wellsfargo.com
• Agenda, Wednesay, 2 May, WSC Call Mary Ellen Zurko
• RE: Secure Internet Letterhead Hallam-Baker, Phillip
• RE: DNSSEC indicator Mary Ellen Zurko
• Re: Secure Internet Letterhead Mary Ellen Zurko
• Fw: ACTION-150 Propose text do drill down on possible classes of conforming implementations -- more concrete than note, more abstract than products Mary Ellen Zurko

Saturday, 28 April 2007

• Secure Internet Letterhead Hallam-Baker, Phillip
• Re: Editing process for Recommendations Thomas Roessler

Friday, 27 April 2007

• Editing process for Recommendations Close, Tyler J.
• baked Note edits Close, Tyler J.
• RE: ISSUE-14: Technologies that reduce risk Close, Tyler J.
• RE: ISSUE-19: Arrangement and formatting of use cases Close, Tyler J.
• RE: ISSUE-20 OPEN Potential additions to Available Security Information Close, Tyler J.
• RE: ISSUE-26 OPEN "currently deployed security information" Close, Tyler J.
• RE: ISSUE-29 OPEN Define user agent in wsc-usecases Close, Tyler J.
• RE: ISSUE-30 allow for remote opening of web browser Close, Tyler J.
• Meeting record: WSC WG weekly 2007-04-18 Thomas Roessler
• RE: ISSUE-31 Correct scenarion 20 intended action Close, Tyler J.
• RE: ACTION-182 - SSL error anti patterns michael.mccormick@wellsfargo.com
• Re: ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) Doyle, Bill
• Fw: [Soups-announce] Call for SOUPS posters and discussion sessions Mary Ellen Zurko
• Re: ISSUE-18: Clarify audience of wsc-usecases Timothy Hahn

Thursday, 26 April 2007

• ISSUE-15 closing Close, Tyler J.
• ISSUE-31 Correct scenarion 20 intended action Mary Ellen Zurko
• ISSUE-30 allow for remote opening of web browser Mary Ellen Zurko
• Re: DNSSEC indicator Stuart E. Schechter
• ISSUE-29 OPEN Define user agent in wsc-usecases Mary Ellen Zurko
• Re: ISSUE-24 OPEN [editorial] Add "known systemic flaws" to goals Thomas Roessler
• ISSUE-26 OPEN "currently deployed security information" Mary Ellen Zurko
• wsc-usecases review Mike Beltzner
• RE: Proposed Recommendation: Page Info Summary Luis Barriga \(KI/EAB\)
• ISSUE-24 OPEN [editorial] Add "known systemic flaws" to goals Mary Ellen Zurko
• ISSUE-23 OPEN Rephrase background on usable security in Process secion Mary Ellen Zurko
• ISSUE-20 OPEN Potential additions to Available Security Information Mary Ellen Zurko
• Re: ISSUE-19: Arrangement and formatting of use cases Mary Ellen Zurko
• Re: ISSUE-18: Clarify audience of wsc-usecases Mary Ellen Zurko
• Re: ISSUE-14: Technologies that reduce risk Mary Ellen Zurko
• Re: ISSUE-12: User-agents - future proofing Mary Ellen Zurko
• Re: ISSUE-7: Mental models? Mary Ellen Zurko
• Re: ISSUE-6 User Interface Issues for Constrained / Mobile Devices Mary Ellen Zurko
• RE: DNSSEC indicator Hallam-Baker, Phillip
• Fw: Dublin workshop on web authoring Mary Ellen Zurko
• RE: DNSSEC indicator Luis Barriga \(KI/EAB\)
• RE: DNSSEC indicator Dan Schutzer
• RE: DNSSEC indicator Dan Schutzer
• Re: DNSSEC indicator Thomas Roessler

Wednesday, 25 April 2007

• Re: ISSUE-69: New goal--Reduce the number of scenarios in which users\' security depends upon authenticating sites Mary Ellen Zurko
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation Hallam-Baker, Phillip
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation michael.mccormick@wellsfargo.com
• Re: Proposed Recommendation: Page Info Summary Mary Ellen Zurko
• Re: ACTION 181: Summary of EV certificate discussion, prototype recommendation Mary Ellen Zurko
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation Hallam-Baker, Phillip
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation michael.mccormick@wellsfargo.com
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation Hallam-Baker, Phillip
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation michael.mccormick@wellsfargo.com
• Re: ISSUE-68: Note summary, goals, and scope should more clearly focus on problem to be solved---impersonation Mary Ellen Zurko
• Regrets Shawn Duffy
• ACTION 181: Summary of EV certificate discussion, prototype recommendation Hallam-Baker, Phillip
• ISSUE-72: Replace term \"Status Quo\" with something more specific Web Security Context Issue Tracker
• ISSUE-71: Change title of Section 7 Web Security Context Issue Tracker
• ISSUE-70: Scope should be defined in terms of concepts, not in terms of use cases Web Security Context Issue Tracker
• ISSUE-69: New goal--Reduce the number of scenarios in which users\' security depends upon authenticating sites Web Security Context Issue Tracker
• ISSUE-68: Note summary, goals, and scope should more clearly focus on problem to be solved---impersonation Web Security Context Issue Tracker
• ISSUE-67: The introduction to the note should include a hyperlink to the charter. Web Security Context Issue Tracker
• Proposed Recommendation: Identity indicator in chrome Johnathan Nightingale
• Re: Summary of "What is a secure page?" discussion, first draft Yngve Nysaeter Pettersen
• Proposed Recommendation: Page Info Summary Johnathan Nightingale
• Re: Summary of "What is a secure page?" discussion, first draft Mary Ellen Zurko
• RE: ACTION-182 - SSL error anti patterns Mary Ellen Zurko
• Regrets: Agenda, Wednesay, 25 April, WSC Call Robert Yonaitis
• Re: Agenda, Wednesay, 25 April, WSC Call Timothy Hahn

Tuesday, 24 April 2007

• Re: Summary of "What is a secure page?" discussion, first draft Yngve N. Pettersen (Developer Opera Software ASA)
• Summary of "What is a secure page?" discussion, first draft Yngve N. Pettersen (Developer Opera Software ASA)
• shared knowledge authentication of web sites Mary Ellen Zurko
• RE: Agenda, Wednesay, 25 April, WSC Call Bruno von Niman
• Re: Shared Public Knowledge Mary Ellen Zurko

Monday, 23 April 2007

• Updating TrustMe wiki page based on telecon Close, Tyler J.
• RE: ACTION-182 michael.mccormick@wellsfargo.com
• RE: Rough proposal: Contextual Password Warnings Dan Schutzer
• Re: Rough rec proposal: revisiting past decisions Mary Ellen Zurko
• Re: Rough rec proposal: revisiting past decisions Thomas Roessler
• Re: Rough proposal: Contextual Password Warnings Thomas Roessler
• Agenda, Wednesay, 25 April, WSC Call Mary Ellen Zurko
• RE: Suggestions for note resulting from a conversation with mez Dan Schutzer
• Suggestions for note resulting from a conversation with mez Stuart E. Schechter
• Re: No Padlock OID Johnathan Nightingale
• RE: ACTION-182 michael.mccormick@wellsfargo.com
• Re: Use Cases Again Mary Ellen Zurko
• RE: Safe Web Browsing Mode Dan Schutzer
• Re: No Padlock OID Stephen Farrell
• ISSUE-66: Suggested rewrite of last paragraph of 10.3 Web Security Context Issue Tracker
• RE: No Padlock OID Hallam-Baker, Phillip

Sunday, 22 April 2007

• Re: No Padlock OID Mike Beltzner
• Re: No Padlock OID Stephen Farrell
• No Padlock OID Hallam-Baker, Phillip
• Re: ACTION-188 summarize robustness practices in terms of limitations on sites' freedom Thomas Roessler
• Re: ACTION-188 summarize robustness practices in terms of limitations on sites\\\\\\\\' freedom George Staikos

Friday, 20 April 2007

• RE: Safe Web Browsing Mode Mary Ellen Zurko
• RE: Favicon anti-pattern Mary Ellen Zurko
• Re: ACTION-182 Mary Ellen Zurko
• ACTION-182 michael.mccormick@wellsfargo.com
• RE: Favicon anti-pattern michael.mccormick@wellsfargo.com
• Look over background for any further recommendations Mary Ellen Zurko
• ISSUE-46: widely deployed baseline, yes; usage and presentation, yes (pubic comment) Doyle, Bill
• RE: ISSUE-47: define extension interface for content-scanning tools (public comment) Doyle, Bill

Thursday, 19 April 2007

• Re: ISSUE-51: distinguished Chrome is not the answer (public comment) Timothy Hahn
• Re: ISSUE-65: testing throughout evolution of product (pubic comment) Mary Ellen Zurko
• Re: ISSUE-64: \'where\' is less universal than \'how\' for drill-down (public comment) Mary Ellen Zurko
• Re: ISSUE-63: consistency is good where it fits; it doesn\'t always fit; so undergird your consistency with a model (public comment) Mary Ellen Zurko
• Re: ISSUE-62: User-adjustable step size is part of Universal Design (public comment) Mary Ellen Zurko
• Re: ISSUE-61: Know you don\'t know your users (public comment) Mary Ellen Zurko
• Re: ISSUE-60: reinvent Help and DoIt (public comment) Mary Ellen Zurko
• Re: ISSUE-59: challenge and recover are essential; one presentation fits all -NOT (pubic comment) Mary Ellen Zurko
• Re: ISSUE-58: simplicity is in the [diverse] world of the user (public comment) Mary Ellen Zurko
• Re: ISSUE-57: qualify your interrupts; communicate subliminally always and through the focus rarely (public comment) Mary Ellen Zurko
• Re: ISSUE-56: habit is little help, here (public comment) Mary Ellen Zurko
• Re: ISSUE-55: realism is not universal, nor does ordinariness befit exceptional communications (public comment) Mary Ellen Zurko
• Meeting record: WSC WG weekly 2007-04-11 Thomas Roessler
• Re: ISSUE-54: user understanding is where it\'s at (pubic comment) Mary Ellen Zurko
• Re: ISSUE-53: augment general usability wisdom because you are operating on a fringe (as is WAI) (Public Comnment) Mary Ellen Zurko
• Re: ISSUE-52: benchmarking success -- it\'s out there (public comment) Mary Ellen Zurko
• Re: ISSUE-51: distinguished Chrome is not the answer (public comment) Mary Ellen Zurko
• RE: Safe Web Browsing Mode Mary Ellen Zurko
• Re: ACTION-188 summarize robustness practices in terms of limitations on sites\\\\\\\\' freedom Mary Ellen Zurko
• Re: ISSUE-50: present web security is not good enough; even \'though fixing that is out of scope for this deliverable (public comment) Mary Ellen Zurko
• Re: ISSUE-49: trust in browser password cache needs to be better justified (pubic comment) Mary Ellen Zurko
• RE: ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) Doyle, Bill

Wednesday, 18 April 2007

• Re: ISSUE-48: platform and browser security out of scope - NOT (public comment) Mary Ellen Zurko
• Re: ISSUE-47: define extension interface for content-scanning tools (public comment) Mary Ellen Zurko
• Re: ISSUE-46: define extension interface for content-scanning tools (public comment) Mary Ellen Zurko
• Re: ISSUE-45: full legal entity identification (is a must) (pubic comment) Mary Ellen Zurko
• Re: ISSUE-44: beyond \'who\' (some day) (pubic comment) Mary Ellen Zurko
• Re: ISSUE-43: don\'t disable assistive technology (public comment) Mary Ellen Zurko
• Use Cases Again Stuart E. Schechter
• Re: ISSUE-42: Re: 3.2 Non-HTTP Web interactions (public comment) Mary Ellen Zurko
• Re: ISSUE-41: limited guidance on presentation OK (public comment) Mary Ellen Zurko
• Re: ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) Mary Ellen Zurko
• Re: ISSUE-39: cooperate with WAI-ARIA \'politeness\' (from public comments) Mary Ellen Zurko
• Re: ISSUE-38: no safe haven in presentation space (from public comments) Mary Ellen Zurko
• RE: Shared Public Knowledge Bob Pinheiro
• RE: Shared Public Knowledge Timothy Hahn
• Re: ISSUE-37: qualify your interrupts (from public comments) Mary Ellen Zurko
• RE: Shared Public Knowledge Mary Ellen Zurko
• RE: Shared Public Knowledge Timothy Hahn

Tuesday, 17 April 2007

• RE: ISSUE-36: presentation norms -- no oneSizeFitsAll (from public comments) Robert Yonaitis
• ACTION-175 - Summarize robustness practices for Firefox Johnathan Nightingale
• Re: ISSUE-36: presentation norms -- no oneSizeFitsAll (from public comments) Mary Ellen Zurko
• regrets for 17 April call Timothy Hahn
• RE: Recommendations for "Lightening Discussions" at next week's meeting michael.mccormick@wellsfargo.com
• Re: ISSUE-35: information overload/underload -- no oneSizeFitsAll (public comment) Mary Ellen Zurko
• Re: ISSUE-34: Formal studies don\'t cover disability access adequately, use experts too - (public comment) Mary Ellen Zurko
• ACTION-194 refine UrlRecommendation Mary Ellen Zurko
• ISSUE-65: testing throughout evolution of product (pubic comment) Web Security Context Issue Tracker
• ISSUE-64: \'where\' is less universal than \'how\' for drill-down (public comment) Web Security Context Issue Tracker
• ISSUE-63: consistency is good where it fits; it doesn\'t always fit; so undergird your consistency with a model (public comment) Web Security Context Issue Tracker
• ISSUE-62: User-adjustable step size is part of Universal Design (public comment) Web Security Context Issue Tracker
• ISSUE-61: Know you don\'t know your users (public comment) Web Security Context Issue Tracker
• ISSUE-60: reinvent Help and DoIt (public comment) Web Security Context Issue Tracker
• ISSUE-59: challenge and recover are essential; one presentation fits all -NOT (pubic comment) Web Security Context Issue Tracker
• ISSUE-58: simplicity is in the [diverse] world of the user (public comment) Web Security Context Issue Tracker
• ISSUE-57: qualify your interrupts; communicate subliminally always and through the focus rarely (public comment) Web Security Context Issue Tracker
• ISSUE-56: habit is little help, here (public comment) Web Security Context Issue Tracker
• ISSUE-55: realism is not universal, nor does ordinariness befit exceptional communications (public comment) Web Security Context Issue Tracker
• ISSUE-54: user understanding is where it\'s at (pubic comment) Web Security Context Issue Tracker
• ISSUE-53: augment general usability wisdom because you are operating on a fringe (as is WAI) (Public Comnment) Web Security Context Issue Tracker
• ISSUE-52: benchmarking success -- it\'s out there (public comment) Web Security Context Issue Tracker
• ISSUE-51: distinguished Chrome is not the answer (public comment) Web Security Context Issue Tracker

Monday, 16 April 2007

• Re: comments on use-cases Maritza Johnson
• Agenda, Wednesay, 18 April, WSC Call Mary Ellen Zurko
• RE: Recommendations for "Lightening Discussions" at next week's meeting Mary Ellen Zurko
• Re: ISSUE-33: Charter retains authority Review of Note Thomas Roessler
• Re: ISSUE-33: Charter retains authority Review of Note Mary Ellen Zurko
• ACTION-188 summarize robustness practices in terms of limitations on sites\\\\\\\\' freedom Mary Ellen Zurko
• Futures area of our wiki Mary Ellen Zurko
• ACTION-189: Cabfourm X.509v3/ PKIX guidelines Hallam-Baker, Phillip
• Cabfourm X.509v3/ PKIX guidelines Hallam-Baker, Phillip
• Re: Action item concerning mixed content / "what is a secure page" Thomas Roessler
• agenda item for this week? (Re: Action item concerning mixed content / "what is a secure page") Thomas Roessler
• RE: FW: .safe TLD idea from ICANN Luis Barriga \(KI/EAB\)
• Re: FW: .safe TLD idea from ICANN Yngve Nysaeter Pettersen
• Re: FW: .safe TLD idea from ICANN Thomas Roessler
• RE: ISSUE-29: Define user agent in wsc-usecases Mary Ellen Zurko
• Re: FW: .safe TLD idea from ICANN Mary Ellen Zurko
• Error handling proposal Mary Ellen Zurko
• ISSUE-50: present web security is not good enough; even \'though fixing that is out of scope for this deliverable (public comment) Web Security Context Issue Tracker
• ISSUE-49: trust in browser password cache needs to be better justified (pubic comment) Web Security Context Issue Tracker
• ISSUE-48: platform and browser security out of scope - NOT (public comment) Web Security Context Issue Tracker
• ISSUE-47: define extension interface for content-scanning tools (public comment) Web Security Context Issue Tracker

Sunday, 15 April 2007

• [fwd] Re: Shared Public Knowledge (from: dan.schutzer@fstc.org) Thomas Roessler
• ISSUE-46: define extension interface for content-scanning tools (public comment) Web Security Context Issue Tracker
• ISSUE-45: full legal entity identification (is a must) (pubic comment) Web Security Context Issue Tracker
• ISSUE-44: beyond \'who\' (some day) (pubic comment) Web Security Context Issue Tracker
• ISSUE-43: don\'t disable assistive technology (public comment) Web Security Context Issue Tracker
• ISSUE-42: Re: 3.2 Non-HTTP Web interactions (public comment) Web Security Context Issue Tracker
• ISSUE-41: limited guidance on presentation OK (public comment) Web Security Context Issue Tracker
• ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) Web Security Context Issue Tracker
• ISSUE-39: cooperate with WAI-ARIA \'politeness\' (from public comments) Web Security Context Issue Tracker
• ISSUE-38: no safe haven in presentation space (from public comments) Web Security Context Issue Tracker
• ISSUE-37: qualify your interrupts (from public comments) Web Security Context Issue Tracker
• ISSUE-36: presentation norms -- no oneSizeFitsAll (from public comments) Web Security Context Issue Tracker

Saturday, 14 April 2007

• Re: Shared Public Knowledge Chuck Wade
• Re: Shared Public Knowledge Stephen Farrell
• RE: Shared Public Knowledge michael.mccormick@wellsfargo.com

Friday, 13 April 2007

• RE: Shared Public Knowledge Mary Ellen Zurko
• Re: DNSSEC indicator Stuart E. Schechter
• Re: DNSSEC indicator Stuart E. Schechter
• RE: DNSSEC indicator michael.mccormick@wellsfargo.com
• RE: DNSSEC indicator michael.mccormick@wellsfargo.com
• Risky display-only use cases (ACTION-193) michael.mccormick@wellsfargo.com
• RE: Shared Public Knowledge Doyle, Bill
• Re: DNSSEC indicator Stuart E. Schechter
• ISSUE-35: information overload/underload -- no oneSizeFitsAll (public comment) Web Security Context Issue Tracker
• ISSUE-34: Formal studies don\'t cover disability access adequately, use experts too - (public comment) Web Security Context Issue Tracker
• ISSUE-33: Charter retains authority Review of Note Web Security Context Issue Tracker
• DNSSEC indicator Dan Schutzer
• RE: ISSUE-29: Define user agent in wsc-usecases Luis Barriga \(KI/EAB\)

Thursday, 12 April 2007

• RE: FW: sitekey auth busted on BoA site michael.mccormick@wellsfargo.com
• Re: FW: sitekey auth busted on BoA site Chuck Wade
• RE: Shared Public Knowledge michael.mccormick@wellsfargo.com
• Re: Shared Public Knowledge Chuck Wade
• "The Emperor's New Security Indicators" michael.mccormick@wellsfargo.com
• FW: sitekey auth busted on BoA site michael.mccormick@wellsfargo.com
• FW: .safe TLD idea from ICANN michael.mccormick@wellsfargo.com
• RE: Comments RE: The Working draft - section 6.2 Robert Yonaitis
• Re: ACTION-172 OPEN Map threat trees to use case dimensions Stuart Schechter 2007-04-04 Mary Ellen Zurko
• ISSUE-32: explain dynamic content better Web Security Context Issue Tracker
• ISSUE-31: Correct scenarion 20 intended action Web Security Context Issue Tracker
• ISSUE-30: Web Security Context Issue Tracker
• ISSUE-29: Define user agent in wsc-usecases Web Security Context Issue Tracker
• Re: Shared Public Knowledge Mary Ellen Zurko
• Re: DNSSEC indicator Stuart E. Schechter
• RE: ISSUE-28: \"available security information\" Mary Ellen Zurko
• Re: DNSSEC indicator Yngve Nysaeter Pettersen
• RE: ACTION-196 Doyle, Bill
• RE: DNSSEC indicator michael.mccormick@wellsfargo.com
• Meeting record: WSC WG weekly 2007-04-04 Thomas Roessler
• Action item summary 2007-04-11 Thomas Roessler
• Re: comments about note Thomas Roessler
• Re: Shared Public Knowledge Chuck Wade
• RE: comments about note Doyle, Bill
• Re: Shared Public Knowledge Stephen Farrell
• Re: Shared Public Knowledge Bob Pinheiro
• Re: Shared Public Knowledge Chuck Wade
• RE: Shared Public Knowledge Dan Schutzer
• Re: Shared Public Knowledge Stephen Farrell

Wednesday, 11 April 2007

• Shared Public Knowledge michael.mccormick@wellsfargo.com
• Re: Firefox usability data on Location Bar Chuck Wade
• Re: Proposed action item concerning robustness of user agent UIs Thomas Roessler
• Re: Available security information section clarification Thomas Roessler
• regrets for 11 April WSC call Timothy Hahn
• Regrets: 11 April, WSC Call Robert Yonaitis
• Re: comments about note Thomas Roessler

Tuesday, 10 April 2007

• RE: comments about note Close, Tyler J.
• RE: ISSUE-27: [editorial?] techniques for content based detection Close, Tyler J.
• RE: comments on use-cases Close, Tyler J.
• RE: Question re: Comments USE-Cases Close, Tyler J.
• RE: Firefox usability data on Location Bar Close, Tyler J.
• RE: Firefox usability data on Location Bar Close, Tyler J.
• Re: ISSUE-27: [editorial?] techniques for content based detection Thomas Roessler
• RE: comments on use-cases Close, Tyler J.
• RE: Comment on Note Close, Tyler J.
• RE: Available security information section clarification Close, Tyler J.
• RE: ISSUE-27: [editorial?] techniques for content based detection Close, Tyler J.
• RE: Available security information section clarification Close, Tyler J.
• RE: ISSUE-28: \"available security information\" Close, Tyler J.
• RE: Agenda, Wednesay, 11 April, WSC Call Bruno von Niman

Monday, 9 April 2007

• Re: ISSUE-28: \"available security information\" Johnathan Nightingale
• Re: Agenda, Wednesay, 11 April, WSC Call Johnathan Nightingale
• Agenda, Wednesay, 11 April, WSC Call Mary Ellen Zurko
• Re: Note review point - Scoping non-UI recs Johnathan Nightingale
• Re: Available security information section clarification Mary Ellen Zurko
• Re: ISSUE-28: \"available security information\" Timothy Hahn
• Re: ISSUE-25: Participants need to review wsc-usecases Mary Ellen Zurko
• Re: ISSUE-28: \"available security information\" Mary Ellen Zurko
• Re: Available security information section clarification Serge Egelman
• Re: status of my action items -- some due date adjustments Thomas Roessler

Sunday, 8 April 2007

• Re: Note review point - Scoping non-UI recs Thomas Roessler
• Re: Available security information section clarification Thomas Roessler
• Re: XSS out of scope Thomas Roessler
• Re: ISSUE-25: Participants need to review wsc-usecases Thomas Roessler
• ISSUE-28: \"available security information\" Web Security Context Issue Tracker
• ISSUE-27: [editorial?] techniques for content based detection Web Security Context Issue Tracker
• ISSUE-26: \"currently deployed security information\" Web Security Context Issue Tracker
• status of my action items -- some due date adjustments Thomas Roessler

Friday, 6 April 2007

• RE: Comments RE: The Working draft - Section 7 Robert Yonaitis
• Re: XSS out of scope Shawn Duffy
• Re: XSS out of scope Mike Beltzner
• RE: ACTION-154 Track HTTP Auth related extensions Bill Doyle 2007-03-20 Doyle, Bill
• Re: XSS out of scope Shawn Duffy
• ACTION-154 Track HTTP Auth related extensions Bill Doyle 2007-03-20 Mary Ellen Zurko
• RE: XSS out of scope Dan Schutzer
• Re: XSS out of scope Mary Ellen Zurko
• Re: Available security information section clarification Mary Ellen Zurko
• Re: Note review point - Scoping non-UI recs Mary Ellen Zurko
• Re: Comment on Note Mary Ellen Zurko
• Re: comments on use-cases Mary Ellen Zurko
• Re: Comments RE: The Working draft - Section 7 Mary Ellen Zurko
• Re: Comments RE: The Working draft - section 6.5 Mary Ellen Zurko
• Re: Comments RE: The Working draft - section 6.2 Mary Ellen Zurko
• Re: Comments RE: The Working draft - section 42. Mary Ellen Zurko

Thursday, 5 April 2007

• ISSUE-25: Participants need to review wsc-usecases Web Security Context Issue Tracker
• Re: XSS out of scope Shawn Duffy
• Action item concerning mixed content / "what is a secure page" Thomas Roessler
• Proposed action item concerning robustness of user agent UIs Thomas Roessler
• Meeting record: WSC WG weekly 2007-03-28 Thomas Roessler
• Action item summary 2007-04-04 Thomas Roessler
• Re: diffmk Thomas Roessler
• Re: Firefox usability data on Location Bar Mike Beltzner
• Re: Comments about the note Mike Beltzner
• Comments about the note Jan Vidar Krey
• RE: review comments due April 4 Close, Tyler J.
• Available security information section clarification Close, Tyler J.
• XSS out of scope Close, Tyler J.

Wednesday, 4 April 2007

• RE: diffmk Close, Tyler J.
• Firefox usability data on Location Bar Close, Tyler J.
• Re: ACTION-149: FSTC's list of authentication techniques (BMA taxonomy) Chuck Wade
• Note review point - Scoping non-UI recs Johnathan Nightingale
• Regrets Serge Egelman
• Re: Question re: Comments USE-Cases Maritza Johnson
• Re: Question re: Comments USE-Cases Mike Beltzner
• Re: Question re: Comments USE-Cases Thomas Roessler
• RE: Question re: Comments USE-Cases Robert Yonaitis
• Re: Question re: Comments USE-Cases Thomas Roessler
• RE: Question re: Comments USE-Cases Bruno von Niman
• Comments on Note Shawn Duffy
• RE: Question re: Comments USE-Cases Dan Schutzer
• Re: Question re: Comments USE-Cases Thomas Roessler
• Re: Question re: Comments USE-Cases Mary Ellen Zurko
• Regrets... and editing Shawn Duffy
• Re: comments on use-cases Maritza Johnson
• RE: Recommendations for "Lightening Discussions" at next week's meeting Mary Ellen Zurko
• Comment on Note Bob Pinheiro
• RE: Recommendations for "Lightening Discussions" at next week's meeting Dan Schutzer
• RE: Recommendations for "Lightening Discussions" at next week's meeting Mary Ellen Zurko
• Comments RE: The Working draft Robert Yonaitis

Tuesday, 3 April 2007

• RE: Recommendations for "Lightening Discussions" at next week's meeting michael.mccormick@wellsfargo.com
• Re: ACTION-149: FSTC's list of authentication techniques (BMA taxonomy) Mary Ellen Zurko
• Re: Question re: Comments USE-Cases Mary Ellen Zurko
• Introduction to group Robert Yonaitis
• Question re: Comments USE-Cases Robert Yonaitis
• Re: Documenting status quo Mary Ellen Zurko
• Fw: ACTION-156: List of privacy and security indicators Mary Ellen Zurko

Monday, 2 April 2007

• Regrets for April 4, Call Robert Yonaitis
• RE: Regrets for April 4, Call Robert Yonaitis

Tuesday, 3 April 2007

• comments about note Doyle, Bill

Monday, 2 April 2007

• Agenda, WEDNESDAY, 4 April, WSC Call Mary Ellen Zurko
• Re: ISSUE-22: Rephrase favicon text Thomas Roessler
• Re: ACTION-106 Propose clarifying language for 8.2.5 Thomas Roessler
• Robustness practices -- pending (but closed) actions. Thomas Roessler
• Re: Recommendations for "Lightening Discussions" at next week's meeting Thomas Roessler
• Re: What is a secure page? Thomas Roessler
• RE: Recommendations for "Lightening Discussions" at next week's meeting Mary Ellen Zurko
• RE: Recommendations for "Lightening Discussions" at next week's meeting Dan Schutzer
• Rough rec proposal: revisiting past decisions Thomas Roessler
• RE: Recommendations for "Lightening Discussions" at next week's meeting michael.mccormick@wellsfargo.com
• Re: Rec Proposal: Separate in-browser editor for entry of Personally Identifiable Information (PII) Thomas Roessler
• Fw: ACTION-154 OPEN Track HTTP Auth related extensions Bill Doyle 2007-03-20 Mary Ellen Zurko
• Lightening Recommendations Mary Ellen Zurko

Last message date: Monday, 30 April 2007 20:15:39 UTC