IETF Logo Mail Archive

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

David Conrad <drc@virtualized.org> Mon, 30 June 2008 13:41 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 C7D733A6857; Mon, 30 Jun 2008 06:41:00 -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 1D5783A6857 for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 06:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level:
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, 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 T9lWEZRAdLTv for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 06:40:58 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id 630673A67F1 for <ietf@ietf.org>; Mon, 30 Jun 2008 06:40:58 -0700 (PDT)
Received: from [10.0.1.198] (c-71-198-3-247.hsd1.ca.comcast.net [71.198.3.247]) by virtualized.org (Postfix) with ESMTP id D3205265F7B; Mon, 30 Jun 2008 06:41:09 -0700 (PDT)
Message-Id: <0B02F7E8-EBFE-401A-9D5E-CF0FBDDFD24D@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Bill Manning <bmanning@ISI.EDU>
In-Reply-To: <20080630024615.GA7021@boreas.isi.edu>
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Date: Mon, 30 Jun 2008 06:41:08 -0700
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>
X-Mailer: Apple Mail (2.924)
Cc: 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> are numeric string representations now, after 30 years

> 	going to be outlawed? if so, on what basis?

?

I'm suggesting that there are technical reasons why strings comprised  
of all numbers and those that start with 0x and contain hex digits  
should not be TLD labels.

In theory, the limitation against all-numeric/hex TLD labels should  
not need to be made.  However, in theory, a label can support any  
octet value between 0 and 255 yet the IETF has gone to great lengths  
to greatly limit the values within "hostname" labels...

Regards,
-drc

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

v2.23.0 | Report a Bug | By Email