[DNSOP] Re: Is DELEXT too restrictive?

Philip Homburg <pch-dnsop-7@u-1.phicoh.com> Tue, 04 August 2026 12:42 UTC

Return-Path: <pch-b55F8B228@u-1.phicoh.com>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id EC24912355DEC for <dnsop@mail2.ietf.org>; Tue, 4 Aug 2026 05:42:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785847342; bh=jP9Zt0W+AjYpKsbBLUuxbGAMOcE0jD0O2pt3meTOtt4=; h=To:Cc:Subject:From:References:In-reply-to:Date; b=jg1zp02k0nonVD8cRCyxDBSalSnwde+Xs5tWi1xDK9AsoP+XvImSb+z9dcICCTBDx uJ/o6+D89T+g2neNza0UdRn+GDzj+ZnUvkY3DJtITHeV+v68AP3PyOIz1ItZcEnrCO 5wgLPHTbD8mcSxDoBFxeSK/n/ppOiatqyOg+AB6U=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAtSF-vd5i5c for <dnsop@mail2.ietf.org>; Tue, 4 Aug 2026 05:42:22 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [IPv6:2a10:3781:2413:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-ECDSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 77EA212355DE7 for <dnsop@ietf.org>; Tue, 4 Aug 2026 05:42:22 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305) (Smail #158) id m1wrETN-0000NzC; Tue, 4 Aug 2026 14:42:21 +0200
Message-Id: <m1wrETN-0000NzC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop-7@u-1.phicoh.com>
Sender: pch-b55F8B228@u-1.phicoh.com
References: <m1wozxZ-0000OVC@stereo.hq.phicoh.net> <538EEAAD-9492-41A2-B412-13BC026F0719@dnss.ec> <m1wp2tq-0000O0C@stereo.hq.phicoh.net> <7EE41823-C911-486E-A49B-2D043DE02046@dnss.ec> <m1wp5jC-0000NrC@stereo.hq.phicoh.net> <ECEF8125-D62A-4109-B8B0-205A7C3200F5@dnss.ec> <m1wquvB-0000NwC@stereo.hq.phicoh.net> <1C0A23F3-92CF-46F7-8DFE-9F804A462D9E@dnss.ec>
In-reply-to: Your message of "Mon, 3 Aug 2026 20:49:44 +0100 ." <1C0A23F3-92CF-46F7-8DFE-9F804A462D9E@dnss.ec>
Date: Tue, 04 Aug 2026 14:42:21 +0200
Message-ID-Hash: BG3GYSEAFRKZCSWC7VYDUJJBM2LQMQFA
X-Message-ID-Hash: BG3GYSEAFRKZCSWC7VYDUJJBM2LQMQFA
X-MailFrom: pch-b55F8B228@u-1.phicoh.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Roy Arends <roy@dnss.ec>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Is DELEXT too restrictive?
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/f-LsIMjU66efYyzk5kt6k5azV58>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

>    I think my proposal keeps DELEXT itself simpler. Rather than
>    having the generic protocol decide, based on a type range,
>    whether NS is replaced, each Delegation Type defines its own
>    interaction with NS.  Existing implementations automatically
>    have a well-defined compatibility behaviour for future Delegation
>    Types that they do not yet implement.

Maybe I misunderstand your proposal. It seems that what you are saying is
the following:

Suppose we have a secondary DNS server. It knows about DELEG but not
anything else. It gets a zone transfer and the zone has a delegation
type record that the server doesn't know about. Now the secondary cannot
serve the zone because it doesn't know the interaction with NS.