IETF Logo Mail Archive

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

David Conrad <drc@virtualized.org> Thu, 17 April 2025 19:47 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 DC36F1DCE541 for <dnsop@mail2.ietf.org>; Thu, 17 Apr 2025 12:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_MESSAGE=0.001, MIME_HTML_MOSTLY=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 k1kdlZ64_wxS for <dnsop@mail2.ietf.org>; Thu, 17 Apr 2025 12:47:36 -0700 (PDT)
Received: from mail-24421.protonmail.ch (mail-24421.protonmail.ch [109.224.244.21]) (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 06DC91DCE534 for <dnsop@ietf.org>; Thu, 17 Apr 2025 12:47:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtualized.org; s=protonmail3; t=1744919252; x=1745178452; bh=t9M7kAYm0rqhz6/fuNpYzqkWZnk+CvZ52KRUmrki+TA=; 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=VfnkFetEjYnH0J1bfPJjB02kgxX2sAihoGK2IOqysIU+TYdoip+/kOPql/hGiJbml PTZs7HG9/hdU6r1vV1j4ndGMysQLl934QD75dKA1WBdY/F+IVcfOTedJ0i6oVsdENb Hs8nkGsuhi66xVV96oOD8UMqtwZr+CHlXd8L1kN+TlPBrYumediQXjnfa9804BTgAG vn56II+r+eeX9Stiy7bLfAnD/EV5DlKzV6/2kKLXfMcn6bG6+5LhoZCvLtRgBFLaDB TLgc5GQIUZUu0ThEVfmhdxtYSOb4k6drg5VpVLOWL5kJVhFKsQFAaU6NIrrVQ4YxNH TZuRIj7fgfiDg==
Date: Thu, 17 Apr 2025 19:47:27 +0000
To: Jim Reid <jim@rfc1035.com>
From: David Conrad <drc@virtualized.org>
Message-ID: <9067E899-0554-45FD-8A2F-3E91E8A85177@virtualized.org>
In-Reply-To: <A7B914F4-78DF-4210-B8B3-49FE852646AD@rfc1035.com>
References: <016201dbaee8$d1106580$73313080$@gmail.com> <B3F33508-46B5-4B19-A265-C4EAFE9D4000@strandkip.nl> <1C9E8ABA-4399-491B-A9F4-D9ACCB1BA72C@virtualized.org> <A7B914F4-78DF-4210-B8B3-49FE852646AD@rfc1035.com>
Feedback-ID: 101327196:user:proton
X-Pm-Message-ID: cf781d6120b7772096f7fbc73d50ba5ad9559dde
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha256"; boundary="------a521549e85eac46f6f8d5594df7021fb4c5f4826fc4671d14fff42fc8db56b1d"; charset="utf-8"
Message-ID-Hash: 25SXLT3OAI2WMGYPABZDVKGNY6BAIKSJ
X-Message-ID-Hash: 25SXLT3OAI2WMGYPABZDVKGNY6BAIKSJ
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: Working Group DNSOP <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] 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/SLiZwsbEItSpgcuuu-E3qYKDs0o>
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>

Jim,

On Apr 17, 2025, at 11:22 AM, Jim Reid <jim@rfc1035.com> wrote:
> If ICANN or some other body wants to have some sort of registry for its "special" TLDs, they can go ahead and do that. There's nothing stopping them. They don't need IETF approval. IMO there's nothing for the IETF to do here - apart from keeping well away from those toxic swamps.

My understanding is that ICANN (or anybody) needs IETF approval to modify https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml. If that’s not the case, “never mind”.

I just think the reliance on lore and oral tradition as opposed to SDO documented specifications to properly develop/operate the DNS should be avoided.

Regards,
-drc




      
    

    

      
        
      
    


 




            


        



      
 


      

        
      

          
    
 

    


 

    



    






    

    


    
  
    
  

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