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

Steve Crocker <steve@shinkuro.com> Wed, 02 July 2008 22:38 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 078343A6A3C; Wed, 2 Jul 2008 15:38:00 -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 9B41A3A6910 for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 10:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.47
X-Spam-Level:
X-Spam-Status: No, score=-1.47 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129]
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 bJ9Hs799CUXP for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 10:10:21 -0700 (PDT)
Received: from execdsl.com (mail.shinkuro.com [216.194.124.237]) by core3.amsl.com (Postfix) with ESMTP id 3F0853A6859 for <ietf@ietf.org>; Wed, 2 Jul 2008 10:10:21 -0700 (PDT)
Received: from [66.92.164.104] (HELO [192.168.2.3]) by execdsl.com (CommuniGate Pro SMTP 4.2.7) with ESMTP id 16796398; Wed, 02 Jul 2008 11:05:34 -0600
In-Reply-To: <20080702165338.78318.qmail@simone.iecc.com>
References: <20080702165338.78318.qmail@simone.iecc.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <C8EA9663-6484-472E-A608-61C00F6BC15F@shinkuro.com>
From: Steve Crocker <steve@shinkuro.com>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Date: Wed, 2 Jul 2008 13:10:18 -0400
To: John Levine <johnl@iecc.com>
X-Mailer: Apple Mail (2.753.1)
X-Mailman-Approved-At: Wed, 02 Jul 2008 15:37:57 -0700
Cc: Steve Crocker <steve@shinkuro.com>, ole@cisco.com, 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"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

While I appreciate the kind words and deference to SSAC, and while we  
would undoubtedly concur with recommendations to reserve names  
like .local, ICANN actually listens to the IETF more directly.   
Moreover, there is a specific slot on the Board of ICANN for a  
Liaison from the IETF.  Thomas Narten does a great job in that role,  
as John Klensin did before him.

Steve


On Jul 2, 2008, at 12:53 PM, John Levine wrote:

> 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

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf