Re: [DNSOP] draft-liman-tld-names-04

Doug Barton <dougb@dougbarton.us> Mon, 22 November 2010 03:52 UTC

Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B0E33A6A00 for <dnsop@core3.amsl.com>; Sun, 21 Nov 2010 19:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RY5L+uP92IiE for <dnsop@core3.amsl.com>; Sun, 21 Nov 2010 19:52:45 -0800 (PST)
Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by core3.amsl.com (Postfix) with ESMTP id 982573A6936 for <dnsop@ietf.org>; Sun, 21 Nov 2010 19:52:45 -0800 (PST)
Received: (qmail 16784 invoked by uid 399); 22 Nov 2010 03:53:39 -0000
Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 22 Nov 2010 03:53:39 -0000
X-Originating-IP: 127.0.0.1
X-Sender: dougb@dougbarton.us
Message-ID: <4CE9E942.20906@dougbarton.us>
Date: Sun, 21 Nov 2010 19:53:38 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101028 Thunderbird/3.1.6
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <B35360B6-0DB9-49CB-B68E-09DFFFB1ACA0@icann.org> <31FCAB67-9E3E-4E2B-957F-1A1F628AA8FB@hopcount.ca> <20101117091928.GA30093@nic.fr>
In-Reply-To: <20101117091928.GA30093@nic.fr>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: multipart/mixed; boundary="------------070505060007090503080304"
Cc: IETF DNSOP WG <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>
Subject: Re: [DNSOP] draft-liman-tld-names-04
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 22 Nov 2010 03:52:47 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 11/17/2010 01:19, Stephane Bortzmeyer wrote:
| On Thu, Nov 11, 2010 at 01:42:24PM -0500,
|   Joe Abley<jabley@hopcount.ca>;  wrote
|   a message of 15 lines which said:
|
|> http://www.ietf.org/id/draft-liman-tld-names-04.txt
|>
|> is the latest iteration of an effort started quite some time ago to
|> clarify the somewhat vague inference in RFC 1123 and create a more
|> precise specification for the syntax of TLD labels in the DNS.
|
| Nice attempt but, as I have already said
| <http://www.ietf.org/mail-archive/web/dnsop/current/msg07058.html>;,
| there is zero technical reason to limit the TLD to alphabetic
| characters and therefore, the rule:
|
| traditional-tld-label = 1*63(ALPHA)
|
| is both a new rule (it was not in RFC 1034 or 1035) and a bad one.
|
| I object to the creation of new rules disguised as clarifications.

Fully agree with Stephane on this. That bit needs to be changed to the
ABNF equivalent of the same LDH rules we use for hostnames. I've also
attached a diff with some related edits. More importantly it's worth
correcting the IANA section to make it clear that the IANA does not
create policy.

To amplify my agreement with Stephane, we have already added LDH labels
to the top level, and the sky did not fall. Therefore the only valid
clarification from a _technical_ perspective is that the aside in 1123
was never a protocol restriction. Anything else is layer 9, and
specifically not our problem.

I also agree with Stephane and Andrew that there are poorly written
programs in the world that will have problems with TLD names that start
with a non-alphabetic. We already lived through the drama that new TLDs
caused 10 years ago (been there, done that), and I agree with Stephane
that whatever drama ensues from a TLD that starts with a digit is
unlikely to cause the network to melt down tomorrow.


Doug

- -- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)

iQEcBAEBCAAGBQJM6elBAAoJEFzGhvEaGryEvggH/jSdN63R0n3bqoDbtXtViYKW
BkiPKyoIoltG4n8lbTB0CClqqsije1ZMoUmuYpXfhMxv2P+qerlg2WmnEcnrzsJL
lomuU7Lwkb6jeff1KkuQXaVYrTCOlkdMghWyPJFsm6nCDE0cx0WFshVCMHiImkGn
mkXcYoE20ae7Sj6uAyHowIxW3r0aJlpNJgAPNf5EtQfHWDdLEsyNJDp+oEGlh/4e
dtAU7d2Sdy0erXX6PLK3OpJVBrG/9G1QUdd4+zPamC+dNXHu5OfGqysA6QVswfwK
O7FtIA/QYkLW+aTgXIxxc33xK5ZpK74GQcL9nIJq/VIa1vQ+ujJJEWI64kFumsI=
=QprP
-----END PGP SIGNATURE-----