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

"Frank Ellermann" <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Thu, 03 July 2008 05:04 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 2815F3A6A81; Wed, 2 Jul 2008 22:04:57 -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 3F3163A6A7F for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 22:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.197
X-Spam-Level:
X-Spam-Status: No, score=0.197 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=3.196, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-1]
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 Y93NThR8t59O for <ietf@core3.amsl.com>; Wed, 2 Jul 2008 22:04:55 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 485D23A6A81 for <ietf@ietf.org>; Wed, 2 Jul 2008 22:04:55 -0700 (PDT)
Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KEH0A-00077R-ID for ietf@ietf.org; Thu, 03 Jul 2008 05:05:02 +0000
Received: from rain.gmane.org ([80.91.229.7]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Thu, 03 Jul 2008 05:05:02 +0000
Received: from hmdmhdfmhdjmzdtjmzdtzktdkztdjz by rain.gmane.org with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Thu, 03 Jul 2008 05:05:02 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: "Frank Ellermann" <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Date: Thu, 3 Jul 2008 05:22:32 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 37
Message-ID: <g4hggt$8sb$1@ger.gmane.org>
References: <558a39a60807011541je1fbefbk118983456d596dba@mail.gmail.com> <200807022323.m62NNwVJ034275@drugs.dv.isc.org>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: rain.gmane.org
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Mark Andrews wrote:

> The Internet went to multi-label hostnames ~20 years ago.

As noted in RFC 2821 as "one dot required" syntax, also
mentioned in RFC 3696.  Recently *overruled* by 2821bis.

> No sane TLD operator can expect "http://tld" or "user@tld"
> to work reliably.  

Certainly not expect, but some gave it nevertheless a try.
My bastard browser from hell let's me say <http://museum./> 
(note trailing dot).

> I suspect there are still mail configuations around that 
> will re-write "user@tld" to "user@tld.ARPA"ARPA".

They didn't note that RFC 2821 upgraded the 821 examples,
sh*t happens... <eg>

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

No, there are enough TLDs disagreeing with this idea...

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

...the 2821bis Last Call ended months ago, and "one dot
required" was discussed long enough.  Change this again,
and I'll scream.

 Frank
-- 
Repost, apparently my first attempt didn't make it.

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