IETF Logo Mail Archive

Re: [DNSOP] Public Suffix List

Gervase Markham <gerv@mozilla.org> Mon, 09 June 2008 16:28 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 29E213A6950; Mon, 9 Jun 2008 09:28:51 -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 437803A69CF for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 09:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.933
X-Spam-Level:
X-Spam-Status: No, score=-2.933 tagged_above=-999 required=5 tests=[AWL=-1.626, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 BZRqvnM-l0ws for <dnsop@core3.amsl.com>; Mon, 9 Jun 2008 09:28:45 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [91.135.15.56]) by core3.amsl.com (Postfix) with ESMTP id 6FC203A689E for <dnsop@ietf.org>; Mon, 9 Jun 2008 09:28:45 -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 1K5kD0-0001ff-Ur; Mon, 09 Jun 2008 17:27:08 +0100
Message-ID: <484D5A44.30603@mozilla.org>
Date: Mon, 09 Jun 2008 17:28:52 +0100
From: Gervase Markham <gerv@mozilla.org>
User-Agent: Thunderbird 3.0a1 (X11/2008050714)
MIME-Version: 1.0
References: <484CFF47.1050106@mozilla.org> <20080609142926.GC83012@commandprompt.com> <484D4191.104@mozilla.org> <20080609162426.GA2596@shareable.org>
In-Reply-To: <20080609162426.GA2596@shareable.org>
X-BlackCat-Spam-Score: -9
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:
> 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.

> Also, wouldn't DNS generally be the appropriate mechanism to say what
> grouping relationships there are under $DOMAIN?  After all, the
> administrative control for the grouping info which you are maintaining
> for *.$DOMAIN, and DNS for *.$DOMAIN, are the same.

It would be an appropriate mechanism; when it does contain this
information, let me know.

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

v2.23.0 | Report a Bug | By Email