aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLinus Nordberg <linus@nordberg.se>2021-09-07 16:45:38 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-02 00:54:13 +0200
commit0f19b7094a3235b1f43539a92aadb1a1001ece11 (patch)
treebcd2b0a6c98f1346e8b70717fc353d447da7dfee
parent746587805605c3edd819e6c133005956c0baa942 (diff)
BGP announcments might have higher requirements on timeliness
They're also not typically communicated in a repository of any kind. BGP updates _could_ of course be logged for non-realtime historical storage (archiving) but as an example this early in the text it's mostly confusing.
-rw-r--r--doc/design.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/design.md b/doc/design.md
index ade95ba..91b5294 100644
--- a/doc/design.md
+++ b/doc/design.md
@@ -28,8 +28,7 @@ Suppose you are an entity that distributes some opaque data. For example,
the opaque data might be
a provenance file,
an executable binary,
- an automatic software update,
- a BGP announcement, or
+ an automatic software update, or
a TPM quote.
You claim to distribute the right opaque data to everyone in a repository.
However, past incidents taught us that word is cheap and sometimes things go