BCP 146, RFC 5406 on Guidelines for Specifying the Use of IPsec Version 2
rfc-editor@rfc-editor.org Wed, 25 February 2009 23:29 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC7293A6AE6 for <ietf-announce@core3.amsl.com>; Wed, 25 Feb 2009 15:29:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.986
X-Spam-Level:
X-Spam-Status: No, score=-16.986 tagged_above=-999 required=5 tests=[AWL=0.613, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IYzqCa5IrGuk for <ietf-announce@core3.amsl.com>; Wed, 25 Feb 2009 15:29:46 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id CE1503A6AD9 for <ietf-announce@ietf.org>; Wed, 25 Feb 2009 15:29:46 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 76757233E98; Wed, 25 Feb 2009 15:29:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 146, RFC 5406 on Guidelines for Specifying the Use of IPsec Version 2
From: rfc-editor@rfc-editor.org
Message-Id: <20090225232912.76757233E98@bosco.isi.edu>
Date: Wed, 25 Feb 2009 15:29:12 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2009 23:29:47 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 146
RFC 5406
Title: Guidelines for Specifying the Use
of IPsec Version 2
Author: S. Bellovin
Status: Best Current Practice
Date: February 2009
Mailbox: bellovin@acm.org
Pages: 13
Characters: 30393
See Also: BCP0146
I-D Tag: draft-bellovin-useipsec-10.txt
URL: http://www.rfc-editor.org/rfc/rfc5406.txt
The Security Considerations sections of many Internet Drafts say, in
effect, "just use IPsec". While this is sometimes correct, more
often it will leave users without real, interoperable security
mechanisms. This memo offers some guidance on when IPsec Version 2
should and should not be specified. This document specifies an Internet
Best Current Practices for the Internet Community, and requests
discussion and suggestions for improvements.
BCP: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
USC/Information Sciences Institute