attachment-0001
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Hi All,</div><div><br></div><div>As part of my contribution to an action item related to monitoring SCAP (Security Content Automation Protocol), I wanted to make known that a new working group has been proposed within the IETF, currently named "SACM"</div><div><br></div><div>The proposed working group is currently just a "BOF", and is still under consideration.</div><div><br></div><div>However, there is a mailing list created for discussion. You can subscribe to the list by visiting this link: <a href="https://www.ietf.org/mailman/listinfo/sacm">https://www.ietf.org/mailman/listinfo/sacm</a></div><div><br></div><div>The description of the list is included below:</div><div><br></div><div>This list is for discussions relating to the applicability of the SCAP content formats to current and emerging IETF protocols. Current SCAP specifications and Internet use scenarios are in scope for this discussion list. Current SCAP specifications include the Common Configuration Enumeration (CCE), Common Vulnerability Evaluation (CVE), Common Platform Enumeration (CPE), Open Vulnerability and Assessment Language (OVAL), and Extensible Configuration Checklist Description Format (XCCDF). <br><br><br>Randy</div><div><br><br></div><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.
</body></html>