Re: [precis] PRECIS bidi rule for usernames

Sam Whited <sam@samwhited.com> Mon, 10 October 2016 04:27 UTC

Return-Path: <sam@samwhited.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 BB7651295D8 for <precis@ietfa.amsl.com>; Sun, 9 Oct 2016 21:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=samwhited.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 7eQ9SSkqOY4n for <precis@ietfa.amsl.com>; Sun, 9 Oct 2016 21:27:23 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (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 4675F129452 for <precis@ietf.org>; Sun, 9 Oct 2016 21:27:23 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id n189so90015131qke.0 for <precis@ietf.org>; Sun, 09 Oct 2016 21:27:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samwhited.com; s=swgoo; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=7YDoeoYYg68P7HShDgvmAP9Yh7odpd01SDv/ioql2RM=; b=znkzHSIXj9YTvyQmO1BJOsS2yYq2x8CWjyxZ9+9Zp4PrIMVd8t2tvaBl+ZpmZB0ITO oInNiXtwzP+X5Xaq47PYV2Wog2L8sZnhxRKxSCHC0QFcmzEZkwMXIkwHKJVXChLBMWck lr2VyYRN0FJKX1aydSVxrPu47lKD9dRfIF7Ng=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=7YDoeoYYg68P7HShDgvmAP9Yh7odpd01SDv/ioql2RM=; b=L62PVtb23Uwg7Njh3NDnM2FabGMt0rzUnkpntKTd0vvDd5rKCLLvAp3Ju287GLChXI R6UzRrbdt1/Gw0Md5uJjRIejLiby804qcFMqMocBvlBBF7TqQnt3ZTp3Vm077IlCrDs3 7qbFD1oF6DZN1fVo7ZWlPi+AWHsZO7TPGolFpCINEXhU06kcbAMlsVKeHX/lzkocFLeC n4K0+hvnzqD3EIUX8n0VmyAx4u4H6/9uPS2mIuvSMTVrJU1OS5EXK9DCznmF4Bh19vgb ACV6GNklFhCr+25Ed7CIKFPQEkRJFpXf9u9nheGtetqDHcqya9tsJ79RSTwIAigqPxQq LSzw==
X-Gm-Message-State: AA6/9RmevF/2noSZfs7Il+ssJXP5AB3pZKQ6dmtpM/dyG0QqT1Au4+pqTyefakS20EM8mhz7ZzibKdDd0/ugMw==
X-Received: by 10.55.188.193 with SMTP id m184mr29059006qkf.129.1476073642338; Sun, 09 Oct 2016 21:27:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.15.166 with HTTP; Sun, 9 Oct 2016 21:26:41 -0700 (PDT)
X-Originating-IP: [2605:a601:1166:8b00:b774:1488:5007:efa9]
In-Reply-To: <c071125b-91d0-377b-3232-e803edd06c05@stpeter.im>
References: <CAHVjMKH6BGhhOoCC=1yv1y5njoq0jobbBPS6eWpB2vwtibASFA@mail.gmail.com> <CAHbk4RK4hVJzVWft9Vzn4Xfi+J_troCMDQi6eCHgFzCSaoDWiw@mail.gmail.com> <c071125b-91d0-377b-3232-e803edd06c05@stpeter.im>
From: Sam Whited <sam@samwhited.com>
Date: Sun, 9 Oct 2016 23:26:41 -0500
Message-ID: <CAHbk4R+sQdtU-BOgd1scmemdb10q8J3YUabG9WR-AW7k7f=u=g@mail.gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/5OU-V2qS8pO-_sWkuMG1qMtx_-g>
Cc: precis@ietf.org
Subject: Re: [precis] PRECIS bidi rule for 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: Mon, 10 Oct 2016 04:27:25 -0000

On Sun, Oct 9, 2016 at 10:12 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> There are plenty of RTL punctuation characters (e.g., U+05BE), and those are
> allowed in RTL strings (even as the last character). RFC 5893 says that an
> RTL string must not have an LTR character at the end, with the result that
> an RTL string cannot end in "."; this helps to prevent confusion in the
> typical presentation of domain names (which is the target use case for RFC
> 5893).

That makes sense; thanks for the clarification.

—Sam



-- 
Sam Whited
pub 4096R/54083AE104EA7AD3