IETF Logo Mail Archive

[DNSOP] Re: [Ext] Re: WG Last Call: draft-ietf-dnsop-delext-02 (En ds 2026-05-07)

Philip Homburg <pch-dnsop-7@u-1.phicoh.com> Wed, 06 May 2026 14:57 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 01ACEE9F7AF7 for <dnsop@mail2.ietf.org>; Wed, 6 May 2026 07:57:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778079463; bh=fJqlLZ9jbxuAojzlDmwGH4NMIKC+ldnBxDP5kqMicWc=; h=To:Cc:Subject:From:References:In-reply-to:Date; b=k9g778YR4xOl/akm+LmEEnAMP9imdHyceimFWe2mathp0IPb6Tqi7NKYaI31adTeO Vp3ToTS2ZfsBb8kiMo14m/plcZKoyOY9O8+BMjl9TcFQcYG2ZDYdqNO7hOVTbHF9sb yVn3qbQfDf9zxI9+rdGPK6JdV1jVFUH/m89QUXb4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, 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 i_2sj8_IEkL1 for <dnsop@mail2.ietf.org>; Wed, 6 May 2026 07:57:42 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [45.83.6.19]) (using TLSv1.2 with cipher ECDHE-ECDSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7F26DE9F7AF2 for <dnsop@ietf.org>; Wed, 6 May 2026 07:57:42 -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 m1wKdgX-0000NgC; Wed, 6 May 2026 16:57:13 +0200
Message-Id: <m1wKdgX-0000NgC@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: <177697395790.1319979.8285443951188947723@dt-datatracker-b45949c58-5szpr> <CADyWQ+EVTDKM0++2tAuYqTUHpjy5SJPyMa0LLJK2R4+gSZp62Q@mail.gmail.com> <6.2.5.6.2.20260504135922.11777e40@elandnews.com> <F1459673-9CCE-4365-9F29-59827CDE7060@icann.org>
In-reply-to: Your message of "Tue, 5 May 2026 00:08:01 +0000 ." <F1459673-9CCE-4365-9F29-59827CDE7060@icann.org>
Date: Wed, 06 May 2026 16:57:12 +0200
Message-ID-Hash: GT7HX3OZOQN6HWGGBTRU6KXLHIZTBOJT
X-Message-ID-Hash: GT7HX3OZOQN6HWGGBTRU6KXLHIZTBOJT
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.arends@icann.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [Ext] Re: WG Last Call: draft-ietf-dnsop-delext-02 (En ds 2026-05-07)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oud7pof26AgjGpr2qfdFpU8JLyk>
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 RR type carries information that is intended to be acted upon
>      by a resolver during the process of following a referral, prior to
>      sending queries to the authoritative servers for the delegated
>      zone.

Just to be clear. The way I read this, if we ever want a new DS type, then
this range cannot be used.

A DS record does not contain any information that is acted upon prior to
sending quesries to authoritative servers.

Is that correct? The draft contains multiple references to DS without making
it clear that DS-like types are not supported.

v2.46.0 | Report a Bug | By Email | System Status