IETF Logo Mail Archive

[DNSOP] Re: [Ext] Re: [EXTERNAL] Re: Call for Adoption: draft-davies-internal-tld

David Conrad <drc@virtualized.org> Sat, 03 May 2025 17:55 UTC

Return-Path: <drc@virtualized.org>
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 B282824708F3 for <dnsop@mail2.ietf.org>; Sat, 3 May 2025 10:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=virtualized.org
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 4SJyydDiChPk for <dnsop@mail2.ietf.org>; Sat, 3 May 2025 10:55:44 -0700 (PDT)
Received: from mail-24420.protonmail.ch (mail-24420.protonmail.ch [109.224.244.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D108624708EA for <dnsop@ietf.org>; Sat, 3 May 2025 10:55:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtualized.org; s=protonmail3; t=1746294942; x=1746554142; bh=wA6YC6HBsc0IVBn+uI/90MCZhu01NzvJ+sDTR84qREM=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=gXvO0vrcV+XGmuzNYPhiu/fuT77ORyCoE4ErC4SZnc63v61OKlmMNbCrySvd/NVAf Koi34LdZcdVe0Uc+SyrCKFwngbsfQghZ0vFJJgUNZZEw5IccBCFQMPYcBLBNnOTZ2v esBPq/2jr24YUnLdsBWuPjHLbdgyrGhcoHVlqc9COjIFZ4VmEKbeZaSIwCFYMER5nB 0PgUKm1YY+R6m9hObklFyt8EU8cr0aMhvCvZLok/AvkPU9fyCvHgT109l5pjUHBk8E w8yJVF08sL3OsxzOh2RHqZpfCvW14FAJDwmOsIvZaxk59HE1w77uhijqRvLhatYeMC Rq5vauNCOsWiQ==
Date: Sat, 03 May 2025 17:55:39 +0000
To: Philip Homburg <pch-dnsop-6@u-1.phicoh.com>
From: David Conrad <drc@virtualized.org>
Message-ID: <9EE8E4CC-04A3-46C7-BDDF-EF538A822AA8@virtualized.org>
In-Reply-To: <m1uBDWf-0000MlC@stereo.hq.phicoh.net>
References: <1C9E8ABA-4399-491B-A9F4-D9ACCB1BA72C@virtualized.org> <C497EC3A-A06B-4DCC-B0C8-382A3424D7D5@strandkip.nl> <SA1PR15MB43700B9B2C9151FB31381082B3BC2@SA1PR15MB4370.namprd15.prod.outlook.com> <866409E5-0D9A-4669-8C6E-C9D1C7BDAA21@dnss.ec> <SA1PR15MB4370BAE2BD669193DDB9AE44B38D2@SA1PR15MB4370.namprd15.prod.outlook.com> <20250502171756.5AC67C762C3C@ary.qy> <SA1PR15MB43704113DF8B19A8A5A66AD6B38D2@SA1PR15MB4370.namprd15.prod.outlook.com> <4B83E121-9562-449C-A00E-2A31894ADED0@icann.org> <m1uBDWf-0000MlC@stereo.hq.phicoh.net>
Feedback-ID: 101327196:user:proton
X-Pm-Message-ID: 6512836098ceaf53871e2fd08013f71677ee2d91
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha256"; boundary="------2a407fa3430ff4be648dee842456e3928e2f256b0ed6644a04777658ffeddf16"; charset="utf-8"
Message-ID-Hash: LMCLOPMQXZH5EQWQG6EZX7EY3F7R2G3C
X-Message-ID-Hash: LMCLOPMQXZH5EQWQG6EZX7EY3F7R2G3C
X-MailFrom: drc@virtualized.org
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: dnsop@ietf.org, Paul Hoffman <paul.hoffman@icann.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [Ext] Re: [EXTERNAL] Re: Call for Adoption: draft-davies-internal-tld
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xe2z91ov0fV7SPBbdTpkZO2onEo>
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>

On May 3, 2025, at 7:07 AM, Philip Homburg <pch-dnsop-6@u-1.phicoh.com> wrote:
> The problem starts when a standards track document promotes a name that
> does not exist for some purposes.

Like:

RFC 2605
RFC 7686
RFC 9476
...?

I don’t think this has been or is the problem. I believe the problem starts when users want to make particular assumptions about names that do not exist (e.g., they should be looked up in some non-DNS system, they are for internal use, etc.)

> That's a situation that requires careful handling. Either by not having
> such a document in the first place or by making sure that the name
> that does not exist can be used safely without manual configuration on
> any end-user device that happens to include a DNSSEC validator.

As Paul points out, this suggests a need for documentation on how an end-user device that happens to include a DNSSEC validator should behave in the face of names that do not exist for some purpose.

Regards,
-drc

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