Re: [EAI] Proposal for Alternate ABNF (was: Consensus Issue #6: current metalanguage model acceptable?)

John C Klensin <klensin@jck.com> Sun, 23 January 2011 10:56 UTC

Return-Path: <klensin@jck.com>
X-Original-To: ima@core3.amsl.com
Delivered-To: ima@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 473143A684C for <ima@core3.amsl.com>; Sun, 23 Jan 2011 02:56:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level:
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.068, 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 Lr5vmIm8K2wb for <ima@core3.amsl.com>; Sun, 23 Jan 2011 02:56:29 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id B65C03A6849 for <ima@ietf.org>; Sun, 23 Jan 2011 02:56:27 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Pgxeu-0000gn-Rr; Sun, 23 Jan 2011 05:59:02 -0500
Date: Sun, 23 Jan 2011 05:58:50 -0500
From: John C Klensin <klensin@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, ima@ietf.org
Message-ID: <8244D38A28FB919303079D4E@PST.JCK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [EAI] Proposal for Alternate ABNF (was: Consensus Issue #6: current metalanguage model acceptable?)
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jan 2011 10:56:30 -0000

--On Saturday, January 22, 2011 22:54 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

>> I can live with this approach.  If it is adopted, I'll help
>> sort out the domain name part.
> 
> As mentioned, IMO, the domain part should "just" say UTF-8 as
> well, though it's fair to point out the dependencies on
> existing RFCs that define DNS.  DNS is a bit trickier than the
> other headers because we explicitly want to disallow the
> punycode I think, and require UTF-8 U-Labels instead.

Shawn,

I know that you want to "disallow" punycode.  In a perfect
world, I would too, and that is part of what
draft-iab-idn-encoding is about.  But, realistically, while we
can try to discourage its use, banning it is just impractical
given that A-labels conform to the RFC 1035 "preferred syntax",
the syntax requirements of RFCs 5321 and 5322, and even the
rather careful rules in RFC 5892 about what does and does not
need to be checked on lookup.

    john