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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 03 July 2008 08:06 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 6B9733A6A9B; Thu, 3 Jul 2008 01:06: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 342523A6A9B for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 01:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 Hg+bpyWgfwQB for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 01:06:33 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id AB39D3A698A for <ietf@ietf.org>; Thu, 3 Jul 2008 01:06:33 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 448151C0145; Thu, 3 Jul 2008 10:06:40 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 3F5B11C0139; Thu, 3 Jul 2008 10:06:40 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id 3BF7658ECD7; Thu, 3 Jul 2008 10:06:40 +0200 (CEST)
Date: Thu, 3 Jul 2008 10:06:40 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Message-ID: <20080703080640.GA8026@nic.fr>
References: <558a39a60807011541je1fbefbk118983456d596dba@mail.gmail.com> <200807022323.m62NNwVJ034275@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <200807022323.m62NNwVJ034275@drugs.dv.isc.org>
X-Operating-System: Debian GNU/Linux lenny/sid
X-Kernel: Linux 2.6.24-1-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.18 (2008-05-17)
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Thu, Jul 03, 2008 at 09:23:58AM +1000,
 Mark Andrews <Mark_Andrews@isc.org> wrote 
 a message of 32 lines which said:

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

[Mark, you used non-RFC2606 names, the IESG will put a DISCUSS against
you.]

I agree but it is not the point: an email adress like
bortzmeyer+ietf@nic.fr is legal and works but not reliably (there are
many stupid broken Web forms which refuse it and tell me it's not
valid).

http://example is legal and should work. If it does not, it may
indicate a broken implementation.

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

There are many broken mail configurations.

> 	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. A TLD is a domain like any other and we should not write special
rules for them.

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

I hate special cases.
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf