Re: [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-13.txt

Andrew McConachie <> Wed, 07 July 2021 14:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3DA593A18E2 for <>; Wed, 7 Jul 2021 07:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bajJSWIELdlR for <>; Wed, 7 Jul 2021 07:02:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AFAEA3A18DD for <>; Wed, 7 Jul 2021 07:02:46 -0700 (PDT)
Received: by with SMTP id 9so2022475qkf.3 for <>; Wed, 07 Jul 2021 07:02:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=MM7AHauJ471bOuVQ2SPoWZM2vnoovpF83T+Pq5lRVN0=; b=V4b9Z3HdzNXEpZ/HTex+6gkbBRkHfgq0PKhvyFKN34B8a4UuFPy7Wp98TiqPV4eOeb HAyvd2cjPfHvInt6+EBREZBfa9DmunvUrLzLA9z7Xov96p96TywYxdsXgG1cNKQ70WP7 Y96YWirJNdrfJ+lbmSBMRZtqfb2JlsAPkiNIi5StjBQiAVU9hmmE6DNdcrg2dI+zj4iu QLnKPjh8nHC2I8ZXqfdIkIyAlZYMBFEBtb5/4DyQ67LL/tjLY/1196paezVZ+fC6c0WH 03H8puiEBY+baZmHLB67zri+6tjESaKA4D6CBU6JGPVeFll1hlBPcsEFgUuJrR/Gq5/h QfKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=MM7AHauJ471bOuVQ2SPoWZM2vnoovpF83T+Pq5lRVN0=; b=MmL+oKdae6biQKscEJ0tMHStmjUeDZtFCTUKbHlx6tDHBOhzB00QMcWLUe2xKk1A8M illmrEIwwLHfnIg0hranRaQh63+dDdsTvI62md0xo0n4LQR19zz6qk1sR3e/fnpbkioe 4QqrhYMlqqdV+Vnax+gjlJImGpC8Kumu5I21WR9/vh8UkTbR9qFMym91+MJyqjySbHmS 3oXx1PRVP4XoLPtn56I6GpKxNSTiEp0uEpDDgG8GW0r/NwneDXtkU8qhet0saarpvBKt g76a3tiabQiU29T5l5oXo9MnGv5Z/mCod5+vCGSkCjeri+YRIOo5GH9woAjG6SmqKLMe tNuQ==
X-Gm-Message-State: AOAM530oly5gRCvsjoqLu6JoeN0Ng9iyB+I+tHmEtX+gRH4SqtxPdYox v120qOVSJWLCSAhOg1DU/COtWg==
X-Google-Smtp-Source: ABdhPJz70eRFzZWVS0ikhyc4QE24msSoDrjItA1xFB9Td+BqFlBtOgBSgLvqb0xDnt7T20AlYl/MxA==
X-Received: by 2002:a37:a18f:: with SMTP id k137mr14937165qke.443.1625666565269; Wed, 07 Jul 2021 07:02:45 -0700 (PDT)
Received: from [] ([2a02:a212:9285:29f0:b52b:8586:5860:e0da]) by with ESMTPSA id a4sm6407095qka.49.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Jul 2021 07:02:44 -0700 (PDT)
From: "Andrew McConachie" <>
To: "Warren Kumari" <>
Date: Wed, 07 Jul 2021 16:02:41 +0200
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <>
In-Reply-To: <>
References: <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_C0FC7BF1-53E6-4451-8F18-ED1A57B807CC_="
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-13.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 07 Jul 2021 14:02:51 -0000

Hi Warren,

I find the terminology in this document somewhat self-contradicting and 

*  pseudo-TLD: A label that appears in a fully-qualified domain name
    in the position of a TLD, but which is not registered in the
    global DNS.  This term is not intended to be pejorative.

*  TLD: The last visible label in either a fully-qualified domain
    name or a name that is qualified relative to the root.

These definitions tell me that a pseudo top-level domain appears in a 
fully-qualified domain name in the top-level position. So is a 
pseudo-TLD something that appears in a *real* domain name? Or is a 
domain name that has a pseudo-TLD a pseudo-domain name? Is foo.alt a 
pseudo-domain name, or a *real* domain name with a pseudo-TLD? It’s 
not clear.

The draft makes a distinction between 'DNS names' and 'domain names’, 
and I understand 'DNS names' to be a subset of 'domain names'. Yet when 
I read the definition of 'domain name' in RFC 7719 I don't see this 
distinction being made. Is the DNS namespace supposed to be a subset of 
the domain namespace? I can't figure it out from the terminology 
sections of this draft and RFC 7719.

"The ALT label MAY be used in any domain name as a pseudo-TLD to signify 
that this is an alternative (non-DNS) namespace, and should not be 
looked up in a DNS context."

*  DNS context: The namespace anchored at the globally-unique DNS
    root.  This is the namespace or context that "normal" DNS uses.

According to the definitions given ‘DNS namespace' and 'DNS context' 
are synonyms, and the antonym of 'DNS namespace' is 'alternative 

So how about we change the sentence to:
"The ALT label MAY be used in any domain name as a pseudo-TLD to signify 
that this is an alternative (non-DNS) namespace, and should not be 
looked up in the DNS namespace."

And change the definition to:

*  DNS namespace: The namespace anchored at the globally-unique DNS
    root.  This is the namespace that the DNS protocol uses.

It's easier to understand if we eliminate the word context entirely and 
just talk about namespaces.


On 21 Jun 2021, at 19:48, wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Domain Name System Operations WG of 
> the IETF.
>         Title           : The ALT Special Use Top Level Domain
>         Authors         : Warren Kumari
>                           Andrew Sullivan
> 	Filename        : draft-ietf-dnsop-alt-tld-13.txt
> 	Pages           : 11
> 	Date            : 2021-06-21
> Abstract:
>    This document reserves a string (ALT) to be used as a TLD label in
>    non-DNS contexts.  It also provides advice and guidance to 
> developers
>    developing alternative namespaces.
>    [Ed note: Text inside square brackets ([]) is additional background
>    information, answers to frequently asked questions, general 
> musings,
>    etc.  They will be removed before publication.  This document is
>    being collaborated on in Github at: 
>    wkumari-dnsop-alt-tld.  The most recent version of the document, 
> open
>    issues, etc should all be available here.  The authors (gratefully)
>    accept pull requests. ]
> The IETF datatracker status page for this draft is:
> There is also an htmlized version available at:
> A diff from the previous version is available at:
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> DNSOP mailing list