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

Andrew Sullivan <ajs@shinkuro.com> Wed, 24 November 2010 14:22 UTC

Return-Path: <ajs@shinkuro.com>
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 AE8FA28C25F for <dnsop@core3.amsl.com>; Wed, 24 Nov 2010 06:22:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Qo-gnSayOv9x for <dnsop@core3.amsl.com>; Wed, 24 Nov 2010 06:22:08 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id B228228C266 for <dnsop@ietf.org>; Wed, 24 Nov 2010 06:22:06 -0800 (PST)
Received: from crankycanuck.ca (external.shinkuro.com [66.92.164.104]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 2C7511ECB408 for <dnsop@ietf.org>; Wed, 24 Nov 2010 14:23:05 +0000 (UTC)
Date: Wed, 24 Nov 2010 09:23:03 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsop@ietf.org
Message-ID: <20101124142303.GB19441@shinkuro.com>
References: <B35360B6-0DB9-49CB-B68E-09DFFFB1ACA0@icann.org> <31FCAB67-9E3E-4E2B-957F-1A1F628AA8FB@hopcount.ca> <20101117091928.GA30093@nic.fr> <4CE9E942.20906@dougbarton.us> <0E561274-43FE-4657-951E-74C8FF0FD307@hopcount.ca> <4CEC43DC.1060709@dougbarton.us> <E7796748-6880-4928-B96D-0024E27E98D5@hopcount.ca> <4CEC69C5.3040209@dougbarton.us> <7B9EF625-1E25-42BE-9546-61C5B7EFC6DA@hopcount.ca> <8CEF048B9EC83748B1517DC64EA130FB43E0037FD1@off-win2003-01.ausregistrygroup.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8CEF048B9EC83748B1517DC64EA130FB43E0037FD1@off-win2003-01.ausregistrygroup.local>
User-Agent: Mutt/1.5.18 (2008-05-17)
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: Wed, 24 Nov 2010 14:22:15 -0000

On Wed, Nov 24, 2010 at 01:15:23PM +1100, James Mitchell wrote:
> If deployed software does not work with a TLD, it is the TLD owner who loses. 

I'm sorry, but that claim is arrant nonsense.  We _all_ lose.  The
IETF is supposed to be about interoperability, and if stuff breaks
because we have decided, "We don't care lalalalalala I can't hear
you there isn't a problem," then we ought to be ashamed of ourselves.

I think Joe's pragmatic approach is the right one: document right now
that whatever the restrictions might historically have been, we are
quite explicitly going to permit at the very least one class of
labels.

If people feel strongly that in fact the TLD label restriction never
was there and should not be, then once this document is published you
all can go out and write the draft, "TLD label character restrictions
considered harmful", and pursue the publication of that as an RFC.  In
the meantime, we have at least a technical document that makes clear
that certain things are permitted.

A
-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.