Guidelines for Writing RFC Text on Security Considerations
draft-iab-secwks-sec-guidelines-00
| Document | Type | Expired Internet-Draft (iab) | |
|---|---|---|---|
| Author | Randall Atkinson | ||
| Last updated | 1997-07-25 | ||
| Stream | Internet Architecture Board (IAB) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | IAB state | (None) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (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-iab-secwks-sec-guidelines-00.txt
https://www.ietf.org/archive/id/draft-iab-secwks-sec-guidelines-00.txt
Abstract
The 'Security Considerations' section of an RFC is a mechanism via which the authors/editors of an RFC communicate to the reader the security issues (including threats) of the RFC topic and discuss mechanisms for mitigating or eliminating those threats. Each risk reduction mechanism not documented directly in that RFC should cite another RFC or document which describes the risk reduction mechanism.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)