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

hellekin <> Tue, 27 September 2016 08:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 540DD12B036 for <>; Tue, 27 Sep 2016 01:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.237
X-Spam-Status: No, score=-9.237 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kGwwdwyDryDg for <>; Tue, 27 Sep 2016 01:37:49 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9EAC612B09F for <>; Tue, 27 Sep 2016 01:37:49 -0700 (PDT)
Received: from Debian-exim by with spam-scanned (Exim 4.71) (envelope-from <>) id 1bontD-00018m-KL for; Tue, 27 Sep 2016 04:37:27 -0400
Received: from ([2001:4830:134:3::e]:59610) by with esmtp (Exim 4.71) (envelope-from <>) id 1bonsz-00010i-EE; Tue, 27 Sep 2016 04:37:09 -0400
Received: from [] (port=40154 helo=[]) by with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <>) id 1bonsx-00061G-Gm; Tue, 27 Sep 2016 04:37:08 -0400
To: Warren Kumari <>
References: <> <> <>
From: hellekin <>
X-Enigmail-Draft-Status: N1110
Message-ID: <>
Date: Tue, 27 Sep 2016 08:33:04 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-detected-operating-system: by GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
Archived-At: <>
Cc: dnsop <>, "" <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-05.txt
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 27 Sep 2016 08:37:51 -0000

On 09/27/2016 02:37 AM, Warren Kumari wrote:
> My opinion really doesn't matter, but I happen to think that, at this
> point, we should evaluate the requested P2P names according to RFC
> 6761  -- you followed the process in effect *at the time*, and jumped
> through many hoops. The process is far from perfect (see
> draft-tldr-sutld-ps) but that *was* the process at that point, and so
> your drafts should (IMO) be evaluated against that. If the IETF had
> been able to quickly and clearly come to consensus that the process
> was broken, and what to do to fix it, I might feel differently, but
> changing the rules retroactively feels unfair.

Thank you for your clarification.  Indeed the discussion was long ago
and details slipped from memory.

> Interestingly enough, just above that mail, Stephane also objected to
> "pseudo-TLD", but we asked the WG for a better term and (IIRC), didn't
> get any better suggestions:
> "Can you suggest a better term (noting that this term is used in both
> RFC6761 and draft-grothoff-iesg-special-use-p2p-names-04)?
> They are things that look like TLDs when leaking into the DNS context,
> but are not actually TLDs.

I remember introducing the term 'pseudo-TLD' in the P2P Names draft and
doing a similar research as the one I cut from your message for brevity.
 At the time I thought the Canada Dry effect would work: it looks like
DNS, it tastes like DNS, but it's not DNS, hence 'pseudo'.  But indeed
that can as well bring confusion.

I have no alternate suggestion at this point, but I have one to avoid
talking about "squatting" names: "using names without ICANN sanction".
It may be longer, but it's more accurate, and doesn't conflate a
legitimate but often criminalized practice with a fact of usage that can
stem from many reasons, one of them being the need of humans to name
things. Using names without ICANN sanction also speaks to people who
don't know why it's a problem, and places it in the correct context
where the problem can then be solved.  Except, of course, if that
particular name represents a technical issue ;o)