From root@core3.amsl.com Fri Jun 11 12:00:02 2010 Return-Path: X-Original-To: precis@ietf.org Delivered-To: precis@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 1B84F3A6991; Fri, 11 Jun 2010 12:00:02 -0700 (PDT) From: IESG Secretary To: ietf-announce@ietf.org Cc: Marc.Blanchet@viagenie.ca, yoshiro.yoneya@jprs.co.jp, precis@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20100611190002.1B84F3A6991@core3.amsl.com> Date: Fri, 11 Jun 2010 12:00:02 -0700 (PDT) Subject: [precis] WG Action: Preparation and Comparison of Internationalized Strings (precis) X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.9 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, 11 Jun 2010 19:00:02 -0000 A new IETF working group has been formed in the Applications Area. For additional information, please contact the Area Directors or the WG Chairs. Preparation and Comparison of Internationalized Strings (precis) --------------------------------------------------- Current Status: Active Working Group Chairs: Marc Blanchet Yoshiro Yoneya Applications Area Directors: Alexey Melnikov Peter Saint-Andre Applications Area Advisor: Peter Saint-Andre Mailing Lists: General Discussion: precis@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/precis Archive: http://www.ietf.org/mail-archive/web/precis/ Description of Working Group: Problem Statement The use of non-ASCII strings in Internet protocols requires additional processing to be handled properly. As part of the Internationalized Domain Names (idn) work in 2003, a method for preparation and comparison of internationalized strings was defined and generalized to be re-used by other protocols. This "stringprep" method [RFC 3454] defines the overall framework whereas specific protocols define their own profiles. Known existing IETF profiles are: - The Nameprep profile [RFC 3490] for use in Internationalized Domain Names in Applications (IDNA) - The iSCSI profile [RFC 3722] for use in Internet Small Computer Systems Interface (iSCSI) Names - The Nodeprep and Resourceprep profiles [RFC 3920] for use in the Extensible Messaging and Presence Protocol (XMPP) - The Policy MIB profile [RFC 4011] for use in the Simple Network Management Protocol (SNMP) - The SASLprep profile [RFC 4013] for use in the Simple Authentication and Security Layer (SASL) - The trace profile [RFC 4505] for use with the SASL ANONYMOUS mechanism - The LDAP profile (RFC 4518] for use with LDAP The IAB completed a review of IDN and made recommendations for change [RFC 4690], which triggered a new version of the IDNA protocol called IDNA2008. Whereas IDNA2003 was tied to Unicode 3.2 via stringprep, IDNA2008 does not use the stringprep method, but instead uses an algorithm based on the properties of Unicode characters, which makes it agile to the Unicode database version. The protocols using stringprep need Unicode version agility and therefore need to investigate whether and how to move away from the current stringprep approach, with the associated challenges of backward compatibility and migration. Objectives The goal of this group is to assess whether a new method based on the new IDNA2008 algorithmic approach is the appropriate path forward for existing stringprep protocols as well as for other application protocols requiring internationalized strings. The group will evaluate if a new generalized framework based on the algorithmic approach is appropriate and, if so, define it. The group will analyze existing stringprep profiles and will do one of the following with regard to each profile: 1. Develop a replacement for the profile in close collaboration with the related protocol working group (if any). 2. Collaborate with another active working group which will be developing the new profile as part of its charter. 3. Advise the authors of profiles for which there is no active working group how to proceed. The group will also define a set of best current practices for preparation and comparison of internationalized strings. Because the framework, profile replacements, and guidelines are very much interrelated, work on them will proceed in parallel as much as possible. Based on normal working group processes for achieving consensus, the group will attempt to gather input from, and may provide advice to, "customers" working on IETF technologies other than those listed above, including but not limited to Network Address Identifiers (RFC 4282) and Kerberos (RFC 4120). However, the group will prioritize work on the listed stringprep profiles higher than work on other technologies, and will formally accept additional tasks as official milestones only after rechartering. In completing its tasks, the working group should collaborate with other teams involved in internationalized identifiers, such as the IETF's IRI and EAI working groups as well as other relevant standards development organizations (e.g., the Unicode Consortium). Deliverables 1. Problem statement / analysis of existing stringprep profiles (Informational). 2. Possible new framework to replace stringprep (Standards Track). 3. Possible replacements for the existing IETF stringprep profiles as listed earlier in this charter (Standards Track). 4. String preparation and comparison guidelines (BCP). Goals and Milestones Aug 2010 - Accept problem statement document as a WG item Nov 2010 - Accept framework document as a WG item Nov 2010 - Accept new profile documents as WG items Dec 2010 - Start Working Group Last Call on problem statement document Jan 2011 - Submit problem statement document to the IESG Jan 2011 - Accept guidelines document as a WG item May 2011 - Start Working Group Last Call on framework document May 2011 - Start Working Group Last Call on new profile documents Jun 2011 - Submit framework document to the IESG Jun 2011 - Submit new profile documents to the IESG Jun 2011 - Start Working Group Last Call on guidelines document Aug 2011 - Submit guidelines document to the IESG From marc.blanchet@viagenie.ca Fri Jun 11 15:10:31 2010 Return-Path: X-Original-To: precis@core3.amsl.com Delivered-To: precis@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3D7128C0ED for ; Fri, 11 Jun 2010 15:10:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.186 X-Spam-Level: X-Spam-Status: No, score=-0.186 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pkdZ3yuD4jRc for ; Fri, 11 Jun 2010 15:10:29 -0700 (PDT) Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by core3.amsl.com (Postfix) with ESMTP id B2DF23A659A for ; Fri, 11 Jun 2010 15:10:26 -0700 (PDT) Received: from mbl.local (unknown [IPv6:2620:0:1000:167a::5]) by jazz.viagenie.ca (Postfix) with ESMTPSA id EBA2B20CBC for ; Fri, 11 Jun 2010 18:10:28 -0400 (EDT) Message-ID: <4C12B454.6070400@viagenie.ca> Date: Fri, 11 Jun 2010 15:10:28 -0700 From: Marc Blanchet User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: precis@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 12 Jun 2010 00:41:24 -0700 Subject: [precis] precis wg meeting in Maastricht X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.9 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, 11 Jun 2010 22:10:31 -0000 Hello, - we have an official wg, great! now we need to do the work! - we have asked a meeting slot for Maastricht. - The charter deliverables are: 1. Problem statement / analysis of existing stringprep profiles (Informational). 2. Possible new framework to replace stringprep (Standards Track). 3. Possible replacements for the existing IETF stringprep profiles as listed earlier in this charter (Standards Track). 4. String preparation and comparison guidelines (BCP). So we will be looking for editors of these documents. I've started a Problem Statement draft for the bof in Anaheim. Looking for a co-editor. please contact me offlist if you are interested in co-editing. If you are planning to write one of the other deliverables, please contact the chairs offlist. If you would like to present in Maastricht, please contact the chairs offlist. Marc & Yoneya, co-chairs. -- ========= IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca DTN news service: http://reeves.viagenie.ca NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca