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

"Frank Ellermann" <nobody@xyzzy.claranet.de> Mon, 30 June 2008 14:19 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 7642D3A6932; Mon, 30 Jun 2008 07:19:53 -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 473113A6932 for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 07:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.835
X-Spam-Level:
X-Spam-Status: No, score=-4.835 tagged_above=-999 required=5 tests=[AWL=0.764, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
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 SD8nTx+0Yeig for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 07:19:51 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 6BC2C3A68B3 for <ietf@ietf.org>; Mon, 30 Jun 2008 07:19:51 -0700 (PDT)
Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KDKEc-0008Jv-G7 for ietf@ietf.org; Mon, 30 Jun 2008 14:20:02 +0000
Received: from hmbg-d9b88e11.pool.mediaways.net ([217.184.142.17]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Mon, 30 Jun 2008 14:20:02 +0000
Received: from nobody by hmbg-d9b88e11.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Mon, 30 Jun 2008 14:20:02 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Date: Mon, 30 Jun 2008 15:37:06 +0200
Organization: <http://purl.net/xyzzy>
Lines: 25
Message-ID: <g4app1$a0$1@ger.gmane.org>
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com><74E3E26A-FCFB-45C1-989A-DD7EA5752974@virtualized.org><6.2.5.6.2.20080627121824.02c55340@resistor.net><BBB8E0B4-7E45-4BE9-B9DF-DEBE294585D6@multicasttech.com><6.2.5.6.2.20080627140118.02a43fd8@resistor.net><6F1CFDA0-A6E2-4257-8C72-0FCD1E117290@virtualized.org><6.2.5.6.2.20080628201322.02e43268@resistor.net><FBBF3BB9-D231-494A-AFBE-7F816DD1180C@virtualized.org><20080630024615.GA7021@boreas.isi.edu> <649DC89B6513C74E89023E29@[192.168.1.110]>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e11.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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

John C Klensin wrote:

> rules like this are ultimately useless unless ICANN agrees to 
> them, presumably via the gNSO, one at a time, and via a PDP 
> process.

As long as PDP translates into "individual Last Call comments"
for a future draft-ietf-idnabis-952bis that's fine.  

Nothing rush like <http://idn.icann.org/Special:Recentchanges>

> it seems to argue that we should be conservation about what
> names we reserve and thereby promote.

Sure, there also rules about not creating confusingly similar
TLDs, proposed TLDs exmaple or examlpe won't pass that check.

> Perhaps we should ask ICANN to reserve all single-letter TLDs
> (in any script) for IETF use.

s/ICANN/IANA/, and that is an odd idea.  We don't need 2**20
example TLDs.  But a few would be nice, for examples in EAI
and IDNAbis drafts, or similar.

 Frank

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