attachment-0001
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><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;">[Revised w/comments]<div><br></div><div>Global: Use document title references instead of RFC references.</div><div><br></div><div>Section 1: Add best practice is to use TLS/RFC 5425 when transmitting log information.</div><div><br></div><div>Page 16, right before Section 5: Remove blank page</div><div><br></div><div>Section 5.1.8: The list of user roles should be alphabetized.</div><div><br></div><div>Section 9: Add best practice is to use TLS/RFC 5425 when transmitting log information, per section 6 item 3 conformance requirement.<br><br>Section 9: Missing references to Transport Layer Security (TLS) Transport Mapping for Syslog [RFC5425], Transmission of Syslog Messages over UDP [RFC5426], Datagram Transport Layer Security Version 1.2 [RFC6347], and Datagram Transport Layer Security (DTLS) Transport Mapping for Syslog</div><div><br></div><div>Section 10.1: Missing references to Datagram Transport Layer Security Version 1.2 [RFC6347] and Datagram Transport Layer Security (DTLS) Transport Mapping for Syslog</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div>__________________________________________________</div><div style="font-family: Helvetica; font-size: medium;">Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<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>