Re: [DNSOP] unrelated name server name recommendation

Paul Vixie <paul@redbarn.org> Tue, 05 March 2024 00:05 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 048ACC1C4D84 for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 16:05:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level:
X-Spam-Status: No, score=-2.196 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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=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 y9JXW4fUmnOw for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 16:04:57 -0800 (PST)
Received: from util.redbarn.org (util.redbarn.org [IPv6:2001:559:8000:cd::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 68A8FC18DB97 for <dnsop@ietf.org>; Mon, 4 Mar 2024 16:04:57 -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 D029B1A2926; Tue, 5 Mar 2024 00:04:56 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=redbarn.org; s=util; t=1709597096; bh=BIz9t8AFH4jSSAjow/rW8Zivxi3HAemysux+no9PRVY=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=iKqAocN4CcsCP4ElCwEEXAsLbYUVW5O1KIBfcmb94fG4mURKIU0KMC0EUVfSkYkFf Ik/Hfo04l+9NJvZzGbLZpfWBpAk3ZcIl9pb1aXfwMerzYEOrHV2D751ogLFDw0JzP4 m5qcIFB5Hogvuuj0yowJ3YJ61cdkBAg87llGxnSo=
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 9B666C3F1F; Tue, 5 Mar 2024 00:04:56 +0000 (UTC)
To: Paul Wouters <paul@nohats.ca>
Cc: dnsop@ietf.org
References: <978e2792-1cdf-b33e-532f-83356a5f1ff2@redbarn.org> <BE280DCA-104F-49AB-B28E-9C703E65E213@nohats.ca>
From: Paul Vixie <paul@redbarn.org>
Message-ID: <9511ad98-2dca-d95e-6e10-9cf6191a14db@redbarn.org>
Date: Mon, 04 Mar 2024 16:04:55 -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: <BE280DCA-104F-49AB-B28E-9C703E65E213@nohats.ca>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/QQ2GVJo8k8zcoYVCHN57iYSpkMc>
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: Tue, 05 Mar 2024 00:05:02 -0000


Paul Wouters wrote on 2024-03-04 11:14:
> On Mar 4, 2024, at 14:04, Paul Vixie
> <paul=40redbarn.org@dmarc.ietf.org> wrote:
>> 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,
> 
> It means every registrant, who doesn’t know about DNS, has to create
> host objects for glue and whenever the ISP changes nameserver names
> (eg gets bought, sold or merges), or IP address, the ISP has to talk
> to the registrant to fix things at their registry. I can promise you
> those in-domain name servers will quickly become very unreliable.

not. the rest of the paragraph you quoted six words from above was:

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

it's not a "has to". i expect it either won't be used when a sale is 
possible, or will be removed prior to such sale. i see fujiwara's 
proposal as a way to reduce distributed system complexity for those who 
can behave this way, and strictly as a recommendation.


-- 
P Vixie