Re: [EAI] [IETF] Barriers to Deployment [ was: Content Issues]

John C Klensin <john-ietf@jck.com> Mon, 17 October 2016 04:23 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD11129515 for <ima@ietfa.amsl.com>; Sun, 16 Oct 2016 21:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level:
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CfkNCEx9ejn for <ima@ietfa.amsl.com>; Sun, 16 Oct 2016 21:23:06 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 161781293E3 for <ima@ietf.org>; Sun, 16 Oct 2016 21:23:06 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1bvzRz-000I1Z-7B; Mon, 17 Oct 2016 00:22:59 -0400
Date: Mon, 17 Oct 2016 00:22:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: nalini.elkins@insidethestack.com
Message-ID: <7FA831D4B3709857DB95DE56@JcK-HP8200>
In-Reply-To: <783239201.731221.1476648090891@mail.yahoo.com>
References: <MWHPR03MB281341141A1CE0C0895F58A482D10@MWHPR03MB2813.namprd03.prod.outlook.com> <01Q668S03W0W00Q5OH@mauve.mrochek.com> <MWHPR03MB2813DA794DF0E1DEF36C8EC982D10@MWHPR03MB2813.namprd03.prod.outlook.com> <532EC6872314DFB0CC2B5F46@JcK-HP5.jck.com> <783239201.731221.1476648090891@mail.yahoo.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
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ima/9bN_9DuZ9HrsLH6UcrXSJuB6kQE>
Cc: Harish Chowdhary <harish@nixi.in>, ima@ietf.org
Subject: Re: [EAI] [IETF] Barriers to Deployment [ was: Content Issues]
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 17 Oct 2016 04:23:07 -0000


--On Sunday, October 16, 2016 20:01 +0000
nalini.elkins@insidethestack.com wrote:

>...
> I have also been following the discussion of the subscription
> to email lists.   I think that joining such lists is one of
> the important uses of email addresses.  I was just talking
> this morning to one of the not-very-computer-literate older
> ladies in the neighborhood and she was telling me about how
> useful she found the neighborhood email group to be.  So, I
> can see that this is something many people (not just IETFers!)
> probably find useful.

Note that there are a couple of things that are very different
between a neighborhood email group and the IETF list.   One is
that the same requirements for transparency and accountability
typically do not apply, at least in the same way.  The other is
closely related to what at least some of us have believed all
along would be the normal deployment model for SMTPUTF8, by
deployment within communities, particularly communities with a
small number of shared primary languages, who conclude that they
need it.   If everyone within a particular community is using
non-ASCII addresses, typically addresses based on the same
language and script, all of the very hard problems about how to
design, e.g., globally-adapted MUAs that are localized to the
language and culture of particular communities (not just the
right script) essentially go away and having to get everyone to
upgrade to make a given list with non-ASCII addresses work
disappear or become much more focused.


> Harish & I will put our heads together and put together some
> bullet points on the potential "Barriers to Deployment" draft
> and then come back to the list for comments on major issues to
> be covered.
> 
> Meanwhile, Harish is trying to get in touch with Don at the
> UASG group.
> 
> I will also ask some of the other people from Latin America /
> Africa who may be interested in this topic to join the IMA
> email list.

Excellent.

> We want to schedule a Bar BoF to discuss these topics in
> Seoul.  I am thinking Thursday morning breakfast meeting.
> Maybe people can respond to me / Harish privately to let us
> know if there are conflicts.   The title of the Bar BoF will
> be "Deployment Issues for IDN / IEA".   This way, we can start
> working on at least consolidating the problems.  Then, work
> quietly to resolve them.
> 
> Thoughts? 

Note that some of the people who have been contributing to this
discussion rarely attend IETF meetings face to face these days.
So think about whether their involvement would be useful enough
for you to arrange for remote participation.

best,
    john