IETF Logo Mail Archive

Re: [DNSOP] draft-ietf-dnsop-alt-tld-19

Vladimír Čunát <vladimir.cunat+ietf@nic.cz> Thu, 15 December 2022 12:04 UTC

Return-Path: <vladimir.cunat+ietf@nic.cz>
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 44F2BC1526FA for <dnsop@ietfa.amsl.com>; Thu, 15 Dec 2022 04:04:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 VzlhhPR53ZhK for <dnsop@ietfa.amsl.com>; Thu, 15 Dec 2022 04:04:27 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 0118DC1526F7 for <dnsop@ietf.org>; Thu, 15 Dec 2022 04:04:26 -0800 (PST)
Received: from [IPV6:2a02:768:2d1c:226:69b2:13e6:b650:d433] (unknown [IPv6:2a02:768:2d1c:226:69b2:13e6:b650:d433]) by mail.nic.cz (Postfix) with ESMTPSA id 1D49F1C1A23; Thu, 15 Dec 2022 13:04:23 +0100 (CET)
Authentication-Results: mail.nic.cz; auth=pass smtp.auth=vladimir.cunat@nic.cz smtp.mailfrom=vladimir.cunat+ietf@nic.cz
Content-Type: multipart/alternative; boundary="------------SLkJyRhl0GNig080d8O529No"
Message-ID: <e8868304-0c00-ee14-2081-1548139a12ba@nic.cz>
Date: Thu, 15 Dec 2022 13:04:22 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1
Content-Language: cs, en-US
To: Martin Schanzenbach <mschanzenbach@posteo.de>, dnsop <dnsop@ietf.org>
References: <221b69b9-adea-d13a-2976-25bc9464621f@lear.ch> <446E3291-1CEA-4061-A63B-49252371B269@nohats.ca> <20221215005928.ammidwbbol5xekz5@werkbank>
From: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>
In-Reply-To: <20221215005928.ammidwbbol5xekz5@werkbank>
X-Virus-Scanned: clamav-milter 0.103.7 at mail
X-Virus-Status: Clean
X-Spamd-Bar: +
X-Spamd-Result: default: False [1.15 / 20.00]; R_MIXED_CHARSET(1.25)[subject]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:44489, ipnet:2a02:768::/32, country:CZ]; TAGGED_FROM(0.00)[ietf]; RCVD_COUNT_ZERO(0.00)[0]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]
X-Rspamd-Action: no action
X-Rspamd-Server: mail
X-Rspamd-Queue-Id: 1D49F1C1A23
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gezXRBvWHfJuPeGPWjYpcR6CziQ>
Subject: Re: [DNSOP] draft-ietf-dnsop-alt-tld-19
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: Thu, 15 Dec 2022 12:04:29 -0000

On 15/12/2022 01.59, Martin Schanzenbach wrote:
> If there is an obvious way to do it, the draft could give an example. Whatever you
> mean by "go to a regulated space" should be given with clear example.

You can simply register a DNS name and use that sub-tree in non-DNS 
context (as well).  That also comes with other advantages, depending on 
your use case, in particular the ability to "do something" also in case 
a user falls through to normal DNS.

I don't think this RFC really needs to explicitly mention such 
alternative approaches, but I wouldn't mind.

v2.23.0 | Report a Bug | By Email