attachment

Randy, Looks good.  Two comments about Configuration State: 1>  We should mandate the use of a cryptographically secure hash function (SHA256/512) 2>  Vendors provide the set of available configuration items but the customer selects which items to include in the hash -- some they care about, some they don't. David H. Whitehead Development Engineer Lexmark International, Inc. 859.825.4914 davidatlexmarkdotcom <table width=100%> <tr valign=top> <td width=40%>Randy Turner <rturner@amalfisystems.com> Sent by: owner-ids@pwg.org 08/15/08 04:02 AM <td width=59%> <table width=100%> <tr valign=top> <td> <div align=right>To</div> <td>ids@pwg.org <tr valign=top> <td> <div align=right>cc</div> <td> <tr valign=top> <td> <div align=right>Subject</div> <td>IDS> DRAFT: IETF NEA proposal</table> <table> <tr valign=top> <td> <td></table> </table> <tt>Hi All, </tt> <tt>Please read the attached RTF and provide any feedback you may have... </tt> <tt>Please excuse the VERY simple, raw formatting I'm using - this has to be in the simplest ASCII text form possible for eventual emailing to the NEA mailing list. </tt> <tt>For now, just concentrate on the content :) :) </tt> <tt>Thanks! Randy </tt> [attachment "draft-nea-proposal.rtf" deleted by Dave Whitehead/Lex/Lexmark]