[sidr] Protocol Action: 'Algorithm Agility Procedure for RPKI.' to Best Current Practice (draft-ietf-sidr-algorithm-agility-12.txt)
The IESG <iesg-secretary@ietf.org> Wed, 20 February 2013 14:48 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 989C221F8803 for <sidr@ietfa.amsl.com>; Wed, 20 Feb 2013 06:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level:
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAIwDLtL7ZjP; Wed, 20 Feb 2013 06:48:02 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54BC521F8821; Wed, 20 Feb 2013 06:48:02 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IANA <drafts-approval@icann.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
X-IETF-Draft-string: draft-ietf-sidr-algorithm-agility
X-IETF-Draft-revision: 12
Message-ID: <20130220144802.1065.48860.idtracker@ietfa.amsl.com>
Date: Wed, 20 Feb 2013 06:48:02 -0800
Cc: sidr mailing list <sidr@ietf.org>, sidr chair <sidr-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [sidr] Protocol Action: 'Algorithm Agility Procedure for RPKI.' to Best Current Practice (draft-ietf-sidr-algorithm-agility-12.txt)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: noreply@ietf.org
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 14:48:03 -0000
The IESG has approved the following document: - 'Algorithm Agility Procedure for RPKI.' (draft-ietf-sidr-algorithm-agility-12.txt) as Best Current Practice This document is the product of the Secure Inter-Domain Routing Working Group. The IESG contact persons are Stewart Bryant and Adrian Farrel. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-sidr-algorithm-agility/ Technical Summary This document specifies the process that Certification Authorities (CAs) and Relying Parties (RPs) participating in the Resource Public Key Infrastructure (RPKI) will need to follow to transition to a new (and probably cryptographically stronger) algorithm set. The process is expected to be completed in a time scale of several years. Consequently, no emergency transition is specified. The transition procedure defined in this document supports only a top-down migration (parent migrates before children). Working Group Summary During WGLC there was some prolonged discussion on whether IETF is the right body for publishing a set of milestones for different phases of algorithm migration and which other entities should be involved (IANA, NROs, etc.). The issue was discussed and the text was improved in this area. There was also an extended discussion during WGLC on whether top-down migration is the right way to do algorithm migration. I think the WG still supports this approach. Document Quality This document is not specifying a protocol, so there are no implementations. However considering past history in the Security Area with algorithm migration in different protocols, such migration event is quite likely, if RPKI ends up being used for any significant period of time. Personnel Alexey Melnikov is the Document Shepherd. Stewart Bryant is the Responsible Area Director. RFC Editor Note Please change the Intended Status from Proposed Standard to BCP