[cabf_validation] FW: Effective Date for New Profiles

Tim Hollebeek tim.hollebeek at digicert.com
Fri Aug 5 14:12:14 UTC 2022

Corey asked me to bring this old proposal to the attention of subcommittee
again, so you all don't have to go digging for it.




From: Tim Hollebeek 
Sent: Thursday, November 18, 2021 10:55 AM
To: CABforum3 <validation at cabforum.org>
Subject: Effective Date for New Profiles



Correctly specifying effective dates is something we've struggled with for a
long time, even with simple ballots.  In the most commonly used current
method, the new version of the document becomes effective on date X, but
contains explicit text within the requirements specifying the details of the
transition and a future effective date Y.  While this is significantly
clearer that previous methods, where the effective dates were in the ballots
but not the requirements themselves, getting it right is challenging,
especially for complicated ballots.


The intent we are trying to express, however, is simple.  Before date Y, use
the old profiles.  After date Y, use the new profiles.  As I've stated on
previous calls, I don't think it is particularly useful to spend time or
effort on creating a document that specifies both profiles, just for the
transition period, and I don't think it's necessary to "freeze" the profiles
in order to do so.  We simply need to state clearly in the requirements
exactly what the requirements are.


So I propose we do exactly that.  Have the profiles section say something
along the lines of:


"All certificates issued after YYYYYYYYYYY MUST comply with the appropriate
profile listed in Section 7.  Certificates issued before that date MAY
comply with the previous profiles and requirements (as documented in BR
version X.X or later)."


I don't care too much about the exact wording, as long as we convey the
intent as clearly, concisely, and accurately as possible.


I discussed this privately with a few people, and we discussed a few other
options, but we kept coming back to this one as the simplest.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/validation/attachments/20220805/eee4c66a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5120 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/validation/attachments/20220805/eee4c66a/attachment.p7s>

More information about the Validation mailing list