Re: [DNSOP] Public Suffix List

Gervase Markham <gerv@mozilla.org> Mon, 09 June 2008 16:50 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 C85B23A6C50; Mon, 9 Jun 2008 09:50:16 -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 A74843A6C50 for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 09:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.553
X-Spam-Level:
X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[AWL=-0.954, 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 scdCcNtkCsJG for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 09:50:14 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [91.135.15.56]) by core3.amsl.com (Postfix) with ESMTP id A5DAE3A6B22 for <dnsop@ietf.org>; Mon, 9 Jun 2008 09:50:14 -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 1K5kXV-0006Qz-WB; Mon, 09 Jun 2008 17:48:16 +0100
Message-ID: <484D5F3B.8040902@mozilla.org>
Date: Mon, 09 Jun 2008 17:50:03 +0100
From: Gervase Markham <gerv@mozilla.org>
User-Agent: Thunderbird 3.0a1 (X11/2008050714)
MIME-Version: 1.0
To: Jamie Lokier <jamie@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>
In-Reply-To: <20080609163659.GC2596@shareable.org>
X-BlackCat-Spam-Score: -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

Jamie Lokier wrote:
> Gervase Markham wrote:
>>> Wouldn't it be more appropriate for MyBank to _itself_ say the history
>>> for these sites should be grouped?  E.g. in an HTTP response header,
>>> or DNS record for mybank.co.uk?
>> The total amount of effort required for this solution is mind-boggling.
> 
> How is it more work for them to publish over DNS or HTTP, than to send
> you the information to publish, with the associated time lag etc?

Your solution requires every site to set HTTP response headers, or every
ISP to contact their customers to get the correct values for the DNS
records.

My solution involves communicating with a far smaller group.

> You've asked for the same thing: for administrators of certain domains
> to provide you with information about independent or related users of
> those subdomains.

But the two plans are talking about two different sets of admins, one
vastly larger than the other.

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