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

David Conrad <drc@virtualized.org> Wed, 24 November 2010 19:25 UTC

Return-Path: <drc@virtualized.org>
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 24DF33A6A85 for <dnsop@core3.amsl.com>; Wed, 24 Nov 2010 11:25:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 dE5aFSK-6BNm for <dnsop@core3.amsl.com>; Wed, 24 Nov 2010 11:25:06 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id 2A4723A6965 for <dnsop@ietf.org>; Wed, 24 Nov 2010 11:24:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id 926A7F5B60E; Wed, 24 Nov 2010 11:25:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehdIBHQ4bJXd; Wed, 24 Nov 2010 11:25:55 -0800 (PST)
Received: from [10.0.1.8] (c-24-130-212-17.hsd1.ca.comcast.net [24.130.212.17]) by virtualized.org (Postfix) with ESMTP id 0994BF5B5E8; Wed, 24 Nov 2010 11:25:54 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20101124142303.GB19441@shinkuro.com>
Date: Wed, 24 Nov 2010 11:25:53 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <CAACE4CC-591B-4237-91A9-717E3BC9C712@virtualized.org>
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> <20101124142303.GB19441@shinkuro.com>
To: Andrew Sullivan <ajs@shinkuro.com>
X-Mailer: Apple Mail (2.1082)
Cc: dnsop@ietf.org
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 19:25:07 -0000

Andrew,

On Nov 24, 2010, at 6:23 AM, Andrew Sullivan wrote:
> 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 don't think anyone is doing this, rather it is the normal situation of trying to strike a balance between 100% backwards compatibility (which limits future innovation) and ignoring the installed base (which breaks things).

> 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.

I would agree that it is important to document existing reality and hence believe the draft should move forward.

> 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.

+1

Regards,
-drc