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

"Frank Ellermann" <nobody@xyzzy.claranet.de> Sat, 28 June 2008 07:14 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 90DF03A6A8A; Sat, 28 Jun 2008 00:14:06 -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 171023A69B8 for <ietf@core3.amsl.com>; Sat, 28 Jun 2008 00:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, 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 zadag4YCV1HK for <ietf@core3.amsl.com>; Sat, 28 Jun 2008 00:14:04 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 29CD93A683D for <ietf@ietf.org>; Sat, 28 Jun 2008 00:14:03 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KCUdK-000403-1n for ietf@ietf.org; Sat, 28 Jun 2008 07:14:06 +0000
Received: from hmbg-d9b88e32.pool.mediaways.net ([217.184.142.50]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 28 Jun 2008 07:14:06 +0000
Received: from nobody by hmbg-d9b88e32.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 28 Jun 2008 07:14:06 +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: Sat, 28 Jun 2008 09:15:34 +0200
Organization: <http://purl.net/xyzzy>
Lines: 47
Message-ID: <g44obh$voh$1@ger.gmane.org>
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e32.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

Marshall Eubanks wrote:

> .internal

What's that supposed to be good for ?  At the moment the
2606bis draft proposes to create a IANA registry of new
reserved TLDs, populated with TLDs surviving IETF review.

> maybe translations of .test

Covered, a copy of the 11 IDN test TLDs created by ICANN
some months ago, complete with A-labels and U-labels, see
http://tools.ietf.org/html/draft-ellermann-idnabis-test-tlds-06#section-4

> .example

Not yet covered, as there's no evidence that ICANN wants
to reserve their initially 11 "example" translations as
TLDs.  With IETF consensus behind it adding them now, or
later in a separate memo, is no issue.

> .invalid .localhost

Bad idea, IMO, these names are not reserved for tests or
examples, but technical reasons, and no subject for I18N.
  
> other languages / character sets.

ITYM languages / scripts, not character sets.  That is a
wide field, as there are dozens of scripts and hundreds
of languages.  If all you want are the *existing* example
translations corresponding to the 11 IDN test TLDs it's
possible.  Otherwise we better wait until the IDN ccTLDs
are on their way in about a year.

>From my POV I'd like to have one I18N example, and don't
care which of the 11 existing strings are reserved, just
take them all is an idea.  But let's not make up things.

> whether there is a better mail list for this discussion

It's as "general" as it can get, and I guess the IDNAbis
folks won't be thrilled if they are hit by side effects
of their effort... ;-)

 Frank

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