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

Keith Moore <moore@network-heretics.com> Tue, 08 July 2008 03:28 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 69FEA28C110; Mon, 7 Jul 2008 20:28:04 -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 3D22C28C112 for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 20:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 SGVUMCSIJpqx for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 20:28:02 -0700 (PDT)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 81B2028C110 for <ietf@ietf.org>; Mon, 7 Jul 2008 20:28:02 -0700 (PDT)
Received: from lust.indecency.org (adsl-6-17-238.tys.bellsouth.net [65.6.17.238]) by m1.imap-partners.net (MOS 3.8.4-GA) with ESMTP id AWH86711 (AUTH admin@network-heretics.com) for ietf@ietf.org; Mon, 7 Jul 2008 20:28:07 -0700 (PDT)
Message-ID: <4872DEC5.9040707@network-heretics.com>
Date: Mon, 07 Jul 2008 23:28:05 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Ted Faber <faber@ISI.EDU>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
References: <20080707211347.GB2222@zod.isi.edu> <200807080018.m680IPi1016117@drugs.dv.isc.org> <20080708013242.GB10677@zod.isi.edu>
In-Reply-To: <20080708013242.GB10677@zod.isi.edu>
Cc: Mark Andrews <Mark_Andrews@isc.org>, Theodore Tso <tytso@MIT.EDU>, 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"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> 
> The site-dependent interpretation of the name is determined not by the
> presence of dot within the name but its absence from the end. 

not so.  in many contexts the trailing dot is not valid syntax.

> I don't buy "unreliable" as a diagnosis for that state of affairs.  "hk"
> operates exactly as any other DNS name with respect to search path. 

search path isn't the only factor here.

there are also protocol specifications that expect DNS names to have 
dots in them.

there are also software implementations that use the presence/absence of 
a dot to distinguish a DNS name from some other kind of name.  in any 
context where both a DNS name and something else can appear, it's useful 
to be able to distinguish the two - and the presence/absence of a dot is 
about the only test that works.

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