FYI - important reading material for all editors
---------- Forwarded message ----------
From: Yoav Nir <ynir.ietf at gmail.com>
Date: Thu, Aug 25, 2016 at 9:24 AM
Subject: [saag] Fwd: New Version Notification for
To: Security Area Advisory Group <saag at ietf.org>
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
This version is mostly RFC 3552 with minor changes:
- Updated references where the original referenced RFCs have been
- Added missing references
- Moved several references from Normative to Informative.
- Minor nit fixes
- New authors; old authors acknowledged in section 7.
Now we can start talking about changes that need to be made.
The XML is maintained in GitHub: https://github.com/IETF-SAAG/RFC3552bis
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.
Begin forwarded message:
*From: *internet-drafts at ietf.org
*Subject: **New Version Notification for draft-nir-saag-rfc3552bis-00.txt*
*Date: *25 August 2016 at 4:15:12 PM GMT+3
*To: *"Yoav Nir" <ynir.ietf at gmail.com>, "Magnus Westerlund" <
magnus.westerlund at ericsson.com>
A new version of I-D, draft-nir-saag-rfc3552bis-00.txt
has been successfully submitted by Yoav Nir and posted to the
Title: Guidelines for Writing RFC Text on Security Considerations
Document date: 2016-08-25
Group: Individual Submission
All RFCs are required to have a Security Considerations section.
Historically, such sections have been relatively weak. This document
provides guidelines to RFC authors on how to write a good Security
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
saag mailing list
saag at ietf.orghttps://www.ietf.org/mailman/listinfo/saag
-------------- next part --------------
An HTML attachment was scrubbed...