Guidelines for Writing RFC Text on Security Considerations
RFC 3552, “Guidelines for Writing RFC Text on Security Considerations”, is a Best Current Practice document published in July 2003 by E. Rescorla, B. Korver. It has since been updated by RFC 8996, RFC 9416. The canonical text is published by the RFC Editor.
Abstract
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.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 3552 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control
- RFC 3553 An IETF URN Sub-namespace for Registered Protocol Parameters
- RFC 3550 RTP: A Transport Protocol for Real-Time Applications
- RFC 3554 On the Use of Stream Control Transmission Protocol with IPsec
- RFC 3549 Linux Netlink as an IP Services Protocol
- RFC 3555 MIME Type Registration of RTP Payload Formats
- RFC 3548 The Base16, Base32, and Base64 Data Encodings
- RFC 3556 Session Description Protocol Bandwidth Modifiers for RTP Control Protocol Bandwidth