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

John Levine <johnl@iecc.com> Wed, 02 July 2008 16:53 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 B3B213A6C91; Wed, 2 Jul 2008 09:53:32 -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 E46C23A67EC for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 09:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.492
X-Spam-Level:
X-Spam-Status: No, score=-10.492 tagged_above=-999 required=5 tests=[AWL=0.407, 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 alJFCW3lAGDB for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 09:53:30 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 2F29B3A6C91 for <ietf@ietf.org>; Wed, 2 Jul 2008 09:53:30 -0700 (PDT)
Received: (qmail 30893 invoked from network); 2 Jul 2008 16:53:38 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 2 Jul 2008 16:53:38 -0000
Date: 2 Jul 2008 16:53:38 -0000
Message-ID: <20080702165338.78318.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-Reply-To: <Pine.GSO.4.63.0807020927290.12027@pita.cisco.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Cc: ole@cisco.com
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

In article <Pine.GSO.4.63.0807020927290.12027@pita.cisco.com> you write:
>Paul,
>
>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.

More likely from the SSAC, which would be even better.

In any event, as I said before, although there's a lot not to like
about ICANN, the chances of them doing anything technically
destructive remains low.

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