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

"J. Trent Adams" <jtrentadams@gmail.com> Mon, 11 March 2013 18:07 UTC

Return-Path: <jtrentadams@gmail.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 5B26E11E81A7 for <apps-discuss@ietfa.amsl.com>; Mon, 11 Mar 2013 11:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.048
X-Spam-Level:
X-Spam-Status: No, score=0.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
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 Y-Kh1vQY3s3K for <apps-discuss@ietfa.amsl.com>; Mon, 11 Mar 2013 11:07:29 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3923A11E81C3 for <apps-discuss@ietf.org>; Mon, 11 Mar 2013 11:07:29 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id 17so5135431iea.26 for <apps-discuss@ietf.org>; Mon, 11 Mar 2013 11:07:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=YBlE7ItANeCDt26l0/r4GWgl+FlA0bBjJT4LwnC/xOk=; b=YOObezghPr3FHaJVgLPacq0EqrM951cQp91MaYeEo+vhBe5eFgK77OTmJ3yX8BVj/B CqFtyotypADjV35K3AovR6eeoMyBoO0p7MQyeQtSI83LgvhMVkLL79QQn4zr34ypHONJ qYY6Q930ELoPN/T+B9M7YTS089SJ8RyhHkhrX4zzC200J2nF3BKbxCkcGcN1/2usT/ly H5zD4RBnTILd9EtpzqkxLrZ9e0VEJ4C4Zq+yxu+Ahgix1e5OXeUVLBph6je4twHp8cJ6 3W9iwo+cn/VEZcfUrJ2uDbIWY/5IRiAJPwaQ5BQG7yUaWCQOhrpqPAofIMkyoEcYlZI/ 66ug==
X-Received: by 10.50.173.102 with SMTP id bj6mr8282806igc.16.1363025248843; Mon, 11 Mar 2013 11:07:28 -0700 (PDT)
Received: from jtrentadams-isoc.local (c-76-25-71-111.hsd1.co.comcast.net. [76.25.71.111]) by mx.google.com with ESMTPS id ip2sm14148719igc.5.2013.03.11.11.07.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Mar 2013 11:07:27 -0700 (PDT)
Message-ID: <513E1D5F.8080806@gmail.com>
Date: Mon, 11 Mar 2013 12:07:27 -0600
From: "J. Trent Adams" <jtrentadams@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <20130310042250.GE33497@mx1.yitter.info>
In-Reply-To: <20130310042250.GE33497@mx1.yitter.info>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Mon, 11 Mar 2013 18:07:30 -0000

1.  Do people think this is work that needs to be done?

Coming up with a workable solution for identifying administrative
boundaries within domains is clearly important for many known use cases,
plus a sufficiently general solution would service many more uses that
are currently unknown.  We undoubtedly need to ween ourselves from the
public suffix list, especially as the longer the issue is left
unaddressed the more hacks or non-scalable work-arounds that will
proliferate.

As a case in point, the emerging DMARC work would benefit from this type
of solution.

2.  Do either of the above proposals seem like a good starting
    point?

Having read
http://tools.ietf.org/html/draft-sullivan-domain-origin-assert-02 pretty
closely, and discussed it with my colleagues, I believe that this is a
perfectly reasonable starting point.

I don't believe it's the perfect solution in its current state (and I
personally prefer the name-only variant), but believe we can easily use
it as a solid aggregation point around which to build the right solution.

3.  If so, who is willing to do work on this (by reviewing and so
    on). 

Yes, I can commit to spending time on this work.


Thanks,
Trent


On 3/9/13 9:22 PM, Andrew Sullivan wrote:
> Dear colleagues,
>
> In the APPSAWG meeting on Monday, the chairs have asked me to take
> five minutes on the subject: topic.  I thought I'd better send a note
> in preparation.
>
> ICANN is in the process of awarding a little under 2000 new TLDs.
> Inspired, I believe, partly by that fact, Phill Hallam-Baker suggested
> a new DNS RRTYPE that would identify a name as a public suffix.
> Unfortunately, he fell ill and didn't have a chance to submit a draft
> on this.
>
> I'm opposed to that particular idea, however, because I think I have
> proposed a more generic mechanism that would still work just as well
> for that use case, and also allow future refinements.  I've outlined
> that mechanism in
> http://tools.ietf.org/html/draft-sullivan-domain-origin-assert-02.
>
> I won't have any slides on Monday; I really just want to learn the
> following:
>
>     1.  Do people think this is work that needs to be done?
>
>     2.  Do either of the above proposals seem like a good starting
>     point?
>
>     3.  If so, who is willing to do work on this (by reviewing and so
>     on).  
>
> (3) is especially important to me, because I received rather too
> little feedback on the draft I offered to think that anyone else is
> interested in pursuing it.  If people are interested in that draft,
> I'm certainly prepared to continue working on it.
>
> Best regards,
>
> A
>

-- 
J. Trent Adams

Profile: http://www.mediaslate.org/jtrentadams/
LinkedIN: http://www.linkedin.com/in/jtrentadams
Twitter: http://twitter.com/jtrentadams