Arturo,

Let me reply to a couple of the questions you raised, in my role as a co-author.

Roque,

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

I agree that several areas of text are confusing. The problems starts in 4.7, which says:

   Phase 4 starts at the Algorithm B Twilight Date.  At that date, the
   Algorithm A is labeled as "old" and the Algorithm B is labeled as
   "current":

The text should probably say:

   Phase 4 starts at the Algorithm A Twilight Date.  At that date, the
   Algorithm A is labeled as "old" and the Algorithm B is labeled as
   "current"

After the diagram, the text says:

   During this phase, all signed product sets MUST be issued using the
   Algorithm Suite A and MAY be issued using the Algorithm Suite C. 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.  Also, every RP MUST validate
   signed product sets using the Algorithm Suite A but also MAY validate
   signed product sets using the Algorithm Suite C.

To avoid confusion (because we re-label the alg suites during this phase), we probably should say something like:

   During this phase, all signed product sets MUST be issued using
   Algorithm Suite A (formerly B) and MAY be issued using Algorithm Suite
   C (formerly A). All signed products sets issued using Suite A MUST be
   published at their corresponding publication points, but signed
   products sets issued using Suite C MAY be published at their corresponding
   publication points.  Also, every RP MUST validate  signed product sets using
   Suite A but also MAY validate signed product sets using Suite C.


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?

The short answer is yes. Based on feedback we received after briefing this
to SIDR at an IETF meeting, we adopted a top-down algorithm transition model.
So, a child can request a cert under the new alg ONLY after its parent has
begun to offer that alg for its signed products. This is stated in 4.2:

   In order to facilitate the transition, CAs will start issuing
   certificates using the Algorithm B in a hierarchical top-down order.
   In our example, CA Y will issue certificates using the Algorithm B
   suite only after CA X has started to do so (CA Y Ready Algorithm B
   Date > CA X Ready Algorithm B Date).  This ordered transition avoids
   the existence of mixed certificates.

...

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.

Section 4.8 (Return to Phase 0) says:
        At this phase, ALL signed product sets using Algorithm Suite
        C MUST be considered invalid.  CAs MUST neither issue nor publish
        signed products using Algorithm Suite C.

Section 6 discusses how to deal with signed products when more than one
instance exists, under different alg suites.  Since 4.8 says that CAs MUST
NOT issue or publish Suite C products, I don't think we need to say anything
in section 6.


Hope this helps,

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

Reply via email to