Re: [DNSOP] Public Suffix List

Gervase Markham <gerv@mozilla.org> Mon, 09 June 2008 15:57 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@optimus.ietf.org
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C5C63A6C66; Mon, 9 Jun 2008 08:57:31 -0700 (PDT)
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1C913A6A94 for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 08:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.52
X-Spam-Level:
X-Spam-Status: No, score=-3.52 tagged_above=-999 required=5 tests=[AWL=-1.051, BAYES_00=-2.599, SARE_RMML_Stock10=0.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pHcaJc2TlGvf for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 08:57:30 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [91.135.15.56]) by core3.amsl.com (Postfix) with ESMTP id E5E1D3A6C66 for <dnsop@ietf.org>; Mon, 9 Jun 2008 08:57:29 -0700 (PDT)
Received: from grmarkham.plus.com ([80.229.30.161] helo=[192.168.1.6]) by haggis.mythic-beasts.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <gerv@mozilla.org>) id 1K5jig-0000hv-JT; Mon, 09 Jun 2008 16:55:42 +0100
Message-ID: <484D52EC.1090608@mozilla.org>
Date: Mon, 09 Jun 2008 16:57:32 +0100
From: Gervase Markham <gerv@mozilla.org>
User-Agent: Thunderbird 3.0a1 (X11/2008050714)
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
References: <484CFF47.1050106@mozilla.org> <484D1533.4060300@spaghetti.zurich.ibm.com> <484D1883.4060002@mozilla.org> <666CCACE-71F0-485D-9C9F-0C3E0C965ADA@virtualized.org>
In-Reply-To: <666CCACE-71F0-485D-9C9F-0C3E0C965ADA@virtualized.org>
X-BlackCat-Spam-Score: -17
Cc: dnsop@ietf.org, ietf-http-wg@w3.org
Subject: Re: [DNSOP] Public Suffix List
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

David Conrad wrote:
>> however, my view is that getting comprehensive buy-in
>> would take quite a lot more time and effort than this method.
> 
> is the common excuse that results in lots of broken crap on the
> Internet.  It is sad to see the same mistake repeated again and again.

Prove me wrong, then. You can send a message to the Technical Contacts
of all 284 domains (I can supply you with a list) saying "Please set up
a resilient, highly-available web service to provide current data on
your registration structure." See what sort of reaction you get.

>>> How can non-TLD's get into this list!?
>> Just by asking; I already got an email from CentralNIC.
> 
> If there is no vetting, doesn't this defeat the purpose?

Who says there's no vetting?

How does adding e.g. CentralNIC defeat the purpose? In some ways, it is
the purpose; CentralNIC customers will no longer be able to conspire to
damage users privacy, and if users accidentally mis-set cookies, other
CentralNIC customers can't steal them.

Gerv
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop