attachment-0001
<br><font size=2 face="sans-serif">Randy,</font>
<br>
<br><font size=2 face="sans-serif">I think this would be a topic for the
IDS group and not for the NAP team meeting. Other opinions ...</font>
<br>
<br><font size=2 face="sans-serif">dhw</font>
<br>
<br><font size=2 face="sans-serif">David H. Whitehead<br>
Development Engineer<br>
Lexmark International, Inc.<br>
859.825.4914<br>
davidatlexmarkdotcom</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Randy Turner <rturner@amalfisystems.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: ids-bounces@pwg.org</font>
<p><font size=1 face="sans-serif">07/20/2009 01:05 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">ids@pwg.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [IDS] IDS CC Today at 4:00 PM EST</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br>
<br><font size=3>Hi Dave & List,</font>
<br>
<br><font size=3>Time permitting, I would also like to see if there is any opportunity for incorporating standard remediation methods</font>
<br><font size=3>for "configuration" of device attributes that conflict with site security policy....</font>
<br>
<br><font size=3>Randy</font>
<br>
<br><font size=3>On Jul 20, 2009, at 9:11 AM, Dave Whitehead wrote:</font>
<br>
<br>
<br><font size=2>Just a reminder of today's conference call ...</font><font size=3>
</font>
<br>
<br><font size=2>dhw</font><font size=3> </font>
<br>
<br><font size=2>David H. Whitehead</font>
<br><font size=2>Development Engineer</font>
<br><font size=2>Lexmark International, Inc.</font>
<br><font size=2>859.825.4914</font>
<br><font size=2>davidatlexmarkdotcom</font><font size=3> </font>
<br><font size=2>dhwatinsightbbdotcom</font><font size=3> </font>
<br>
<br><font size=2>==========================================================</font><font size=3>
</font>
<br>
<br><font size=3>Call-in toll-free number (US/Canada): 1-866-469-3239 </font>
<br>
<br><font size=3>Call-in toll number (US/Canada): 1-650-429-3300 </font>
<br>
<br><font size=3>Call-in toll number (US/Canada): 1-408-856-9570 </font>
<br>
<br><font size=3>Attendee access code: (by request only) </font>
<br>
<br>
<br><font size=2>IDS CC Agenda </font><font size=3> </font>
<br><font size=2>July 20, 2009</font><font size=3> </font>
<br>
<br><font size=2>Assign Scribe</font><font size=3> </font>
<br><font size=2>PWG IP Statement</font><font size=3> </font>
<br><font size=2>Review Action Items</font><font size=3> </font>
<br><font size=2>IDS-NAP Meeting Agenda</font><font size=3> </font>
<br><font size=2> Assign Scribe</font><font size=3>
</font>
<br><font size=2> PWG IP Statement</font><font size=3>
</font>
<br><font size=2> Introductions</font><font size=3>
</font>
<br><font size=2> Short overview of NAP (Microsoft)</font><font size=3>
</font>
<br><font size=2> How the IDS group proposes
to map attributes to the NAP protocol (IDS)</font><font size=3> </font>
<br><font size=2> Discuss the alignment of attributes</font><font size=3>
</font>
<br><font size=2> Discuss questions to the NAP
team</font><font size=3> </font>
<br><font size=2> Discuss remote attestation
– how to make sure the remote device does not lie about its statement
of health (without a TPM, how reliable can it be?) Is this an important
concern of the NAP team?</font><font size=3> </font>
<br><font size=2> Review the questions previously
submitted to the NAP team in April. Expand on the answers as possible.</font><font size=3>
</font>
<br><font size=2>Other Announcements</font><font size=3> </font>
<br><font size=2>Adjourn</font><font size=3> </font>
<br><font size=3>-- </font>
<br><font size=3>This message has been scanned for viruses and </font>
<br><font size=3>dangerous content by </font><a href=http://www.mailscanner.info/><font size=3 color=blue><b><u>MailScanner</u></b></font></a><font size=3>,
and is </font>
<br><font size=3>believed to be clean. _______________________________________________</font>
<br><font size=3>ids mailing list</font>
<br><a href=mailto:ids@pwg.org><font size=3 color=blue><u>ids@pwg.org</u></font></a>
<br><font size=3>https://www.pwg.org/mailman/listinfo/ids</font>
<br>
<br>
<br><font size=3>-- </font>
<br><font size=3>This message has been scanned for viruses and </font>
<br><font size=3>dangerous content by </font><a href=http://www.mailscanner.info/><font size=3 color=blue><b><u>MailScanner</u></b></font></a><font size=3>,
and is </font>
<br><font size=3>believed to be clean. </font>
<br><tt><font size=2>_______________________________________________<br>
ids mailing list<br>
ids@pwg.org<br>
https://www.pwg.org/mailman/listinfo/ids</font></tt>
<br>
<br>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.