Dear WG, 

We just submitted a new version of the agility draft, where we believe we 
addressed all the comments during WGLC.

Particularly:
        - Decoupling the documents to be updated in two, one signaling the 
algorithms and another one (BCP) with the specific dates.
        - Adding a roll-over mechanism for the process.
        - Several text improvements and editorial nits

Regards,
Roque


Begin forwarded message:

> From: [email protected]
> Date: November 29, 2011 6:10:26 PM GMT+01:00
> To: [email protected]
> Cc: [email protected], [email protected], [email protected]
> Subject: New Version Notification for draft-ietf-sidr-algorithm-agility-04.txt
> 
> A new version of I-D, draft-ietf-sidr-algorithm-agility-04.txt has been 
> successfully submitted by Roque Gagliano and posted to the IETF repository.
> 
> Filename:      draft-ietf-sidr-algorithm-agility
> Revision:      04
> Title:                 Algorithm Agility Procedure for RPKI.
> Creation date:         2011-11-29
> WG ID:                 sidr
> Number of pages: 29
> 
> Abstract:
>   This document specifies the process that Certification Authorities
>   (CAs) and Relying Parties (RP) 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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to