IETF Logo Mail Archive

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

Paul Wouters <paul@nohats.ca> Wed, 14 December 2022 16:13 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 683D4C14CE37 for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2022 08:13:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (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 jlsBXhDC5ycW for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2022 08:13:19 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.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 153B6C14F72D for <dnsop@ietf.org>; Wed, 14 Dec 2022 08:13:18 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4NXL4s1B7Dz36c; Wed, 14 Dec 2022 17:13:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1671034397; bh=A9Cv5yMytuGc36+3ftbM2wTAhHZzfLJyFGaKEDGxzwQ=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=YSLevCVpxe4hiT9Otl0CMQ6vwTaWLG4XIgdqQIFHOtGLIVWT7s61aenXKAHpAAtl6 PQibB7+9WxSOyAnujAmVzjC9U1OSdgc804v0150PRepw3u9oNdfXjK4RJzGF06HcJ7 n7e8e10EGJiOObANF5/9Hupj6qrvWndBXdvN4InA=
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 Q_T-BxhEtjMF; Wed, 14 Dec 2022 17:13:16 +0100 (CET)
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; Wed, 14 Dec 2022 17:13:16 +0100 (CET)
Received: from smtpclient.apple (unknown [193.110.157.208]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 5D513423157; Wed, 14 Dec 2022 11:13:15 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Paul Wouters <paul@nohats.ca>
Mime-Version: 1.0 (1.0)
Date: Wed, 14 Dec 2022 11:13:14 -0500
Message-Id: <9C02A5E7-3EA5-40EB-B265-4989D9961B6E@nohats.ca>
References: <20221214103710.zm6t5oshhnfwsm4g@werkbank>
Cc: Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@icann.org>, dnsop <dnsop@ietf.org>
In-Reply-To: <20221214103710.zm6t5oshhnfwsm4g@werkbank>
To: Martin Schanzenbach <mschanzenbach@posteo.de>
X-Mailer: iPhone Mail (19G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jvWqxO4eQFxmrAikfGbshLwe2Do>
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: Wed, 14 Dec 2022 16:13:24 -0000

On Dec 14, 2022, at 05:37, Martin Schanzenbach <mschanzenbach@posteo.de> wrote:
> 
> 
> I think my main issue is the word "wholly".
> The developer cannot be "wholly" responsible.
> I can choose a label (e.g. "foo.alt") that is not already taken right
> now.
> But I cannot really do anything if somebody else comes along and uses
> the same label. It is not my responsibility to mitigate the emerging
> collisions. Or how is it expected that I do that? Change my design?
> Bribe the other group?

If this is your concern, anchor your alternative space into a DNS namespace.

If you want to be able to pick any string, it’s only fair others can do the same. Ones reaps what one sows.

> "bob.foo.alt" still squarely falls into "my" namespace

It is indeed not “yours”. If you want a unique name solely belonging to you, you have to play with the rules set out for those. 

Paul

v2.23.0 | Report a Bug | By Email