Subject: [sidr] Fwd: New Version Notification for draft-ietf-sidr-algorithm-agility-07.txt

From: "Roque Gagliano (rogaglia)" <[email-masked]>
Date: Sun, 23 Sep 2012 19:30:47 +0000

Hi WG,

This update took care of some nits detected by the WG chairs before heading to IETF LC.

Roque

   From 06 to 07:

   1.  Added definition for "Correspond"

   2.  Added reference of correspondence between suites in phase 2 and 3

   3.  Small nit on the revocation definition.

Begin forwarded message:

From: <[email-masked]<mailto:[email-masked]>>
Date: September 23, 2012 9:27:43 PM GMT+02:00
To: <[email-masked]<mailto:[email-masked]>>
Cc: <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>
Subject: New Version Notification for draft-ietf-sidr-algorithm-agility-07.txt

A new version of I-D, draft-ietf-sidr-algorithm-agility-07.txt
has been successfully submitted by Roque Gagliano and posted to the
IETF repository.

Filename: draft-ietf-sidr-algorithm-agility
Revision: 07
Title: Algorithm Agility Procedure for RPKI.
Creation date: 2012-09-23
WG ID: sidr
Number of pages: 30
URL:             http://www.ietf.org/internet-drafts/draft-ietf-sidr-algorithm-agility-07.txt
Status:          http://datatracker.ietf.org/doc/draft-ietf-sidr-algorithm-agility
Htmlized:        http://tools.ietf.org/html/draft-ietf-sidr-algorithm-agility-07
Diff:            http://www.ietf.org/rfcdiff?url2=draft-ietf-sidr-algorithm-agility-07

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 months or 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 IETF Secretariat