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

Friday, 31 August 2007

• RE: Different protections for different kinds of spoofing (Was: PII Editor Bar & Trusted Browser Component) Close, Tyler J.
• RE: Measuring and optimizing user effort (Was: PII Editor Bar & Trusted Browser Component) Close, Tyler J.
• Re: New Use Case for W3C WSC Ian Fette
• RE: New Use Case for W3C WSC Dan Schutzer
• RE: FW: ISSUE-83: Scenario updates (for certain abilities andfunctional limitations) Dan Schutzer

Thursday, 30 August 2007

• RE: New Use Case for W3C WSC michael.mccormick@wellsfargo.com
• RE: New Use Case for W3C WSC michael.mccormick@wellsfargo.com
• Re: FW: ISSUE-83: Scenario updates (for certain abilities andfunctional limitations) Thomas Roessler
• RE: FW: ISSUE-83: Scenario updates (for certain abilities andfunctional limitations) Dan Schutzer
• Re: Non-form-filler users (Was: PII Editor Bar & Trusted Browser Component) Thomas Roessler
• Re: Non-form-filler users (Was: PII Editor Bar & Trusted Browser Component) Ian Fette
• Re: Different protections for different kinds of spoofing (Was: PII Editor Bar & Trusted Browser Component) Ian Fette
• Re: Measuring and optimizing user effort (Was: PII Editor Bar & Trusted Browser Component) Ian Fette

Wednesday, 29 August 2007

