Skip to main content

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

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Yoav Nir , Magnus Westerlund
Last updated 2017-02-26 (Latest revision 2016-08-25)
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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
Magnus Westerlund

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