Re: [DNSOP] Public Suffix List

Jamie Lokier <jamie@shareable.org> Tue, 10 June 2008 10:09 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 0646F3A6980; Tue, 10 Jun 2008 03:09:33 -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 46F663A6986 for <dnsop@core3.amsl.com>; Tue, 10 Jun 2008 03:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.266
X-Spam-Level:
X-Spam-Status: No, score=-4.266 tagged_above=-999 required=5 tests=[AWL=-1.667, 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 Jzv5DKIdy7Kt for <dnsop@core3.amsl.com>; Tue, 10 Jun 2008 03:09:30 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id 1B2593A680B for <dnsop@ietf.org>; Tue, 10 Jun 2008 03:09:29 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1K60mz-0006rz-M4; Tue, 10 Jun 2008 11:09:17 +0100
Date: Tue, 10 Jun 2008 11:09:17 +0100
From: Jamie Lokier <jamie@shareable.org>
To: Gervase Markham <gerv@mozilla.org>
Message-ID: <20080610100917.GA25910@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>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <484D5F3B.8040902@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:
> > 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.

No, I don't think so.

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.

> > 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.

See above.

-- Jamie
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
httpsFrom dnsop-bounces@ietf.org  Tue Jun 10 03:09:33 2008
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 0646F3A6980;
	Tue, 10 Jun 2008 03:09:33 -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 46F663A6986
	for <dnsop@core3.amsl.com>om>; Tue, 10 Jun 2008 03:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.266
X-Spam-Level: 
X-Spam-Status: No, score=-4.266 tagged_above=-999 required=5
	tests=[AWL=-1.667, 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 Jzv5DKIdy7Kt for <dnsop@core3.amsl.com>om>;
	Tue, 10 Jun 2008 03:09:30 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115])
	by core3.amsl.com (Postfix) with ESMTP id 1B2593A680B
	for <dnsop@ietf.org>rg>; Tue, 10 Jun 2008 03:09:29 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63)
	(envelope-from <jamie@shareable.org>)
	id 1K60mz-0006rz-M4; Tue, 10 Jun 2008 11:09:17 +0100
Date: Tue, 10 Jun 2008 11:09:17 +0100
From: Jamie Lokier <jamie@shareable.org>
To: Gervase Markham <gerv@mozilla.org>
Message-ID: <20080610100917.GA25910@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>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <484D5F3B.8040902@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:
> > 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.

No, I don't think so.

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.

> > 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.

See above.

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


/www.ietf.org/mailman/listinfo/dnsop