• Re: ISSUE-103: Should unknown CAs and self-signed certificates be treated the same way? [Techniques] Thomas Roessler
• RE: FW: ISSUE-83: Scenario updates (for certain abilities andfunctional limitations) Dan Schutzer
• Re: FW: ISSUE-83: Scenario updates (for certain abilities andfunctional limitations) Thomas Roessler
• RE: The purpose of Note use-cases Dan Schutzer
• Re: The purpose of Note use-cases Ian Fette
• Re: The purpose of Note use-cases Thomas Roessler
• Re: Security Considerations (Re: Current state of editor's draft / IdentitySignal) Thomas Roessler
• The purpose of Note use-cases Close, Tyler J.
• Different protections for different kinds of spoofing (Was: PII Editor Bar & Trusted Browser Component) Close, Tyler J.
• Non-form-filler users (Was: PII Editor Bar & Trusted Browser Component) Close, Tyler J.
• Measuring and optimizing user effort (Was: PII Editor Bar & Trusted Browser Component) Close, Tyler J.
• [fwd] TLS protected draft (from: yngve@opera.com) Thomas Roessler
• ISSUE-106 (cert/URL matching): We need to define details of cert/URL matching [Techniques] Web Security Context Working Group Issue Tracker
• RE: New Use Case for W3C WSC Dan Schutzer
• Re: PII Editor Bar & Trusted Browser Component Ian Fette

Tuesday, 28 August 2007

• RE: PII Editor Bar & Trusted Browser Component Close, Tyler J.
• RE: New Use Case for W3C WSC Close, Tyler J.
• RE: New Use Case for W3C WSC Mary Ellen Zurko
• RE: New Use Case for W3C WSC Dan Schutzer
• RE: New Use Case for W3C WSC Dan Schutzer
• Re: New Use Case for W3C WSC Ian Fette
• RE: New Use Case for W3C WSC Dan Schutzer

Monday, 27 August 2007

• RE: New Use Case for W3C WSC Audian Paxson
• RE: New Use Case for W3C WSC Audian Paxson

Saturday, 25 August 2007

• Security Considerations (Re: Current state of editor's draft / IdentitySignal) Thomas Roessler
• Deployment practices (Re: Current state of editor's draft / IdentitySignal) Thomas Roessler
• Identity Signals: Nicknames and certificate attributes (Re: Current state of editor's draft / IdentitySignal) Thomas Roessler
• Certificate status checks vs validity period; self-signed certs (Re: Current state of editor's draft / IdentitySignal) Thomas Roessler
• Old SSL (Re: Current state of editor's draft / IdentitySignal) Thomas Roessler
• Web Page vs Rich Client (Re: Current state of editor's draft / IdentitySignal) Thomas Roessler

Friday, 24 August 2007

• RE: New Use Case for W3C WSC Dan Schutzer
• Re: New Use Case for W3C WSC Ian Fette
• RE: New Use Case for W3C WSC Dan Schutzer
• Re: New Use Case for W3C WSC Ian Fette
• RE: New Use Case for W3C WSC Dan Schutzer
• Re: New Use Case for W3C WSC Serge Egelman
• RE: New Use Case for W3C WSC Dan Schutzer
• Re: New Use Case for W3C WSC Serge Egelman
• RE: New Use Case for W3C WSC Dan Schutzer
• RE: New Use Case for W3C WSC Dan Schutzer
• Re: Current state of editor's draft / IdentitySignal Mary Ellen Zurko
• Re: New Use Case for W3C WSC Bob Pinheiro
• Re: New Use Case for W3C WSC Serge Egelman
• Re: New Use Case for W3C WSC Serge Egelman
• Re: New Use Case for W3C WSC Ian Fette
• RE: New Use Case for W3C WSC Dan Schutzer
• RE: New Use Case for W3C WSC Dan Schutzer
• Re: New Use Case for W3C WSC Bob Pinheiro
• Re: New Use Case for W3C WSC Ian Fette
• Re: New Use Case for W3C WSC Bob Pinheiro
• Re: New Use Case for W3C WSC Ian Fette
• Re: Agenda: WSC WG weekly 2007-08-29 Thomas Roessler
• Agenda: WSC WG weekly 2007-08-29 Thomas Roessler
• Re: New Use Case for W3C WSC Timothy Hahn
• RE: New Use Case for W3C WSC Mary Ellen Zurko
• RE: New Use Case for W3C WSC Dan Schutzer
• Re: Interest in "code sprint" at one of our f2fs? Thomas Roessler
• Re: Interest in "code sprint" at one of our f2fs? Thomas Roessler
• Interest in "code sprint" at one of our f2fs? Mary Ellen Zurko
• Re: New Use Case for W3C WSC Mary Ellen Zurko
• ISSUE-101: Create "visiting known site that is now malware" use case as per ACTION-275 [Note: use cases etc.] Mary Ellen Zurko
• Re: ISSUE-92: P3P and Internet filters Mary Ellen Zurko
• FW: ISSUE-83: Scenario updates (for certain abilities andfunctional limitations) Mary Ellen Zurko
• New Use Case for W3C WSC Dan Schutzer

Wednesday, 22 August 2007

• Re: straw poll: Is page info summary a non-Goal? Mary Ellen Zurko
• Re: straw poll: Is page info summary a non-Goal? Serge Egelman
• RE: straw poll: Is page info summary a non-Goal? Mary Ellen Zurko

Tuesday, 21 August 2007

• RE: Agenda: WSC WG distributed meeting, Wednesday, 2007-08-22 Audian Paxson
• Re: Next face-to-face: October 2/3 Austin Texas Thomas Roessler
• RE: Next face-to-face: October 2/3 Austin Texas michael.mccormick@wellsfargo.com
• RE: straw poll: Is page info summary a non-Goal? michael.mccormick@wellsfargo.com
• Agenda: WSC WG distributed meeting, Wednesday, 2007-08-22 Mary Ellen Zurko
• RE: straw poll: Is page info summary a non-Goal? Timothy Hahn
• Re: straw poll: Is page info summary a non-Goal? Thomas Roessler
• RE: straw poll: Is page info summary a non-Goal? Dan Schutzer

Monday, 20 August 2007

• Re: straw poll: Is page info summary a non-Goal? Johnathan Nightingale
• Re: ISSUE-105: What information should be communicated about client state? [Techniques] Johnathan Nightingale
• FW: ISSUE-83: Scenario updates (for certain abilities andfunctional limitations) Dan Schutzer

Sunday, 19 August 2007

• ISSUE-105: What information should be communicated about client state? [Techniques] Web Security Context Working Group Issue Tracker
• Updated editor's draft: PageInfoSummary (ACTION-281) Thomas Roessler
• ISSUE-104: Some information in certificates is not trustworthy [Techniques] Web Security Context Working Group Issue Tracker

Thursday, 16 August 2007

• RE: New use case for malware at previously visited site Dan Schutzer
• PII Editor Bar & Trusted Browser Component Thomas Roessler
• Re: New use case for malware at previously visited site Ian Fette
• RE: New use case for malware at previously visited site Luis Barriga (KI/EAB)
• Meeting record: WSC WG weekly 2007-08-08 Thomas Roessler

Wednesday, 15 August 2007

• straw poll: Is page info summary a non-Goal? Close, Tyler J.
• Re: Agenda: WSC WG distributed meeting, Wednesday, 2007-08-15 Shawn Duffy
• RE: Agenda: WSC WG distributed meeting, Wednesday, 2007-08-15 Doyle, Bill

Tuesday, 14 August 2007

• Re: ISSUE-97: Should logotypes be tied to EV certificates?[Techniques] Mike Beltzner
• RE: ISSUE-97: Should logotypes be tied to EV certificates?[Techniques] michael.mccormick@wellsfargo.com
• Re: Agenda: WSC WG distributed meeting, Wednesday, 2007-08-15 Thomas Roessler
• Agenda: WSC WG distributed meeting, Wednesday, 2007-08-15 Mary Ellen Zurko

Monday, 13 August 2007

• RE: ISSUE-97: Should logotypes be tied to EVcertificates?[Techniques] michael.mccormick@wellsfargo.com
• ACTION-278 Audian Paxson
• Some numbers for our use-case scenarios Close, Tyler J.
• Re: ISSUE-97: Should logotypes be tied to EV certificates?[Techniques] Serge Egelman
• Re: Summary of "What is a secure page?" discussion, first draft Anil Saldhana
• Re: Proposal: error handling / minimizing trust decisions Thomas Roessler
• reference for myspace worm? Thomas Roessler
• Re: ISSUE-97: Should logotypes be tied to EV certificates?[Techniques] Thomas Roessler
• Re: ISSUE-97: Should logotypes be tied to EV certificates?[Techniques] Stephen Farrell
• Re: ISSUE-97: Should logotypes be tied to EV certificates?[Techniques] Thomas Roessler
• RE: ISSUE-97: Should logotypes be tied to EV certificates?[Techniques] michael.mccormick@wellsfargo.com
• Re: ISSUE-6 / ACTION-239: Mobile/device browsing Jan Vidar Krey
• Meeting record: WSC WG weekly 2007-08-01 Thomas Roessler

Sunday, 12 August 2007

• Proposal: error handling / minimizing trust decisions Thomas Roessler
• ISSUE-103: Should unknown CAs and self-signed certificates be treated the same way? [Techniques] Web Security Context Working Group Issue Tracker
• Re: ISSUE-97: Should logotypes be tied to EV certificates? [Techniques] Thomas Roessler
• Re: ISSUE-78: Definitions Thomas Roessler
• Re: ISSUE-92: P3P and Internet filters Thomas Roessler
• ISSUE-102: What should be our notion of "EV" certificates? [Techniques] Web Security Context Working Group Issue Tracker
• RE: ISSUE-97: Should logotypes be tied to EV certificates? [Techniques] Dan Schutzer
• RE: first cut usability walk through Dan Schutzer

Friday, 10 August 2007

• RE: ISSUE-92: P3P and Internet filters Close, Tyler J.
• ACTION-256 completed Mike Beltzner
• RE: first cut usability walk through Audian Paxson
• Re: first cut usability walk through Mary Ellen Zurko
• Re: first cut usability walk through Serge Egelman
• RE: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Audian Paxson
• RE: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Audian Paxson
• Re: favicons: updated editor's draft [ACTION-276] Mike Beltzner
• RE: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] michael.mccormick@wellsfargo.com
• Re: first cut usability walk through Mary Ellen Zurko
• RE: ISSUE-97: Should logotypes be tied to EV certificates? [Techniques] michael.mccormick@wellsfargo.com
• Re: ISSUE-98: Which kind of logotype should be preferred? [Techniques] Ian Fette
• RE: ISSUE-98: Which kind of logotype should be preferred? [Techniques] michael.mccormick@wellsfargo.com
• Re: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Ian Fette
• Re: favicons: updated editor's draft [ACTION-276] Ian Fette
• RE: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] michael.mccormick@wellsfargo.com
• RE: favicons: updated editor's draft [ACTION-276] michael.mccormick@wellsfargo.com
• Re: favicons: updated editor's draft [ACTION-276] Ian Fette
• RE: favicons: updated editor's draft [ACTION-276] michael.mccormick@wellsfargo.com
• Re: ISSUE-77: Reference threat work in wsc-usecases Mary Ellen Zurko
• ISSUE-101: Create "visiting known site that is now malware" use case as per ACTION-275 [Note: use cases etc.] Web Security Context Working Group Issue Tracker
• Re: ISSUE-100: Update acknowledgementst to list everyone who contributed [Note: use cases etc.] Ian Fette
• WSC Open Action Items Mary Ellen Zurko
• Proactive apoligies if I falsely nag you this week Mary Ellen Zurko
• ACTION-221 Match RobustSecurityIndicators against other proposals; ensure nothing gets lost Mary Ellen Zurko
• Re: ISSUE-100: Update acknowledgementst to list everyone who contributed [Note: use cases etc.] Johnathan Nightingale
• Robustness through a shared secret Mary Ellen Zurko
• Re: ISSUE-100: Update acknowledgementst to list everyone who contributed [Note: use cases etc.] Mary Ellen Zurko
• Re: ISSUE-100: Update acknowledgementst to list everyone who contributed [Note: use cases etc.] Mike Beltzner
• ISSUE-100: Update acknowledgementst to list everyone who contributed [Note: use cases etc.] Web Security Context Working Group Issue Tracker
• Re: summary from brainstorming session in Dublin Johnathan Nightingale

Thursday, 9 August 2007

• Survey tool Audian Paxson
• Re: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Ian Fette
• Re: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Johnathan Nightingale
• Re: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Ian Fette
• Re: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Thomas Roessler
• Re: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Ian Fette
• RE: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Dan Schutzer
• Re: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Thomas Roessler
• Re: ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Johnathan Nightingale
• Re: "industry standards" Johnathan Nightingale
• Re: "industry standards" Thomas Roessler

Wednesday, 8 August 2007

• Re: "industry standards" Johnathan Nightingale
• RE: ISSUE-38: no safe haven in presentation space (from publiccomments) Close, Tyler J.
• RE: ISSUE-73: Proposed changes to process chapter Close, Tyler J.
• RE: Trusted Browser Component (Re: Action 213: write a lightningproposal on wiki) Close, Tyler J.
• RE: ISSUE-76: add file extension remark to security context information list Close, Tyler J.
• updated editor's draft: IdentitySignal Thomas Roessler
• ISSUE-99: What certificate fields must be included in the identity signal? [Techniques] Web Security Context Working Group Issue Tracker
• Re: icon internationalization Timothy Hahn
• "industry standards" Thomas Roessler
• icon internationalization Thomas Roessler
• ISSUE-98: Which kind of logotype should be preferred? [Techniques] Web Security Context Working Group Issue Tracker
• ISSUE-97: Should logotypes be tied to EV certificates? [Techniques] Web Security Context Working Group Issue Tracker
• ISSUE-96: Should support for logotypes be a SHOULD or a MAY? [Techniques] Web Security Context Working Group Issue Tracker
• Re: favicons: updated editor's draft [ACTION-276] Thomas Roessler
• Re: favicons: updated editor's draft [ACTION-276] Mike Beltzner
• favicons: updated editor's draft [ACTION-276] Thomas Roessler
• Meeting record: WSC WG weekly 2007-07-25 Thomas Roessler
• Resurfacing and regrets Shawn Duffy
• [tracker only] ACTION-275 Thomas Roessler
• FYI: trust anchor management BOF at IETF 69 (ACTION-267) Thomas Roessler

Tuesday, 7 August 2007

• Re: Agenda: WSC WG distributed meeting, Wednesday, 2007-08-08 - regrets Timothy Hahn
• Re: Agenda: WSC WG distributed meeting, Wednesday, 2007-08-08 Maritza Johnson
• Agenda: WSC WG distributed meeting, Wednesday, 2007-08-08 Mary Ellen Zurko
• Re: meeting Aug 8th regrets Anil Saldhana

Monday, 6 August 2007

• RE: first cut usability walk through Close, Tyler J.

Saturday, 4 August 2007

• meeting Aug 8th regrets Doyle, Bill

Friday, 3 August 2007

• Re: first cut usability walk through Serge Egelman
• Re: ACTION-275 Ian Fette
• Re: ACTION-275 Anil Saldhana
• Re: ACTION-252 OPEN Map out some study proposals for existing recommendations, co-ordinate with Rachna who owns u Serge Egelman
• ACTION-277 Definition of Location Bar provided in Glossary Timothy Hahn
• Re: ISSUE-73: Proposed changes to process chapter Mary Ellen Zurko
• ACTION-275 Ian Fette
• Re: WSC Open Action Items Thomas Roessler
• WSC Open Action Items Mary Ellen Zurko
• marking template sections as optional for robustness only proposals Mary Ellen Zurko
• Re: Robustness proposal - Overriding SCI presentation Thomas Roessler
• Robustness proposal - Overriding SCI presentation Mary Ellen Zurko
• Re: first cut usability walk through Thomas Roessler

Thursday, 2 August 2007

• Current state of editor's draft / IdentitySignal Thomas Roessler
• RE: New use case for malware at previously visited site Dan Schutzer
• RE: ISSUE-95: bookmark API interactions Close, Tyler J.

Wednesday, 1 August 2007

• New use case for malware at previously visited site Ian Fette
• Re: ISSUE-95: bookmark API interactions Thomas Roessler
• RE: ISSUE-77: Reference threat work in wsc-usecases Doyle, Bill
• ISSUE-95: bookmark API interactions Web Security Context Issue Tracker
• summary from brainstorming session in Dublin Thomas Roessler
• Re: first cut usability walk through Serge Egelman
• draft minutes from 8/01 call Maritza Johnson
• Re: ISSUE-77: Reference threat work in wsc-usecases Mary Ellen Zurko
• Re: first cut usability walk through Maritza Johnson
• Re: first cut usability walk through Timothy Hahn
• Re: first cut usability walk through Thomas Roessler
• first cut usability walk through Rachna Dhamija

Last message date: Friday, 31 August 2007 22:25:45 UTC