Re: [EAI] General issues and strategy (was: Re: Content Issues [ was: Internationalized Email Internet Draft])

<nalini.elkins@insidethestack.com> Fri, 14 October 2016 16:29 UTC

Return-Path: <nalini.elkins@insidethestack.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 C3559129855 for <ima@ietfa.amsl.com>; Fri, 14 Oct 2016 09:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 A3lJWSOUrtZi for <ima@ietfa.amsl.com>; Fri, 14 Oct 2016 09:28:58 -0700 (PDT)
Received: from nm27-vm2.bullet.mail.ne1.yahoo.com (nm27-vm2.bullet.mail.ne1.yahoo.com [98.138.91.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82007129548 for <ima@ietf.org>; Fri, 14 Oct 2016 09:28:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1476462538; bh=hkG5rXQHnNWl3pgyF0TilihCRNDVVBHtJP0juQjBbnE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=rCvqUxGkTkduzoDjG7FcuqHrUdjFO3lB1YKq1NISrRaXe15YVxbgkapuVyyMosBX3YdeQW+mufxEJ43S5dpENQZBavBqFETOJXjtK/83jIdLbLWum5uWK6Chp+dgQDvYWUlLX7/MJB0aTfq4URT3AD+EG2sIy8hbta68VwQBpAqelST5JnohrxuZrphpV/Mi7Jb7r3m8CpOkn4VAmFD5AODHiPAh1DBsNOryn+5Khmj9kBqypOrbwj2EZXyHiu+tQkocA2fDOv9XameCTduzPhjCh7lgEbfESEa6GHQ0jY3GMj0tM6FkuCIN7CziO/OwrB/l17/0W1rFI8/f+F1T8w==
Received: from [98.138.100.113] by nm27.bullet.mail.ne1.yahoo.com with NNFMP; 14 Oct 2016 16:28:58 -0000
Received: from [98.138.226.169] by tm104.bullet.mail.ne1.yahoo.com with NNFMP; 14 Oct 2016 16:28:58 -0000
Received: from [127.0.0.1] by omp1070.mail.ne1.yahoo.com with NNFMP; 14 Oct 2016 16:28:58 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 79155.65209.bm@omp1070.mail.ne1.yahoo.com
X-YMail-OSG: HdUt53kVM1mAdlbDeJVssVZguO7bOJwf2KYJpQMqv9ld6UlZnULipFFKdcGnQzt RPUYb6ZyriWRSdfmW5loY8gp0Cy2F0qhYtFNBQgeWJpRKgNYY8dv6J5PMzwZgUJ2FeCDKQdCfs3A c91Uk5AwJ8C9Z9iiiHK7veHztdEL.8bUgF8hytf0WSjmAvckMNS09_pcWz8X44._nJXgEUf8e9Jj x09qoKGZEsaIvvuZIF9cqw2Wed21Ta8CyZZJ945NiTAPl.JBe6ojFS.5pmtpvP19JUqy5cyPsZG8 465byYLYdW8_Dh1EthBdSmfaeVn1ljlruqdh_H08khPOqVhHY1oUqcmDM4ep7GQAZtKMmXShnPkG yLPC7y3hfaYeWz8L0VOyLzqChFPzmhd25nSl6u1qlLZ.EewKuQe7hgaR5TQywt3eZQJ9G2vE2YTl kwLPjUZLrfQf17xdIs5HJnJgKZDsVI9GvBSye0z7O9J8c2DzAFTCDbsPpradFYkY_jZsNsEBU0Q7 Wry.oWUnDgCxcrVSZ_39D.haERRVaSU0f9c.wSnYTLiRASo6IBShfGlxCs2PxwOWu
Received: from jws200181.mail.ne1.yahoo.com by sendmailws109.mail.ne1.yahoo.com; Fri, 14 Oct 2016 16:28:57 +0000; 1476462537.634
Date: Fri, 14 Oct 2016 16:28:56 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: John C Klensin <klensin@jck.com>, "HANSEN, TONY L" <tony@att.com>, "ima@ietf.org" <ima@ietf.org>
Message-ID: <1130669068.355429.1476462536866@mail.yahoo.com>
In-Reply-To: <8B119C286A3CFDE08C598251@JcK-HP8200>
References: <20161006055447.32573.qmail@pro-236-157.rediffmailpro.com> <9EC0EB65-9C58-43ED-9A80-1DA32C58E3E0@att.com> <E125B6AC26988823306936BF@JcK-HP5.jck.com> <489025644.216489.1476451836537@mail.yahoo.com> <8B119C286A3CFDE08C598251@JcK-HP8200>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_355428_1558044639.1476462536862"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ima/4Cdx0RPtBXC-Wj2eLmbxuBvgrEk>
Cc: Harish Chowdhary <harish@nixi.in>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [EAI] General issues and strategy (was: Re: Content Issues [ was: Internationalized Email Internet Draft])
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Fri, 14 Oct 2016 16:29:02 -0000

John,

--On Friday, October 14, 2016 13:30 +0000
nalini.elkins@insidethestack.com wrote:

>> John / Tony,
>> I am going to split your comments into separate threads so
>> that I can keep track of each.   
>>...
>> Yes.  I see your point.   Let me say first the basic thing
>> that we are trying to do is to discuss the holistic user
>> experience of internationalized emails from an operational
>> point of view.   In so doing, the co-mingling happened.  We
>> could do a second draft for content issues or change the
>> abstract of this one to better state what our real goal is.
>> Secondly, as you guys know well, there are lots of other
>> issues with IDN, browser support, etc.   What we were
>> actually hoping is that we could have a forum (perhaps like
>> DNSOps or v6Ops) where we could come together to define and
>> discuss such problems, move towards best practices (or work
> arounds! Not that I like that, but it happens.)   Because we
>> have not even started on problems that we see such as search
>> algorithm ranking of IDNs and so on.   We were hoping that
>> others would step up to author such other drafts.

>A few very general comments about context.  This might
>anticipate some future note from you, so I hope I can get it off
>quickly...

>(1) I trust you are aware of the ICANN=-sponsored "Universal
>Acceptance" effort, which is covering some of this same ground.
>Personally, I believe they are seriously out in the weeds, doing
>a good deal of work on assumptions about the DNS and the EAI
>work that are just not valid for a number of technical reasons,
>but it would be unfortunate to waste whatever cycles are
>associated with duplicative efforts.  As far as I know, Don
>Holland is still lead; I think he is on the EAI list but am not
>sure.

Yes.  I am aware of this & want to get Don Holland involved.  I somehow had the idea he would be in Seoul but maybe I am wrong.  I think I will try to have a private conversation with him and Harish ahead of time.

>(2) I trust you are also aware that there is an IAB I18N>program.  It has been, again IMO, fairly unhealthy in the last
>couple of years, largely because the available cycles of the
>most active and expert people have disappeared into the IANA
>Transition activity.  If you want a forum or workshop, they
>might be a good place to start.  Ted Hardie is lead; I have no
>idea whether he is on the EAI list.
I had a very brief conversation with Ted Hardie over email.  I will contact him again.

>(3) Despite the obvious interest and importance of this issue, I
>have observed very little actual energy in the IETF for dealing
>with it or i18n issues more generally.  By the time the EAI WG
>got its documents out, there was little interest in specific
>work beyond "we just want this to work".  By the time the PRECIS
>WG got its RFCs out, there was little general interest in
>careful review of documents (resulting in a need to start work
>on revisions almost immediately thereafter).  AFAICT, the
>strongest and most general sentiment in the WG was "just tell me
>what to do so I don't need to understand or think about this".
>That is understandable, but not a good foundation for getting
>work done.  The community has been completely unable to engage
>with the "non-decomposing character" issue that has paralyzed
>some important IDNA applications for a couple of years now (IMO,
>the LUCID BOF, supposedly addressed to that issue, did a good
>job of illustrating the more fundamental problems with IETF
>engagement, including a lengthy discussion of just how to spell
>Zürich in English (or, for that matter, in various versions of
>German).  

>(4) Even among those who were active in the EAI work, there has
>been, AFAICT, silence so far except from Tony and myself.  I
>know that some are off chasing general equivalence of DNS names.
>I believe that effort shows a fundamental lack of understanding
>of the properties of the relevant data structures but it seems
>to be getting agenda time in Seoul (see "DNSBUNDLED" on Jari's
>"New Work in Seoul" BOF list).


Sure.  I understand your frustration.  
Harish and I have been in touch with the community in Africa and Latin America as well, as of course, India.   If you will, since this is more of a problem for the non-English speaking world, then those of us who actually speak languages other than English should step up to the plate and be responsible for doing work.  One of the representatives for one of the communities has told me that they may fund someone to come to Seoul just to work on this project.
We have also started a conversation with some of the OS / browser manufacturers - the Mozillas and Microsofts of the world.
I want to get a core group of maybe 5 - 10 people from various communities and then people from the OS / browser world.  It will take some time to get critical mass but as you say, the issue is very critical.  That is definitely being seen at least in the non-Western parts of the world.  (Sorry, I don't know if I am being somehow politically incorrect in phrasing this!)
I hope that you and Tony can guide us.  It will take us some time to come up to speed.  It has definitely helped to do a proof of concept implementation.  Harish and I conference call every week sometimes for two hours to discuss these issues.   We have learned a lot in the past two months.  Mostly based on problems that I have had!
We appreciate very much your and Tony's efforts to get the WG and documents to this stage.  But, now we need to work on implementation and migration issues.   I hope you will be available to guide us.  I am not thinking that we will expect you to be responsible for doing all the work.
I was born in India.  Many, many of the people in India do not (and never will) speak English.   Two of the happiest years of my life were living at the edge of the bush in French speaking West Africa.  Again, English was not widely spoken. 
But, English is the de-facto language of the Internet.  The next billion people on the Internet need access in local language.   I think that at the IETF one thing that we can do is quietly and thoughtfully concentrate and work out the technical issues.   That is our strength.   It will take us some time to form a core group.   My hope is that by IETF99, we will have enough people to do something interesting.

>(5) You should also be sure you understand that many of the
>issues with non-ASCII identifiers, especially identifiers 

Yes.   Are there any RFCs or papers that you might point me to?

>(5) If you want rapid deployment of fully-internationalized
>email messages, it is important that you understand that there
>were alternate hypotheses for how to get both the IDN and that
>work done.  For IDNs, we could have changed the DNS and server
>matching algorithms (which might have permitted approximate
>matching and made a number of issues with comparison and
>normalization much easier) or we could have adopted an "above
>DNS" model which would have also helped with the matching and
>search issues. However, there was a great deal of pressure, some
>of it emotional and paralleling the comments about "English" in
>your draft, for "fast" and "in the DNS", and that got us the
>mappings, restrictions, and trick encoding of IDNA.  Every bit
>of new evidence or pressure for synonymous labels and matching
>that is predictable given local language culture is an argument
>that we got it wrong and should have gone for one of the other
>approaches, probably a member of the "Above DNS" family.  For
>EAI, there was a similar choice.  We could have stuck with
>all-ASCII address local parts and focused on better use of
>encoded names (e.g., by making it clear that not copying a name
>phrase into a reply or to or from an address book was a very bad
>practice, encouraging address book lookups by the name phrase or
>equivalent as well as the address, etc., thereby saving a good
>many transition and interoperability problems.  I note that was
>the solution adopted by the ITU, an organization with far more
>representation and influence from countries and people who speak
>English as a second language if at all, for a broad range of
>I19n issues.  Instead, there was a strong commitment in the WG
>and those who pushed for it to have all-non-ASCII mailbox
>addresses and to phase out the encoded word approach.  At least
>a significant fraction of the WG understood the likely (or
>certain) costs of that decision including slow deployment and
>interoperability issues that would likely limit EAI use to
>"within community" communications.  If, at any point, you want
>to argue for discarding SMTPUTF8 and returning to an encoded
>word model, there are less difficult (but also less culturally
>and aesthetically attractive) ways to move forward.


This is very interesting.  Let me think it over and we may want to discuss in our core group.   We also need the people from DNS involved.  Let me talk to a few people over there & pick their brains.

best,
  john


>(BTW, as a further illustration of the "too few people with
>spare cycles" problem, I'm writing this note rather than working
>on the current round of PRECIS revision drafts (and they are, in
>turn, holding up work in URNBIS) and am copying Peter, who I
>don't think is on the EAI list either, so he knows what is
>happening.)
John, thank you for everything you have done & for all your help with this.
Nalini