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

Keith Moore <moore@network-heretics.com> Tue, 08 July 2008 20:22 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 94E2C28C2F5; Tue, 8 Jul 2008 13:22:36 -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 0D81F3A698F for <ietf@core3.amsl.com>; Tue, 8 Jul 2008 13:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.742
X-Spam-Level:
X-Spam-Status: No, score=-2.742 tagged_above=-999 required=5 tests=[AWL=-0.143, 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 Wh-EYovf-uOg for <ietf@core3.amsl.com>; Tue, 8 Jul 2008 13:22:35 -0700 (PDT)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 5EF4B3A695F for <ietf@ietf.org>; Tue, 8 Jul 2008 13:22:35 -0700 (PDT)
Received: from lust.indecency.org (mail.fiveman.com [72.242.14.234] (may be forged)) by m1.imap-partners.net (MOS 3.8.4-GA) with ESMTP id AWI92540 (AUTH admin@network-heretics.com) for ietf@ietf.org; Tue, 8 Jul 2008 13:22:40 -0700 (PDT)
Message-ID: <4873CC8F.3010601@network-heretics.com>
Date: Tue, 08 Jul 2008 16:22:39 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
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> <4873AE46.6010906@isi.edu> <4873B2C0.1020008@network-heretics.com> <4873B353.20302@isi.edu> <4873B5F8.1060702@network-heretics.com> <4873B846.5070803@isi.edu> <4873B993.9040705@network-heretics.com> <4873C6FE.2000601@isi.edu>
In-Reply-To: <4873C6FE.2000601@isi.edu>
Cc: Ted Faber <faber@ISI.EDU>, 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

>> 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.

it's nonsensical for you to unilaterally declare that such names are 
relative, when well over two decades of practice indicates otherwise.

(and remember, some of these apps predate DNS and the whole notion of 
relative names)

it's almost as if the very concept of relative names in DNS is itself a 
bug - especially if you insist that handling of DNS names be absolutely 
uniform from one app to the next.  IMHO they cause far more problems 
than they're worth.

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