Protocol Action: Guidelines for Writing RFC Text on Security Considerations to BCP
The IESG <iesg-secretary@ietf.org> Fri, 14 February 2003 00:00 UTC
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21608; Thu, 13 Feb 2003 19:00:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 18jTEP-0000JO-00 for ietf-announce-list@ran.ietf.org; Thu, 13 Feb 2003 18:57:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 18jTEF-0000Hl-00 for all-ietf@ran.ietf.org; Thu, 13 Feb 2003 18:57:19 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21044; Thu, 13 Feb 2003 18:50:16 -0500 (EST)
Message-Id: <200302132350.SAA21044@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Guidelines for Writing RFC Text on Security Considerations to BCP
Date: Thu, 13 Feb 2003 18:50:16 -0500
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
The IESG has approved the Internet-Draft 'Guidelines for Writing RFC
Text on Security Considerations' <draft-iab-sec-cons-03.txt> as a BCP.
This document is the product of the Internet Architecture Board.
The IESG contact persons are Erik Nordmark and Thomas Narten.
Technical Summary
All RFCs are required by [RFC 2223] to contain a Security Considera-
tions section. The purpose of this is both to encourage document
authors to consider security in their designs and to inform the
reader of relevant security issues. This memo is intended to provide
guidance to RFC authors in service of both ends.
Working Group Summary
This document is not a product of a working group.
Protocol Quality
This document has been reviewed for the IESG by Erik Nordmark.