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

Lyman Chapin <lyman@acm.org> Mon, 07 July 2008 15:45 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 CC89F28C192; Mon, 7 Jul 2008 08:45:54 -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 24FC63A68B4 for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 13:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.911
X-Spam-Level:
X-Spam-Status: No, score=-102.911 tagged_above=-999 required=5 tests=[AWL=-0.312, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 6OHapjlz5yo7 for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 13:59:00 -0700 (PDT)
Received: from hobbiton.shire.net (hobbiton.shire.net [209.41.94.250]) by core3.amsl.com (Postfix) with ESMTP id 46E3A3A6812 for <ietf@ietf.org>; Thu, 3 Jul 2008 13:59:00 -0700 (PDT)
Received: from c-75-67-86-24.hsd1.nh.comcast.net ([75.67.86.24] helo=[10.0.1.29]) by hobbiton.shire.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.51) id 1KEVtU-000HLo-N4; Thu, 03 Jul 2008 14:59:08 -0600
In-Reply-To: <BLU137-W18376D2DBA85C8F712C06F93980@phx.gbl>
References: Your message of <200807022323.m62NNwVJ034275@drugs.dv.isc.org> <BLU137-W18376D2DBA85C8F712C06F93980@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <8953A1CE-E953-409F-A692-BD12DF4ADE61@acm.org>
From: Lyman Chapin <lyman@acm.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Date: Thu, 3 Jul 2008 16:59:50 -0400
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.753)
X-SA-Exim-Connect-IP: 75.67.86.24
X-SA-Exim-Mail-From: lyman@acm.org
X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false
X-Mailman-Approved-At: Mon, 07 Jul 2008 08:45:53 -0700
Cc: 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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

I understand the objection to MX records in TLDs based on the past  
history of how single label hostnames were (and, as Mark points out,  
undoubtedly still are) handled. If it were possible to put that  
aside, would you have any other objection to single label hostnames?  
I know that at least some of the interest in new gTLDs has been  
expressed by companies that like the idea of using a globally- 
recognized trademark as a TLD - for example,  
"customerservice@ibm" (not to imply that IBM is one of the companies  
that has expressed this sort of interest).

I'm familiar with <draft-klensin-rfc2821bis-10.txt> and understand  
the importance of using only FQDNs in SMTP exchanges given that "[i]n  
the case of a top-level domain used by itself in an email address, a  
single string is used without any dots." What I'm interested in is  
any reason to proscribe the use of a TLD as a single label hostname  
(particularly for email addresses) other than the fact that there is  
software out there that will interpret it incorrectly -

- Lyman

On Jul 2, 2008, at 8:07 PM, Bernard Aboba wrote:
>
> Mark Andrews said:
>
> "The Internet went to multi-label hostnames ~20 years ago.We added  
> ".ARPA" to all the single label hostnames as partof that process.  
> The only hold over is "localhost" andthat 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  
> configuationsaround that will re-write "user@tld" to  
> user@tld.ARPA.Should we be writting a RFC which states that MX and  
> addressrecords SHOULD NOT be added to the apex of a TLD zone?
>
> Should we be writting a RFC which states that single labelhostnames/ 
> mail domains SHOULD NOT be looked up "as is" inthe DNS?"
>
> Both sound like good ideas to me.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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