attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:x = "urn:schemas-microsoft-com:office:excel" xmlns:p = "urn:schemas-microsoft-com:office:powerpoint" xmlns:a = "urn:schemas-microsoft-com:office:access" xmlns:dt = "uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s = "uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs = "urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b = "urn:schemas-microsoft-com:office:publisher" xmlns:ss = "urn:schemas-microsoft-com:office:spreadsheet" xmlns:c = "urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc = "urn:schemas-microsoft-com:office:odc" xmlns:oa = "urn:schemas-microsoft-com:office:activation" xmlns:html = "http://www.w3.org/TR/REC-html40" xmlns:q = "http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D = "DAV:" xmlns:mt = "http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 = "http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois = "http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir = "http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds = "http://www.w3.org/2000/09/xmldsig#" xmlns:dsp = "http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc = "http://schemas.microsoft.com/data/udc" xmlns:xsd = "http://www.w3.org/2001/XMLSchema" xmlns:sub = "http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec = "http://www.w3.org/2001/04/xmlenc#" xmlns:sp = "http://schemas.microsoft.com/sharepoint/" xmlns:sps = "http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs = "http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf = "http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p = "http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf = "http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss = "http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi = "http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi = "http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver = "http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels = "http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp = "http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t = "http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m = "http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl = "http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl = "http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.6001.18203" name=GENERATOR> <STYLE>@font-face { font-family: Cambria Math; } @font-face { font-family: Calibri; } @font-face { font-family: Tahoma; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } A:link { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } A:visited { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto } TT { FONT-FAMILY: "Courier New"; mso-style-priority: 99 } SPAN.EmailStyle19 { COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply } .MsoChpDefault { mso-style-type: export-only } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US vLink=purple link=blue bgColor=#ffffff> <DIV> </DIV> <DIV> </DIV> <DIV>Following up on Bill's comments regarding "a bit more vigor" with regards to TCG goals, I think there is an area that is ripe for pursuing that has</DIV> <DIV>been more or less avoided by the PWG IDS group, and that is "remediation"; preferably "automated remediation".</DIV> <DIV> </DIV> <DIV>Randy</DIV> <BLOCKQUOTE dir=ltr style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV> <DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black">From: <A title=wamwagner@COMCAST.NET href="mailto:wamwagner@COMCAST.NET">William Wagner</A> </DIV> <DIV style="FONT: 10pt arial">To: <A title=STDS-2600@LISTSERV.IEEE.ORG href="mailto:STDS-2600@LISTSERV.IEEE.ORG">STDS-2600@LISTSERV.IEEE.ORG</A> </DIV> <DIV style="FONT: 10pt arial">Sent: Friday, April 10, 2009 9:32 AM</DIV> <DIV style="FONT: 10pt arial">Subject: Re: [2600] IDS> minutes from April 8 2009 TCG HCWG charter discussion teleconference</DIV> <DIV> </DIV> <DIV class=Section1> All,<o:p></o:p> <o:p> </o:p> I suggest that the TCG HCWG, being part of the TCG and privy to the objectives and plans of the TCG, should concentrate on the how  hardcopy equipment  is to be compatible with the protocols, specification and practices that TCG is developing. It does not seem reasonable either from the  industry  of from the TCG perspective that the TCG HCWG go beyond consideration of TCG principals with respect to hardcopy equipment. This is not to suggest that there is little work there. Understanding what the TCG is doing and applying it to hardcopy equipment, developing use cases, and either developing or identifying solutions would seem to be important both to the meet the objectives of the TCG and to provide the industry with interoperable approaches.<o:p></o:p> <o:p> </o:p> However, the TCG HCWG should seek to address the hardcopy specific aspects in a way that is not incompatible with approaches being developed by the industry to satisfy similar objectives under different auspices.  It is unclear what body, if any, will seek to standardize methods of meeting the requirements in IEEE2600; that is a separate issue. However, following up on a request from the TCG HCWG,  the PWG IDS group is seeking to address the hardcopy equipment health attributes in a way compatible with both TCG/NEA and NAP (and perhaps the several other proprietary network access control methods in existence). Therefore, some degree of mutual cooperation and overlap is highly desirable.<o:p></o:p> <o:p> </o:p> Perhaps I see the TCG HCWG continuing to operate as it has with respect to network access control, but with a bit more vigor. That is, the HCWG might best act in determining HC specific use cases for TCG objectives, evaluating whether TCG or other protocols or procedures are effective and practical in addressing these objectives, and if necessary developing requirements specifications  for what additional features  to existing solutions or completely new solutions are necessary. However,  I suggest that the actual designs addressing any such requirements specifications best be done by a broader, non restricted industry group that can consider them in a wider non-TCG specific sense.<o:p></o:p> <o:p> </o:p> I think these sentiments may  be in agreement with Dave and Randy�s comments. <o:p></o:p> <o:p> </o:p> Bill Wagner<o:p></o:p> <o:p> </o:p> <DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none"> From: owner-ids@pwg.org [mailto:owner-ids@pwg.org] On Behalf Of Dave Whitehead Sent: Friday, April 10, 2009 9:55 AM To: Randy Turner Cc: ids@pwg.org; owner-ids@pwg.org; STDS-2600@LISTSERV.IEEE.ORG Subject: Re: IDS> minutes from April 8 2009 TCG HCWG charter discussion teleconference<o:p></o:p></DIV> <o:p> </o:p> All, I agree with Randy that the goals and objectives of the various bodies should not overlap.  The goals and objectives of the TCG HCWG need to be complementary to those of the P2600 and PWG IDS groups. dhw David H. Whitehead Development Engineer Lexmark International, Inc. 859.825.4914 davidatlexmarkdotcom <o:p></o:p> <TABLE class=MsoNormalTable style="WIDTH: 100%" cellPadding=0 width="100%" border=0> <TBODY> <TR> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; WIDTH: 40%; PADDING-TOP: 0.75pt" vAlign=top width="40%"> "Randy Turner" <rturner@amalfisystems.com> Sent by: owner-ids@pwg.org <o:p></o:p> 04/10/09 01:01 AM <o:p></o:p></TD> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; WIDTH: 59%; PADDING-TOP: 0.75pt" vAlign=top width="59%"> <TABLE class=MsoNormalTable style="WIDTH: 100%" cellPadding=0 width="100%" border=0> <TBODY> <TR> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top> To<o:p></o:p></TD> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top> <STDS-2600@LISTSERV.IEEE.ORG> <o:p></o:p></TD></TR> <TR> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top> cc<o:p></o:p></TD> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top> <ids@pwg.org> <o:p></o:p></TD></TR> <TR> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top> Subject<o:p></o:p></TD> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top> IDS> minutes from April 8 2009 TCG HCWG charter discussion teleconference<o:p></o:p></TD></TR></TBODY></TABLE> <o:p> </o:p> <TABLE class=MsoNormalTable cellPadding=0 border=0> <TBODY> <TR> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top></TD> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE> <TT>Hi All,</TT> <TT>After reading the minutes from the latest TCG HCWG re-chartering discussion,</TT> <TT>I have the following comment...</TT> <TT>I think, at a minimum, any new charter for the TCG HCWG should be filtered</TT> <TT>through the goals and objectives of the p2600 work</TT> <TT>and the PWG-IDS activity to determine any new objectives.</TT> <TT>in other words,</TT> <TT>o1 = set of p2600 goals and objectives (both core standard and protection</TT> <TT>profiles)</TT> <TT>o2 = set of PWG IDS goals and objectives (including NEA/TNC + IDS</TT> <TT>attributes)</TT> <TT>o3 = The union of o1 and o2 (i.e., o1 U o2)</TT> <TT>o4 = The set of proposed TCG HCWG goals and objectives</TT> <TT>The intersection of o3 and o4 should be the empty set</TT> <TT>Thanks,</TT> <TT>Randy</TT> <TT>----- Original Message -----</TT> <TT>From: "Brian Smithson" <brian.smithson@RICOH-USA.COM></TT> <TT>To: <STDS-2600@LISTSERV.IEEE.ORG></TT> <TT>Sent: Thursday, April 09, 2009 1:13 PM</TT> <TT>Subject: [2600] minutes from April 8 2009 TCG HCWG charter discussion</TT> <TT>teleconference</TT> <TT>> Please see the attached meeting minutes from yesterday's teleconference</TT> <TT>> discussion of the TCG Hardcopy Workgroup charter revision.</TT> <TT>></TT> <TT>> Many thanks to Shah Bhatti for leading the discussion, Seigo Kotani for</TT> <TT>> acting as interim chair and BoD liaison, Steve Hanna for providing</TT> <TT>> perspective from the TNC WG, and Lee Farrell for contributing his</TT> <TT>> excellent notes to the production of these minutes.</TT> <TT>></TT> <TT>> --</TT> <TT>> Regards,</TT> <TT>> Brian Smithson</TT> <TT>> PM, Security Research</TT> <TT>> PMP, CISSP, CISA, ISO 27000 PA</TT> <TT>> Advanced Imaging and Network Technologies</TT> <TT>> Ricoh Americas Corporation</TT> <TT>> (408)346-4435</TT> <TT>></TT> <TT>></TT> <o:p></o:p></DIV></BLOCKQUOTE></BODY></HTML>