From internet-drafts@ietf.org Fri Jan 13 13:56:18 2012 Return-Path: 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 BD69E1F0C4B; Fri, 13 Jan 2012 13:56:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4LsZIgvJMh5; Fri, 13 Jan 2012 13:56:18 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B59C1F0C38; Fri, 13 Jan 2012 13:56: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: 3.64p1 Message-ID: <20120113215618.8950.79377.idtracker@ietfa.amsl.com> Date: Fri, 13 Jan 2012 13:56:18 -0800 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-problem-statement-04.txt X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 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, 13 Jan 2012 21:56:18 -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 Interna= tionalized Strings Working Group of the IETF. Title : Stringprep Revision Problem Statement Author(s) : Marc Blanchet Andrew Sullivan Filename : draft-ietf-precis-problem-statement-04.txt Pages : 18 Date : 2012-01-13 Using Unicode codepoints in protocol strings that expect comparison with other strings requires preparation of the string that contains the Unicode codepoints. Internationalizing Domain Names in Applications (IDNA2003) defined and used Stringprep and Nameprep. Other protocols subsequently defined Stringprep profiles. A new approach different from Stringprep and Nameprep is used for a revision of IDNA2003 (called IDNA2008). Other Stringprep profiles need to be similarly updated or a replacement of Stringprep needs to be designed. This document outlines the issues to be faced by those designing a Stringprep replacement. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-precis-problem-statement-04.= txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-precis-problem-statement-04.t= xt From ajs@anvilwalrusden.com Fri Jan 13 13:57:25 2012 Return-Path: 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 2559C1F0C44 for ; Fri, 13 Jan 2012 13:57:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.662 X-Spam-Level: X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jIMIZ0y1fVtS for ; Fri, 13 Jan 2012 13:57:24 -0800 (PST) Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id A2D8A1F0C38 for ; Fri, 13 Jan 2012 13:57:24 -0800 (PST) Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 1812B1ECB41D for ; Fri, 13 Jan 2012 21:57:24 +0000 (UTC) Date: Fri, 13 Jan 2012 16:57:22 -0500 From: Andrew Sullivan To: precis@ietf.org Message-ID: <20120113215721.GJ7411@mail.yitter.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [precis] [internet-drafts@ietf.org: New Version Notification for draft-ietf-precis-problem-statement-04.txt] X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 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, 13 Jan 2012 21:57:25 -0000 This is a straightforward keepalive (or in this case, rejuvinate): no changes. A proper next release is in process. ----- Forwarded message from internet-drafts@ietf.org ----- Date: Fri, 13 Jan 2012 13:56:18 -0800 From: internet-drafts@ietf.org To: ajs@anvilwalrusden.com Cc: marc.blanchet@viagenie.ca, ajs@anvilwalrusden.com Subject: New Version Notification for draft-ietf-precis-problem-statement-04.txt A new version of I-D, draft-ietf-precis-problem-statement-04.txt has been successfully submitted by Andrew Sullivan and posted to the IETF repository. Filename: draft-ietf-precis-problem-statement Revision: 04 Title: Stringprep Revision Problem Statement Creation date: 2012-01-13 WG ID: precis Number of pages: 18 Abstract: Using Unicode codepoints in protocol strings that expect comparison with other strings requires preparation of the string that contains the Unicode codepoints. Internationalizing Domain Names in Applications (IDNA2003) defined and used Stringprep and Nameprep. Other protocols subsequently defined Stringprep profiles. A new approach different from Stringprep and Nameprep is used for a revision of IDNA2003 (called IDNA2008). Other Stringprep profiles need to be similarly updated or a replacement of Stringprep needs to be designed. This document outlines the issues to be faced by those designing a Stringprep replacement. The IETF Secretariat ----- End forwarded message ----- -- Andrew Sullivan ajs@anvilwalrusden.com From yoshiro.yoneya@jprs.co.jp Wed Jan 25 18:19:34 2012 Return-Path: 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 5367A21F8567; Wed, 25 Jan 2012 18:19:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U3Q7td4gScbq; Wed, 25 Jan 2012 18:19:33 -0800 (PST) Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) by ietfa.amsl.com (Postfix) with ESMTP id 41C4721F8566; Wed, 25 Jan 2012 18:19:33 -0800 (PST) Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id q0Q2JWRO002365; Thu, 26 Jan 2012 11:19:32 +0900 X-AuditID: ac120820-b7f826d000006983-08-4f20b83452b9 Received: from NOTE550 (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 26.96.27011.438B02F4; Thu, 26 Jan 2012 11:19:32 +0900 (JST) Date: Thu, 26 Jan 2012 11:19:31 +0900 From: Yoshiro YONEYA To: Message-Id: <20120126111931.b9ed97df.yoshiro.yoneya@jprs.co.jp> In-Reply-To: <8BC845943058D844ABFC73D2220D46650B552749@nics-mail.sbg.nic.at> References: <8BC845943058D844ABFC73D2220D46650B552749@nics-mail.sbg.nic.at> X-Mailer: Sylpheed 3.1.2 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDIsWRmVeSWpSXmKPExsWyRoiFT9dkh4K/wZJ3zBYd71axWuz6/ofV gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZEzbmFMyXrrh/o5WtgbFdrIuRk0NCwETi8/z3bBC2 mMSFe+vBbCGB44wSby/UgNgsAqoS307sYwSx2QQMJH4t+80EYosIiEqs/riKFcRmFhCWuPOk C6xGWMBcYurmTrA5vAL2Ei3HIXo5BXwkGm50QM33luidOwsozgG010Ji6zpLEJNXQFDi7w5h iIlaEg9/3WKBsOUltr+dwzyBkX8WQtUsJFWzkFQtYGRexSiTn5amW5yal1Kcm25gqFdSma+X VVBUrJcMojcxggOPQ2EH44xTBocYBTgYlXh4FZwV/IVYE8uKK3MPMUpyMCmJ8m7YChTiS8pP qcxILM6ILyrNSS0+xCjBwawkwitmD5TjTUmsrEotyodJSXOwKInzHj+7w09IID2xJDU7NbUg tQgmK8PBoSTBq7sdqFGwKDU9tSItM6cEIc3EwQkynAdoeChIDW9xQWJucWY6RP4Uo6SUOK8y SEIAJJFRmgfX+4pRHOgFYV5bkCwPMInAdb0CGsgENHCprjzIwJJEhJRUA+PmF59UjqT/8l+9 MUPx5AkbjZK4HP2vVRXT5qp/7V2uOdNZXuvhlr8Jua/Vkjw0Jigai0ryOiY8Wm4Qy51rXvdy Q0jyoe9S7nJ3dPaLlr62jqxeb/V6z09dV/Hrs2R+q+Rt81T/MMn6QO6fdUu/26xiNbrHouGl tSk+feEEV+65lRbuf7zP7VFiKc5INNRiLipOBAB5FFk93wIAAA== Cc: precis@ietf.org Subject: Re: [precis] Internationalization & Comparison, 2nd try X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.12 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, 26 Jan 2012 02:19:34 -0000 Hi, IETF precis WG (CC'ed) is discussing comparison of internationalized strings. Would you please see if precis framework (work on progress) is applicable? Regards, -- Yoshiro YONEYA On Wed, 25 Jan 2012 15:35:39 +0100 Alexander Mayrhofer wrote: > Based on the discussions during last week's Design Team call, i have > drafted a new revision of the "Internationalization" Text - see below. I > still haven't found a proper headline for the "comparison & case > sensititivity" section, suggestions welcome. > > Thanks to Ken for the valuable comments on my initial text - very > useful. > > Generally, comments on the text are very much appreciated. > > -- snip -- > > X. Internationalization > ------------------------ > > X.1. Character Encoding > ---------------------------- > > If elements contain non-ASCII characters, the UTF-8 [RFC3629] character > encoding MUST be used. If the transport protocol allows for explicit > declaration of the character encoding used, clients and servers SHOULD > explicitely declare the content to be UTF-8, but MAY in turn assume that > content that is received without such declaration is using UTF-8. > > X.2. Language identification > --------------------------------- > > Where messages in human-readable languages are used in the protocol, > those messages SHOULD be tagged according to RFC 4646, and the transport > protocol MUST support a respective mechanism to transmit such tags > together with those human readable messages. If absent, the language of > the message defaults to "en" (English). > > X.3. Time zones > ------------------- > > Date and time attribute values MUST be represented in Universal > Coordinated Time (UTC) using the Gregorian calendar. The actual > date/time format > used MUST be specified by the respective transport protocol. > > Y. Comparison Operations > ----------------------------- > > The protocol contains two types of elements. The first type, called > "blobs" for the purpose of this document, contains data that is moved by > means of that protocol, but is neither used to identifier objects, or to > refer between objects. The other type is called "identifier", and is > either used to address an object, or to refer between objects. > > The following elements are "Identifiers": > > * rant > * rar > * dgName > * rrName > * rgName > * egrRteName > > All other elements contained in the protocol fall under the "blobs" > category. For "identifiers", the following rules apply: > > * Identifiers are case insensitive, and MUST use Unicode Normalization > Form C (NFC) in comparison and mapping operations > ..* Characters allowed in Identifierst MUST consist of Characters > exclusively from those character classes: TODO > * The Registry MUST store such identifiers in their lower case > mapping, and MUST correctly map upper case representations of that > identifier to their lower case equivalent in comparison operations. > ..* Clients SHOULD lowercase such identifiers before sending them to the > Registry > > If "blob" type elements are ever to be compared, byte-wise comparison > MUST be used. > _______________________________________________ > drinks mailing list > drinks@ietf.org > https://www.ietf.org/mailman/listinfo/drinks > >