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

[Joe Touch <touch at ISI.EDU>]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)



Keith Moore wrote:
...
> Many, many working groups have looked at the problems associated with 
> relative names and determined that they're not acceptable.  It's a "bug" 
> that relative names are forbidden in these apps, nor that the final "." 
> is implicit and in many cases disallowed.  These are carefully 
> considered design features.  (for instance, forbidding the final "." 
> makes it simpler to compare domain names for equivalence.)

It's nonsensical for an application to decide that relative names are 
unacceptable, but to require users to input names as relative.

An explicit trailing '.' has either no impact on comparison or can only 
help. If all names have the '.' impicitly, it can be chopped off as 
redundant when it is provided by the user. If the From ietf-bounces at ietf.org  Tue Jul  8 12:59:11 2008
Return-Path: <ietf-bounces at ietf.org>
X-Original-To: ietf-web-archive at megatron.ietf.org
Delivered-To: ietfarch-ietf-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B7E128C233;
	Tue,  8 Jul 2008 12:59:11 -0700 (PDT)
X-Original-To: ietf at core3.amsl.com
Delivered-To: ietf at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E4993A695F
	for <ietf at core3.amsl.com>; Tue,  8 Jul 2008 12:59:10 -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 cycwq04kGF4s for <ietf at core3.amsl.com>;
	Tue,  8 Jul 2008 12:59:09 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64])
	by core3.amsl.com (Postfix) with ESMTP id 63F163A689C
	for <ietf at ietf.org>; Tue,  8 Jul 2008 12:59:09 -0700 (PDT)
Received: from [127.0.0.1] (nib.isi.edu [128.9.160.144])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m68JwsCo018432
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits%6 verify=NOT);
	Tue, 8 Jul 2008 12:58:56 -0700 (PDT)
Message-ID: <4873C6FE.2000601 at isi.edu>
Date: Tue, 08 Jul 2008 12:58:54 -0700
From: Joe Touch <touch at ISI.EDU>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Keith Moore <moore at network-heretics.com>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
References: <20080708020228.GC10677 at zod.isi.edu>	<200807080254.m682sG2Q007427 at drugs.dv.isc.org>	<20080708161335.GB2519 at zod.isi.edu>	<4873948A.2040904 at network-heretics.com>
	<4873AE46.6010906 at isi.edu>	<4873B2C0.1020008 at network-heretics.com>
	<4873B353.20302 at isi.edu> <4873B5F8.1060702 at network-heretics.com>
	<4873B846.5070803 at isi.edu> <4873B993.9040705 at network-heretics.com>
In-Reply-To: <4873B993.9040705 at network-heretics.com>
X-Enigmail-Version: 0.95.6
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch at isi.edu
Cc: Ted Faber <faber at ISI.EDU>, Mark Andrews <Mark_Andrews at isc.org>,
	Theodore Tso <tytso at MIT.EDU>, ietf at ietf.org
X-BeenThere: ietf at 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 at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf at ietf.org>
List-Help: <mailto:ietf-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="==============50292718=="
Sender: ietf-bounces at ietf.org
Errors-To: ietf-bounces at ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)



Keith Moore wrote:
...
> Many, many working groups have looked at the problems associated with 
> relative names and determined that they're not acceptable.  It's a "bug" 
> that relative names are forbidden in these apps, nor that the final "." 
> is implicit and in many cases disallowed.  These are carefully 
> considered design features.  (for instance, forbidding the final "." 
> makes it simpler to compare domain names for equivalence.)

It's nonsensical for an application to decide that relative names are 
unacceptable, but to require users to input names as relative.

An explicit trailing '.' has either no impact on comparison or can only 
help. If all names have the '.' impicitly, it can be chopped off as 
redundant when it is provided by the user.'.' is not implicit, 
then you're preventing the user from providing it.

All the '.' does is inhibit the resolver from trying a list of suffixes 
in succession; its presence makes resolution and comparison easier, not 
harder.

Joe

Attachment: signature.asc
Description: OpenPGP digital signature

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