Re: [precis] names and usernames

Peter Saint-Andre <> Mon, 13 February 2017 00:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0BC6C129486 for <>; Sun, 12 Feb 2017 16:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key) header.b=uccgEO76; dkim=pass (1024-bit key) header.b=V0rEEXEb
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5ZqiZbo90Y_K for <>; Sun, 12 Feb 2017 16:02:32 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 49A5D120726 for <>; Sun, 12 Feb 2017 16:02:32 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal []) by mailnew.nyi.internal (Postfix) with ESMTP id 9B6BE13A4; Sun, 12 Feb 2017 19:02:31 -0500 (EST)
Received: from frontend1 ([]) by compute2.internal (MEProxy); Sun, 12 Feb 2017 19:02:31 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=fRBXonyFkDQGk0s rPOEARgU197M=; b=uccgEO76uvnB4LgPfgw8htyV6icMkusKvarvZ6vNVR7e9mR EV90bpMHzsU7tvg9RGh9y1XXpop0GNln5S92rCY4APHyAKNyW+FnSHNvoALsZkSU oLi5H6jY9zfdnQW6TfuKCWvt7jZ0L83wvluBOKuLGQE8Am+tq5Bdavl4Z35Q=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=fRBXonyFkDQGk0srPOEARgU197M=; b=V0rEEXEbyOiqJQv4/Etm uVzs6qrM+FQ1aPU9XRfKIouxy3DcpteMWWFoGsdFw5vivKGlqNHD2p5OT0KdQd2r dUm53XYdaLClcX+HquC9aIzgChsmyOaMP8DM57Z7kkV0MK0OXa2rqFK0QsTrbKKL ioG6OweCUX0kHE9Cz7AUEr4=
X-ME-Sender: <xms:l_egWCe_ZquTY5g3sXGkHrXCsxshJOsA-RiUPSKI93ASY_6pG_9y_Q>
X-Sasl-enc: r0cHKAgzLqw94goTs44uAashWNpjmykH12M8wvFEJB0v 1486944151
Received: from aither.local (unknown []) by (Postfix) with ESMTPA id DBE0A7E2E6; Sun, 12 Feb 2017 19:02:30 -0500 (EST)
To: John C Klensin <>,
References: <> <2F562E0E75615D28FB8474A8@PSB>
From: Peter Saint-Andre <>
Message-ID: <>
Date: Sun, 12 Feb 2017 17:02:30 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <2F562E0E75615D28FB8474A8@PSB>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [precis] names and usernames
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 13 Feb 2017 00:02:34 -0000

Agreed. I'm trying to get input from relevant experts, because I 
strongly doubt that we have the relevant expertise within the WG.


On 2/12/17 4:43 PM, John C Klensin wrote:
> 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
> <> 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