The lede buried here (or maybe not here but in the root program policies for MTCs) is that they’ll be 7 day maximum lifetime. And ACME only. And potentially the only thing Chrome supports (meaning you have to) by mid-2028.
If you don’t have your public TLS automated today, better get started…
Fixes/Mitigates a huge problem with OCSP and CRL scaling in a world where every website has a cert.
Shorter lifetimes are good. Kind of an antipattern when you thought you got a cert forever, (like 2+ years) and it turns out getting them short lived is just better for everyone.
Shorter lifetimes are the better revocation mechanism (no need for revocation, just wait a bit). This I-D is about optimizing PQC and combining in certificate transparency (CT).
This document describes Merkle Tree certificates, a new form of X.509
certificates which integrate public logging of the certificate, in
the style of Certificate Transparency. The integrated design reduces
logging overhead in the face of both shorter-lived certificates and
large post-quantum signature algorithms, while still achieving
comparable security properties to existing X.509 constructions and
Certificate Transparency. Merkle Tree certificates additionally
admit an optional size optimization that avoids signatures
altogether, at the cost of only applying to up-to-date relying
parties and older certificates.
IOW: it's an optimization for PQC signature algorithms.
The lede buried here (or maybe not here but in the root program policies for MTCs) is that they’ll be 7 day maximum lifetime. And ACME only. And potentially the only thing Chrome supports (meaning you have to) by mid-2028.
If you don’t have your public TLS automated today, better get started…
Fixes/Mitigates a huge problem with OCSP and CRL scaling in a world where every website has a cert.
Shorter lifetimes are good. Kind of an antipattern when you thought you got a cert forever, (like 2+ years) and it turns out getting them short lived is just better for everyone.
Shorter lifetimes are the better revocation mechanism (no need for revocation, just wait a bit). This I-D is about optimizing PQC and combining in certificate transparency (CT).
Given I know what X.509 certificate chain and Merkle tree are.
Can someone give a cliff note version of what this RFC brings to the table?
It's in the abstract:
IOW: it's an optimization for PQC signature algorithms.This looks fantastic. (Huge fan of Merkle trees and this is a great use for them)
So, it's like a centralized blockchain of sorts?
POA network... but ya