Re: [DNSOP] Call for Adoption: draft-pwouters-powerbind

John R Levine <johnl@taugh.com> Fri, 01 May 2020 19:18 UTC

Return-Path: <johnl@taugh.com>
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 EB7923A1A48 for <dnsop@ietfa.amsl.com>; Fri, 1 May 2020 12:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=wSHSpxdt; dkim=pass (1536-bit key) header.d=taugh.com header.b=kZMN5Mv+
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bl-4uFXUqQNR for <dnsop@ietfa.amsl.com>; Fri, 1 May 2020 12:18:27 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 6BEC63A1A46 for <dnsop@ietf.org>; Fri, 1 May 2020 12:18:27 -0700 (PDT)
Received: (qmail 55687 invoked from network); 1 May 2020 19:18:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d983.5eac7601.k2005; i=johnl-iecc.com@submit.iecc.com; bh=O5Y2Z5R/ivRIGS8pFR4H4KzNL7ilnXXdR0sJjTu73BE=; b=wSHSpxdtxgptwyafkV73MR10kKUSBCwg1sY2+l5UugunbX8pdIRaeTYTB8vIKc2O5D8WrJ0fGneSYh807EeEK8kYyQdGohyML6AftkYMF3LGCsUDMDTX5Sz9EXsLMvSCVpJ9OrfR75aH3qD6meHUxJsyrhqDTZFYjrL7sLTNGlNQTEA+t+fQ+GI8QGsS/BiUsPN23FYfr+BJtt8gZGN8hjnkMOI3TwJJChgG0pzza6QuYa7M8pygL7/Mqb2ci72f
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d983.5eac7601.k2005; olt=johnl-iecc.com@submit.iecc.com; bh=O5Y2Z5R/ivRIGS8pFR4H4KzNL7ilnXXdR0sJjTu73BE=; b=kZMN5Mv+DCj8+IfNk51dK0iAQ1DoA0Io3B1SYimMsc7rZToOsUHsWEYoLjsM+WjdWwBNxBxVT9m7ovOuyBdz0sqDaNj4jeuWnwLznvwc2UWQDCUz0/Xdh37FL97vXhBrq92IvIl9ls3/YQAPMXsuLC4y8MO8JNwYutUAT8S8mrhod6Ae3cwQO+QG2IJhfwUrEwv39tTS+i/wraRWiCptdo/BlKjg4ABlGq1lzSbY0BF3c1melaKacvQW+uOMm2ch
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 01 May 2020 19:18:25 -0000
Date: 1 May 2020 15:18:25 -0400
Message-ID: <alpine.OSX.2.22.407.2005011511480.33352@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Joe Abley" <jabley@hopcount.ca>
Cc: "IETF DNSOP WG" <dnsop@ietf.org>
In-Reply-To: <63868088-59C8-44A2-9FB3-EC17EC23667D@hopcount.ca>
References: <yblr1w438fb.fsf@w7.hardakers.net> <20200501014428.427E818950D7@ary.qy> <CA+nkc8B44xPK=QxRsOsPtY1V0NT7Bji7Cf2AiPp2SH29oG6gNw@mail.gmail.com> <alpine.OSX.2.22.407.2005011422400.33172@ary.qy> <63868088-59C8-44A2-9FB3-EC17EC23667D@hopcount.ca>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DyNAfLDONB9oKpRTojUkRluCgnI>
Subject: Re: [DNSOP] Call for Adoption: draft-pwouters-powerbind
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 01 May 2020 19:18:30 -0000

> In a sense, a glue record with the same owner name as a zone cut could be equivalent to a glue record with an owner name that is subordinate to a zone cut. I don't have enough of the spec in my head to know why they would definitively be different from the protocol perspective. I realise it's not normal, but I don't know that it's prohibited.
>
> I definitely don't know operationally how different DNS or registrar software implementations treat that case. I don't think the registry systems I'm familiar with allow host and domain objects with the same name to coexist, but I realise I could quite well be wrong.

I'm pretty sure I've never seen it in any TLD file.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly