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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 30 June 2008 19:03 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 79DF73A6ACB; Mon, 30 Jun 2008 12:03:12 -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 0AD153A6ACB for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 12:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 D7FChrfQZqT8 for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 12:03:11 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by core3.amsl.com (Postfix) with ESMTP id C447E3A683C for <ietf@ietf.org>; Mon, 30 Jun 2008 12:03:01 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 6861594A0E; Mon, 30 Jun 2008 21:03:08 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id C09371906DF; Mon, 30 Jun 2008 21:01:53 +0200 (CEST)
Date: Mon, 30 Jun 2008 21:01:53 +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: <20080630190153.GB31520@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> <20080630064127.GA5829@sources.org> <3B2E8E96-ACAA-4A13-BBE2-33DC80DDADC6@virtualized.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <3B2E8E96-ACAA-4A13-BBE2-33DC80DDADC6@virtualized.org>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux lenny/sid
User-Agent: Mutt/1.5.18 (2008-05-17)
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Mon, Jun 30, 2008 at 05:49:18AM -0700,
 David Conrad <drc@virtualized.org> wrote 
 a message of 11 lines which said:

> Speaking technically, how would you distinguish the top-level domain
> "127.0.0.1" from the IP address 127.0.0.1?

A word while passing here: is there a document (RFC, Posix standard,
whatever) which says which is the right result in such a case?

There are protocol-specific rules. RFC 3986, section 3.2.2, clearly
says that the IP address wins and so your example would be regarded
as the localhost IP address, wether the TLD ".1" is delegated or no.

But I do not find generic rules.

RFC 3493 which specifies getaddrinfo is not very clear. Section 6.1
apparently does not address your issue.

So, I would say there is a normalization failure here: since 127.0.0.1
can be a domain name and an IP address, we really should have
precedence rules for such case (instead of asking ICANN to solve them
by forbidding all-numeric TLD).

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