[DNSOP] Re: Is DELEXT too restrictive?

Philip Homburg <pch-dnsop-7@u-1.phicoh.com> Mon, 03 August 2026 16:00 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 CAD71122C3618 for <dnsop@mail2.ietf.org>; Mon, 3 Aug 2026 09:00:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785772845; bh=t6yRXBnIQ2T1ovnIAr2l6N+DpYypr3ERNhGFgXFHYnM=; h=To:Cc:Subject:From:References:In-reply-to:Date; b=tcy05ZbLPypgF+YSwTCt8dyzFT4GHL2liCtNOBZC97ozFrmqop9yLH5H8zwvpj2Yt nLedLiEfawKstAX3xHBO0qKzLdpJ84ThYRvNQPW0gzk2GpnWLTjjujnB55S3ULxT61 VSkKcBRzFet7kliS/cLwG+dOd72gejSDFoq2Mdys=
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 MXLP5Q12CGV6 for <dnsop@mail2.ietf.org>; Mon, 3 Aug 2026 09:00:45 -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 E87FD122C35C5 for <dnsop@ietf.org>; Mon, 3 Aug 2026 09:00:41 -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 m1wqv5a-0000NeC; Mon, 3 Aug 2026 18:00:30 +0200
Message-Id: <m1wqv5a-0000NeC@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> <20260729165200.06E34117AEC43@ary.qy>
In-reply-to: Your message of "29 Jul 2026 12:51:59 -0400 ." <20260729165200.06E34117AEC43@ary.qy>
Date: Mon, 03 Aug 2026 18:00:29 +0200
Message-ID-Hash: KO3BUK2XFJ3CG2IC7VNHIGONHBJD63HI
X-Message-ID-Hash: KO3BUK2XFJ3CG2IC7VNHIGONHBJD63HI
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: John Levine <johnl@ietf.email>
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/t8uQFy0IBIzUXkB5F_lD0EYsMmQ>
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>

> >The DE flag really was introduced as a capability negotiation mechanism. Lat
> er, it turned out that sending both NS
> >and DELEG in the referral didnt actually cause interoperability problems (I 
> believe Shumon and I were the ones who
> >tested this).
> 
> In the other direction, if you have a delegation point with only
> DELEG, and you sent a response to an old non-aware resolver with
> an authority section that has DELEG and maybe DS and maybe some
> RRSIGs, will resolvers ignore the useless (to them) stuff and treat
> it as NODATA, or barf because the authority section has garbage?
> 
> I have no idea, perhaps people have tried it out.
> 
> If the answer is NODATA the case for the DE bit is a lot weaker.

There is a problem with DELEG validation. I don't remember all corner cases,
but DELEG-unaware validating resolvers may conclude bogus if they receive
DELEG records (which they believe is a child-side type) with a parent-side
signature.