[saag] Fwd: BCP 201, RFC 7696 on Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 19 November 2015 01:19 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5F61B32D7 for <saag@ietfa.amsl.com>; Wed, 18 Nov 2015 17:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.886
X-Spam-Level:
X-Spam-Status: No, score=-4.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8E-um9Ktony for <saag@ietfa.amsl.com>; Wed, 18 Nov 2015 17:19:04 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A956E1A0029 for <saag@ietf.org>; Wed, 18 Nov 2015 17:19:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 93D51BE55 for <saag@ietf.org>; Thu, 19 Nov 2015 01:18:59 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uH57rgFfPa7T for <saag@ietf.org>; Thu, 19 Nov 2015 01:18:57 +0000 (GMT)
Received: from [10.87.48.91] (unknown [86.46.27.72]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id A0EE7BE53 for <saag@ietf.org>; Thu, 19 Nov 2015 01:18:56 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1447895937; bh=fJdHeW/sXxa9v7U193dfT2TJ92mYY/Xa3HyVP1UUQJg=; h=Subject:References:To:From:Date:In-Reply-To:From; b=Oqu33VDZGg8h8UobbHvVZfAOiLCKLEStA16payeXj/pp3er9cZ6uoSHOHmHdlOYCZ Mw0vWXJhizeyrmkHVGu1Vzlu7dxgDQ8XQ0XkkUf6D6aRKZqMG+pxaE9H3mSj1Y3VnO XZ90nnA5E0rs7UBrkpe9MMo6krJBEcPTVWegaE1s=
References: <20151119011248.EF374180005@rfc-editor.org>
To: "saag@ietf.org" <saag@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
X-Forwarded-Message-Id: <20151119011248.EF374180005@rfc-editor.org>
Message-ID: <564D2380.80403@cs.tcd.ie>
Date: Thu, 19 Nov 2015 01:18:56 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151119011248.EF374180005@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/bXsPHfZQzrGjrYtqc5Dvy4BTyk0>
Subject: [saag] Fwd: BCP 201, RFC 7696 on Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2015 01:19:08 -0000
This was discussed on here, so here's the RFC/BCP numbers... Cheers and thanks for the good discussion on this one, S. -------- Forwarded Message -------- Subject: BCP 201, RFC 7696 on Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms Date: Wed, 18 Nov 2015 17:12:48 -0800 (PST) From: rfc-editor@rfc-editor.org Reply-To: ietf@ietf.org To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org CC: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. BCP 201 RFC 7696 Title: Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms Author: R. Housley Status: Best Current Practice Stream: IETF Date: November 2015 Mailbox: housley@vigilsec.com Pages: 19 Characters: 50543 See Also: BCP 201 I-D Tag: draft-iab-crypto-alg-agility-08.txt URL: https://www.rfc-editor.org/info/rfc7696 DOI: http://dx.doi.org/10.17487/RFC7696 Many IETF protocols use cryptographic algorithms to provide confidentiality, integrity, authentication, or digital signature. Communicating peers must support a common set of cryptographic algorithms for these mechanisms to work properly. This memo provides guidelines to ensure that protocols have the ability to migrate from one mandatory- to-implement algorithm suite to another over time. 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 https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://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 Association Management Solutions, LLC
- [saag] Fwd: BCP 201, RFC 7696 on Guidelines for C… Stephen Farrell