Re: [DNSOP] Public Suffix List

Henrik Nordstrom <henrik@henriknordstrom.net> Tue, 10 June 2008 20:45 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 B246A3A6A8F; Tue, 10 Jun 2008 13:45: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 331453A68A9 for <dnsop@core3.amsl.com>; Tue, 10 Jun 2008 13:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.338
X-Spam-Level:
X-Spam-Status: No, score=-4.338 tagged_above=-999 required=5 tests=[AWL=-1.739, 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 0L6dpC0RGlXC for <dnsop@core3.amsl.com>; Tue, 10 Jun 2008 13:45:33 -0700 (PDT)
Received: from vps1.henriknordstrom.net (vps1.henriknordstrom.net [195.20.207.177]) by core3.amsl.com (Postfix) with ESMTP id C47323A6AEA for <dnsop@ietf.org>; Tue, 10 Jun 2008 13:45:31 -0700 (PDT)
Received: from henriknordstrom.net (183.159.216.81.static.tb.siw.siwnet.net [81.216.159.183]) by vps1.henriknordstrom.net (8.13.8/8.13.8/Debian-3) with ESMTP id m5AKjp27030623; Tue, 10 Jun 2008 22:45:51 +0200
Received: from henrik ([127.0.0.1]) (authenticated bits=0) by henriknordstrom.net (8.12.11.20060308/8.12.8) with ESMTP id m5AKjq5i027174 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Jun 2008 22:45:52 +0200
From: Henrik Nordstrom <henrik@henriknordstrom.net>
To: Gervase Markham <gerv@mozilla.org>
In-Reply-To: <1213098354.17978.5.camel@henriknordstrom.net>
References: <484CFF47.1050106@mozilla.org> <20080609142926.GC83012@commandprompt.com> <484D4191.104@mozilla.org> <20080609162426.GA2596@shareable.org> <484D5A44.30603@mozilla.org> <1213098354.17978.5.camel@henriknordstrom.net>
Date: Tue, 10 Jun 2008 22:45:52 +0200
Message-Id: <1213130752.17978.37.camel@henriknordstrom.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.3 (2.10.3-9.fc7)
X-Virus-Scanned: ClamAV version 0.91, clamav-milter version 0.91 on henriknordstrom.net
X-Virus-Status: Clean
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (vps1.henriknordstrom.net [195.20.207.177]); Tue, 10 Jun 2008 22:45:51 +0200 (CEST)
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: multipart/mixed; boundary="===============0296170759=="
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

On tis, 2008-06-10 at 13:45 +0200, Henrik Nordstrom wrote:
> On mån, 2008-06-09 at 17:28 +0100, Gervase Markham wrote:
> 
> > It would be an appropriate mechanism; when it does contain this
> > information, let me know.
> 
> It won't until someone specifies in how the data should be represented
> in DNS. And DNS is where it belongs, in the zone it relates to.

Some more brain cells fired in a later response and DNS is after all not
the proper location for this to work out in HTTP. See separate response.

Regards
Henrik
On tis, 2008-06-10 at 13:45 +0200, Henrik Nordstrom wrote:
> On mån, 2008-06-09 at 17:28 +0100, Gervase Markham wrote:
> 
> > It would be an appropriate mechanism; when it does contain this
> > information, let me know.
> 
> It won't until someone specifies in how the data should be represented
> in DNS. And DNS is where it belongs, in the zone it relates to.

Some more brain cells fired in a later response and DNS is after all not
the proper location for this to work out in HTTP. See separate response.

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