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

Peter Thomassen <peter@desec.io> Thu, 15 December 2022 14:24 UTC

Return-Path: <peter@desec.io>
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 9E673C1516F8 for <dnsop@ietfa.amsl.com>; Thu, 15 Dec 2022 06:24:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 (2048-bit key) header.d=a4a.de
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 XFXBUlPb5_r4 for <dnsop@ietfa.amsl.com>; Thu, 15 Dec 2022 06:24:38 -0800 (PST)
Received: from mail.a4a.de (mail.a4a.de [IPv6:2a01:4f8:10a:1d5c:8000::8]) (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 16B30C14CE38 for <dnsop@ietf.org>; Thu, 15 Dec 2022 06:24:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=a4a.de; s=20170825; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:Subject:From :References:Cc:To:MIME-Version:Date:Message-ID:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=dN65lL7YENwgIApKi3aUOkYyktjgoGec7eTDF7cLhXY=; b=Q+2Jg+SO0ahJJjVRjDC54nVkzX Z7b4qfkcEvW3DEKtOG7pTJEG+mT7C92UpE1JNkYRzk5JSZ0t+yl136yOt3VrK7xoGJW1gqR/xSzR7 j8fcBIpcveB15TdJJreeqkevkG5dTt3OztngsRZmkassjo7+yXJoqiAoTt3YQUSdn3B6lCg4E/W2e 5A2eE2L432645I36m+vUhyafgwAlcBikGCi8dS00C4sy3LCgxPDtFw5VKvuQS6b0/crur9XOZpLdw pFGgu7YUqrxdw3bJjg+oths0OpLSme7RcppejcVLagzE9zlHjfMyn71Sj1Uy6/s2QdTDpZz0RXHDO TMUL5+LQ==;
Received: from [2a00:20:6010:3dea:ef1:df8e:3c0a:7aba] by mail.a4a.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from <peter@desec.io>) id 1p5p9u-0005fH-3D; Thu, 15 Dec 2022 15:24:26 +0100
Message-ID: <abc5cf60-a746-d1eb-2b79-0c9b84bdcb21@desec.io>
Date: Thu, 15 Dec 2022 15:24:25 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
Content-Language: en-US
To: Martin Schanzenbach <mschanzenbach@posteo.de>, Paul Wouters <paul@nohats.ca>
Cc: Eliot Lear <lear@lear.ch>, Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@icann.org>, dnsop <dnsop@ietf.org>
References: <221b69b9-adea-d13a-2976-25bc9464621f@lear.ch> <446E3291-1CEA-4061-A63B-49252371B269@nohats.ca> <20221215005928.ammidwbbol5xekz5@werkbank>
From: Peter Thomassen <peter@desec.io>
In-Reply-To: <20221215005928.ammidwbbol5xekz5@werkbank>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/VRqSX5UxVAfvL7Vss166we7ueWQ>
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 14:24:42 -0000


On 12/15/22 01:59, Martin Schanzenbach wrote:
> On 14.12.22 12:25, Paul Wouters wrote:
>> On Dec 14, 2022, at 11:29, Eliot Lear <lear@lear.ch> wrote:
>>>> On 14.12.22 17:13, Paul Wouters wrote:
>>>> "bob.foo.alt" still squarely falls into "my" namespace
>>>> It is indeed not “yours”.
>>> ... from the perspective of DNS.  Whether it is "yours" or "mine" from the perspective of GNS is a matter for GNS to resolve (for example).
>>>
>> I was not talking from the perspective of IETF or DNS. The .alt is the Wild West. Even GNS cannot claim exclusivity of a chunk of it. It is competing with all the other unregulated namespaces.
>>
> 
> Then the draft should just say that. And not insinuate that as a dev I
> can or should do something about that.

I second that. I can understand that alternative namespace developers don't know what to do about their "responsibility" to deal with conflicts.

It seems to me that the motivation behind the sentence
	"Developers are wholly responsible for dealingwith any collisions that may occur under .alt"

really is that the IETF does not feel responsible. So perhaps let's write
	"The .alt namespace is unmanaged. Mitigation or resolution of any collisions that may occur under .alt are outside the scope of this document and outside the IETF's remit. Developers are advised to consider the associated risks when using names under .alt."

... or similar. This way, it's very clear that "getting into collision territory" is a conscious choice, but hopefully with reduced risk for the kind of misunderstanding that started this particular subthread.

Best,
Peter

-- 
https://desec.io/