Re: [DNSOP] unrelated name server name recommendation

Paul Vixie <paul@redbarn.org> Mon, 04 March 2024 19:04 UTC

Return-Path: <paul@redbarn.org>
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 D724FC17C884 for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 11:04:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.188
X-Spam-Level:
X-Spam-Status: No, score=-7.188 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, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redbarn.org
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 gH_6Dk0WRexc for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 11:03:53 -0800 (PST)
Received: from util.redbarn.org (util.redbarn.org [24.104.150.222]) (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 79921C151088 for <dnsop@ietf.org>; Mon, 4 Mar 2024 11:03:49 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.redbarn.org", Issuer "RapidSSL TLS RSA CA G1" (not verified)) by util.redbarn.org (Postfix) with ESMTPS id 161A11A2926; Mon, 4 Mar 2024 19:03:47 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=redbarn.org; s=util; t=1709579027; bh=RmAwzW0y4RhwM0BslLqd4zSS6vGZTbnSarT1z1HNTSE=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=TuUuTJXkrGAFDiPIpD3MKft3lL4rT9FcfdpsaR78ADzrERqr5y3t2E+BD0c99W+9/ lwNI/fRE/Au21iPahJypIvooYrto/JWYvy2nAQd/YwEDhWuwWzzLCEZJGVS6Ko/V1M ODD/Bd13P5QeNQaZug5sXhk/ztqYqoJ+U6TkzsZQ=
Received: from [24.104.150.175] (dhcp-175.access.rits.tisf.net [24.104.150.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 180DAC3F1F; Mon, 4 Mar 2024 19:03:46 +0000 (UTC)
To: Ben Schwartz <bemasc=40meta.com@dmarc.ietf.org>
Cc: Kazunori Fujiwara <fujiwara@jprs.co.jp>, "dnsop@ietf.org" <dnsop@ietf.org>
References: <20240304.133402.1564724475540797830.fujiwara@jprs.co.jp> <SA1PR15MB4370D2EB41A14F843A660F26B3232@SA1PR15MB4370.namprd15.prod.outlook.com>
From: Paul Vixie <paul@redbarn.org>
Message-ID: <978e2792-1cdf-b33e-532f-83356a5f1ff2@redbarn.org>
Date: Mon, 04 Mar 2024 11:03:44 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/7.0.60
MIME-Version: 1.0
In-Reply-To: <SA1PR15MB4370D2EB41A14F843A660F26B3232@SA1PR15MB4370.namprd15.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/m8Mp6HUKJGoP5ycL7mOMnTv34Ro>
Subject: Re: [DNSOP] unrelated name server name recommendation
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: Mon, 04 Mar 2024 19:04:01 -0000


Ben Schwartz wrote on 2024-03-04 07:20:
> To rephrase, it sounds like you are proposing a rule that zones should 
> be configured to use at most one glueless delegation step.

i think it's the inverse. according to fujiwara-san's comments each zone 
must have at least one in-zone name server name:

<<the domain names that host the name server names MUST be resolvable by 
delegations using one or more in-domain name server names.>>

this means a zone will always be reachable through at least one in-zone 
data path (name server name and associated address records.) the result 
would be that a full resolver would never have to pause its current 
lookup while searching for address records matching an out-of-zone name 
server name.

i think it's a solid recommendation, but can only be a SHOULD not a 
MUST, both because of the installed base / long tail, and the 
impossibility of enforcing it, and the market needs of parking lots.

-- 
P Vixie