Re: [precis] names and usernames

John C Klensin <john-ietf@jck.com> Sun, 12 February 2017 23:43 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF9DC129472 for <precis@ietfa.amsl.com>; Sun, 12 Feb 2017 15:43:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 iCtPo_xD_jkS for <precis@ietfa.amsl.com>; Sun, 12 Feb 2017 15:43:34 -0800 (PST)
Received: from bsa2.jck.com (ns.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 4175C120726 for <precis@ietf.org>; Sun, 12 Feb 2017 15:43:34 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cd3no-000BBT-17; Sun, 12 Feb 2017 18:43:32 -0500
Date: Sun, 12 Feb 2017 18:43:24 -0500
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, precis@ietf.org
Message-ID: <2F562E0E75615D28FB8474A8@PSB>
In-Reply-To: <cbc41f53-8d39-76ad-a2a7-276d50db9bac@stpeter.im>
References: <cbc41f53-8d39-76ad-a2a7-276d50db9bac@stpeter.im>
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.70
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/precis/r35ZIeldGz1QhNqvjtp-Nd671lo>
Subject: Re: [precis] names and usernames
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Feb 2017 23:43:36 -0000

Peter,

Just to be clear to you and the WG, I don't have a strong
opinion about what decision the WG should make in these cases,
but I do believe the decision must be explicit and the result of
discussion, not something that happens as an accident without
knowledge of the relevant cases.

best,
   john


--On Sunday, February 12, 2017 16:29 -0700 Peter Saint-Andre
<stpeter@stpeter.im> wrote:

> John Klensin has brought to my attention that it is currently
> impossible to represent some people's names in PRECIS
> usernames because some of the relevant Unicode code points are
> disallowed by the IdentifierClass defined in RFC 7564 (and
> thus by the UsernameCaseMapped and UsernameCasePreserved
> profiles defined in RFC 7613).
> 
> First, RFC 7564 disallows "default ignorable" code points in
> the IdentifierClass. However, as I understand it some of these
> code points are need to represent characters in names that
> might be desirable to people living within communities that
> use Indic script and eastern Arabic script (e.g., Persian and
> writing systems derived from Persian). In particular, the
> Unicode Standard specifies that ZWJ and ZWNJ are "default
> ignorable" and it seems that these code points are especially
> important in this context.
> 
> Second, apparently some Chinese family names are typically
> written (especially outside the People's Republic of China)
> using characters that the Unicode Consortium assigns to
> non-BMP code points, or assigns in the BMP but as
> compatibility decomposable characters (and thus disallowed by
> RFC 7564 in the IdentifierClass).
> 
> I'm not sure whether we can solve these problems
> (internationalization is messy and we've never tried to
> guarantee that any particular name or preferred string could
> be represented in PRECIS usernames), but input from people
> with a deeper understanding of these issues would be
> appreciated. I have attempted to reach out to relevant
> experts, and will report back to this list with any findings.
> 
> In the meantime, I plan to submit revised I-Ds addressing
> other issues with the PRECIS specifications sometime this
> evening.
> 
> Peter
> 
> _______________________________________________
> precis mailing list
> precis@ietf.org
> https://www.ietf.org/mailman/listinfo/precis