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

Joe Touch <touch@ISI.EDU> Tue, 08 July 2008 18:13 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 C68753A6A76; Tue, 8 Jul 2008 11:13:45 -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 64E003A69E6 for <ietf@core3.amsl.com>; Tue, 8 Jul 2008 11:13:44 -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 9QU5fAEiUFFX for <ietf@core3.amsl.com>; Tue, 8 Jul 2008 11:13:43 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 291F23A6801 for <ietf@ietf.org>; Tue, 8 Jul 2008 11:13:43 -0700 (PDT)
Received: from [128.9.168.63] (bet.isi.edu [128.9.168.63]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m68IDXaK012307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Jul 2008 11:13:35 -0700 (PDT)
Message-ID: <4873AE46.6010906@isi.edu>
Date: Tue, 08 Jul 2008 11:13:26 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
References: <20080708020228.GC10677@zod.isi.edu> <200807080254.m682sG2Q007427@drugs.dv.isc.org> <20080708161335.GB2519@zod.isi.edu> <4873948A.2040904@network-heretics.com>
In-Reply-To: <4873948A.2040904@network-heretics.com>
X-Enigmail-Version: 0.95.6
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Theodore Tso <tytso@MIT.EDU>, Mark Andrews <Mark_Andrews@isc.org>, Ted Faber <faber@ISI.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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Keith Moore wrote:
|
|
| Ted Faber wrote:
|> On Tue, Jul 08, 2008 at 12:54:16PM +1000, Mark Andrews wrote:
|>>     "hk." is not a syntactically valid hostname (RFC 952).
|>>     "hk." is not a syntactically valid mail domain.
|>>     Periods at the end are not legal.
|>>
|>>     RFC 1035 has *nothing* to do with defining what is legal
|>>     as a hostname.
|>
|> Fair enough.
|> By RFC952 standards "hk" is a perfectly fine hostname.
|>
|> By RFC1035 standards, if you look it or any other DNS name up using the
|> DNS resolver, that resolver will treat the name as relative unless it
|> ends with a dot.   Arguing that hk is an unreliable hostname if you
|> look it up as a relative pathname is pretty much the same as arguing
|> that www.isi.deterlab.net is an unreliable hostname.  Both of them are
|> subject to the search path without that trailing dot.
|
| RFC1035 may recognize the trailing dot, but (for better or worse) many
| applications do not recognize it, and some explicitly forbid it.

RFC1043 defines the dot. The fact that some apps don't recognize it is a
bug. Given its impact, let's not call it a feature or BCP.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIc65GE5f5cImnZrsRApEwAKCBFc5Ss/pi7xbFpT8KOrt+35vQQACfYWBy
204MtY5DKH73CfaI4SEMbV4=
=zH2v
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf