Re: Services and top-level DNS names (was: Re: Update of RFC 2606

John Levine <johnl@iecc.com> Fri, 04 July 2008 21:13 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC51B3A6B60; Fri, 4 Jul 2008 14:13:46 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 478BB3A6B60 for <ietf@core3.amsl.com>; Fri, 4 Jul 2008 14:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.695
X-Spam-Level:
X-Spam-Status: No, score=-10.695 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_MED=-4]
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 xu1fa4H+udFW for <ietf@core3.amsl.com>; Fri, 4 Jul 2008 14:13:45 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id EA51D3A6898 for <ietf@ietf.org>; Fri, 4 Jul 2008 14:13:44 -0700 (PDT)
Received: (qmail 69446 invoked from network); 4 Jul 2008 21:13:51 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 4 Jul 2008 21:13:51 -0000
Date: 4 Jul 2008 21:13:51 -0000
Message-ID: <20080704211351.34237.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Services and top-level DNS names (was: Re: Update of RFC 2606
In-Reply-To: <BLU137-W4119825EB30C448D9C87B7939B0@phx.gbl>
Organization:
X-Headerized: yes
Mime-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>Is generic "buyer beware" disclaimer really sufficient here? 

The cost to get a domain from ICANN under the new rules is estimated
to be about $100,000.  Don't you think we can assume that people who
are laying out that kind of money are big boys and girls who will do
adequate due diligence?

>The problem isn't just "inability to use" -- it's that other parties
>exist who may claim the usage right, and provide citations to RFCs to
>back up their claim.

There are several ICANN documents describing the new process that
include a set of recommendations to guide the process.  You must have
read them, since you are concerned about this proposal.  Do you think
that recommendations 3, 4, and 20 are adequate to address this
problem?  If not, why not?

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://www.johnlevine.com, ex-Mayor
"More Wiener schnitzel, please", said Tom, revealingly.
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf