Guidelines for Writing RFC Text on Security Considerations
draft-nir-saag-rfc3552bis-00

Document Type Expired Internet-Draft (individual)
Last updated 2017-02-26 (latest revision 2016-08-25)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-nir-saag-rfc3552bis-00.txt

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.

Authors

Yoav Nir (ynir.ietf@gmail.com)
Magnus Westerlund (magnus.westerlund@ericsson.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)