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

"Frank Ellermann" <nobody@xyzzy.claranet.de> Mon, 30 June 2008 03:29 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 CD09F3A696E; Sun, 29 Jun 2008 20:29:09 -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 772853A695A for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 20:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.856
X-Spam-Level:
X-Spam-Status: No, score=-4.856 tagged_above=-999 required=5 tests=[AWL=0.743, 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 hoFomN1Thv7k for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 20:29:07 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 911C63A696E for <ietf@ietf.org>; Sun, 29 Jun 2008 20:29:07 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KDA4r-0000VV-27 for ietf@ietf.org; Mon, 30 Jun 2008 03:29:17 +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 03:29:17 +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 03:29:17 +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 05:31:47 +0200
Organization: <http://purl.net/xyzzy>
Lines: 24
Message-ID: <g49ju3$jn7$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>
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

David Conrad wrote:

> Would there be the downside to this?

Hi, that's already planned, I'm lazy, here's a copy:

| that will be done in an draft-ietf-idnabis-952bis to nail the
| two RFC 1123 <toplabel> errata, see the "A-label" thread(s)
| on the IDNAbis list: 
|
| <http://thread.gmane.org/gmane.ietf.idnabis/2176/focus=2194>
|
| Executive summary:  Obsoletes RFC 952, updates RFC 1123,
| defines  toplabel = letter 0*61( ldh ) letdig
[...]
| it is not the job of RFC 2606 to obsolete RFC 952 and update
| RFC 1123.  John said it is also not the job of 
| draft-ietf-idnabis-rationale, therefore we settled on "needs
| its own RFC" (John is for BCP).
[...]
| Minus references, legalese, and weasel words it is *one line
| ABNF* (as shown above), but admittedly loaded.

 Frank

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