Re: [DNSOP] [Ext] Possible alt-tld last call?

Paul Wouters <paul@nohats.ca> Mon, 24 October 2022 19:45 UTC

Return-Path: <paul@nohats.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 A7B61C1522DD for <dnsop@ietfa.amsl.com>; Mon, 24 Oct 2022 12:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 ZfwaAkfvL4IE for <dnsop@ietfa.amsl.com>; Mon, 24 Oct 2022 12:45:53 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AF93C1524B6 for <dnsop@ietf.org>; Mon, 24 Oct 2022 12:45:52 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4Mx5Cd2Xcdz1p4; Mon, 24 Oct 2022 21:45:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1666640749; bh=6CcFHTV1Mk/6c6QhkMrnDNYMBOHwrRHyys0wqVZ0Q9g=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=sTRgEye6mv21vnRycD82YBALdkK+PyitkrXJkGDEptZ/gzyO+KRKGbTv5zurXIYts 0a7liVKGkGn9yhrrQ9cVttihyazd6V4AnuteTLjvGHuhTuRxArFwU6Lk1nSxC+NfJ+ pMKsWZAZsl1eqZFCaxGCvikbGmDA/7mI3tqegvYQ=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id KbcE8xkbe1pa; Mon, 24 Oct 2022 21:45:47 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 24 Oct 2022 21:45:47 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id C496E3FB96C; Mon, 24 Oct 2022 15:45:46 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C17D33FB96B; Mon, 24 Oct 2022 15:45:46 -0400 (EDT)
Date: Mon, 24 Oct 2022 15:45:46 -0400
From: Paul Wouters <paul@nohats.ca>
To: Brian Dickson <brian.peter.dickson@gmail.com>
cc: "dnsop@ietf.org" <dnsop@ietf.org>
In-Reply-To: <CAH1iCipNcsFnCSu338o3gfgfXyT5=r+=uvgbHKkSWL8F=ak7eg@mail.gmail.com>
Message-ID: <221db3c6-1cf0-f954-b87-aec0d0a6d55a@nohats.ca>
References: <D4D1C61C-6DAF-4D02-A861-D808270687B0@pir.org> <F514B317-18E8-4EEC-8049-A5BCAB4EB6B6@icann.org> <7A6FC59E-590C-411F-A83C-26E12172FB43@virtualized.org> <8B1A1AA1-A19E-4D26-8DB3-52B377EDA140@icann.org> <48CA0E74-2103-4691-9AC5-AB3E3360573A@virtualized.org> <9EB3910D-9ACE-476E-AEB6-798B9E5321FF@icann.org> <6471571B-0DC3-4978-8177-AEBE590C2085@virtualized.org> <BY5PR11MB4196CCA9F8FC2AE3679E6C57B52C9@BY5PR11MB4196.namprd11.prod.outlook.com> <7F3255E1-054D-4CA2-98CE-7518A0FBBE77@virtualized.org> <MN2PR11MB42079F9F77ECA7644458853EB52C9@MN2PR11MB4207.namprd11.prod.outlook.com> <CF130BA4-2FF8-4257-9B5F-3886851AC019@virtualized.org> <0809cd98-9d13-de7f-6522-bd9547c5e4b2@redbarn.org> <CAH1iCipNcsFnCSu338o3gfgfXyT5=r+=uvgbHKkSWL8F=ak7eg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rv3q5ptVAxEwLnHf8Kjein80r4Y>
Subject: Re: [DNSOP] [Ext] Possible alt-tld last call?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 24 Oct 2022 19:45:57 -0000

On Mon, 24 Oct 2022, Brian Dickson wrote:

> Just to expand on this idea (which I quite like), the original AS112 was enhanced to handle new/arbitrary names, so
> that AS112 operators don't need to do anything to support being a sink for new domains.
> 
> This was done in RFC7534 and RFC7535, using the new "empty.as112.arpa" target for use via DNAME.
> (The DNAME bit is so there isn't a delegation for which the AS112 operator would need to have a zone configured.)
> 
> Using this via the root zone would be a new kind of entry for the root zone, but is otherwise non-controversial
> (IMHO).
> It would basically look like: 
>       alt. DNAME empty.as112.arpa

this is dangerous. Anyone who runs an as112 node, or an attacker who
compromises one, can then serve a "real" .alt to a percentage of
queriers. Imagine millions being lost in some cryptocurrency .alt
non-dns scheme.

Paul