Re: [apps-discuss] "finding registered domains"

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 12 March 2013 20:24 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9111E11E818C for <apps-discuss@ietfa.amsl.com>; Tue, 12 Mar 2013 13:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.508
X-Spam-Level:
X-Spam-Status: No, score=-0.508 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_75=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVXCX6rjx5qQ for <apps-discuss@ietfa.amsl.com>; Tue, 12 Mar 2013 13:24:49 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E899E11E8187 for <apps-discuss@ietf.org>; Tue, 12 Mar 2013 13:24:48 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-2430.meeting.ietf.org [130.129.36.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 4F3148A031 for <apps-discuss@ietf.org>; Tue, 12 Mar 2013 20:24:48 +0000 (UTC)
Date: Tue, 12 Mar 2013 16:24:42 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: apps-discuss@ietf.org
Message-ID: <20130312202442.GE41728@mx1.yitter.info>
References: <20130310042250.GE33497@mx1.yitter.info> <7B65185F-2517-4800-AE6A-CBA88F8B5720@vpnc.org> <CAL0qLwaGY0TYOndAUgbVYG5qDKKfP2U5Wuc5+oBXgyJ_kz9wSg@mail.gmail.com> <CAL0qLwYq1bgUykCfPQz7tvMBsxyfXSyBDTQQp=VQPu=74v_G0w@mail.gmail.com> <20130311210857.GG38441@mx1.yitter.info> <CAL0qLwY9YyLpHF9XYbm5zCC1+3PzCtdcmgyC6eiQ-P7QBKiDyA@mail.gmail.com> <20130312184051.GE39324@mx1.yitter.info> <CAL0qLwaD_6k36ZzAFO_KKkP=ud_Cd=-4P+vH_UQ58p6BcuY25A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAL0qLwaD_6k36ZzAFO_KKkP=ud_Cd=-4P+vH_UQ58p6BcuY25A@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [apps-discuss] "finding registered domains"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 20:24:50 -0000

On Tue, Mar 12, 2013 at 03:52:20PM -0400, Murray S. Kucherawy wrote:
> If for example I decide I need to evaluate foo.bar.example.com, I would
> issue a WEIRDS query for that string, and presumably get back
> example.comas that's the registered domain.  (This is a particular
> point for the
> WEIRDS community to confirm.)

Why would the correct answer not be from foo.bar.example.com or
bar.example.com (or, actually, both)?

A large amount of the assumed background is the deployed convention of
label.example.com.  The "registered domain" here is example.com.  And
while that is the most common case, it doesnt cover everything.
Indeed, if that convention _were_ reliable, we wouldn't need the
public suffix list at all.  

Moreover, if my parent can assert things about me, then unless I run a
WEIRDS server I wouldn't have a way of disagreeing with that parent.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com