IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Thu, 15 December 2022 06:53 UTC

Return-Path: <lear@lear.ch>
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 9413EC151708 for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2022 22:53:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=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=lear.ch
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 b5tdTQmC0o-j for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2022 22:53:18 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [IPv6:2a00:bd80:aa::2]) (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 5F83BC14CE5B for <dnsop@ietf.org>; Wed, 14 Dec 2022 22:53:15 -0800 (PST)
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1671087181; bh=O2/q8IRvFWeHgPKE5WlI5/0phinzz2dKuZy6kHNN0GQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=jVktHnjcnZhJxl0YujeOOJ5Og1IMdf5WiMuIsFwcqayqvAaQoQy+lCpIaaG4jHbVP 1b5YdwYQEH571QfwI00zsoX5xo5Rti/3hExyj38Wk+GxS3VTBTK5p57SWti0WmpaLN 6TWaIMCYfUAp6IrKfeQkCZdnFFE74nQTMCEnH6rQ=
Received: from [IPV6:2001:420:c0f8:1002::191] ([IPv6:2001:420:c0f8:1002:0:0:0:191]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 2BF6qwM2128956 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 15 Dec 2022 07:53:00 +0100
Content-Type: multipart/alternative; boundary="------------lh446h9K8DG4dZf5suYNvSer"
Message-ID: <a9bcfbf3-3ebd-fecf-4b8c-795299a22e33@lear.ch>
Date: Thu, 15 Dec 2022 07:52:57 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.5.1
Content-Language: en-US
To: Paul Wouters <paul@nohats.ca>, Martin Schanzenbach <schanzen@gnu.org>
Cc: dnsop <dnsop@ietf.org>
References: <221b69b9-adea-d13a-2976-25bc9464621f@lear.ch> <446E3291-1CEA-4061-A63B-49252371B269@nohats.ca> <20221215003319.3u3gsem4ll5pzoki@werkbank> <8c63ae68-0afe-d1df-879c-ea72f8b12023@nohats.ca>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <8c63ae68-0afe-d1df-879c-ea72f8b12023@nohats.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6Tegx30_38dYD8qjwqgUqhLZZo4>
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 06:53:22 -0000

On 15.12.22 03:51, Paul Wouters wrote:
> I don't interpret it as "the person responsible for fixing the
> conflict". I think if one opts to use a name under .alt, one has to
> engineer in how to deal with conflicts in that namespace. It is a
> fundamental feature/bug of it. 

That is true with *any* namespace.  The reason we are here is that we 
are attempting to engineer how to deal with conflicts with the DNS name 
space.  Also,  some conflicts may be okay in .ALT, depending on how it 
is used (imagine locally scoped well known names, for instance).  We 
really can't say since we're not setting engineering goals or standards 
for its use. So let's be quiet on the matter, other than to say that how 
others use ALT is out of scope.

Eliot

v2.23.0 | Report a Bug | By Email