[Sks-devel] Bad signature

2012-05-17 Thread Gabor Kiss
> Date: Fri, 18 May 2012 00:37:28 +0200 > From: Kristian Fiskerstrand > To: sks-devel@nongnu.org > Subject: Re: [Sks-devel] Request for reporting of upstream bandwidth capacity > Hi Gio, > > When you say ranked higher, are you referring to the nominal SRV > weight reported? Please not that what

Re: [Sks-devel] Request for reporting of upstream bandwidth capacity

2012-05-17 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2012-05-17 23:24, Giovanni Mascellani wrote: > Hi. > > Il 17/05/2012 23:19, > kristian.fiskerstr...@sumptuouscapital.com > ha >> (aside) It would be very interesting to receive feedback from >> users of the various geo-pools on whether any change

Re: [Sks-devel] Request for reporting of upstream bandwidth capacity

2012-05-17 Thread Giovanni Mascellani
Hi. Il 17/05/2012 23:19, kristian.fiskerstr...@sumptuouscapital.com ha > (aside) It would be very interesting to receive feedback from users > of the various geo-pools on whether any changes have been noticed > from the client side Well, it's not really the answer to your question, but a strange

Re: [Sks-devel] Request for reporting of upstream bandwidth capacity

2012-05-17 Thread kristian . fiskerstrand
Hi Jeff, This is basically what the various measurement clients around the world are doing to estimate the first part of the equation, the responsetime, which is the factor with the highest loading. It retrieve my key 0x6b0b9508 that is currently approx 66 KiB on every run, measure the conn t

Re: [Sks-devel] Request for reporting of upstream bandwidth capacity

2012-05-17 Thread Jeffrey Johnson
On May 16, 2012, at 2:35 PM, Kristian Fiskerstrand wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 2012-05-16 20:22, Robert J. Hansen wrote: >> On 05/16/2012 01:12 PM, Kristian Fiskerstrand wrote: >>> As upstream bandwidth capacity is one of the considerations that >>> is taken