IETF Logo Mail Archive

Re: [DNSOP] Tell me about tree walks

Joe Abley <jabley@hopcount.ca> Wed, 11 November 2020 22:45 UTC

Return-Path: <jabley@hopcount.ca>
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 561D43A11B5 for <dnsop@ietfa.amsl.com>; Wed, 11 Nov 2020 14:45:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 cPP9aopQGr32 for <dnsop@ietfa.amsl.com>; Wed, 11 Nov 2020 14:45:56 -0800 (PST)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 422673A11B1 for <dnsop@ietf.org>; Wed, 11 Nov 2020 14:45:56 -0800 (PST)
Received: by mail-qv1-xf2a.google.com with SMTP id q7so1801605qvt.12 for <dnsop@ietf.org>; Wed, 11 Nov 2020 14:45:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FdUmOzHeOpOWWiCw232fkCAVGRTcDwwNFYS8AVn5zZ0=; b=O+IM3Mr7dPFn6PeU7wxDpjP4rS3dYUUhynBdt44YG+NlgqgydcKyGHpTq3/g0EWs4Z qplfCX2Ngi9FASBdZK9eHMbXM2Ae7ywLn+hsoQRDwxheFNxj42Jf5WwkunXLadZCcEi7 z2wT3ZVpqg0xwBfebpcGVbKck4ajSVwz2g3Wg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FdUmOzHeOpOWWiCw232fkCAVGRTcDwwNFYS8AVn5zZ0=; b=TqM0Hv5znELBRPxltiOH5HtmyV8RqqZwdHkcbQPGadELt/OLc8UYouHRhlpgMIUqdC HhRR6iFesm0ontGIXFMBJccDTpNCB71cQ7P9FUEaE4t/uGsT4uJkqnmCiDhWusZ1nc20 NPnGkr6eIme/uEJ39RM+z/Jso6bsW9UYgiLohegmaHlYf8cIShAcrSjPnYPxVSH/fZ0q XudsuR+ALBWd8q3xrvJz3uCww5+lxyBsa7qJqMDuh7INqGF3jpbl975usN/xUtDauYiK 1pKcp4pdMUbuUClmC0SbZNb54tklTYlSEvoQwcaBC0SHqitdAd0XKlzeIHRA1DYfhf2P //+Q==
X-Gm-Message-State: AOAM531unYGTR3Zs0qj02GqouN24XntEwCf2PN3EtQ5PsUuot8gylXeK L7yPQ7ZulcizvMF/sLoVIEFhZy8CUQJsK//W7lk=
X-Google-Smtp-Source: ABdhPJxoJnbjUleXMkFiiO7SVlneJaC4y4jZ1uGyBJqlsmMWNx4mEowOlyOgZ6JAtmMTyk2msozTFg==
X-Received: by 2002:ad4:468b:: with SMTP id bq11mr25680741qvb.8.1605134755084; Wed, 11 Nov 2020 14:45:55 -0800 (PST)
Received: from ?IPv6:2607:f2c0:e784:c7:78ca:a6da:d149:3ab9? ([2607:f2c0:e784:c7:78ca:a6da:d149:3ab9]) by smtp.gmail.com with ESMTPSA id t20sm3644792qtt.70.2020.11.11.14.45.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Nov 2020 14:45:54 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20201111220822.34bia6nagfnimwuw@family.redbarn.org>
Date: Wed, 11 Nov 2020 17:45:52 -0500
Cc: Tony Finch <dot@dotat.at>, dnsop@ietf.org, John Levine <johnl@taugh.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D01ED99-7F80-4D0E-A791-7DFF84E0F75C@hopcount.ca>
References: <20201111181423.7B1A9262936D@ary.qy> <alpine.DEB.2.20.2011112128510.17264@grey.csi.cam.ac.uk> <20201111220822.34bia6nagfnimwuw@family.redbarn.org>
To: Paul Vixie <paul@redbarn.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hiL9m56ODstsRsBsGsonKaIKyAc>
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:45:57 -0000

On 11 Nov 2020, at 17:08, Paul Vixie <paul@redbarn.org> wrote:

> if you guys are going to automate and secure the public suffix list
> functionality, please spare a thought for automated / at-scale ("not
> in whois") identification of the domain's registrar and registrant.

I understand the reason why being able to identify the registrar for a particular domain is useful (or "necessary" depending on your perspective). I don't understand the overlap between this problem and the problem that John is trying to solve, though. Could you explain?


Joe

v2.23.0 | Report a Bug | By Email