From stpeter@stpeter.im Tue Dec 3 05:35:09 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24E551AE13B for ; Tue, 3 Dec 2013 05:35:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 xKz9xuDnssKG for ; Tue, 3 Dec 2013 05:35:05 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 6F31F1AE114 for ; Tue, 3 Dec 2013 05:35:05 -0800 (PST) Received: from ergon.local (unknown [24.8.184.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C47EA4032B; Tue, 3 Dec 2013 06:35:01 -0700 (MST) Message-ID: <529DDE07.5090000@stpeter.im> Date: Tue, 03 Dec 2013 06:35:03 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Takahiro Nemoto References: <528EC808.9010300@stpeter.im> <528F7133.3000905@babelmonkeys.de> <528FD866.6080402@stpeter.im> <56B02476-036C-4A39-9971-163D60B27ED7@kmd.keio.ac.jp> In-Reply-To: <56B02476-036C-4A39-9971-163D60B27ED7@kmd.keio.ac.jp> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: precis@ietf.org Subject: Re: [precis] framework-12 X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 13:35:09 -0000 On 11/26/13 10:53 AM, Takahiro Nemoto wrote: > On 2013/11/23, at 7:19, Peter Saint-Andre wrote: >> On 11/22/13 7:58 AM, Florian Zeitz wrote: >>> On 22.11.2013 03:57, Peter Saint-Andre wrote: >>>> In the interest of easing further reviews during WGLC (and because >>>> I will be offline next week), I shall submit version -12 of the >>>> framework in a few minutes. >>>> >>>> Peter >>>> >>> From looking at the diff this seems good. Thank you for your work. >>> >>> Only remark I still have is that both IdentifierClass and >>> FreeformClass are missing OldHangulJamo in the list of disallowed >>> categories, which is inconsistent with the algorithm. >> >> You are right! I've missed that error all this time... >> >> Peter > I think the framework-12 looks good except the point about OldHangleJamo. After the WGLC call ends, I will publish -13 containing that fix. > BTW, I have compared the codepoint table to my codepoint table, > which is generated by my code, by using diff. > Codepoint values in the framework-12 and codepoint values in my table are all the same :) Excellent! Thank you for checking. Peter -- Peter Saint-Andre https://stpeter.im/ From internet-drafts@ietf.org Tue Dec 3 18:01:21 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC241AE010; Tue, 3 Dec 2013 18:01:21 -0800 (PST) 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] autolearn=ham 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 0b98dWvpwRTQ; Tue, 3 Dec 2013 18:01:19 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DAF01AE160; Tue, 3 Dec 2013 18:01:18 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131204020118.24372.32702.idtracker@ietfa.amsl.com> Date: Tue, 03 Dec 2013 18:01:18 -0800 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-nickname-08.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 02:01:21 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Preparation and Comparison of Internation= alized Strings Working Group of the IETF. Title : Preparation and Comparison of Nicknames Author(s) : Peter Saint-Andre Filename : draft-ietf-precis-nickname-08.txt Pages : 9 Date : 2013-12-03 Abstract: This document describes how to prepare and compare Unicode strings representing nicknames, primarily for use within textual chatrooms. This profile is intended to be used by messaging and text conferencing technologies such as the Extensible Messaging and Presence Protocol (XMPP), the Message Session Relay Protocol (MSRP), and Centralized Conferencing (XCON). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-precis-nickname There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-precis-nickname-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-nickname-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Tue Dec 3 18:01:34 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B78181AE017; Tue, 3 Dec 2013 18:01:34 -0800 (PST) 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] autolearn=ham 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 F1a4DY5Kf6BY; Tue, 3 Dec 2013 18:01:33 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 404081AE173; Tue, 3 Dec 2013 18:01:32 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131204020132.23626.78917.idtracker@ietfa.amsl.com> Date: Tue, 03 Dec 2013 18:01:32 -0800 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-saslprepbis-06.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 02:01:35 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Preparation and Comparison of Internation= alized Strings Working Group of the IETF. Title : Preparation and Comparison of Internationalized Strings = Representing Usernames and Passwords Author(s) : Peter Saint-Andre Alexey Melnikov Filename : draft-ietf-precis-saslprepbis-06.txt Pages : 18 Date : 2013-12-03 Abstract: This document describes methods for handling Unicode strings representing usernames and passwords. This document obsoletes RFC 4013. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-precis-saslprepbis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-precis-saslprepbis-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-saslprepbis-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From stpeter@stpeter.im Tue Dec 3 18:04:23 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8031AE16E for ; Tue, 3 Dec 2013 18:04:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 zptWwh2F-XyO for ; Tue, 3 Dec 2013 18:04:21 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E64B31AE017 for ; Tue, 3 Dec 2013 18:04:20 -0800 (PST) Received: from ergon.local (unknown [24.8.184.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7F4B04032B; Tue, 3 Dec 2013 19:04:17 -0700 (MST) Message-ID: <529E8DA0.2080103@stpeter.im> Date: Tue, 03 Dec 2013 19:04:16 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: "precis@ietf.org" X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [precis] updated nickname and saslprepbis I-Ds X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 02:04:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've updated the nickname and saslprepbis I-Ds to include some examples of strings that match (or don't match) the rules for each profile, as I have previously done for 6122bis in the XMPP WG. Hopefully folks find these examples useful. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSno2gAAoJEOoGpJErxa2pXpEP/iTcQSzhB2bZ+a2GvvZfH6j/ Mf5/jEG/OPxmNup68X2FP1nh6HRFBiU35h1ybHHLz9oL/9ujoSgco483+1bzY81m kxzpd9mwyxrZJElOQ1jtFh14FjPo5TB9bRwPXOHjZYuGc9a7MkOLf/hEmC3nml0i 6sCsyZdxG+dhiK2EXCnV2yFt08yxEJlZh5d/GfHT2ue85xAAJsAgimFvOZ0L1quN 8Z6ZhTnLK6FjZgT/4ZSJNxoq811OP4TStSquFS9X0TpmUbW/Pmw6Ra3+UkvFPnSl Jh0NyEu0sJSq9Z9haIDIvmiraxO8NnwzJxh4msSTAxeVP92sw1rwRzfyd39fsKE2 wMOwaOEBbNhT84O3jcBAFkSKDYuFN4KVkTFx56EHZy+zoM5RBepjafi2VzKsvGcH yXJez3V53PF9J3baIDI52UcMo/JsifobeNcjr788qiKV00ZQbJCa3gmRbjSvgcLw SFk2MK7RzjuNas49MI8XhBBynSctL2OlevSMgBZ/cmxdBdfeAa+tyuxcSQTKbIOQ MZaaveZmx3MX6ME0kMVtDvs/1mlJUS+vChzZuOcDPaZ1SuKjskXDWyYDD/AWlrhV g7oi5N60kDherJrmFLQK8EcwuRnwj77bR4kHFpqWXNbWrvOpBz+u6dz+3bElScKz 9xQ33Wbxt6Rpt73X1mqa =TgPG -----END PGP SIGNATURE----- From stpeter@stpeter.im Wed Dec 4 13:18:02 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 778661AD94A for ; Wed, 4 Dec 2013 13:18:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.903 X-Spam-Level: X-Spam-Status: No, score=-3.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 TNtYRexWoiwR for ; Wed, 4 Dec 2013 13:18:00 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 283091ADFFF for ; Wed, 4 Dec 2013 13:18:00 -0800 (PST) Received: from sjc-vpn2-300.cisco.com (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 3D61740332; Wed, 4 Dec 2013 14:17:56 -0700 (MST) Message-ID: <529F9C02.5090402@stpeter.im> Date: Wed, 04 Dec 2013 14:17:54 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: "precis@ietf.org" X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [precis] terminology question X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 21:18:02 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When talking about mapping of fullwidth and halfwidth characters (e.g., U+FF01 to U+0021), RFC 5895 uses the term "decomposition mappings": 2. Fullwidth and halfwidth characters (those defined with Decomposition Types and ) are mapped to their decomposition mappings as shown in the Unicode character database. In the PRECIS documents, we somehow used the term "decomposition equivalents": ... width mapping is in general RECOMMENDED because allowing fullwidth and halfwidth characters to remain unmapped to their decomposition equivalents would violate the principle of least user surprise. The Unicode Standard seems to use the term "compatibility variants", e.g., consider the following text in Chapter 5: Identifying one character as a compatibility variant of another character (or sequence of characters) suggests that in many circumstances the first can be remapped to the second without the loss of any textual information other than formatting and layout. and: Fullwidth variants of the ASCII digits are simply compatibility variants of regular digits and should be treated as regular Western digits. See also Chapter 2: Compatibility variants are a subset of compatibility characters, and have the further characteristic that they represent variants of existing, ordinary, Unicode characters. For example, compatibility variants might represent various presentation or styled forms of basic letters: superscript or subscript forms, variant glyph shapes, or vertical presentation forms. They also include halfwidth or fullwidth characters from East Asian character encoding standards, Arabic contextual form glyphs from preexisting Arabic code pages, Arabic ligatures and ligatures from other scripts, and so on. Compatibility variants also include CJK compatibility ideographs, many of which are minor glyph variants of an encoded unified CJK ideograph. It seems to me that following the Unicode Standard here would be best, unless we have a good reason not to do so. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSn5wCAAoJEOoGpJErxa2p2uoP/jKibubSA3GDI/FwuGVL3UuQ KVIhqSWphZ4qbPJdBfRq8zmApYYtA+aXgxROg2UYDgMXIOihYKNSwoHpR8QTrilz Xi4+KHaBUu3Ba3aRnkmC51YLn664LGJVGyhJvSxv7KQmJwO66MmXIJ1uEDSFHtp4 BJqRF6/Ug94cZgAFb8dy9m4Eb/hvh4aZrzuSYrEpANvuebCTo+cp+I8Rm9sqFUXw taRvxhOhbYGdR6nofMdwdX2wO/vH7/HcSXVhXJNuKdo93UXXWd2bjW5vsGH7I+VC 2BUs3H69tx0B3EkR4zFl9I/cZITkwbni2+e15YbIasHEZ/r+X3okHBza0bZxZ2qC 1uN4Nko2RPwssShE8GI6gFpFKNtowQjE494PmKAQDbGGkmAybzlD8qrD5xG5vNuv NQxKEBOG4wrP5EPdTKLDIV4gN51dl5elSi/i7tnXuREq5aVqXtPLQcwGqBujyPHl ABIuugVEQYAZNKnj2wrvIcjtyP7nTm67GixRkZzwM6yiaxrgRY6EAqS7WPXjcQ6s WKYBz6Zt2QqNbi8PIPOSgBLoUIyuitjgUO7WE5oEAoLjC4ijpHrLx3PnSrmTzupj Bdp2lRMA235rTOug7sxJrorVAFGxHzLIY0+sKAJRp1gGwd+1bfSlKcy1P2ai2cor sTVvKftf99TewlgRKz0j =tLkL -----END PGP SIGNATURE----- From derhoermi@gmx.net Wed Dec 4 17:45:08 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0FE31AE2EE for ; Wed, 4 Dec 2013 17:45:08 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham 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 qaoxVzoCPm3p for ; Wed, 4 Dec 2013 17:45:07 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id DF71E1AE2D8 for ; Wed, 4 Dec 2013 17:45:06 -0800 (PST) Received: from netb.Speedport_W_700V ([84.180.230.94]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0MQzoI-1WAtV23Jsc-00ULZ8 for ; Thu, 05 Dec 2013 02:45:03 +0100 From: Bjoern Hoehrmann To: Peter Saint-Andre Date: Thu, 05 Dec 2013 02:45:04 +0100 Message-ID: <3gmv99lpndbkfar5adlk1s0r3bt5khlhg2@hive.bjoern.hoehrmann.de> References: <529F9C02.5090402@stpeter.im> In-Reply-To: <529F9C02.5090402@stpeter.im> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:KoJQqRDMBpQAqkCneFGisMUYadqAw1Pb9lanaH7jUdXlEq6DhOL jZSq+oREfC5pHG4eVUcy6mudcfAXCiNzBoZzjlNmwV8Ft9yB/MO/+GS3uBtmDkgoF48wA4g uYIl4hC9xVTrmlxmhkgtNllz7KYHLbzruebwzdFGuZKgXpRKxXAlBA+U7dmjUgkTw06Emmw XoGanyhEClaPH3a/FlKsg== Cc: "precis@ietf.org" Subject: Re: [precis] terminology question X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 01:45:08 -0000 * Peter Saint-Andre wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >When talking about mapping of fullwidth and halfwidth characters >(e.g., U+FF01 to U+0021), RFC 5895 uses the term "decomposition mappings": > > 2. Fullwidth and halfwidth characters (those defined with > Decomposition Types and ) are mapped to their > decomposition mappings as shown in the Unicode character > database. > >In the PRECIS documents, we somehow used the term "decomposition >equivalents": > > ... width mapping > is in general RECOMMENDED because allowing fullwidth and halfwidth > characters to remain unmapped to their decomposition equivalents > would violate the principle of least user surprise. > >The Unicode Standard seems to use the term "compatibility variants", >e.g., consider the following text in Chapter 5: Quick usability check: if the "decomposition mapping" of X is `NFD(X)` then the Unicode term is the least obvious and should be avoided. If it's something else entirely, both "decomposition" terms are bad. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ From florob@babelmonkeys.de Wed Dec 4 18:17:03 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8A01ADFFC for ; Wed, 4 Dec 2013 18:17:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.551 X-Spam-Level: X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.001] autolearn=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 R_IQeUycUNcr for ; Wed, 4 Dec 2013 18:17:02 -0800 (PST) Received: from babelmonkeys.de (babelmonkeys.de [IPv6:2a02:d40:3:1:10a1:5eff:fe52:509]) by ietfa.amsl.com (Postfix) with ESMTP id EC3211AE008 for ; Wed, 4 Dec 2013 18:17:01 -0800 (PST) Received: from xdsl-84-44-143-129.netcologne.de ([84.44.143.129] helo=[192.168.0.140]) by babelmonkeys.de with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1VoOXU-00059p-VA for precis@ietf.org; Thu, 05 Dec 2013 03:19:41 +0100 Message-ID: <529FE214.9080601@babelmonkeys.de> Date: Thu, 05 Dec 2013 03:16:52 +0100 From: Florian Zeitz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: precis@ietf.org References: <529F9C02.5090402@stpeter.im> <3gmv99lpndbkfar5adlk1s0r3bt5khlhg2@hive.bjoern.hoehrmann.de> In-Reply-To: <3gmv99lpndbkfar5adlk1s0r3bt5khlhg2@hive.bjoern.hoehrmann.de> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [precis] terminology question X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 02:17:03 -0000 On 05.12.2013 02:45, Bjoern Hoehrmann wrote: > * Peter Saint-Andre wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> When talking about mapping of fullwidth and halfwidth characters >> (e.g., U+FF01 to U+0021), RFC 5895 uses the term "decomposition mappings": >> >> 2. Fullwidth and halfwidth characters (those defined with >> Decomposition Types and ) are mapped to their >> decomposition mappings as shown in the Unicode character >> database. >> >> In the PRECIS documents, we somehow used the term "decomposition >> equivalents": >> >> ... width mapping >> is in general RECOMMENDED because allowing fullwidth and halfwidth >> characters to remain unmapped to their decomposition equivalents >> would violate the principle of least user surprise. >> >> The Unicode Standard seems to use the term "compatibility variants", >> e.g., consider the following text in Chapter 5: > > Quick usability check: if the "decomposition mapping" of X is `NFD(X)` > then the Unicode term is the least obvious and should be avoided. If > it's something else entirely, both "decomposition" terms are bad. > The terminology used in the RFC 5895 quote is definitely correct. However, for the PRECIS documents we might have to go on a case by case basis. There are (AFAIK) generally these different concepts: * "decomposition mapping": This is defined in the UnicodeData.txt file, and maps a single codepoint, to one or multiple codepoints (canonical mapping, and compatibility mapping are subtypes of this) * "(canonical|compatibility) decomposition": This is NFD() and NFKD() respectively. Notably these are defined on strings, not on single codepoints * "compatibility variants": These are closely related to the "decomposition mappings", but most importantly always just a single character/codepoint. For an exact definition Section 2.3 of Unicode is helpful. Full-/halfwidth characters do fall into this category, but it is not more correct to use this term than referring to the "decomposition mapping" property IMHO. Regards, Florian From derhoermi@gmx.net Thu Dec 5 06:37:14 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1A91AE028 for ; Thu, 5 Dec 2013 06:37:14 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham 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 BcAW_1Ig9vkD for ; Thu, 5 Dec 2013 06:37:12 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8CC1ADFD3 for ; Thu, 5 Dec 2013 06:37:12 -0800 (PST) Received: from netb.Speedport_W_700V ([91.35.7.188]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0LvUwp-1VOyA43043-010dQG for ; Thu, 05 Dec 2013 15:37:08 +0100 From: Bjoern Hoehrmann To: Florian Zeitz Date: Thu, 05 Dec 2013 15:37:10 +0100 Message-ID: <5n31a9dd3i9u1csu5tkvh7rkeak08mq215@hive.bjoern.hoehrmann.de> References: <529F9C02.5090402@stpeter.im> <3gmv99lpndbkfar5adlk1s0r3bt5khlhg2@hive.bjoern.hoehrmann.de> <529FE214.9080601@babelmonkeys.de> In-Reply-To: <529FE214.9080601@babelmonkeys.de> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:nxg1smwBW0KKG/85hE2CsTdtFQAfF+mWSzpi5/zQeofwWBJBNXH I+1r3Bot6giaAf621n3lRtLy+3j3NY0WEECd93+Gw3T//ZII01EvUJq3Uz3DNW4hMVA9/1I vAyWzJtY4XDLkcwCDmtk17Pd3iHaGFWj9EJT33vWHu2QGbuXFfDhS4WWwTfeKesF2o40dIA F2EhDMnPq/xbhKMqlthtg== Cc: precis@ietf.org Subject: Re: [precis] terminology question X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 14:37:14 -0000 * Florian Zeitz wrote: >The terminology used in the RFC 5895 quote is definitely correct. >However, for the PRECIS documents we might have to go on a case by case >basis. > >There are (AFAIK) generally these different concepts: >* "decomposition mapping": This is defined in the UnicodeData.txt > file, and maps a single codepoint, to one or multiple codepoints > (canonical mapping, and compatibility mapping are subtypes of this) Right, the Unicode database property name is `Decomposition_Mapping`. In UAX15 long forms like "canonical Decomposition_Mapping values" are used. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ From stpeter@stpeter.im Thu Dec 5 08:58:34 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB151AE0C9 for ; Thu, 5 Dec 2013 08:58:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 gtsJSnxppfbN for ; Thu, 5 Dec 2013 08:58:32 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 995761AE0A7 for ; Thu, 5 Dec 2013 08:58:32 -0800 (PST) Received: from ergon.local (unknown [64.101.72.104]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 538E840332; Thu, 5 Dec 2013 09:58:28 -0700 (MST) Message-ID: <52A0B0B3.8060508@stpeter.im> Date: Thu, 05 Dec 2013 09:58:27 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Bjoern Hoehrmann , Florian Zeitz References: <529F9C02.5090402@stpeter.im> <3gmv99lpndbkfar5adlk1s0r3bt5khlhg2@hive.bjoern.hoehrmann.de> <529FE214.9080601@babelmonkeys.de> <5n31a9dd3i9u1csu5tkvh7rkeak08mq215@hive.bjoern.hoehrmann.de> In-Reply-To: <5n31a9dd3i9u1csu5tkvh7rkeak08mq215@hive.bjoern.hoehrmann.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: precis@ietf.org Subject: Re: [precis] terminology question X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 16:58:34 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/5/13 7:37 AM, Bjoern Hoehrmann wrote: > * Florian Zeitz wrote: >> The terminology used in the RFC 5895 quote is definitely >> correct. However, for the PRECIS documents we might have to go on >> a case by case basis. >> >> There are (AFAIK) generally these different concepts: * >> "decomposition mapping": This is defined in the UnicodeData.txt >> file, and maps a single codepoint, to one or multiple codepoints >> (canonical mapping, and compatibility mapping are subtypes of >> this) > > Right, the Unicode database property name is > `Decomposition_Mapping`. In UAX15 long forms like "canonical > Decomposition_Mapping values" are used. You are right. Sentences like "map to decomposition mappings" sound ugly, but let's use the correct term. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSoLCyAAoJEOoGpJErxa2p+kgP/2nwEgizuwCw+kjt1yNUNgmK ztW+Ro996GseY7T6Dcx1cOQAecIX2J6eXXcun+2NUFmBwTTX9UTuDByswLV4oFeF YEbSS63NZo4BWQrXt3jK2ny5Z8dVEQhcvmYUHcklGzoMi8rT/elL2Z/qNBVoXAMl CUFWOKf2p+PuHTnr6ulQGKNRdQ2lxbhP3cPIffna0RMOtGV/hHze55pTvXoQk6z2 SjH/VyYGZqs4+ZlROtPsVzfQt3LmUo6uqqNw5VHaOYrSTr4bVPvP1OyP81WvxVSn qVTiRAPBQqfCG6utV5moqrnzEjdDq/1ZlznYV8I/S8Sc6gICMmzRj4Sq3TlNeSbl LnRxVILxAAvtNbLt/igcsOaUA/XnwqfSw6FQO5OVUawl/fVHFaZONChy79kWOibN YcSw0SuEpSX19nLae45xVnpZu7GMZyrJCC72k0qhfJp+MEQDVOgrk5m7dA+oBf61 T5Igs+wL2hfpVFRF5DWDkac2r6GOP99CHm8ijV1C99ooXafe3TU1aXo6L+0v+CRL 3t5XFji18HPLnrdZ2kNPX8jqUVPZkNOcvAKubp4b1DfAmo5ZfqcsTmYp3RFtyVB9 NhRg9DA8tiNhF2p5jDCDt024/Wqpda5cwHOrrshKpPkmrceIWTdPA3iatOoxeVtd AIpx6NTZHQ+Sd18IBkiG =denZ -----END PGP SIGNATURE----- From internet-drafts@ietf.org Thu Dec 5 19:42:41 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 410071AE27E; Thu, 5 Dec 2013 19:42:41 -0800 (PST) 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] autolearn=ham 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 4KWo4tSs9ZUu; Thu, 5 Dec 2013 19:42:39 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E71E1AE282; Thu, 5 Dec 2013 19:42:38 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131206034238.7372.76785.idtracker@ietfa.amsl.com> Date: Thu, 05 Dec 2013 19:42:38 -0800 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-framework-13.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Dec 2013 03:42:41 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Preparation and Comparison of Internation= alized Strings Working Group of the IETF. Title : PRECIS Framework: Preparation and Comparison of Internat= ionalized Strings in Application Protocols Author(s) : Peter Saint-Andre Marc Blanchet Filename : draft-ietf-precis-framework-13.txt Pages : 63 Date : 2013-12-05 Abstract: Application protocols using Unicode characters in protocol strings need to properly prepare such strings in order to perform valid comparison operations (e.g., for purposes of authentication or authorization). This document defines a framework enabling application protocols to perform the preparation and comparison of internationalized strings ("PRECIS") in a way that depends on the properties of Unicode characters and thus is agile with respect to versions of Unicode. As a result, this framework provides a more sustainable approach to the handling of internationalized strings than the previous framework, known as Stringprep (RFC 3454). This document obsoletes RFC 3454. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-precis-framework There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-precis-framework-13 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-framework-13 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From stpeter@stpeter.im Thu Dec 5 19:46:05 2013 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77BB31AE286 for ; Thu, 5 Dec 2013 19:46:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 EKCvctkfnD5L for ; Thu, 5 Dec 2013 19:46:03 -0800 (PST) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B22FC1AE282 for ; Thu, 5 Dec 2013 19:46:03 -0800 (PST) Received: from ergon.local (unknown [24.8.184.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 14DC740332; Thu, 5 Dec 2013 20:45:59 -0700 (MST) Message-ID: <52A14877.6050103@stpeter.im> Date: Thu, 05 Dec 2013 20:45:59 -0700 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: precis@ietf.org References: <20131206034238.7372.76785.idtracker@ietfa.amsl.com> In-Reply-To: <20131206034238.7372.76785.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [precis] I-D Action: draft-ietf-precis-framework-13.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Dec 2013 03:46:05 -0000 Some small fixes as discussed on the list. I now consider this ready for IETF Last Call. On 12/5/13 8:42 PM, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Preparation and Comparison of Internationalized Strings Working Group of the IETF. > > Title : PRECIS Framework: Preparation and Comparison of Internationalized Strings in Application Protocols > Author(s) : Peter Saint-Andre > Marc Blanchet > Filename : draft-ietf-precis-framework-13.txt > Pages : 63 > Date : 2013-12-05 > > Abstract: > Application protocols using Unicode characters in protocol strings > need to properly prepare such strings in order to perform valid > comparison operations (e.g., for purposes of authentication or > authorization). This document defines a framework enabling > application protocols to perform the preparation and comparison of > internationalized strings ("PRECIS") in a way that depends on the > properties of Unicode characters and thus is agile with respect to > versions of Unicode. As a result, this framework provides a more > sustainable approach to the handling of internationalized strings > than the previous framework, known as Stringprep (RFC 3454). This > document obsoletes RFC 3454. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-precis-framework > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-precis-framework-13 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-precis-framework-13 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis >