Re: [DNSOP] Public Suffix List

David Conrad <drc@virtualized.org> Mon, 09 June 2008 16:26 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 8EF063A6A85; Mon, 9 Jun 2008 09:26:52 -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 632BB3A6976 for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 09:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.469
X-Spam-Level:
X-Spam-Status: No, score=-6.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 qmuiIrSsIVaR for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 09:26:50 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id 952E23A689E for <dnsop@ietf.org>; Mon, 9 Jun 2008 09:26:50 -0700 (PDT)
Received: from [10.0.1.198] (c-71-198-3-247.hsd1.ca.comcast.net [71.198.3.247]) by virtualized.org (Postfix) with ESMTP id CB199237B49; Mon, 9 Jun 2008 09:27:09 -0700 (PDT)
Message-Id: <C5894EBB-D4AA-40AD-8A38-2F4CD8A07D66@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Gervase Markham <gerv@mozilla.org>
In-Reply-To: <484D52EC.1090608@mozilla.org>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Mon, 9 Jun 2008 09:27:08 -0700
References: <484CFF47.1050106@mozilla.org> <484D1533.4060300@spaghetti.zurich.ibm.com> <484D1883.4060002@mozilla.org> <666CCACE-71F0-485D-9C9F-0C3E0C965ADA@virtualized.org> <484D52EC.1090608@mozilla.org>
X-Mailer: Apple Mail (2.924)
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

Gervase,

On Jun 9, 2008, at 8:57 AM, Gervase Markham wrote:
> 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)

I suspect I might have a better list than you (:-) hint: I work at  
ICANN).

> 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.

My reading of Yngve's draft (in particular, section 5.1) led me to  
believe that all TLDs would not need to run such a service, rather  
that such a service be available in a "well known" place (I think the  
right approach would be for IANA to maintain pointers to well known  
places, but that's an implementation detail).

I'm curious: have you consulted with the various TLD-related  
organizations (e.g., ccNSO, gNSO, CENTR, APTLD, AfTLD, LACTLD, etc.)  
on how to solve this problem?

In any event, while I think the goal you are trying to reach is a good  
one, I suspect the implementation approach you're suggesting will lead  
to regrets.  However, your code and all that...

>>>> 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?

"Just by asking".

I gather I misunderstood.

Regards,
-drc

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