Re: [DNSOP] Public Suffix List

Kim Davies <kim.davies@icann.org> Mon, 09 June 2008 19:08 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@lists.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 15A973A6CA6; Mon, 9 Jun 2008 12:08:54 -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 D39823A6CA6 for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 12:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 3BFu2UMBZxxh for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 12:08:51 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id EA0903A6C9E for <dnsop@ietf.org>; Mon, 9 Jun 2008 12:08:51 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.233]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Mon, 9 Jun 2008 12:09:12 -0700
From: Kim Davies <kim.davies@icann.org>
To: David Conrad <drc@virtualized.org>, Gervase Markham <gerv@mozilla.org>
Date: Mon, 9 Jun 2008 12:09:09 -0700
Thread-Topic: [DNSOP] Public Suffix List
Thread-Index: AcjKYolu+dvyE8EvTb61z0saG5uvZgAAcHuJ
Message-ID: <C472CDE5.34D8%kim.davies@icann.org>
In-Reply-To: <9C47AC3F-A0EA-48BB-9B28-DFD2C4855EB3@virtualized.org>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, "ietf-http-wg@w3.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

On 9/06/08 11:56 AM, "David Conrad" <drc@virtualized.org> wrote:
>
> On Jun 9, 2008, at 9:34 AM, Gervase Markham wrote:
>>> 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?
>>
>> No. What do you think they'd say that hasn't been said in this thread
>> already?
>
> You're talking about essentially creating a registry of their registry
> policies and distributing it statically via your product.  I would
> imagine they might be interested and might even have some useful input
> to provide.  Some might even think it rude (even Microsoftian :-)) not
> to ask.  But perhaps I've been at layer 9 too long.

This thread sounds remarkably like deja vu. Indeed, the TLD community was
rather upset a few years ago by Mozilla taking unilateral action to
introduce a hard-coded white-list of acceptable IDN TLDs without prior
consultation. It is not unreasonable to think that doing so for a second
time, with the benefit of hindsight, would be received negatively.

I'd also speculate much of the pros and cons to this discussion are equally
applicable to the IDN whitelist. (
http://www.mozilla.org/projects/security/tld-idn-policy-list.html)

kim

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