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

[Roque Gagliano <[e-mail]>]

Dear WG,

I uploaded a new version of the draft preparing it for WGLC.

The only change is a requirement from the BGPSEC team to include a paragraph in section 4.2 that clarifies that "mixed" certs are not allowed only for CA certs but may be possible for EE certs that do not validate repository objects (i.e. BGPSEC certs).


Regards,
Roque


Begin forwarded message:

> From: [e-mail]
> Date: August 2, 2011 11:20:22 AM GMT+02:00
> To: [e-mail]
> Cc: [e-mail], [e-mail], [e-mail]
> Subject: New Version Notification for draft-ietf-sidr-algorithm-agility-03.txt
> 
> A new version of I-D, draft-ietf-sidr-algorithm-agility-03.txt has been successfully submitted by Roque Gagliano and posted to the IETF repository.
> 
> Filename:	 draft-ietf-sidr-algorithm-agility
> Revision:	 03
> Title:		 Algorithm Agility Procedure for RPKI.
> Creation date:	 2011-08-02
> WG ID:		 sidr
> Number of pages: 25
> 
> 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