[DNSOP] .belkin as a special use name

Jim Reid <jim@rfc1035.com> Thu, 16 February 2017 18:29 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 351681293DC for <dnsop@ietfa.amsl.com>; Thu, 16 Feb 2017 10:29:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P52NRShH0LOb for <dnsop@ietfa.amsl.com>; Thu, 16 Feb 2017 10:29:41 -0800 (PST)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48FFE129406 for <dnsop@ietf.org>; Thu, 16 Feb 2017 10:22:17 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 3EB02242125A; Thu, 16 Feb 2017 18:21:57 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_945F498E-769E-432A-A869-DCCFE326C46E"; protocol="application/pgp-signature"; micalg=pgp-sha256
X-Pgp-Agent: GPGMail
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <399731CA-227F-4FC3-B009-4D1861C2BC3F@icann.org>
Date: Thu, 16 Feb 2017 18:21:56 +0000
Message-Id: <91AE52F4-A179-4469-A4E3-7E90265702AD@rfc1035.com>
References: <F56640AF-27DF-425F-B844-8453DE02987E@icann.org> <A4F1EFFD-FC65-4C69-92E8-A6587AD767EF@vigilsec.com> <9F197C8D-77F6-430F-8D71-B338BFB998EB@gmail.com> <399731CA-227F-4FC3-B009-4D1861C2BC3F@icann.org>
To: Ed Lewis <edward.lewis@icann.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8RhTLZcOTPv5qJChIxxOBUBXea8>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: [DNSOP] .belkin as a special use name
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:29:42 -0000

> On 16 Feb 2017, at 17:47, Edward Lewis <edward.lewis@icann.org> wrote:
> 
> What about .belkin, often cited as a string seen but not allocated?

It was so prominent in one year’s root server DITL data (in the top 20 TLDs that were queried?) that it was mentioned in the 2013 Interisle Name Collision report I helped to produce. IIRC it didn’t show up much in the other year of DITL data that got crunched for that report. Or the previous years of DITL data that were analysed after that report had been published.

It’ll just be a simple matter of progamming and a few CPU-months to run through the datasets at DNS-OARC and get the top N TLD strings for in the root server DITL data since 2006. I’m not sure this would be much help to the WG’s consideration of what to do about special use labels though. That data might be useful for anyone who has the urge to compile yet another list of these heavily-used-but-not-properly-registered* labels/TLDs.

I’d be willing to gather that information if someone can make a convincing case for doing that.

*for some definition of these 6 words.