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

John Levine <johnl@iecc.com> Sun, 29 June 2008 20:23 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 499773A69D0; Sun, 29 Jun 2008 13:23:41 -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 01BAD3A6A34 for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 13:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.084
X-Spam-Level:
X-Spam-Status: No, score=-10.084 tagged_above=-999 required=5 tests=[AWL=0.815, 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 iKUfUd2rMph6 for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 13:23:39 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id AD8033A6856 for <ietf@ietf.org>; Sun, 29 Jun 2008 13:23:38 -0700 (PDT)
Received: (qmail 92460 invoked from network); 29 Jun 2008 20:23:48 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 29 Jun 2008 20:23:48 -0000
Date: 29 Jun 2008 20:23:48 -0000
Message-ID: <20080629202348.91058.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: <20080629195117.GA28916@sources.org>
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

>> It seems like additional TLD domains, beyond just the 4 in RFC 2606,
>> should be either reserved or blocked.

In view of Recommendation 4 in ICANN's new GTLD process document, why
do you think this is necessary?

You have read the report, haven't you?

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