Re: [Sks-devel] Dumps/importing & de-peering (WAS: Re: SKS apocalypse mitigation)

[Andrew Gallagher]

> On 5 May 2018, at 15:00, brent s. <address@hidden> wrote:
> 
> (a) is taken care of by recon already (in a way),

According to a list message from earlier today it is not. If the delta is 
small, recon proceeds. If it is large, it breaks catastrophically. There is no 
(current) way to test nicely.

> but the problem for
> (b) is the "standard place" - SKS/recon/HKP/peering is, by nature,
> unfederated/decentralized. sure, there's the SKS pool, but that
> certainly isn't required for peering (even with keyservers that ARE in
> the pool) nor running sks. how does one decide the "canonical" dump to
> be downloaded in (b)?

There can be no canonical dump of course. Each peer can provide its own dump at 
a well known local URL. This is even more important if and when we allow 
divergent policy. 

A