IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Wed, 14 December 2022 16:29 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 4EF1CC14F745 for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2022 08:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.887
X-Spam-Level:
X-Spam-Status: No, score=-5.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, 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=fail (1024-bit key) reason="fail (message has been altered)" 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 WB6miejwy7BP for <dnsop@ietfa.amsl.com>; Wed, 14 Dec 2022 08:29:21 -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 86FB4C14CF00 for <dnsop@ietf.org>; Wed, 14 Dec 2022 08:29:20 -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=1671035323; bh=GthWGjiMs5nbupl009hUsl9gnTxajOeM8CwSkj1pFI4=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=Vh8LofYtOnpu1w4VX4Au2QAgm6FLmscE1caF9ZlCRFTo1y9GVyCb0rjzo+EjbLMKq CSV3Bt7HZ+dTl4mBTrE6IgJfEcyggbU3LzjVXwkVMZ0bY6sd+kz78NoXAWBLYeQmz5 t1CZxSaAkDpwz6ssJmLk0Pw6DVBUsXohd7La51iU=
Received: from [192.168.0.130] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 2BEGSgA5113546 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 14 Dec 2022 17:28:42 +0100
Content-Type: multipart/alternative; boundary="------------6M9wD4CjGr0EB0IafNdn5sWQ"
Message-ID: <221b69b9-adea-d13a-2976-25bc9464621f@lear.ch>
Date: Wed, 14 Dec 2022 17:28:42 +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 <mschanzenbach@posteo.de>
Cc: Joe Abley <jabley@hopcount.ca>, Paul Hoffman <paul.hoffman@icann.org>, dnsop <dnsop@ietf.org>
References: <20221214103710.zm6t5oshhnfwsm4g@werkbank> <9C02A5E7-3EA5-40EB-B265-4989D9961B6E@nohats.ca>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <9C02A5E7-3EA5-40EB-B265-4989D9961B6E@nohats.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bYKjrX2OrNJC8e6YKT2AkvOhh_Y>
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:29:26 -0000

We're off in the woods again.  Let's keep these two principles in mind:

  * The DNS resolution mechanisms are not expected to resolve, let alone
    secure names ending in .ALT.
  * How other resolution mechanisms secure names is their affair.

Therefore, any collisions that occur within .ALT are for alternate 
resolution mechanisms themselves to resolve (or not, as they see fit).  
Which brings me to this:

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).

Eliot

v2.23.0 | Report a Bug | By Email