IETF Logo Mail Archive

[DNSOP] Re: what problem are we trying to solve, was Call for Adoption: draft-davies-internal-tld

John Levine <johnl@taugh.com> Tue, 06 May 2025 13:37 UTC

Return-Path: <johnl@iecc.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 CFC64255D6D1 for <dnsop@mail2.ietf.org>; Tue, 6 May 2025 06:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="W8hE1O2M"; dkim=pass (2048-bit key) header.d=taugh.com header.b="qObBEOfY"
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 TzAHFpqdlg8T for <dnsop@mail2.ietf.org>; Tue, 6 May 2025 06:37:22 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 5381F255D6CC for <dnsop@ietf.org>; Tue, 6 May 2025 06:37:22 -0700 (PDT)
Received: (qmail 22779 invoked from network); 6 May 2025 13:37:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=58f9681a1091.k2505; t=1746538631; x=1746884231; bh=o9AAJL4plL+JdhhkzXXbIciy6S1TxnFuuXzLKITmfYs=; b=W8hE1O2MXq4NCdfyRtcGSIuCCVF5W1c9+meApRnzo3KWFXPkk6QjixGN8QqX/f3Yl/RzTU0UXyGvpmwROvfCiFJ/ne8isB3z1mEsL/bSoXYb7160rmExNqB8fpCp3Ux1s/5+gLPjfvtu2YaaW6QAKdo28mlUb4jv+Kn7IoKbPObSB+uaUxl3UYiPOitMy6aYwSUun/L/cat7lJ4iOpMzH6FS3ay56uNL1/NmSbIyX/ezDhjz3U3bdQjACrYR7Sel/sa6BrX1rSLSb5bIEW830ew5BT3mgsOgMZFO9n4OtPUziwiTodYCTwXC+zTaZdDW7nq7NLDuV7kpRXtlViMC2Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=58f9681a1091.k2505; bh=o9AAJL4plL+JdhhkzXXbIciy6S1TxnFuuXzLKITmfYs=; b=qObBEOfYNxSbx8fOEwyerJSH73BZLVgIl6f2GEMTMmrMkIxUHAuF6WvElKV8DHqwAhFPA9UHiCUODsAWWFqtjAgTdifw/1Yac46LiFgGfJ3wiY6SVfDwLAgzN8mI77gYdo0B6nwTOEHSPEemwm35NIZTlyNDQ58jiS4e5bGoDwIZWF8BDOvv2/VKTupJAyju9zENjzZ6lgD0O/XlgvsciLO+6PTju+QSNMyxxYij5Rs6gwPAkXz+Eccwmyfe+1xcisFeYxX7BGH/qOcarQqhcKVSeZpZlYWc8Ibo63lVy2kNFTyA1DaFWcfNO0GJGmslnvltrD+Tr5EFZIBfwhf2Ng==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 06 May 2025 13:37:21 -0000
Received: by ary.qy (Postfix, from userid 501) id 199BCC803209; Tue, 6 May 2025 09:37:20 -0400 (EDT)
Date: Tue, 06 May 2025 09:37:20 -0400
Message-Id: <20250506133721.199BCC803209@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <m1uCDdk-0000LlC@stereo.hq.phicoh.net>
Organization: Taughannock Networks
References: <1C9E8ABA-4399-491B-A9F4-D9ACCB1BA72C@virtualized.org> <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> <9EE8E4CC-04A3-46C7-BDDF-EF538A822AA8@virtualized.org> <m1uBHRs-0000LsC@stereo.hq.phicoh.net> <BE3A5560-740A-47A9-835B-8C8EEF2B50B9@virtualized.org> <m1uCDdk-0000LlC@stereo.hq.phicoh.net>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: ZMUL5RJK5OCR75L6HW3XOVKFWO2CTE4I
X-Message-ID-Hash: ZMUL5RJK5OCR75L6HW3XOVKFWO2CTE4I
X-MailFrom: johnl@iecc.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: pch-dnsop-6@u-1.phicoh.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: what problem are we trying to solve, was 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/CkQ4I3-_hhsYcZxvarDa781cTB4>
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>

It appears that Philip Homburg  <pch-dnsop-6@u-1.phicoh.com> said:
>So what does .internal have to make it so special that it warrents its own
>RFC? It is reserved by ICANN. That's it. ICANN reserved it for a 
>specific purpose, but does that warrant special treatment at the protocol
>level? 

Right.  Or to answer the question, no.

>But my main requirement is that if we publish a standards track document
>then it should not lead to DNSSEC validation errors or have requirements
>where mobile DNSSEC validators magically add (negative) trust anchors
>depending on which network the device is currently connected to.

I'd flip it around. If we think it is important that DNSSEC works if you have
subtrees with local anchors or no anchors, we should work on that. Saying "add
blah to the root because I think that will keep some validators from returning
errors" isn't it.

R's,
John

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