IETF Logo Mail Archive

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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 01 July 2008 19:48 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 108543A686C; Tue, 1 Jul 2008 12:48:13 -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 2C9103A6843 for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 12:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 msTcl5cyEfnu for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 12:48:07 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by core3.amsl.com (Postfix) with ESMTP id C4F243A686C for <ietf@ietf.org>; Tue, 1 Jul 2008 12:48:06 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id D148E94093; Tue, 1 Jul 2008 21:48:08 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id 258BE1906DF; Tue, 1 Jul 2008 21:44:17 +0200 (CEST)
Date: Tue, 01 Jul 2008 21:44:17 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tony Finch <dot@dotat.at>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Message-ID: <20080701194417.GA14688@sources.org>
References: <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> <20080630190153.GB31520@sources.org> <alpine.LSU.1.10.0807011737360.30078@hermes-1.csi.cam.ac.uk>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <alpine.LSU.1.10.0807011737360.30078@hermes-1.csi.cam.ac.uk>
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 Tue, Jul 01, 2008 at 05:40:35PM +0100,
 Tony Finch <dot@dotat.at> wrote 
 a message of 18 lines which said:

> RFC 1123 section 2.1, especially the last sentence.

Well, the last sentence will no longer be true if all-numeric TLDs are
allocated but, before that, one finds:

> The host SHOULD check the string syntactically for a dotted-decimal
> number before looking it up in the Domain Name System.

which seems to reply to David Conrad's question: if all the
implementations are correct, 127.0.0.1 will always be an IP address,
even if the TLD ".1" is allocated.
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email