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

Warren Kumari <warren@kumari.net> Wed, 16 April 2025 12:58 UTC

Return-Path: <warren@kumari.net>
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 50EDE1CF582C for <dnsop@mail2.ietf.org>; Wed, 16 Apr 2025 05:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=kumari.net
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 qnaSvEyibsRa for <dnsop@mail2.ietf.org>; Wed, 16 Apr 2025 05:58:26 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 780F61CF57F9 for <dnsop@ietf.org>; Wed, 16 Apr 2025 05:58:26 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5e61d91a087so9951000a12.0 for <dnsop@ietf.org>; Wed, 16 Apr 2025 05:58:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google; t=1744808305; x=1745413105; darn=ietf.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KPD9dt98YlR3BAB8FSxH9l28oPmMFhVD5eqvOx9yyDE=; b=DuqM+j5B9Q8w4fezfRznRtqOaKUMG7T4BqGyPLR9cK7CQXbpkVJt08y9ZJHxBL+SDB jqAOGdRFS4V7lkLE7lOcvO4VCQ6OaZ1i98kaUv40mMka0N9CwIduVBFayX7NeBt7R9Qc MUM9uzTt6jOPAGt+IMAUDADMnZqQgHytQQesQgSkqjAFdou+5RxSuIz7cjZYKpsDtpFz QwxXUWeJQvf+WPMxi+AzhIyGU8VTXsCbvtkw78hIqSRPXJe/t1X4fdovFOK8yg8RUpMr c8KMpnXzPTruiohw5VxjLAnPKgWuayipsUV4JwoBKwYXsvK3TpHI4Xc8src6/91ekibk 8Hmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744808305; x=1745413105; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KPD9dt98YlR3BAB8FSxH9l28oPmMFhVD5eqvOx9yyDE=; b=U9bhFTPSYC3XIeI3EMlAPI3wgHZjRPhhiaz8irn9P5c1M8Aknk2EWKFcQiaI1xcTp9 qHMlWyvufNq0kB1r9If/HWf/tSLM/AimFJNsmGAy4xdNL8YlvfANUyk3S8iwdmk9k1Ln /8mABMGq9Wwf/7iEtND/vzbFK4IztmXHM54o5NR98Q16q04+Lv1Gdv9AZZVU9+EG5hQF gMs+pdQ9FlmnfnpoU/QXK/UE6zG8qsMZyfQxoC9vFO4Xgxz/x8jKIFRpoTfFnvIJYED3 K8IuIQhBKfkyuHwjIhRjerYdfD4Z75t7dHjNo1HPImrX6VwUPKRVbBd8MSooKWRmbkU+ 5TiA==
X-Forwarded-Encrypted: i=1; AJvYcCU/N0yv35Qc8zd9vKK7XXxq6e1VDxSAiZu/RE8MMFQJR9d6G5pu8Mca3aYuorScQnughlGvlQ==@ietf.org
X-Gm-Message-State: AOJu0YyQSBtNg1B09KooNRPBAxvJEYVXXdf7mbmmhJjb48KrVuqXby7G 9TX3nq04UXz9Wuuc+AA8sfqgPxxBKm9yUGYqh8p9yPJ0zr9C69wQCURcUU9z+gLUQf+DseCoXYp na3My0TdR9SomH5BbBFXWw3ZftKJoS2MvdpHitQ==
X-Gm-Gg: ASbGncuXuz0fDYO+9cUJT0+07U8NYvB9Fv9g456YDX97lcr5o4YwOijCtXKZ3GJHyi1 ykVzCkv3TdYTc5WMDL/lTJ7ou9Scz6hd2laruuU589BnxTrYjSm7lZVUrO3NAdDgrRJ111Uczjw kZ9MUhPyqIjqO1vKGWfD8aRIZihfSTSkTCii8IovnD7anMaw==
X-Google-Smtp-Source: AGHT+IHtdCMnNdDonkZYh+WimTeq7zQo8vPpRZx5hAQAeLM86snxwS2YBZHNXZ5bRdrPXk1Z94nFoafiwj1S4B5BfJI=
X-Received: by 2002:a05:6402:2755:b0:5ec:939e:a60e with SMTP id 4fb4d7f45d1cf-5f4b6df2b65mr1449165a12.0.1744808305251; Wed, 16 Apr 2025 05:58:25 -0700 (PDT)
Received: from 649336022844 named unknown by gmailapi.google.com with HTTPREST; Wed, 16 Apr 2025 05:58:24 -0700
Received: from 649336022844 named unknown by gmailapi.google.com with HTTPREST; Wed, 16 Apr 2025 05:58:24 -0700
Mime-Version: 1.0
In-Reply-To: <e9193eec-06a4-491b-b35c-2cd53e44b8ba@NLnetLabs.nl>
References: <85BB19F8-03C2-4F36-A878-0AE46CD912C6@gmail.com> <FCB15449-C511-4959-8709-B6BB66B03E11@strandkip.nl> <e9193eec-06a4-491b-b35c-2cd53e44b8ba@NLnetLabs.nl>
X-Mailer: Superhuman Desktop (2025-04-15T23:45:50Z)
X-Superhuman-ID: m9jxsvf4.090bc39c-ef9a-4b72-b0fc-20c66b23bb9f
X-Superhuman-Draft-ID: draft00c453010baba0c9
From: Warren Kumari <warren@kumari.net>
Date: Wed, 16 Apr 2025 05:58:24 -0700
X-Gm-Features: ATxdqUGJbdoMwDORO-MCvr2na5OwEPnZEmz022ZoetcESZW_Rd-EgpQFqsxRk94
Message-ID: <CAHw9_iKsKYviTNHBVd7fXJ0HXKHj+d7qCXDJALk-WrEWVS=HfA@mail.gmail.com>
To: Benno Overeinder <benno@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary="0000000000003c703a0632e4d772"
Message-ID-Hash: 7EYRC3JDYXVMFNINQQXJDP25DIBVCOI6
X-Message-ID-Hash: 7EYRC3JDYXVMFNINQQXJDP25DIBVCOI6
X-MailFrom: warren@kumari.net
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: Joe Abley <jabley@strandkip.nl>, Geoff Huston <gih902@gmail.com>, DNSOP Working Group <dnsop@ietf.org>, DNSOP Chairs <dnsop-chairs@ietf.org>
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/HibRiBh08elf3_rLt1X6fOwwV_A>
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 Wed, Apr 16, 2025 at 8:30 AM, Benno Overeinder <benno@nlnetlabs.nl>
wrote:

