Re: [DNSOP] Public Suffix List

Patrik Fältström <patrik@frobbit.se> Mon, 09 June 2008 13:55 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 134ED28C147; Mon, 9 Jun 2008 06:55:57 -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 D078C3A6C74 for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 06:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.118
X-Spam-Level:
X-Spam-Status: No, score=0.118 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_NUMERIC_HELO=2.067]
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 aJAxevOdw0u8 for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 06:55:52 -0700 (PDT)
Received: from frobbit.se (klara.frobbit.se [85.30.129.37]) by core3.amsl.com (Postfix) with ESMTP id AE29B3A6976 for <dnsop@ietf.org>; Mon, 9 Jun 2008 06:55:51 -0700 (PDT)
Received: from [64.103.25.233] (account paf HELO 78.156.199.226.bredband.tre.se) by frobbit.se (CommuniGate Pro SMTP 5.0.10) with ESMTPA id 6461638; Mon, 09 Jun 2008 15:56:08 +0200
Message-Id: <46A2CA74-3AE2-4B4E-B528-D4A12236B3C1@frobbit.se>
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <patrik@frobbit.se>
To: Gervase Markham <gerv@mozilla.org>
In-Reply-To: <484D330B.2030604@mozilla.org>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Mon, 9 Jun 2008 15:56:01 +0200
References: <484CFF47.1050106@mozilla.org> <0A0401AF-0DDF-491A-8118-4945DEE64DE7@frobbit.se> <484D330B.2030604@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

On 9 jun 2008, at 15.41, Gervase Markham wrote:

> Patrik Fältström wrote:
>> The problem with any such mechanisms is that the barrier of entry for
>> new players (that does not match the currently used list -- including
>> non-upgraded software) is increased. More than what people think.
>
> This isn't so. For TLDs not in the list, the usual rules (about e.g.
> cookie setting) would be applied. In other words, the situation is no
> different to what it is now. This information is additive.

What about new structures in a TLD that is in the list?

I.e. I do understand what you want to do, but am nervous still about  
the result if the list is not updated. Yes, you say your software is  
updated often, and sure, you might be the best in the class.

I just felt it was sort of my job to point out the risks, specifically  
as the risks are written down.

What you at the end of the day do is of course up to you. ;-)

    Patrik

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