idnits 2.17.1 draft-iab-sec-cons-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 72 4 RFC 3552 6 Title: Guidelines for Writing RFC Text on Security 7 Considerations 8 Author(s): E. Rescorla, B. Korver 9 Status: Best Current Practice 10 Date: July 2003 11 Mailbox: ekr@rtfm.com, bkorver@xythos.com 12 Pages: 44 13 Characters: 110393 14 SeeAlso: BCP 72 16 I-D Tag: draft-iab-sec-cons-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3552.txt 20 All RFCs are required to have a Security Considerations section. 21 Historically, such sections have been relatively weak. This document 22 provides guidelines to RFC authors on how to write a good Security 23 Considerations section. 25 This document is a product of the Internet Architecture Board. 27 This document specifies an Internet Best Current Practices for the 28 Internet Community, and requests discussion and suggestions for 29 improvements. Distribution of this memo is unlimited. 31 This announcement is sent to the IETF list and the RFC-DIST list. 32 Requests to be added to or deleted from the IETF distribution list 33 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 34 added to or deleted from the RFC-DIST distribution list should 35 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 37 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 38 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 39 help: ways_to_get_rfcs. For example: 41 To: rfc-info@RFC-EDITOR.ORG 42 Subject: getting rfcs 44 help: ways_to_get_rfcs 46 Requests for special distribution should be addressed to either the 47 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 48 specifically noted otherwise on the RFC itself, all RFCs are for 49 unlimited distribution.echo 50 Submissions for Requests for Comments should be sent to 51 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 52 Authors, for further information.