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

Mark Andrews <Mark_Andrews@isc.org> Wed, 02 July 2008 23:24 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 B31FC3A6C8E; Wed, 2 Jul 2008 16:24:11 -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 950763A6998 for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 16:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level:
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.071, 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 DNVIC1PH0FSY for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 16:24:08 -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 420DD3A66B4 for <ietf@ietf.org>; Wed, 2 Jul 2008 16:24:07 -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 m62NNwVJ034275; Thu, 3 Jul 2008 09:23:59 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200807022323.m62NNwVJ034275@drugs.dv.isc.org>
To: "James Seng" <james@seng.sg>
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-reply-to: Your message of "Wed, 02 Jul 2008 06:41:37 +0800." <558a39a60807011541je1fbefbk118983456d596dba@mail.gmail.com>
Date: Thu, 03 Jul 2008 09:23:58 +1000
Cc: dcrocker@bbiw.net, IETF Discussion <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

> Which brings up a question can a TLD be used like a domain name?
> 
> not just http://microsoft/ but bill.gate@microsoft will likely to fail to.
> 
> james
> 
	The Internet went to multi-label hostnames ~20 years ago.
	We added ".ARPA" to all the single label hostnames as part
	of that process.  The only hold over is "localhost" and
	that is implemeted locally, not in the global DNS.

	No sane TLD operator can expect "http://tld" or "user@tld"
	to work reliably.  I suspect there are still mail configuations
	around that will re-write "user@tld" to "user@tld.ARPA"ARPA".

	Should we be writting a RFC which states that MX and address
	records SHOULD NOT be added to the apex of a TLD zone?

	Should we be writting a RFC which states that single label
	hostnames/mail domains SHOULD NOT be looked up "as is" in
	the DNS?

	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