Hi Arturo, Thanks for your review. I will add some comments to Steve's response:
> Roque, > > Some comments about the draft. > > I think that in phase 3 it is implicit that CAs must sign using algs A > and B (it's a must in phase 2). Wouldn't be a good idea to make an explicit > statement in phase 3 as well? > > There are some indent issues with some of the examples, i.e: > > |-> CA-Y-Certificate-Algorithm-Suite-A (Cert-YA) > |-> CA-Z-Certificate-Algorithm-Suite-A (Cert-ZA) > |-> CA-Z-CRL-Algorithm-Suite-A (CRL-ZA) > |-> CA-Z-Signed-Objects-Algorithm-Suite-A > |-> CA-Y-CRL-Algorithm-Suite-A (CRL-YA) > |-> CA-Y-Signed-Objects-Algorithm-Suite-A > |-> CA-X-CRL-Algorithm-Suite-A (CRL-XA) > |-> CA-X-Signed-Objects-Algorithm-Suite-A > > I guess it should be something like: > > CA X-Certificate-Algorithm-Suite-A (Cert-XA) > | > |-> CA-Y-Certificate-Algorithm-Suite-A (Cert-YA) > |-> CA-Z-Certificate-Algorithm-Suite-A (Cert-ZA) > |-> CA-Z-CRL-Algorithm-Suite-A (CRL-ZA) > |-> CA-Z-Signed-Objects-Algorithm-Suite-A > |-> CA-Y-CRL-Algorithm-Suite-A (CRL-YA) > |-> CA-Y-Signed-Objects-Algorithm-Suite-A > |-> CA-X-CRL-Algorithm-Suite-A (CRL-XA) > |-> CA-X-Signed-Objects-Algorithm-Suite-A > > > In phase 4 the table has indent issues too. > (Roque) thanks, will correct. > And after the table, this text is confusing: > > ""All signed products sets issued using the Algorithm Suite A MUST be > published at their corresponding publication point but signed > products sets issued using the Algorithm Suite C MAY be published at > their corresponding publication points." > > Do you mean? > > "All signed products sets issued using the Algorithm Suite A and Algorithm > Suite C MUST be > published at their corresponding publication points." > (Roque) See Steve's answer > In section 5 I have a basic question What happen if the child ask the > parent to sign with Alg. B but the parent only supports A, it just fails? Is > there any message defined in the up/down specification to deal with this and > signal the error? > (Roque) I want to add that each algorithm suite correspond to a different "resource class" of the provisioning protocol. Consequently, you would be trying to access a class that does not exist in the server and you should get the error code : "1201 request - no such resource class" Thanks! Roque > Section 6 answered a question that I had when I was reading the first > part of the draft: > > "As a general rule, the validation of signed products using different > algorithm suites are > independent and the RP MUST NOT keep any relationship between the > different hierarchies" Also it says that an object is valid if it is valid > in algs. A OR B. May be it would be good to mention this somewhere in the > first part of the document but without going to too much detail. > > Also in the same section 6, I think that there is important to mention > that in phase 0 (coming back to) the objects signed with C are not longer > valid. > > Finally, Section 9. I would prefer a MUST instead. > > I think that's all so far. > > Best wishes, > -as > > On 27 Feb 2011, at 19:51, Roque Gagliano wrote: > >> Dear WG, >> >> We just submitted the -00 version of this algorithm agility draft, now as a >> WG item. >> >> The document includes the different changes requested since Beijing from the >> individual submission, notably: >> 1. Change form "laisez faire" to "top-down" >> 2. Included Multi Algorithm support in the RPKI provisioning >> protocol >> >> 3. Included Validation of multiple instance of signed products >> >> 4. Included Revocations >> >> 5. Included Key rollover >> >> 6. Included Repository structure >> >> 7. Included Security Considerations >> >> 8. Included Acknowledgements >> >> We look forward for your comments. >> Regards, >> Roque. >> >> >> On Feb 26, 2011, at 9:45 PM, [email protected] wrote: >> >>> A New Internet-Draft is available from the on-line Internet-Drafts >>> directories. >>> This draft is a work item of the Secure Inter-Domain Routing Working Group >>> of the IETF. >>> >>> >>> Title : Algorithm Agility Procedure for RPKI. >>> Author(s) : R. Gagliano, et al. >>> Filename : draft-ietf-sidr-algorithm-agility-00.txt >>> Pages : 25 >>> Date : 2011-02-26 >>> >>> This document specifies the process that Certificate 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 support only a top-down migration >>> (parent migrates before children). >>> >>> A URL for this Internet-Draft is: >>> http://www.ietf.org/internet-drafts/draft-ietf-sidr-algorithm-agility-00.txt >>> >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>> >>> Below is the data which will enable a MIME compliant mail reader >>> implementation to automatically retrieve the ASCII version of the >>> Internet-Draft. >>> <Mail Attachment>_______________________________________________ >>> sidr mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/sidr >> >> _______________________________________________ >> sidr mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/sidr >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
