That's probably better asked on the Chromium ct-policy list - [email protected]
The current Chrome implementation is based on rounded down month calculation, not days. In this case, if 825 days exceeds 27 months, then at present, it would require 4 SCTs, not 3. On Wed, Nov 1, 2017 at 7:19 AM, Doug Beattie via Public <[email protected] > wrote: > Hi Devon, > > > > Are you planning to change the 27-month references to 825 days at some > point? In some cases, 825 days might exceed 27 months but it’s our > understanding that this would still only require 3 SCTs. > > > > Doug > > > > *From:* Public [mailto:[email protected]] *On Behalf Of *Devon > O'Brien via Public > *Sent:* Tuesday, October 31, 2017 7:19 PM > *To:* CA/Browser Forum Public Discussion List <[email protected]> > *Subject:* [cabfpub] CT Policy moving to a new repository > > > > Hello CA/B Forum, > > > > In order to better align Google's github repositories, we have moved the > Chromium CT Policy documentation to a new home within the /chromium repo. > > > > All existing links to the old repository (https://github.com/ > GoogleChrome/ct-policy) should now redirect to the new one ( > https://github.com/chromium/ct-policy) > > > > For your convenience, we've created a permanent short-link to the repo > here: > > https://goo.gl/chrome/ct-policy > > > > We will also be updating all affected links on https://www.chromium.org/ > and https://www.certificate-transparency.org/ to the new shortened URL. > > > > I look forward to seeing those of you attending the CT Policy Days this > week. > > > > -Devon > > _______________________________________________ > Public mailing list > [email protected] > https://cabforum.org/mailman/listinfo/public > >
_______________________________________________ Public mailing list [email protected] https://cabforum.org/mailman/listinfo/public
