Re: Update of RFC 2606 based on the recent ICANN changes ?

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 02 July 2008 17:45 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 4E27C3A6CAF; Wed, 2 Jul 2008 10:45:33 -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 8EF233A6CA7 for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 10:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_101=0.6]
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 fdLGLG9HUXaw for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 10:45:30 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 028773A6C68 for <ietf@ietf.org>; Wed, 2 Jul 2008 10:45:29 -0700 (PDT)
Received: from [10.20.30.162] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m62HjRu7035852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Jul 2008 10:45:29 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624081ec4916d89dfac@[10.20.30.162]>
In-Reply-To: <Pine.GSO.4.63.0807020927290.12027@pita.cisco.com>
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com> <74E3E26A-FCFB-45C1-989A-DD7EA5752974@virtualized.org> <6.2.5.6.2.20080627121824.02c55340@resistor.net> <A9ACF7FB-BC78-44D9-AA61-4FCACE821677@virtualized.org> <9486A1E5-864F-4B23-9EBA-697C1A7A7520@ca.afilias.info> <200807012051.m61KpLeq021685@cichlid.raleigh.ibm.com> <105D288AF30DA6D8EE55976A@p3.JCK.COM> <200807021417.m62EHckw017869@cichlid.raleigh.ibm.com> <p0624081cc4915ab876b2@[10.20.30.162]> <Pine.GSO.4.63.0807020927290.12027@pita.cisco.com>
Date: Wed, 2 Jul 2008 10:45:26 -0700
To: Ole Jacobsen <ole@cisco.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Cc: The IETF <ietf@ietf.org>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

At 9:30 AM -0700 7/2/08, Ole Jacobsen wrote:
>But it is still the case that an application for say .local would need
>to go through some review process (regardless of price) which would
>include input from the IETF ICANN rep. I see little reason why or how
>a TLD that would be damaging, confusing, or otherwise "bad" for the
>IETF would/could just "slip through" this process.

Fully agree.

>What am I missing here?

That there could/would be others arguing that the IETF is 
over-stating the damage from a particular proposal. Anyone who is 
willing to pay the exorbitant^W application fee obviously is willing 
to defend their choice of name. On something like .local (and, I 
predict, ".1"), the counter-argument to anything the IETF says is 
"that's possibly true, but not likely". We can't prove future harm, 
and they can belittle us for being "too cautious". They have money 
behind them, and we have our reputation. ICANN gets to weigh those 
two against each other. This is somewhat parallel to the political 
process in most capitalist democracies.

--Paul Hoffman, Director
--VPN Consortium
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf