aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-10 20:00:58 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-10 20:08:14 +0200
commit90f8d431fe694b0b6b040c31447d961bcc75e52f (patch)
tree7094a76fc23e558a31f329892a00878f012ce7a1
parent8211f0ecdf8a65584d34ee177616dda80ebcab17 (diff)
keep summary session at its current location
I don't think it improves our design document by being moved. We already have a summary of properties in the introduction, and an easier primer at the start of Section 3 that is strongly coupled to Figure 1. Perhaps it is no longer necessary though. When we wrote this we did not have a summary of properties in introduction, or a relatively detailed walk-through of the log's intended usage-pattern. I'm fine with both keeping as is or deleting if it feels redundant.
-rw-r--r--doc/design.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/design.md b/doc/design.md
index 22ceb1d..03769d2 100644
--- a/doc/design.md
+++ b/doc/design.md
@@ -301,7 +301,6 @@ specific in sigsum. At a minimum, a monitor needs to locate relevant public key
may also need to be aware of how to locate the data that a given checksum represents.
### 3.3 - Summary
-[[move the summary to the top of section 3? /ln]]
Sigsum logs are sharded and shut down at predefined times. A sigsum log can
shut down _safely_ because verification on the verifier-side is not interactive.