Re: [EAI] Test - driven schedule (Re: Rechartering)

John C Klensin <klensin@jck.com> Thu, 23 July 2009 15:42 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 E8E993A69F8 for <ima@core3.amsl.com>; Thu, 23 Jul 2009 08:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.238
X-Spam-Level:
X-Spam-Status: No, score=-2.238 tagged_above=-999 required=5 tests=[AWL=0.361, 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 RNbt-QbzLJ8G for <ima@core3.amsl.com>; Thu, 23 Jul 2009 08:42:22 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 831433A6941 for <ima@ietf.org>; Thu, 23 Jul 2009 08:42:22 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1MU0QE-0002eG-S9; Thu, 23 Jul 2009 11:41:31 -0400
Date: Thu, 23 Jul 2009 11:41:29 -0400
From: John C Klensin <klensin@jck.com>
To: YAO Jiankang <yaojk@cnnic.cn>, Harald Alvestrand <harald@alvestrand.no>, Shawn Steele <Shawn.Steele@microsoft.com>
Message-ID: <8BC1BBA8349DC191FB83819F@JcK-eee9.example.com>
In-Reply-To: <448338030.08886@cnnic.cn>, <021001ca0b70$4bf6ab20$236ff1da@whatisfuture>
References: <mailman.13830.1247508102.4936.ima@ietf.org> <CAD7705D4A93814F97D3EF00790AF0B315FA6650@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A5BABF8.4080900@isode.com> <CAD7705D4A93814F97D3EF00790AF0B315FA6AAF@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A60AA0B.4000106@alvestrand.no> <CAD7705D4A93814F97D3EF00790AF0B315FCA179@TK5EX14MBXC104.redmond.corp.microsoft.com> , <EA9664FBEBEB7127550C3D30@[192.168.1.110]> <CAD7705D4A93814F97D3EF00790AF0B315FCB1CA@TK5EX14MBXC104.redmond.corp.microsoft.com> , <F2BC6EC973C4D97B22FB5FE1@p3.int.jck.com> <CAD7705D4A93814F97D3EF00790AF0B315FDE04F@tk5ex14mbxc105.redmond.corp.microsoft.com> <448328271.18687@cnnic.cn> <448338030.08886@cnnic.cn>, <021001ca0b70$4bf6ab20$236ff1da@whatisfuture>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: ima@ietf.org
Subject: Re: [EAI] Test - driven schedule (Re: Rechartering)
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: Thu, 23 Jul 2009 15:42:24 -0000

--On Thursday, July 23, 2009 16:33 +0800 YAO Jiankang
<yaojk@cnnic.cn> wrote:

> From: "Harald Alvestrand" <harald@alvestrand.no>
> To: "Shawn Steele" <Shawn.Steele@microsoft.com>
> Cc: <ima@ietf.org>
> Sent: Thursday, July 23, 2009 1:49 PM
> Subject: [EAI] Test - driven schedule (Re: Rechartering)
> 
> 
>> Shawn Steele wrote:
>>>   
>>>> But I personally think that the odds of getting a site that
>>>> can't manage "john+ietf@bogus.domain.name" to be able to
>>>> handle <иван@bogus.domain.name <john@bogus.domain.name>>
>>>> within my lifetime are pretty small.
>>>>     
>>> 
>>> I'd agree, but john@bogus.domain.name should still work :)0
>>> 
>>> So, I pretty much agree with your points, but you aren't
>>> giving me much hope of EAI being adaquate to those criteria
>>> in the next decade.  I still think some sort of schedule
>>> would be interesting to help us figure out how to proceed in
>>> addressing your concerns.
>>>   
>> Would it be interetsing to (for at least 5 minutes) explore
>> the idea of  a test-driven schedule, rather than a
>> calendar-driven one?
> 
> It is a good news. 
> I think that both the test work and standard track progress
> work can be drivend in the parallel way.

I didn't see "parallel" in Harald's suggestion.  And I do think
the suggestion is a good one.  

I think it is also worth pointing out that some of the recent
discussions on this list may suggest changes in the SMTP
extension and header specs.  Those changes may or may not be
necessary, which is another testing and thinking topic, but they
represent decisions that need to be made and it would be better
to make them with data than without.

For example, experience elsewhere (including in the IDNABIS
discussions) makes it fairly clear that either NFC or NFD
normalization is a necessity if one is going to compare two
Unicode strings.  Without one or the other, two different ways
of entering exactly the same character will not compare equal.
A given user may have only one way to enter a particular
character while another user may have only the other way
available.

That suggests that we should _at least_ recommend normalization
in the SMTP server (much as 5321 recommends case-insensitive
matching) and that we should think about requiring it.  But,
again, data would help.

     john