> Hi Geoff, Joe, all,
>
> I understand the confusion caused by the Editor note at the beginning of
> Section 5.1. We have discussed the status of the document with the authors,
> and the intention is for it to be published as a Proposed Standard in order
> to add the label to the Special-Use Domain Name registry.
>
> If the draft is adopted by the DNSOP working group, Section 5, IANA
> Considerations, will be updated accordingly. With Proposed Standard status,
> the .internal label is intended to be added to the Special-Use Domain Name
> registry.
>


Yup, what Benno said…


The "It not yet decided.." text was added when it was still unclear if A:
DNSOP might be willing to adopt it and B: if DNSOP would want it to be
added to the SUDN registry if so.

I agree that having DNSOP adopt it and not add it to SUDN would be weird,
and I obviously think that it should be added, but I did not want to be
presumptive.

So, if adopted by DNSOP, I / we will:
1: update the track to PS
2: remove the "It not yet decided…"
3: discuss Tommy Jensen's "considering "MAY" for allowing resolution
libraries to treat this specially"
4: whatever else the WG wants… :-)

W


> We hope this answers your questions.
>
> On behalf of the DNSOP co-chairs,
> -- Benno
>
> On 16/04/2025 13:17, Joe Abley wrote:
>
> Hi Geoff,
>
> I have previously disagreed with you about whether adding this name to the
> special use domain names registry is a good idea. But I very much agree
> with you about this adoption call, or at least I am confused about the same
> things that you say you are confused about.
>
> If we are not adding this domain to the registry in question, we don't
> need a document. Surely clarity on that fundamental question should come
> first.
>
> Joe
>
> On 15 Apr 2025, at 22:24, Geoff Huston <gih902@gmail.com> wrote:
>
> I am left asking myself: what is the purpose of this document?
>
> I had assumed that the purpose was to provide RFC documentation to justify
> the inclusion of this label in the Special Use Domain Name registry, but
> the draft reads: "(Editor note: It not yet decided if the "internal"
> top-level domain should be added to the list of special-use domain
> names..."
>
> If there is no intent to add this label to the Special Use registry then
> what is the intent of this document and why is it being proposed to be an
> RFC?
>
> Why is DNSOP being asked to adopt this document if there is no clarity as
> to what is being proposed here?
>
> thanks,
>
>    Geoff
>
> On 15 Apr 2025, at 6:38 pm, Benno Overeinder <benno@nlnetlabs.nl> wrote:
>
> All,
>
> At IETF 122, there appeared to be some agreement to adopt this work within
> DNSOP.
>
> Below are the relevant meeting minutes and a link to the presentation from
> the session:
>
> A Top-level Domain for Private Use, Warren Kumari
>        https://datatracker.ietf.org/doc/draft-davies-internal-tld/
>        Ted: Should work on this
>        Tommy Jensen: Work on here
>                Consider that libraries MAY treat it as special to catch
> things
>                from going upstream
>        Stuart Cheshire: Agree with logic, should be listed in registry
>        Jim: Not for IETF because ICANN told us what to do
>                Maybe figure out the process
>                Thanks for bearing with all the machinations
>        Mark: Locally served registry requires that the names have insecure
>        delegations in the DNS
>                Bring-your-own-devices work because of this insecure
> validation
>        Suzanne: How much work is needed?
>                Warren: Almost no work
>
> https://datatracker.ietf.org/meeting/122/materials/slides-122-dnsop-
> sessa-draft-davies-internal-tld-a-top-level-domain-for-private-use-00
>
> Warren Kumari has responded to some of the questions raised at the mic
> during the session in an email to the mailing list.
>
> This email begins a Call for Adoption for draft-davies-internal-tld,
> "A Top-level Domain for Private Use."
>
> You can find the draft here: https://datatracker.ietf.org/doc/draft-
> davies-internal-tld/
>
> Please review the draft and share your thoughts on the mailing list,
> clearly stating whether you support its adoption by DNSOP.  Also let us
> know if you are willing to contribute text, provide reviews, or help in
> other ways.
>
> Due to the Easter holiday, we are extending the usual timeline for this
> call.
>
> The Call for Adoption will end on May 2, 2025.
>
> Thanks,
>
> For DNSOP co-chairs
> -- Benno
>
> _______________________________________________
> DNSOP mailing list -- dnsop@ietf.org
> To unsubscribe send an email to dnsop-leave@ietf.org
>
> _______________________________________________
> DNSOP mailing list -- dnsop@ietf.org
> To unsubscribe send an email to dnsop-leave@ietf.org
>
> _______________________________________________
> DNSOP mailing list -- dnsop@ietf.org
> To unsubscribe send an email to dnsop-leave@ietf.org
>
> --
> Benno J. Overeinder
> NLnet Labs
> https://www.nlnetlabs.nl/
>
> _______________________________________________
> DNSOP mailing list -- dnsop@ietf.org
> To unsubscribe send an email to dnsop-leave@ietf.org
>
>