Re: [DNSOP] Public Suffix List

Jamie Lokier <jamie@shareable.org> Tue, 10 June 2008 11:16 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 02EC13A69CF; Tue, 10 Jun 2008 04:16:20 -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 6B0F23A69CF for <dnsop@core3.amsl.com>; Tue, 10 Jun 2008 04:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.066
X-Spam-Level:
X-Spam-Status: No, score=-4.066 tagged_above=-999 required=5 tests=[AWL=-1.467, 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 PQw+KPdLVkoV for <dnsop@core3.amsl.com>; Tue, 10 Jun 2008 04:16:17 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id 509803A6829 for <dnsop@ietf.org>; Tue, 10 Jun 2008 04:16:17 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1K61qA-0007Cg-Cj; Tue, 10 Jun 2008 12:16:38 +0100
Date: Tue, 10 Jun 2008 12:16:38 +0100
From: Jamie Lokier <jamie@shareable.org>
To: Gervase Markham <gerv@mozilla.org>
Message-ID: <20080610111638.GF25910@shareable.org>
References: <484CFF47.1050106@mozilla.org> <20080609142926.GC83012@commandprompt.com> <484D4191.104@mozilla.org> <20080609162426.GA2596@shareable.org> <484D5A44.30603@mozilla.org> <20080609163659.GC2596@shareable.org> <484D5F3B.8040902@mozilla.org> <20080610100917.GA25910@shareable.org> <484E53B2.6030404@mozilla.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <484E53B2.6030404@mozilla.org>
User-Agent: Mutt/1.5.13 (2006-08-11)
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 Markham wrote:
> Jamie Lokier wrote:
> > The information would be published in the ISP's TLD-alike domain, not
> > the customer's subdomains.  E.g. 'co.uk', not 'mybank.co.uk', assuming
> > the information is "each domain $WORD.co.uk is independent".
> > 
> > The values are the same information that you are gathering.  The
> > ISP/NIC (Nominet UK for .co.uk) does not need to contact their
> > customers for this: it's a .co.uk policy.
> 
> OK. Then we are basically back to Yngve's suggestion. But this does
> require universal take-up for universal support - and that, as someone
> else has pointed out, makes it (in my opinion) doomed.

Or you gather data and hard-code it as a starting point, but
simultaneously provide a mechanism for others to publish information
about themselves which you use in real time, which overrides the
hard-coded data if they use it.

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