From 0f19b7094a3235b1f43539a92aadb1a1001ece11 Mon Sep 17 00:00:00 2001 From: Linus Nordberg Date: Tue, 7 Sep 2021 16:45:38 +0200 Subject: 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. --- doc/design.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'doc') 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 -- cgit v1.2.3