[dbound] resuscitating dbound (2022)

Paul Vixie <paul@redbarn.org> Fri, 17 June 2022 16:11 UTC

Return-Path: <paul@redbarn.org>
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 7FD1EC15D88D for <dbound@ietfa.amsl.com>; Fri, 17 Jun 2022 09:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Level:
X-Spam-Status: No, score=-7.109 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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redbarn.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vMtVfx3G87yy for <dbound@ietfa.amsl.com>; Fri, 17 Jun 2022 09:11:32 -0700 (PDT)
Received: from util.redbarn.org (util.redbarn.org [24.104.150.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55033C14CF12 for <dbound@ietf.org>; Fri, 17 Jun 2022 09:11:15 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by util.redbarn.org (Postfix) with ESMTPS id 13BB41A2423 for <dbound@ietf.org>; Fri, 17 Jun 2022 16:11:13 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=redbarn.org; s=util; t=1655482273; bh=u8FSG8stB21fB1A8cbMZ8qKhkWLb7dGMKHew8MKg5cQ=; h=To:From:Subject:Date; b=XT99s7d6r9TaVVpXesyt3WsI8ElLtiE8zi0LFsNU1LWYx9VT7J5culQJK99MnFjfk /8tBqZOZJA6PX+4WEeK/48aXgEagsMlq7tmFl7qLZ6x5ilr+WZpBPNv6gDUwcgkhbN 691lFdNDTkBdejZQ2BqDJDRhyOtWhWs74HxEX+do=
Received: from [24.104.150.173] (dhcp-173.access.rits.tisf.net [24.104.150.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id F1EC37597E for <dbound@ietf.org>; Fri, 17 Jun 2022 16:11:12 +0000 (UTC)
To: dbound@ietf.org
From: Paul Vixie <paul@redbarn.org>
Message-ID: <aa13b014-56eb-fe14-8765-66972cc7246f@redbarn.org>
Date: Fri, 17 Jun 2022 09:11:14 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/7.0.56
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/wyTRyYj_I5Z2nvY4PGDxF9MpOPU>
Subject: [dbound] resuscitating dbound (2022)
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 17 Jun 2022 16:11:39 -0000

hello gentle beings. while at $dayjob, the topic of the public suffix 
list and its scaling limits has come up. i've agreed to gauge the 
community's interest in restarting the DBound WG, and so, here i am. i 
was not a member of the WG during its first heyday because my duties 
both to then-$dayjob and the DNS technical community were elsewhere.

i've re-read the "About dbound" text at 
<https://www.ietf.org/mailman/listinfo/dbound> and it seems to be 
exactly correct, and in that correctness, very prescient. i've read the 
drafts circulated "back in the day" and they seem competent and 
practicable. before i ask for a BOF at IETF 114, i thought i'd better 
talk to the known community of interest (that is, this mailing list).

who here is supportive of resuscitation? (and, who is opposed?)

what authors (prior, or newly active) are interested in contributing?

who in the technical community is known to be missing from this m/l (who 
might be interested in participating but doesn't know about DBound)?

thanks for any input.

-- 
P Vixie