Update: Let’s Encrypt has now switched back to the erratum 5065 algorithm for CAA, the algorithm we’ve used since launch with the exception of the past two weeks.
Details: The CA/Browser Forum passed ballot 214 yesterday, switching to CAA erratum 5065. The ballot does not take effect until a standard 30-day Intellectual Property Review period has passed. However, Mozilla, Google, Microsoft, and Apple have each indicated that they consider it acceptable for CAs to use either the RFC 6844 algorithm or the erratum 5065 algorithm until then, after which point only erratum 5065 will be acceptable.