> 23 May 2017 14:42 Eran Messeri <[email protected]> wrote: > > *Overview*: > > - UA vendor ("auditor") periodically collects an STH (denoted "official" > STH [1]) from each log, distributes it to its UAs ("clients"). Clients are > expected to cache all STHs. > - CA/Site Owner ("submitter") submits (pre)certificate to the log, gets > SCT [2]. > - Submitter waits until the next official STH that includes the > certificate, gets an inclusion proof to be served alongside the certificate > + SCT. > - In the TLS handshake, clients get certificate + SCT + inclusion proof > to an official STH they know about [5]. > > > The purpose of the UA vendor sending down the official STH is to provide > third-party verification of the consensus. > The purpose of the submitter bundling the STH + inclusion proof is to avoid > the client having to retrieve it via some other protocol
I may have misunderstood something, but why would the STH not always be included with the inclusion proof? What is the reason for all this extra complexity (UA vendor distributing the STH, inclusion proof not self-contained)? /Magnus _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
