Re: [DNSOP] Tell me about tree walks

Paul Vixie <paul@redbarn.org> Wed, 11 November 2020 22:23 UTC

Return-Path: <vixie@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD23B3A1186 for <dnsop@ietfa.amsl.com>; Wed, 11 Nov 2020 14:23:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 knfPDAi7FC0C for <dnsop@ietfa.amsl.com>; Wed, 11 Nov 2020 14:23:04 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4C0E3A1184 for <dnsop@ietf.org>; Wed, 11 Nov 2020 14:23:04 -0800 (PST)
Received: by family.redbarn.org (Postfix, from userid 716) id 9BCF1C3F03; Wed, 11 Nov 2020 22:23:04 +0000 (UTC)
Date: Wed, 11 Nov 2020 22:23:04 +0000
From: Paul Vixie <paul@redbarn.org>
To: John R Levine <johnl@taugh.com>
Cc: dnsop@ietf.org
Message-ID: <20201111222304.qx2m3sbebcoz6rhp@family.redbarn.org>
References: <20201111181423.7B1A9262936D@ary.qy> <alpine.DEB.2.20.2011112128510.17264@grey.csi.cam.ac.uk> <20201111220822.34bia6nagfnimwuw@family.redbarn.org> <68cf5d93-baca-95a-4b2b-567cc5751af0@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <68cf5d93-baca-95a-4b2b-567cc5751af0@taugh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jZu8ZTLbs5_Q1DY_QiVsok7GZtA>
Subject: Re: [DNSOP] Tell me about tree walks
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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>
X-List-Received-Date: Wed, 11 Nov 2020 22:23:06 -0000

On Wed, Nov 11, 2020 at 05:17:54PM -0500, John R Levine wrote:
> > if you guys are going to automate and secure the public suffix list
> > functionality, ...
> 
> Not a chance.

seems like we're passing like ships in the night here.

> > icann will likely never require it, but hopefully ietf can specify
> > it, after which the invisible hand of the market can decide it.
> 
> Doubly not a chance.  Having been hanging around the "expedited" process at
> ICANN I can assure you that the registries will voluntarily provide no WHOIS
> data at all.  The business plan, you know.

i know about the business plans. so icann will never require it. but if
there's an ietf specified way for a registrar to signal their role in all
their domains, it'll be seen by at least one of them as a market
differentiator. (i know the ones i'll be proposing this to.)

that's all we need.

so instead of debating whether icann is or is not a regulator and whether they
have or have not been captured by their industry and whether they can or
cannot require anything controversial, can we debate instead whether the
ietf, being above the fray, can possibly specify a scalable ("not in whois")
method of automatic identification of a domain's registrar?

i brought this up because this marker's presence would also help with the
kinds of tree walking and public-suffix-list functionalities we use today.
so, there's technical merit here, it's not strictly a defense budget play.

-- 
Paul Vixie