attachment
<div dir="ltr"><div><div><div>Hi,<br><br></div>Quoting from Dave Harrington's note on IETF SACM WG list today:<br><br>"You seem to be making security optional, with "MAY support mutual<br>
authentication" etc.
Please look at RFC3365, which specifies an IETF <br>requirement for IETF
standards.<br>
<br>The IESG will consider the RFC3365 requirements when deciding whether <br>to
approve our documents.<br>
<br>
If we are going to talk about "policy", we should make sure our terminology<br>
is consistent with previous IETF publications related to policy. I'd start with <br>RFC4949, since we are a SEC area WG.<br><br>We should probably at least look at:<br>
<br>RFC2753 - A Framework for Policy-based Admission Control<br>
RFC2768 - Network Policy and Services: A Report of a Workshop on Middleware<br>
RFC3060 - Policy Core Information Model -- Version 1 Specification<br>
RFC3198 - Terminology for Policy-Based Management<br>
RFC3571 - Framework Policy Information Base for Usage Feedback<br><br>Policy-based management, of which at least part of SACM appears to be a<br>
subset, has been discussed in the IETF.
There are a number of IETF standards <br>and documents that resulted from prior
efforts.<br><br>A great deal of thought went into the work, and we should not ignore what<br>
has already been done.<br>
<br>RFC3060 has a data model (and an inherent information model) for describing<br>
policies, including policies, groups, rules, properties of rules (enabled,
priority, <br>etc.), conditions, periods, actions, constraints, repository, associations, <br>aggregations, components, and so on.<br>
<br>They may not apply directly to the work we are doing, but the discussions we<br>
have been having certainly seem to be related to this prior work.<br><br>
RFC3571 has an information model for monitoring the usage of policies.<br>
This includes allowing one architectural entity (I'll be glad when we reach<br>consensus on some terms we can use to talk about these things)<br>
<br>To query another architectural entity (such as an evaluator) to determine
which<br>policies (evaluations) are supported, intervals for periodic
reporting, actions, <br>thresholds, etc.<br>
<br>
Much of the work on policy was a joint effort with people from DMTF."<br><br><br></div>Cheers,<br></div>- Ira<br><br><br><div><div><div><div><div>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music/High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>
mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline">
</div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div>
</div></div></div></div></div>