From b8b64ee52de9e216fe441aa6ae6d446d1ba719c1 Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Thu, 7 Oct 2021 18:01:13 +0200 Subject: added example of non-scope in our architecture --- doc/design.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'doc/design.md') diff --git a/doc/design.md b/doc/design.md index c9659d5..ef32efd 100644 --- a/doc/design.md +++ b/doc/design.md @@ -268,13 +268,15 @@ append-only before doing a cosignature operation. Cosignatures are posted back to the logs so that signers can easily fetch the finalized cosigned tree heads. It takes five to ten minutes before a signer's distribution phase can start. -The added latency is a trade-off that simplifies the entire log ecosystem by -removing the need for reactive gossip-audit protocols +The added latency is a trade-off that simplifies sigsum logging by removing the +need for reactive gossip-audit protocols [\[G1,](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7346853) [G2,](https://datatracker.ietf.org/doc/html/draft-ietf-trans-gossip-05) [G3,](https://petsymposium.org/2021/files/papers/issue2/popets-2021-0024.pdf) [G4\]](https://docs.google.com/document/d/16G-Q7iN3kB46GSW5b-sfH5MO3nKSYyEb77YsM7TMZGE/edit). +Use-cases like instant certificate issuance are not supported by design. + #### 3.2.4 - Distribution After a signer collected proofs of public logging the distribution phase can start. Distribution happens using the same mechanism that is normally used for -- cgit v1.2.3