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

Andrew Sullivan <ajs@shinkuro.com> Fri, 26 November 2010 22:29 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 D10EB28C12C for <dnsop@core3.amsl.com>; Fri, 26 Nov 2010 14:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.631
X-Spam-Level:
X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[AWL=-0.032, 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 21y-DP3rDI83 for <dnsop@core3.amsl.com>; Fri, 26 Nov 2010 14:29:25 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id B0E1A28C128 for <dnsop@ietf.org>; Fri, 26 Nov 2010 14:27:53 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4C4351ECB408 for <dnsop@ietf.org>; Fri, 26 Nov 2010 22:28:41 +0000 (UTC)
Date: Fri, 26 Nov 2010 17:28:39 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsop@ietf.org
Message-ID: <20101126222839.GZ21047@shinkuro.com>
References: <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> <4CED5DF3.2030106@dougbarton.us> <20101125145643.GC21047@shinkuro.com> <4CF0318A.1090205@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4CF0318A.1090205@dougbarton.us>
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: Fri, 26 Nov 2010 22:29:33 -0000

On Fri, Nov 26, 2010 at 02:15:38PM -0800, Doug Barton wrote:

> Ah, now I get it. You're arguing that the protocol restriction did exist  
> in the past, and now we're relaxing it, but only slightly.

No, I'm arguing, just as the document does, that some people may have
understood this to be a protocol restriction because the document was
not crystal clear about what was policy and what was not.  My personal
view is that it _was_ policy, that it was called out as such, and that
if things break then that's a pity.  But as an IETF geek, I'm
concerned about interoperability.  And so since the protocol/policy
line was not always drawn as brightly in the past as it maybe could
have been, let's explicitly say that certain things are just hunky
dory.

In my opinion, the alternative to this is to say nothing.  If you are
right and there never was any protocol issue here, then ICANN has
taken over that problem and we don't have to solve it. 

A

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