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

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 01 July 2008 22:26 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 C82AC3A6BD4; Tue, 1 Jul 2008 15:26:20 -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 34FD83A6B30 for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 15:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 pA3RHvKFbL6e for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 15:26:18 -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 E86C33A68B3 for <ietf@ietf.org>; Tue, 1 Jul 2008 15:26:17 -0700 (PDT)
Received: from [10.20.30.162] (adsl-66-125-125-65.dsl.pltn13.pacbell.net [66.125.125.65]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m61MQONV038550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 1 Jul 2008 15:26:25 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240808c4905ec8295c@[10.20.30.162]>
In-Reply-To: <105D288AF30DA6D8EE55976A@p3.JCK.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>
Date: Tue, 1 Jul 2008 15:26:23 -0700
To: ietf@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes?
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 5:53 PM -0400 7/1/08, John C Klensin wrote:
>Pretend I'm a fine, upstanding, citizen who is in the domain
>names business (I guess that would make me a "domaineer" :-))
>and whose business model is based on traffic concentration and
>redirection. 
>
>I think I would really like to own "local", although not as much
>as I'd like to own "example.com" or any other name to which the
>IETF or various protocol designs provide free advertising and
>traffic direction.  Every leaked name that might reference a web
>page would drive traffic to my site, as well as every action
>that led those who didn't know what was going on to open
>http://www.local./ to figure out what was going on.
>
>In a more sane world, no one rational would want to build a
>business or other activity around a TLD named "local".   But
>this is demonstrably not a sane world.

+1. I was approached by one such fine, upstanding citizen who asked 
which names "currently reserved by the IETF" would be most valuable 
for a search page.

This does not mean that ICANN won't listen to the IETF; it means that 
there will be voices more familiar to ICANN saying things different 
than we are.

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