IETF Logo Mail Archive

[dd] DELEG and the DNS camel

Jim Reid <jim@rfc1035.com> Wed, 20 March 2024 05:49 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dd@ietfa.amsl.com
Delivered-To: dd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61BEC14F749 for <dd@ietfa.amsl.com>; Tue, 19 Mar 2024 22:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 i1CqnzPF4nbx for <dd@ietfa.amsl.com>; Tue, 19 Mar 2024 22:48:58 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2963C14F6B3 for <dd@ietf.org>; Tue, 19 Mar 2024 22:48:57 -0700 (PDT)
Received: from smtpclient.apple (dhcp-8280.meeting.ietf.org [31.133.130.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 8E18E2420E4A; Wed, 20 Mar 2024 05:48:51 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <26106.28843.737951.303072@gro.dd.org>
Date: Wed, 20 Mar 2024 05:48:47 +0000
Cc: "dd@ietf.org" <dd@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8DC50CB9-998D-4DAD-BA99-8F70E7B0F217@rfc1035.com>
References: <D52147D7-C779-46C4-8B27-C27502D541D0@icann.org> <26106.28843.737951.303072@gro.dd.org>
To: David Lawrence <tale@dd.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/2VU2EzL6cd-32sK9p-UCF27IuoA>
Subject: [dd] DELEG and the DNS camel
X-BeenThere: dd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DNS Delegation <dd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dd>, <mailto:dd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dd/>
List-Post: <mailto:dd@ietf.org>
List-Help: <mailto:dd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dd>, <mailto:dd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2024 05:49:00 -0000


> On 20 Mar 2024, at 05:14, Dave Lawrence <tale@dd.org> wrote:
> 
> Does the existence of the camel mean that we never do anything more to change the DNS?  

Of course not. Though I for one would be a lot happier if we had a one-in, one-out policy when it comes to DNS RFCs.

ISTR a discussion 10+ years ago about the DNS protocol spec sprawling over a gazillion RFCs. Camels aside, it would be a good idea to be mindful of that. Other than a total rewrite of RFC1035 I have no suggestions on how to fix this.

v2.23.0 | Report a Bug | By Email