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

Mark Andrews <Mark_Andrews@isc.org> Tue, 01 July 2008 00: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 ED54C3A6AFB; Mon, 30 Jun 2008 17:14: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 E6F543A681F for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 17:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level:
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104, 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 N3wDX-9SzvyP for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 17:13:59 -0700 (PDT)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by core3.amsl.com (Postfix) with ESMTP id A050F3A695A for <ietf@ietf.org>; Mon, 30 Jun 2008 17:13:58 -0700 (PDT)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.2) with ESMTP id m610E2eB004129; Tue, 1 Jul 2008 10:14:04 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200807010014.m610E2eB004129@drugs.dv.isc.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-reply-to: Your message of "Mon, 30 Jun 2008 21:01:53 +0200." <20080630190153.GB31520@sources.org>
Date: Tue, 01 Jul 2008 10:14:02 +1000
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>
MIME-Version: 1.0
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).

	I think you will find that getaddrinfo() implementations
	catch IP address rather than look them up.  The question is
	more what they catch rather than when they catch.

	For IPv6 it is pretty straight forward.  There is a recommend
	a followed syntax.

	IPv4 on the other hand has lots of history involved.  OS's
	with lots of history tend to support very liberal syntaxes.
	OS's with not so much history tend to be limited to dotted
	decimal quad.

	ICANN is in a position to look at what the various OS's
	accept and rejects TLD's application that will potentially
	conflict with the existing practice of any current OS.  This
	will prevent users that switch OS's and use something other
	than dotted decimal quad getting a match in the DNS when
	the new OS is not as permissive as the old OS.

> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf