RFC 3552: Guidelines for Writing RFC Text on Security Considerations
In plain English — editorial summary, not part of the RFC
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 Considerations section. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3552
- Published
- July 2003
- Authors
- E. Rescorla; B. Korver
- Status
- BEST CURRENT PRACTICE
- Stream
- IAB
- Area
- —
- Pages
- 44
- Also known as
- BCP72
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7749The "xml2rfc" Version 2 VocabularyObsoleted
February 2016
- RFC 7994Requirements for Plain-Text RFCsUpdated
December 2016
- RFC 7996SVG Drawings for RFCs: SVG 1.2 RFCObsoleted
December 2016
- RFC 5406Guidelines for Specifying the Use of IPsec Version 2Current
February 2009
- RFC 1199Request for Comments Summary Notes: 1100-1199Current
December 1991
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?