[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] SKS apocalypse mitigation
From: |
Andrew Gallagher |
Subject: |
Re: [Sks-devel] SKS apocalypse mitigation |
Date: |
Sat, 5 May 2018 09:00:43 +0100 |
> On 5 May 2018, at 07:00, Gabor Kiss <address@hidden> wrote:
>
> Okay, brain storming in progress. :-)
:-)
> Requests may be "iterative" or "recursive" (words are stolen from DNS).
> Users send recursive request: "I don't care how many peers
> you ask, but tell me the key with all signatures."
The DNS has a hierarchical structure that allows the authoritative source for
data to be found within a small number of requests that depends on the number
of components in the fqdn. There is no such structure in sks, and no way of
knowing that all I no has been found, so the *best* case scenario is that every
server has to be polled for every request.
> How to maintain a pool of servers like above? How to measure their
> quality?
Sorry, my use of “pool” was inaccurate. I meant to refer to all connected and
responsive servers. “Graph” is maybe the better term.
A
- Re: [Sks-devel] SKS apocalypse mitigation, Andrew Gallagher, 2018/05/03
- Re: [Sks-devel] SKS apocalypse mitigation, Phil Pennock, 2018/05/05
- Re: [Sks-devel] SKS apocalypse mitigation, Andrew Gallagher, 2018/05/05
- Re: [Sks-devel] SKS apocalypse mitigation, Phil Pennock, 2018/05/05
- Re: [Sks-devel] SKS apocalypse mitigation, Andrew Gallagher, 2018/05/05
- Re: [Sks-devel] SKS apocalypse mitigation, Andrew Gallagher, 2018/05/05
- Re: [Sks-devel] SKS apocalypse mitigation, Phil Pennock, 2018/05/06
- Re: [Sks-devel] SKS apocalypse mitigation, Andrew Gallagher, 2018/05/23
- Re: [Sks-devel] SKS apocalypse mitigation, Ari Trachtenberg, 2018/05/05