...

4.        The NEW CA enters a Staging Period.  This duration of the
          Staging Period is determined by the CA, but it SHOULD be no
          less than 24 hours.  (It is RECOMMENDED that the staging period
          be no longer than 48 hours.) ...


Given that during the staging period the only things that are published are the CA, the CRL and the Manifest for the new CA (sobordinate products are only published on the expiration of the staging period when the actual cutover happens), then relying parties are not burdened by having to deal with two sets of signed products. In many ways the staging period is a "pre-loaded new key in waiting" and in theory could be held in this state indefinitely.

So I wonder:

 a) why a max period is necessary to stipulate, and

b) if it is necessarily a good idea, then is this a substantive change that means that the document should head back to the WG for a review?

My personal opinion is that this is harmless and it is not necessary to alter the document to specify a max period.

    Geoff

Upon further reflection, I agree with Geoff's observation that the burden on
RPs is pretty minimal, since we're talking about only 3 objects (CA cert, a null CRL, and a trivial manifest). So, I am less inclined to stipulate a max period,
although I don't think it would be bad to suggest (as implementation guidance)
that a few days (as Terry suggested) is probably sufficient.

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

Reply via email to