IETF Logo Mail Archive

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

Mark Andrews <Mark_Andrews@isc.org> Wed, 09 July 2008 01:51 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 F2FDF3A6952; Tue, 8 Jul 2008 18:51:31 -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 0A7B43A681A for <ietf@core3.amsl.com>; Tue, 8 Jul 2008 18:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.66
X-Spam-Level:
X-Spam-Status: No, score=-2.66 tagged_above=-999 required=5 tests=[AWL=-0.061, 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 SEZQiyGX-4ZV for <ietf@core3.amsl.com>; Tue, 8 Jul 2008 18:51:29 -0700 (PDT)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by core3.amsl.com (Postfix) with ESMTP id 5BA133A6863 for <ietf@ietf.org>; Tue, 8 Jul 2008 18:51:27 -0700 (PDT)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.2) with ESMTP id m691pYYq069173; Wed, 9 Jul 2008 11:51:34 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200807090151.m691pYYq069173@drugs.dv.isc.org>
To: Joe Touch <touch@ISI.EDU>
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Date: Wed, 09 Jul 2008 11:51:34 +1000
Cc: Ted Faber <faber@ISI.EDU>, 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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>>> 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.
> 
> I didn't declare it; 1034 did. 

	And RFC 1535 got resolvers to try search lists last if there
	was a period in the name.   This removed the need for final
	periods for any legal fully qualified host name.

	"hk" is not a legal fully qualified host name.  Demanding that
	applications support final dots to support uses that are outside
	of the original design scope is nonsensical.

	Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email