[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BCP 72, RFC 3552 on Guidelines for Writing RFC Text on Security Considerations
A new Request for Comments is now available in online RFC libraries.
Title: Guidelines for Writing RFC Text on Security
Author(s): E. Rescorla, B. Korver
Status: Best Current Practice
Date: July 2003
Mailbox: firstname.lastname@example.org, email@example.com
SeeAlso: BCP 72
I-D Tag: draft-iab-sec-cons-03.txt
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
This document is a product of the Internet Architecture Board.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.