We applaud the recent addition of CAA checking requirements to the Baseline 
Requirements. However, there are known problems with the CAA checking algorithm 
specified in RFC 6844, and those problems are leading to many reports from our 
subscribers. The issues are described here:

https://community.letsencrypt.org/t/legacy-caa-implementation/

We would like to ask the Mozilla and Google root programs on this list to 
immediately grant at least temporary dispensation for CAs to implement the CAA 
checking algorithm as described in this errata:

https://www.rfc-editor.org/errata/eid5065

We believe that the algorithm described in this errata is a better algorithm, 
and that the IETF working group behind CAA agrees. We believe a CA/B Forum 
ballot will pass in the near term to make the algorithm compliant.

A CA/B Forum ballot will take some time to pass, however, and subscribers are 
hurting now. Therefore we believe the right course of action is for root 
programs to grant at least temporary dispensation for CAs to implement the 
errata algorithm starting immediately.

Let’s Encrypt has implemented the errata algorithm for CAA checking for some 
time now, until Thursday (yesterday) morning, when we switched to the RFC 6844 
algorithm for compliance reasons. Let’s Encrypt acknowledges that we did not 
move to the compliant algorithm until after the compliance deadline and we 
apologize for that. We should have sought dispensation before the compliance 
deadline and not having done so was wrong regardless of whether or not 
dispensation is granted now. Nonetheless, we believe the right thing to do 
going forward is to allow any CA to at least temporarily implement the errata 
algorithm.
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to