Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Policy proposal for removal of non-responding T2 servers

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Policy proposal for removal of non-responding T2 servers


Chronological Thread 
  • From: opennic AT lewman.us
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] Policy proposal for removal of non-responding T2 servers
  • Date: Wed, 15 Aug 2012 15:15:14 -0400
  • Organization: The Tor Project, Inc.

On Tue, 14 Aug 2012 22:16:02 -0600
Jeff Taylor <shdwdrgn AT sourpuss.net> wrote:
> There are three situations that should be addressed. The first is
> when the server simply stops responding to DNS queries, and appears
> to have gone offline completely. Of course not everyone monitors
> their servers on a daily basis, and there could be situations such as
> when the admin goes on vacation. There could also be issues with
> their internet provider. In most cases, I would expect the admin to
> at least notify the mailing list if there is an extended problem that
> they are trying to fix. However when there are no notifications and
> the admin cannot be contacted, I would like to propose that their
> server be automatically removed after 14 days.

14 days is generous. Most DNS issues are measured in 1-2 days.

> The second situation is when the server is online, but failing some of
> the zone tests. Again there are a lot of factors to consider, but the
> concern is that their server is not responding reliably to all
> queries, and users of that server will not be able to reach all
> OpenNic domains. This situation has more pitfalls, but in the end it
> comes down to making sure the users get the answers that they
> expect. So I would also propose a 14-day grace period for this
> situation.

Sounds good.

> The third situation is overall reliability. If a server only answered
> queries 50% of the time, you wouldn't want to use it. Because we are
> recording test results for each server, we can create a historical
> profile to rate the reliability. I think the easiest way to score a
> server would be to check the percentage of passes over the last X
> days. So how many days do we want to look at, and at what percentage
> do we consider the server unreliable? As an initial starting point
> (and because conflicting rules between the first and second
> situations would make programming tricky), I am going to suggest
> removal if a server drops below 66.7% in 60 days. That is an
> extremely lenient score, but it would actually remove at least seven
> tier-2 servers immediately.

I suggest 30 days.

--
Andrew
http://tpo.is/contact
pgp 0x6B4D6475



Archive powered by MHonArc 2.6.19.

Top of Page