P2600 : Hardcopy Device and System Security

Action Items

  


 

Action Items from the P2600 Standards Development Project, as of December 18, 2008, are listed here. To make inquiries or request changes, please contact the P2600 Secretary, brian.smithson@ricoh-usa.com.

This file is also available as an easier-to-read Excel worksheet.
 
Action Item # Entry date Original Due date Planned date of completion Actual date of completion Assignee
[ -> others to
do the same]		 Clause Section Action Status
A=abandoned
C=complete
H=on hold
P=partial		 Disposition
246 9/6/2006 10/16/2006     Wright general   Find out what copyright license terms could be offered on an IEEE std and what that means for a published Protection Profile P Discussions and negotiations are happening.
396 8/21/2007 11/15/2007 1/22/2009   Smithson all   send AI reminders (again)    
485 10/24/2008 11/27/2008     Nevo Guide   ask atsec about the appropriate escalation path for questions about a PP (see October comment #46)    
487 12/11/2008 12/12/2008     Smithson PPs   ask atsec about scope of I&A audit items (includes logout?) and relationship with audit item for SSL.3 P inquiry sent to atsec
488 12/11/2008 2/5/2009     Smithson PPs   fix heading/text problem in PP-A (and others?) around clause 18.2    
489 12/11/2008 2/5/2009     Smithson PP-B   correct NVS package in PP-B -- should apply only to TSF Data    
490 12/11/2008 2/5/2009     Smithson PPs   update drafts according to approved comments from Plantation meeting    
491 12/12/2008 12/19/2008     Smithson PPs   update PP eval schedule (remove old stuff, add additional RevCom milestones, show final IEEE publication 3-6 months from approval)    
492 12/12/2008 2/5/2009     Sukert PP-E   work with Harry Lewis to get a core group established and then look at getting a PAR for a new project    
                     
                     
COMPLETED ITEMS APPEAR BELOW:
1 5/19/2005 7/11/2005 8/1/2005 8/4/2005 Smithson     post details for September meeting at Ricoh C  
2 4/12/2005 5/19/2005 9/1/2005 1/4/2006 Wright 2, annex   update bibliography C  
3 4/12/2005 5/19/2005 9/1/2005 10/11/2005 Sukert 3, annex   add terms from section 2 C draft in 2005-10
4 4/12/2005 5/19/2005 9/1/2005 8/4/2005 Smithson 5   reference mitigation techniques in section 3 rather than using ones from NIST document C  
5 4/12/2005 5/19/2005 9/1/2005 8/5/2005 Smithson 6   define assets (from section 3) C  
6 4/12/2005 5/19/2005 9/1/2005 10/11/2005 Sukert 3, annex   add acronyms from old sections 2 and 4 C draft in 2005-10
7 4/12/2005 5/19/2005 9/1/2005 8/4/2005 Smithson 5   add explanatory text about choosing security env based on asset value rather than topology or name of env C  
8 4/12/2005 5/19/2005   9/15/2005 Haapanen 7   decide if we want to include security env columns in final doc A restructuring of the presentation of threats removed this column.
9 4/12/2005 5/19/2005 9/1/2005   Haapanen 8   complete missing sections C  
10 4/12/2005 5/19/2005 9/1/2005 8/5/2005 Smithson 8, 6   move asset section from section 3 to section 1 C  
11 4/12/2005 5/19/2005 9/1/2005   Haapanen 8   finish actual recommendations, align with clause 7 threats C aligned; recommendations largely complete
12 5/19/2005 7/11/2005 9/16/2005 2/23/2006 Smithson new PP annex   paste NIAP robustness level text into a new annex (see NIAP instruction #5); ensure that our definitions and theirs are consistent C consistency issues to be discussed at March 06 meeting
13 5/19/2005 7/11/2005   6/12/2006 Smithson PPs   consider NIAP instruction #3, modifying their text to suit our target environment (for NIAP environments) C I suggest that we insert this block of text as a new section 3.1 in each PP (choosing the appropriate robustness for each PP). See email discussion.
14 5/19/2005 7/11/2005 9/1/2005 4/26/2006 Smithson-> Nevo PP   add ALC_FLR2 and AVA_MSU.1 per NIAP instruction #4 A subsumed by AI#68
15 5/19/2005 7/11/2005     Smithson -> Nevo PP