[Sovereign Keys] A design question: How should timelines and mirrors operate?

Georg Koppen g.koppen at jondos.de
Tue Feb 28 00:09:42 PST 2012


> Also, a good question is how to handle permanent failures of a timeline.
> For example a timeline operator could go bankrupt, or loose the private
> key.

Then it dies, I guess. Like in:

"The timeline servers might have their private keys compromised or
revoked, in which case they will die."

> All client, that insist opon this timeline would act like under an
> attack, because no fresh responses from this timeline are available
> anymore.

Clients are not insisting on a particular timeline, rather:

'Clients query one of the M comprehensive mirrors of timelines with a
query that asks "what are all the timeline entries that pertain to name
X since entry Y?"'

(see the mirror's response in section 4.a. Queries to Mirrors for the
full context)

Mirrors in turn "keep full, up to date copies of *all* [emphasis added]
the trusted timelines."

(all quotes are from the current spec)


Georg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://lists.eff.org/pipermail/sovereign-keys/attachments/20120228/00ed4415/attachment.sig>


More information about the Sovereign-Keys mailing list