Re: [dbound] The proposals before us

"John R Levine" <johnl@taugh.com> Sun, 11 September 2016 03:44 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2658812B1C6 for <dbound@ietfa.amsl.com>; Sat, 10 Sep 2016 20:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=g+yghOUJ; dkim=pass (1536-bit key) header.d=taugh.com header.b=kSESCpN5
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4uEJmUm6uY1Z for <dbound@ietfa.amsl.com>; Sat, 10 Sep 2016 20:44:41 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0205D12B1C2 for <dbound@ietf.org>; Sat, 10 Sep 2016 20:44:40 -0700 (PDT)
Received: (qmail 33358 invoked from network); 11 Sep 2016 03:44:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=824d.57d4d326.k1609; bh=J6baNsEsTyFjP6NKheN5/cWzWitbN5ghAph1MDg3kEE=; b=g+yghOUJFGLU/i7SeRJSaakmVrTk+7Q4lxJJTVQWznd1hWn2hnno7jjWZWM3oWVVtwThlmH0C2PiZGX85I2lfsx5qwv/Py2xyHMGUy4vUoBIXoqtCpvIvS2XsIN4/cfvWAIXWHTnBN/shZOSMceE2KNL3ztYEFVGJIzTT+9bo/I3aqwTfdXmt8QtwVNMjCAVMY+9l7YXD9gvgwPt6/yh9i3ea2LtrCUBXSIgZrEZlEWjJ3LdsGVVUWURAQnFqrF1
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=824d.57d4d326.k1609; bh=J6baNsEsTyFjP6NKheN5/cWzWitbN5ghAph1MDg3kEE=; b=kSESCpN5+Rmct6/BJsUd56CLKe5zRuwzt6MkU/futE6CI0awXAziHPp3NVrk8n6fSOskZHsTf2X0P69RTmhMdq+oST3irjOr1XAib3W1r7+hRzbyldE1x7J1BqY3ULQYc9bNLZ892kwZV7NvdFNThgC4wBHQXfoxQNqfm9mTrsrLwTUgdY9x+5J+N90Hm/ahk31T/GNim9QUM/eyvkOeOJYiKhvLN48zTWv0z/nLV41PIIb+7qC+VBkF0lnk5dck
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 11 Sep 2016 03:44:38 -0000
Date: 10 Sep 2016 23:44:39 -0400
Message-ID: <alpine.OSX.2.11.1609102313420.53927@ary.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Casey Deccio" <casey@deccio.net>
In-Reply-To: <8C13CBDD-A213-47F0-8755-C1A5F0190EE9@deccio.net>
References: <20160910211314.47140.qmail@ary.lan> <8C13CBDD-A213-47F0-8755-C1A5F0190EE9@deccio.net>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/XSSfP0WPlPLMQTa8SKUh0h9LelI>
Cc: dbound@ietf.org
Subject: Re: [dbound] The proposals before us
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: DNS tree bounds <dbound.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dbound>, <mailto:dbound-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound/>
List-Post: <mailto:dbound@ietf.org>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dbound>, <mailto:dbound-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Sep 2016 03:44:44 -0000

> The pertinent information was included in the text that immediately 
> followed the snippet that you included above.  Since it was omitted, 
> I'll include it again here (some emphasis added):

I have a problem, in that I have read this document multiple times and 
have no clue what the actual series of queries and responses would be, 
given the complexity of the lookup algorithm and the situation where some 
subtrees can be cached via a fetch result. It'd be a big help if you could 
give some examples.

Could you tell us what the queries would be for abc.def.com if the org
domain is def.com, or for ghi.blogspot.com, where the org domain is
ghi.blogspot.com, or jkl.mno.uk and jkl.mno.co.uk, where the org domains
are mno.uk and mno.co.uk?  That would certainly clarify things for me.


>> The current behavior is typically to look in the PSL and if the domain
>> isn't there, the code does whatever it does. ...

> The algorithms on the Public Suffix List page [2] and in section 3.2 of 
> RFC 7489 [3] seem pretty clear.  The algorithm is longest match--there 
> really isn't a notion of "if the domain isn't there".

Let's say you're looking up the domain bulgaria.xn--90ae.  That's a
name in a real TLD, and the TLD doesn't appear in the PSL.  What does
the code do now?  Looking at some of the PSL libraries, the results
look pretty random.  Some raise exceptions, some fall off the ends of
routines and return null or a random result.

R's,
John