[sidr] Last Call: <draft-ietf-sidr-algorithm-agility-11.txt> (Algorithm Agility Procedure for RPKI.) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Thu, 24 January 2013 18:52 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-ID: <20130124185246.30200.56205.idtracker@ietfa.amsl.com>
Date: Thu, 24 Jan 2013 10:52:46 -0800
Cc: sidr@ietf.org
Subject: [sidr] Last Call: <draft-ietf-sidr-algorithm-agility-11.txt> (Algorithm Agility Procedure for RPKI.) to Best Current Practice
Precedence: list
Reply-To: ietf@ietf.org

The IESG has received a request from the Secure Inter-Domain Routing WG
(sidr) to consider the following document:
- 'Algorithm Agility Procedure for RPKI.'
  <draft-ietf-sidr-algorithm-agility-11.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-02-07. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   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).

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-sidr-algorithm-agility/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-sidr-algorithm-agility/ballot/


No IPR declarations have been submitted directly on this I-D.

This draft was previously last called with an intended status of
Proposed Standard. The purpose of this last call is to determine
if there is IETF consensus to publish this draft as a BCP.

[sidr] Last Call: <draft-ietf-sidr-algorithm-agil… The IESG