[IPsec] FW: BCP 146, RFC 5406 on Guidelines for Specifying the Use of IPsec Version 2
Yaron Sheffer <yaronf@checkpoint.com> Thu, 26 February 2009 06:17 UTC
Return-Path: <yaronf@checkpoint.com>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EE5C28C1EE for <ipsec@core3.amsl.com>; Wed, 25 Feb 2009 22:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 Hk4eSFLtRNGO for <ipsec@core3.amsl.com>; Wed, 25 Feb 2009 22:17:09 -0800 (PST)
Received: from dlpdemo.checkpoint.com (dlpdemo.checkpoint.com [194.29.32.54]) by core3.amsl.com (Postfix) with ESMTP id EE9B228C1ED for <ipsec@ietf.org>; Wed, 25 Feb 2009 22:17:08 -0800 (PST)
Received: by dlpdemo.checkpoint.com (Postfix, from userid 105) id 009952AC003; Thu, 26 Feb 2009 08:17:28 +0200 (IST)
Received: from michael.checkpoint.com (michael.checkpoint.com [194.29.32.68]) by dlpdemo.checkpoint.com (Postfix) with ESMTP id AB5C52AC001 for <ipsec@ietf.org>; Thu, 26 Feb 2009 08:17:27 +0200 (IST)
X-CheckPoint: {49A63316-10000-88241DC2-7B6}
Received: from il-ex01.ad.checkpoint.com (localhost [127.0.0.1]) by michael.checkpoint.com (8.12.10+Sun/8.12.10) with ESMTP id n1Q6HQsZ020880 for <ipsec@ietf.org>; Thu, 26 Feb 2009 08:17:27 +0200 (IST)
Received: from il-ex01.ad.checkpoint.com ([194.29.32.26]) by il-ex01.ad.checkpoint.com ([194.29.32.26]) with mapi; Thu, 26 Feb 2009 08:17:26 +0200
From: Yaron Sheffer <yaronf@checkpoint.com>
To: "ipsec@ietf.org" <ipsec@ietf.org>
Date: Thu, 26 Feb 2009 08:17:24 +0200
Thread-Topic: BCP 146, RFC 5406 on Guidelines for Specifying the Use of IPsec Version 2
Thread-Index: AcmXoRQBtQ6LvNQ9SkCbltN2qvhdBgAOI2mw
Message-ID: <7F9A6D26EB51614FBF9F81C0DA4CFEC8D9A7BED544@il-ex01.ad.checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [IPsec] FW: BCP 146, RFC 5406 on Guidelines for Specifying the Use of IPsec Version 2
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2009 06:17:10 -0000
This BCP has been more than 6 years in the making, it is still mostly relevant, but not entirely. Yaron -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org Sent: Thursday, February 26, 2009 1:29 To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org Cc: rfc-editor@rfc-editor.org Subject: BCP 146, RFC 5406 on Guidelines for Specifying the Use of IPsec Version 2 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 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce Scanned by Check Point Total Security Gateway. Scanned by Check Point Total Security Gateway. Email secured by Check Point
- [IPsec] FW: BCP 146, RFC 5406 on Guidelines for S… Yaron Sheffer