attachment
<div dir="ltr"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div style="display:inline">FYI - important reading material for all editors<br></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div></div></div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Yoav Nir</b> <span dir="ltr"><<a href="mailto:ynir.ietf@gmail.com">ynir.ietf@gmail.com</a>></span><br>Date: Thu, Aug 25, 2016 at 9:24 AM<br>Subject: [saag] Fwd: New Version Notification for draft-nir-saag-rfc3552bis-00.txt<br>To: Security Area Advisory Group <<a href="mailto:saag@ietf.org">saag@ietf.org</a>><br><br><br><div style="word-wrap:break-word">Hi.<div><div><br></div><div>As discussed at the SAAG meeting in Berlin, this is version -00 of the the revision of RFC 3552 (“Guidelines for Writing RFC Text on Security Considerations”).</div><div><br></div><div>This version is mostly RFC 3552 with minor changes:</div><div><ul><li>Updated references where the original referenced RFCs have been obsoleted</li><li>Added missing references</li><li>Moved several references from Normative to Informative. </li><li>Minor nit fixes</li><li>New authors; old authors acknowledged in section 7.</li></ul><div><br></div><div>Now we can start talking about changes that need to be made.</div><div><br></div><div>The XML is maintained in GitHub: <a href="https://github.com/IETF-SAAG/RFC3552bis" target="_blank">https://github.com/<wbr>IETF-SAAG/RFC3552bis</a></div><div><br></div><div>Feel free to suggest changes using PRs or emails to this list. Please email this list with a link even if you submit a PR, because discussions happen on list, not on GitHub.</div><div><br></div><div>Regards</div><div><br></div><div>Yoav</div><div><br><blockquote type="cite"><div>Begin forwarded message:</div><br><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif;color:rgba(0,0,0,1.0)"><b>From: </b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif"><a href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a><br></span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif;color:rgba(0,0,0,1.0)"><b>Subject: </b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif"><b>New Version Notification for draft-nir-saag-rfc3552bis-00.<wbr>txt</b><br></span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif;color:rgba(0,0,0,1.0)"><b>Date: </b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif">25 August 2016 at 4:15:12 PM GMT+3<br></span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif;color:rgba(0,0,0,1.0)"><b>To: </b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif">"Yoav Nir" <<a href="mailto:ynir.ietf@gmail.com" target="_blank">ynir.ietf@gmail.com</a>>, "Magnus Westerlund" <<a href="mailto:magnus.westerlund@ericsson.com" target="_blank">magnus.westerlund@ericsson.<wbr>com</a>><br></span></div><br><div><div><br>A new version of I-D, draft-nir-saag-rfc3552bis-00.<wbr>txt<br>has been successfully submitted by Yoav Nir and posted to the<br>IETF repository.<br><br>Name:<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>draft-nir-saag-rfc3552bis<br>Revision:<span style="white-space:pre-wrap"> </span>00<br>Title:<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>Guidelines for Writing RFC Text on Security Considerations<br>Document date:<span style="white-space:pre-wrap"> </span>2016-08-25<br>Group:<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>Individual Submission<br>Pages:<span style="white-space:pre-wrap"> </span><span style="white-space:pre-wrap"> </span>44<br>URL: <a href="https://www.ietf.org/internet-drafts/draft-nir-saag-rfc3552bis-00.txt" target="_blank">https://www.ietf.<wbr>org/internet-drafts/draft-nir-<wbr>saag-rfc3552bis-00.txt</a><br>Status: <a href="https://datatracker.ietf.org/doc/draft-nir-saag-rfc3552bis/" target="_blank">https://datatracker.<wbr>ietf.org/doc/draft-nir-saag-<wbr>rfc3552bis/</a><br>Htmlized: <a href="https://tools.ietf.org/html/draft-nir-saag-rfc3552bis-00" target="_blank">https://tools.ietf.org/<wbr>html/draft-nir-saag-<wbr>rfc3552bis-00</a><br><br><br>Abstract:<br> All RFCs are required to have a Security Considerations section.<br> Historically, such sections have been relatively weak. This document<br> provides guidelines to RFC authors on how to write a good Security<br> Considerations section.<br><br><br><br><br>Please note that it may take a couple of minutes from the time of submission<br>until the htmlized version and diff are available at <a href="http://tools.ietf.org" target="_blank">tools.ietf.org</a>.<br><br>The IETF Secretariat<br><br></div></div></blockquote></div><br></div></div></div><br>______________________________<wbr>_________________<br>
saag mailing list<br>
<a href="mailto:saag@ietf.org">saag@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/saag" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/saag</a><br>
<br></div><br></div>