WSC Open Action Items

1) Do not let your Action Items go past due. It creates overhead for me, 
which is time I could spend on the content of the group, instead of trying 
to figure out what I should do about overdue action items. 

2) Complete your Action Item by the Due Date. Make sure to send an email 
to publis-wsc-wg with the exact ID (upper case, with the "-", for example, 
ACTION-3) for tracking purposes. 

3) Do NOT close them yourself; I'll do that. That's how they get into the 
agenda, so I can give you props during the meeting. 

4) If a personal emergency arises so that at the last minute you cannot 
possibly complete the Action Item by the Due Date, reset the Due Date. It 
takes only 30 seconds.

Thank you to all of you who do all this without regular personal 
reminders. 


[OPEN] ACTION-211: George Staikos to add robustness info to wiki that may 
turn into recommendation - due 2007-06-30

[OPEN] ACTION-214: Bill Doyle to solicit commentary on Threat Trees from 
MITRE INFOSEC community - due 2007-06-15

[OPEN] ACTION-221: Mary Ellen Zurko to Match RobustSecurityIndicators 
against other proposals; ensure nothing gets lost - due 2007-07-08

[OPEN] ACTION-225: Serge Egelman to "Are users necessary?"-- Build 
taxonomy of trust situations where user intervention is required - due 
2007-06-24

[OPEN] ACTION-226: Tyler Close to Improve description of SSL/TLS history 
(sec.8.1) - due 2007-06-18

[OPEN] ACTION-230: Bill Doyle to Define robustness for WSC glossary - due 
2007-12-06

[OPEN] ACTION-232: Serge Egelman to Share results from his study once he 
has them - due 2007-06-30

[OPEN] ACTION-235: Rachna Dhamija to Update / create a user testing 
timeline with things like IRB turnaround, setup, etc. - due 2007-06-27

[OPEN] ACTION-236: Rachna Dhamija to Track donations of time and resources 
for usability testing - due 2007-06-27

[OPEN] ACTION-238: Rachna Dhamija to Create and document user testing plan 
(with links to timeline, donations, prototypers, etc) - due 2007-06-27

[OPEN] ACTION-239: Jan Vidar Krey to Document security robustness 
practises on mobile and embedded devices (such as phones, etc.) - due 
2007-06-27

[OPEN] ACTION-240: Stephen Farrell to pick up on ACTION-177, complement 
with review of TLS spec and exceptions given there; goal is to limit user 
interaction when not needed - due 2007-06-26

[OPEN] ACTION-241: Thomas Roessler to Look at better issue tracking for 
rec-track documents - due 2007-08-21

[OPEN] ACTION-243: Mary Ellen Zurko to Propose link from note to threat 
trees - due 2007-06-27

[OPEN] ACTION-248: Johnathan Nightingale to Ensure that the robustness 
stuff (MozillaCurrentPractises) ends up in the recommendations - due 
2007-06-22

[OPEN] ACTION-252: Serge Egelman to Map out some study proposals for 
existing recommendations, co-ordinate with Rachna who owns usability 
testing plan in general - due 2007-07-06

[OPEN] ACTION-256: Mike Beltzner to Summarize and bring back issues to 
working group - due 2007-06-15

[OPEN] ACTION-257: Rachna Dhamija to Expand on the proposal and 
incorporate today\\\\'s discussions - due 2007-06-25

[OPEN] ACTION-259: Rachna Dhamija to Work with Stephen, Chuck to revisit 
threat trees; work out process to join them to substantial work - due 
2007-06-27

[OPEN] ACTION-260: Phillip Hallam-Baker to to write up non-indication cert 
attribute - due 2007-06-29