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

Karl Dyson <karldyson@gmail.com> Fri, 18 April 2025 10:20 UTC

Return-Path: <karldyson@gmail.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 47B991E070D5 for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 03:20:23 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=gmail.com
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 cfiwQlSEXY4l for <dnsop@mail2.ietf.org>; Fri, 18 Apr 2025 03:20:22 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D7EA51E070D0 for <dnsop@ietf.org>; Fri, 18 Apr 2025 03:20:22 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-43cf06eabdaso16748865e9.2 for <dnsop@ietf.org>; Fri, 18 Apr 2025 03:20:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744971621; x=1745576421; darn=ietf.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=4ff2vG6wknr1Fxu8jRTm8/sbGZu0bsheT4WB8EvoQlg=; b=Floz9N/ZgqoRhmIKOkgWDZN9HD5AgzrtwJeTZbF/rCppLPyQKZHOu1FPYcMGzbcmt8 XjmWyTFkCuXS5plj0QmUxiW7WYTxAbWsy83XzE9HCVU6iAmqPat8gezKda+qo2/6kf8H WKqQu1Us2PxGAGtsaxVg3PRg3ee1b49MQnmQxloNORVgor4IEQITotmwW7rdLhyFHq0n i8VjpWgUbzcnLBWT8IlYuvaap2/9jNjGL7LL+px00lbMkQDj5ErpSEH07a7jRamIELNs gimWvT8O9uwHplmh2jqUIPkkD8N3MGqAdhszBotZLIOmIxSI712PGtvO1RuPJG6N0LRR /3Xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744971621; x=1745576421; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=4ff2vG6wknr1Fxu8jRTm8/sbGZu0bsheT4WB8EvoQlg=; b=Zj9ZU2ADj3k0RIWhFLX2pGLnJ+B2RaNohZIYd3DSy9Lf01eBfkDRg41HDlKiDhS00V UlNoVCfqwuHMVXhyzRWp/eVS5ORFHWqNqeQZHjJgzE446glOb2r2iWiVjz7rgxAX6LkS RqOLAktk/DuZ8/1mvP6MXERaFMRPQynhOTMJpRrIFCYcZqgTbiQXZLkcqKUMZxuRtEOc WuIdeYfcfLaPNH8ZTxmO2HrkjYsWIwpT9PGmWNIYwiDMeO5K8hLh/ocGsdXHARBO/F4A +h0M3PgC74GuY7jY1pW7zl66yo0/xNSOavws9pPwz4fMggbscO0qYS+bjoPaHGBCfugC 62IQ==
X-Gm-Message-State: AOJu0Yye7XGgP38EmphTLMgdzcsDHxWvruWrgUR/yla5n5K9jwzFoOy4 oW18CrbcJ24YppR/42OsiE+6+XeFwFR75eRD5AziRdcfMTbrMUl70zw9QVu9
X-Gm-Gg: ASbGncu4Ye+MSig0Y0vYX3G4yzKWLMfnQhStuGOnqSBVWqArQHyDP487UMYR7TWUvv2 YrczAgmpEcyGURgi7lPaeaatWuKvakgR1CKqGfVOmJ1Ooo0zQC01qWY788w0dmmtuXYyG4JgcmP xeNLa06rZnVe+3AWEwAwyHyGKy/T6Ihw08LJpOgPM65RfznZzAbzVmyIfAqdgFjNsPvYdukD178 DZb9MybvuRs/f3oIIvCAxnNu6e/omv6Pb/AHTQA9Nm2LR/fu9EZNUvWeUB/4qz3c6pMQw+0VKZw ZR2DntlNf1GqAHDT1TEgIlrJQflv6tWUTlGDGPC2IVbXocqnkQ==
X-Google-Smtp-Source: AGHT+IFYk8ysV11iwlAByA2ZGYGfzg7t/vBY89nasH5cDE/MXJNAvWvFol1IDrpxGb/r5wUCh/eRFg==
X-Received: by 2002:a5d:588c:0:b0:38d:d666:5457 with SMTP id ffacd0b85a97d-39efbadef97mr1702715f8f.42.1744971621424; Fri, 18 Apr 2025 03:20:21 -0700 (PDT)
Received: from carbon.junesta.net (carbon.junesta.net. [2001:19f0:7401:8ac9::157]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-39efa43d07csm2379856f8f.58.2025.04.18.03.20.20 for <dnsop@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Apr 2025 03:20:21 -0700 (PDT)
Date: Fri, 18 Apr 2025 10:20:19 +0000
From: Karl Dyson <karldyson@gmail.com>
To: dnsop@ietf.org
Message-ID: <20250418102019.hzgh5bm7676rqcki@carbon.junesta.net>
References: <a7220ba0-5e8c-4273-a353-c8371ea23c50@NLnetLabs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <a7220ba0-5e8c-4273-a353-c8371ea23c50@NLnetLabs.nl>
Message-ID-Hash: 3PZZL267B6PI645JG53BTVLJGTYAF4P3
X-Message-ID-Hash: 3PZZL267B6PI645JG53BTVLJGTYAF4P3
X-MailFrom: karldyson@gmail.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] 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/TBFxKjjrp95luSKJLAeRZxlUCWU>
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 Tue, Apr 15, 2025 at 10:38:42AM +0200, Benno Overeinder wrote:
> All,
> 
> At IETF 122, there appeared to be some agreement to adopt this work within
> DNSOP.
> 

I support adoption of this on the basis that I think that guidance is
needed for (at least) operators.

.internal isn't special in most ways; ICANN have reserved it for
private/internal use much like RFC1918 address space is reserved for
private/internal use.

.internal should not get any special processing by DNS servers any more
than 10.0.0.0/8 gets any special handling by routers or firewalls.

I wouldn't want to find that, for example, records within it are not
cached or some other unexpected handling by auth or recursive resolvers.

I'd want to be able to create a zone for it and/or delegate from it
within a private network of DNS servers, and have all the usual
recursion and/or forwards and/or caching work.

Some guidance to operators that says "suggested practice for use of this
TLD within your network is A, B and C, noting that this TLD will not
work on the internet".

Best wishes,
Karl

-- 
Karl Dyson