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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 30 June 2008 06:43 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 7FDBF3A695A; Sun, 29 Jun 2008 23:43:03 -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 5720C3A695A for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 23:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599]
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 vpLqeYmxBelV for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 23:43:01 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by core3.amsl.com (Postfix) with ESMTP id 592443A6856 for <ietf@ietf.org>; Sun, 29 Jun 2008 23:43:00 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 183C4949EC; Mon, 30 Jun 2008 08:43:07 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id 6F02D1906E2; Mon, 30 Jun 2008 08:41:27 +0200 (CEST)
Date: Mon, 30 Jun 2008 08:41:27 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: David Conrad <drc@virtualized.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Message-ID: <20080630064127.GA5829@sources.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
Content-Disposition: inline
In-Reply-To: <FBBF3BB9-D231-494A-AFBE-7F816DD1180C@virtualized.org>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux lenny/sid
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: SM <sm@resistor.net>, IETF Discussion <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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Sun, Jun 29, 2008 at 05:54:41PM -0700,
 David Conrad <drc@virtualized.org> wrote 
 a message of 41 lines which said:

> I'm suggesting it would be helpful if there were an RFC directing
> IANA to establish a registry that contains both labels and rules
> (e.g, no all-numeric strings, no strings that start with 0x and
> contain hexadecimal values, the string 'xn--', the 2606 strings,
> etc.) that specify what cannot be placed into the root zone.
>
> Would there be the downside to this?

There is one (regarding rules, not regarding labels): a TLD is a
domain like any other. It has nothing special, technically
speaking. Since IETF is supposed to work in the field of technology,
not politics, I would object to any registry that lays down special
rules for TLDs, besides the normal RFC 1034/1123/2181 rules (which
apply to every domain).

Reserving TLDs (like ".example") is a different thing: we don't create
new rules, we just use our privilege to get a TLD without paying
100,000 US $ to ICANN. 
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf