From stpeter@stpeter.im Wed Aug 1 05:53:39 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 DA75411E827B for ; Wed, 1 Aug 2012 05:53:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.607 X-Spam-Level: X-Spam-Status: No, score=-101.607 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, 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 pvgzYO0ZmI6A for ; Wed, 1 Aug 2012 05:53:38 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C58D221F88B5 for ; Wed, 1 Aug 2012 05:53:38 -0700 (PDT) Received: from [192.168.0.2] (unknown [67.177.192.224]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5A39640446; Wed, 1 Aug 2012 07:13:24 -0600 (MDT) Message-ID: <50187210.6050207@stpeter.im> Date: Tue, 31 Jul 2012 18:02:24 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Takahiro Nemoto References: <20120705151138.23413.75939.idtracker@ietfa.amsl.com> <4FF5CF39.9040209@stpeter.im> <414B4EE1-C085-468F-9D01-353CA9B52610@kmd.keio.ac.jp> <50048564.30508@stpeter.im> <5006D25C.6000606@stpeter.im> <30419105-0D09-4492-8FF8-5066938DD5F6@kmd.keio.ac.jp> In-Reply-To: <30419105-0D09-4492-8FF8-5066938DD5F6@kmd.keio.ac.jp> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: precis@ietf.org Subject: Re: [precis] I-D ACTION:draft-nemoto-precis-framework-implement-report-00.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: Wed, 01 Aug 2012 12:53:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/27/12 7:50 AM, Takahiro Nemoto wrote: > > On 2012/07/19, at 0:12, Peter Saint-Andre wrote: > >> On 7/18/12 4:24 AM, Takahiro Nemoto wrote: >>> >>> On 2012/07/17, at 6:19, Peter Saint-Andre wrote: >>> >>>> On 7/5/12 10:14 PM, Takahiro Nemoto wrote: >>>> As to special mappings like "Map to SPACE" and "Map to >>>> Nothing", it seems to me that in a post-stringprep system we >>>> can handle those by more carefully defining the string >>>> classes. >>> >>> Sorry, but I don't get it. What does a post-stringprep system >>> mean? >> >> A system that uses PRECIS. >> >> Because PRECIS uses an inclusion model (only characters / code >> points / codepoint classes that are explicitly allowed can be >> included in a conformant string), I don't see any reason to have >> these "mapped to space" or "mapped to nothing" rules in >> PRECIS-based systems. For example, just allow space (U+0020) but >> not other space characters. > > "mapped to nothing" may generate zero-length strings and it may > cause vulnerabilities for applications. That is a very good point! > Therefore, I think I just want to give application developers a > heads-up about this in the protocol or the security > sonsiderations. But, I don't necessarily want to define > application-level restrictions in the protocol. I think that is a reasonable approach. So we need to write a sentence or two of advice to designers of application protocols that use PRECIS. > So I would like to hear more member's comments about this. We don't have members, we have participants. :) Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAYchAACgkQNL8k5A2w/vwUJQCgpfxk6ZbXquOt5pInKqf6nFbq +p8AoJ6qODNj9rsJSkS2CfwlIg2s7vMB =8wad -----END PGP SIGNATURE----- From ietf@meetecho.com Wed Aug 1 11:21:26 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 D7B7F11E81F0 for ; Wed, 1 Aug 2012 11:21:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.339 X-Spam-Level: X-Spam-Status: No, score=-0.339 tagged_above=-999 required=5 tests=[AWL=0.380, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] 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 hTgzEMvNDSwr for ; Wed, 1 Aug 2012 11:21:26 -0700 (PDT) Received: from smtplq03.aruba.it (smtplq-out5.aruba.it [62.149.158.25]) by ietfa.amsl.com (Postfix) with SMTP id 7DE9411E8146 for ; Wed, 1 Aug 2012 11:21:18 -0700 (PDT) Received: (qmail 22587 invoked by uid 89); 1 Aug 2012 18:21:16 -0000 Received: from unknown (HELO smtp8.aruba.it) (62.149.158.228) by smtplq03.aruba.it with SMTP; 1 Aug 2012 18:21:16 -0000 Received: (qmail 17584 invoked by uid 89); 1 Aug 2012 18:21:16 -0000 Received: from unknown (HELO ?130.129.21.177?) (alex@meetecho.com@130.129.21.177) by smtp8.ad.aruba.it with ESMTPA; 1 Aug 2012 18:21:15 -0000 Message-ID: <50197397.80608@meetecho.com> Date: Wed, 01 Aug 2012 20:21:11 +0200 From: Meetecho IETF support User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: precis@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: smtplq03.aruba.it 1.6.2 0/1000/N Subject: [precis] Meetecho support for PRECIS WG 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: Wed, 01 Aug 2012 18:21:27 -0000 Hi all, a virtual room has been reserved on the Meetecho system for Wednesday's PRECIS WG meeting session. Access to the on-line session (including audio and video streams) will be available at: http://www.meetecho.com/ietf84/precis The Meetecho session automatically logs you into the standard IETF jabber room. So, from there, you can have an integrated experience involving all media and allowing you to interact with the room. Remote participants might also send their own voice to the room, if they want to, by either calling a landline phone number, or using our embedded VoIP applet (in this last case they are *strongly* advised to use a headset). A tutorial of interactivity features of the tool can be found at: http://www.meetecho.com/ietf84 Cheers, the Meetecho team -- Meetecho s.r.l. Web Conferencing and Collaboration Tools www.meetecho.com From Marc.Blanchet@viagenie.ca Wed Aug 1 17:51:21 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 405F511E8106 for ; Wed, 1 Aug 2012 17:51:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 Wsxa4ICnDQKI for ; Wed, 1 Aug 2012 17:51:20 -0700 (PDT) Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id CACD311E8210 for ; Wed, 1 Aug 2012 17:51:20 -0700 (PDT) Received: from [IPv6:2001:df8::80:4d21:5d5b:efe:b8e] (unknown [IPv6:2001:df8:0:80:4d21:5d5b:efe:b8e]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C5274415E5 for ; Wed, 1 Aug 2012 20:51:19 -0400 (EDT) From: Marc Blanchet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 1 Aug 2012 17:51:17 -0700 Message-Id: <10B9D71C-6579-4B14-975B-83A67A056A40@viagenie.ca> To: precis@ietf.org Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Subject: [precis] today's meeting notes 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, 02 Aug 2012 00:51:21 -0000 Hello, thank to all note takes, we have meeting notes posted. http://www.ietf.org/proceedings/84/minutes/minutes-84-precis Please send edits to the chairs (precis-chairs@tools.ietf.org). Regards, Marc&Yoneya-san From stpeter@stpeter.im Wed Aug 1 20:24:00 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 896B921F8BC2 for ; Wed, 1 Aug 2012 20:24:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.761 X-Spam-Level: X-Spam-Status: No, score=-102.761 tagged_above=-999 required=5 tests=[AWL=-0.162, 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 ooUXeUFhrK3W for ; Wed, 1 Aug 2012 20:23:59 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id CC91021F8BC1 for ; Wed, 1 Aug 2012 20:23:59 -0700 (PDT) Received: from [192.168.0.4] (unknown [67.177.192.224]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 6EBE540075; Wed, 1 Aug 2012 21:43:47 -0600 (MDT) Message-ID: <5019F2D0.3060107@stpeter.im> Date: Wed, 01 Aug 2012 21:24:00 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Marc Blanchet References: <10B9D71C-6579-4B14-975B-83A67A056A40@viagenie.ca> In-Reply-To: <10B9D71C-6579-4B14-975B-83A67A056A40@viagenie.ca> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: precis@ietf.org Subject: Re: [precis] today's meeting notes 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, 02 Aug 2012 03:24:00 -0000 On 8/1/12 6:51 PM, Marc Blanchet wrote: > Hello, > thank to all note takes, we have meeting notes posted. > > http://www.ietf.org/proceedings/84/minutes/minutes-84-precis Yes, thanks to the note-takers -- very complete! Peter -- Peter Saint-Andre https://stpeter.im/ From stpeter@stpeter.im Wed Aug 1 20:27:54 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 82F9F21F877A for ; Wed, 1 Aug 2012 20:27:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.743 X-Spam-Level: X-Spam-Status: No, score=-102.743 tagged_above=-999 required=5 tests=[AWL=-0.144, 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 qz1EsPxTDP-j for ; Wed, 1 Aug 2012 20:27:53 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB6621F8779 for ; Wed, 1 Aug 2012 20:27:53 -0700 (PDT) Received: from [192.168.0.4] (unknown [67.177.192.224]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 35D3E40075 for ; Wed, 1 Aug 2012 21:47:41 -0600 (MDT) Message-ID: <5019F3BA.5000204@stpeter.im> Date: Wed, 01 Aug 2012 21:27:54 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "precis@ietf.org" X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [precis] SpecialCasing 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, 02 Aug 2012 03:27:54 -0000 We spent a lot of time today discussing Section 4.3 of draft-yoneya-precis-mappings, including the possibility of creating an IANA registry. As I mentioned during the meeting, I really do think that this section is simply citing a few examples from the SpecialCasing.txt file in the Unicode character database. I suggest that we make the connection explicit and just re-use the SpecialCasing rules. They might not be "complete" in some sense, but they are well-defined and thus easily used in PRECIS mappings. Peter -- Peter Saint-Andre https://stpeter.im/ From internet-drafts@ietf.org Wed Aug 1 21:00:23 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 21B4311E817B; Wed, 1 Aug 2012 21:00:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.482 X-Spam-Level: X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, 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 SXBz12+9Rwq3; Wed, 1 Aug 2012 21:00:22 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24D1211E8173; Wed, 1 Aug 2012 21:00:22 -0700 (PDT) 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.33 Message-ID: <20120802040022.9812.94134.idtracker@ietfa.amsl.com> Date: Wed, 01 Aug 2012 21:00:22 -0700 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-framework-05.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: Thu, 02 Aug 2012 04:00:23 -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-05.txt Pages : 65 Date : 2012-08-01 Abstract: Application protocols using Unicode code points in protocol strings need to prepare such strings in order to perform comparison operations (e.g., for purposes of authentication or authorization). This document defines a framework enabling application protocols to handle various classes of strings in a way that depends on the properties of Unicode code points and that 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). A specification that reuses this framework can either directly use the base string classes or subclass the base string classes as needed. This framework takes an approach similar to the revised internationalized domain names in applications (IDNA) technology (RFC 5890, RFC 5891, RFC 5892, RFC 5893, RFC 5894) and thus adheres to the high-level design goals described in RFC 4690, albeit for application technologies other than the Domain Name System (DNS). 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-05 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-framework-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From stpeter@stpeter.im Wed Aug 1 21:15:39 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 8F01711E812C for ; Wed, 1 Aug 2012 21:15:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.729 X-Spam-Level: X-Spam-Status: No, score=-102.729 tagged_above=-999 required=5 tests=[AWL=-0.130, 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 ZAeWptGcdUdP for ; Wed, 1 Aug 2012 21:15:38 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id BF02B11E80E1 for ; Wed, 1 Aug 2012 21:15:36 -0700 (PDT) Received: from [192.168.0.4] (unknown [67.177.192.224]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0587A40075 for ; Wed, 1 Aug 2012 22:35:23 -0600 (MDT) Message-ID: <5019FEE7.6090804@stpeter.im> Date: Wed, 01 Aug 2012 22:15:35 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: precis@ietf.org References: <20120802040022.9812.94134.idtracker@ietfa.amsl.com> In-Reply-To: <20120802040022.9812.94134.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [precis] I-D Action: draft-ietf-precis-framework-05.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: Thu, 02 Aug 2012 04:15:40 -0000 Updated to reflect today's discussions. /psa On 8/1/12 10:00 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-05.txt > Pages : 65 > Date : 2012-08-01 > > Abstract: > Application protocols using Unicode code points in protocol strings > need to prepare such strings in order to perform comparison > operations (e.g., for purposes of authentication or authorization). > This document defines a framework enabling application protocols to > handle various classes of strings in a way that depends on the > properties of Unicode code points and that 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). A > specification that reuses this framework can either directly use the > base string classes or subclass the base string classes as needed. > This framework takes an approach similar to the revised > internationalized domain names in applications (IDNA) technology (RFC > 5890, RFC 5891, RFC 5892, RFC 5893, RFC 5894) and thus adheres to the > high-level design goals described in RFC 4690, albeit for application > technologies other than the Domain Name System (DNS). 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-05 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-precis-framework-05 > > > 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 > From internet-drafts@ietf.org Wed Aug 1 22:50:38 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 B55AA11E8116; Wed, 1 Aug 2012 22:50:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.473 X-Spam-Level: X-Spam-Status: No, score=-102.473 tagged_above=-999 required=5 tests=[AWL=0.126, 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 DDYQ6Ls1-yjN; Wed, 1 Aug 2012 22:50:37 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC62111E809A; Wed, 1 Aug 2012 22:50:37 -0700 (PDT) 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.33 Message-ID: <20120802055037.23207.29170.idtracker@ietfa.amsl.com> Date: Wed, 01 Aug 2012 22:50:37 -0700 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-nickname-00.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: Thu, 02 Aug 2012 05:50:39 -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-00.txt Pages : 6 Date : 2012-08-01 Abstract: This document describes how to prepare and compare Unicode strings representing nicknames, primarily as used within textual chatrooms. This profile is intended to be used by chatroom technologies based on both the Message Session Relay Protocol (MSRP) and the Extensible Messaging and Presence Protocol (XMPP). 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-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From jhildebr@cisco.com Thu Aug 2 09:24: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 4070D11E808E for ; Thu, 2 Aug 2012 09:24:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 k-QScs48c6MU for ; Thu, 2 Aug 2012 09:24:16 -0700 (PDT) Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 4A77011E80E8 for ; Thu, 2 Aug 2012 09:24:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jhildebr@cisco.com; l=1110; q=dns/txt; s=iport; t=1343924656; x=1345134256; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=XCLVaeEG3zLGxnLWyCRLOJDj4i1JdMYksLUIhXBDaNg=; b=UTbHNYIVANSlXCdvCvSxnpfmQTi3mlUNsEqeE5Hn++y8xI1NoNrTbeVG 1DMEvT7aP4BF8zwPcF2k7CvEHmY/dHX92w5Op1GTWd6beDnLaA4PRVnF+ coYCIBahz0a9I2Rf/bNQ0y7SnHMcCTCFpK/5pmj9YHN1E/o0RnefZdtZO k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EADypGlCtJV2Z/2dsb2JhbABFuQyBB4IiAQQBAQEPASc0HQEINjcLJQIEARIih2sLnGWgTQSSTQOVR44ngWaCXw X-IronPort-AV: E=Sophos;i="4.77,702,1336348800"; d="scan'208";a="107916847" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 02 Aug 2012 16:24:16 +0000 Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q72GOGJn002236 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Aug 2012 16:24:16 GMT Received: from xmb-rcd-x10.cisco.com ([169.254.15.184]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0298.004; Thu, 2 Aug 2012 11:24:15 -0500 From: "Joe Hildebrand (jhildebr)" To: Peter Saint-Andre , "precis@ietf.org" Thread-Topic: [precis] SpecialCasing Thread-Index: AQHNcF7Q0qszItvRQkKVHZXHBBNByJdGlDqA Date: Thu, 2 Aug 2012 16:24:14 +0000 Message-ID: In-Reply-To: <5019F3BA.5000204@stpeter.im> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.3.120616 x-originating-ip: [10.21.117.212] x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19078.004 x-tm-as-result: No--36.458300-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: text/plain; charset="us-ascii" Content-ID: <1B91ED8ED0A608419D328ED61111BBEB@cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [precis] SpecialCasing 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, 02 Aug 2012 16:24:18 -0000 After looking at this table, I think it captures precisely the sort of information that I was trying to describe for the registry. Therefore, I agree with Peter. Can we add a reference to section 3.13 of the Unicode Standard to section 4.3 of the draft, please? On 8/1/12 8:27 PM, "Peter Saint-Andre" wrote: >We spent a lot of time today discussing Section 4.3 of >draft-yoneya-precis-mappings, including the possibility of creating an >IANA registry. As I mentioned during the meeting, I really do think that >this section is simply citing a few examples from the SpecialCasing.txt >file in the Unicode character database. I suggest that we make the >connection explicit and just re-use the SpecialCasing rules. They might >not be "complete" in some sense, but they are well-defined and thus >easily used in PRECIS mappings. > >Peter > >--=20 >Peter Saint-Andre >https://stpeter.im/ > > >_______________________________________________ >precis mailing list >precis@ietf.org >https://www.ietf.org/mailman/listinfo/precis > --=20 Joe Hildebrand From david.black@emc.com Fri Aug 3 09:05:11 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 97B2721F8D3A for ; Fri, 3 Aug 2012 09:05:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.468 X-Spam-Level: X-Spam-Status: No, score=-102.468 tagged_above=-999 required=5 tests=[AWL=0.131, 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 ywZBR1Tk8QmC for ; Fri, 3 Aug 2012 09:05:10 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id BB91321F8CCD for ; Fri, 3 Aug 2012 09:05:10 -0700 (PDT) Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q73G59o6020549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 3 Aug 2012 12:05:09 -0400 Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for ; Fri, 3 Aug 2012 12:04:54 -0400 Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.222.70.172]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q73G4rkt019266 for ; Fri, 3 Aug 2012 12:04:53 -0400 Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub32.corp.emc.com ([128.222.70.172]) with mapi; Fri, 3 Aug 2012 12:04:52 -0400 From: To: Date: Fri, 3 Aug 2012 12:04:51 -0400 Thread-Topic: Late comments on problem-statement-06 Thread-Index: Ac1xHW6s7JXycQe3TH+1GM95krtj8Q== Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208E80169@MX15A.corp.emc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: [precis] Late comments on problem-statement-06 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, 03 Aug 2012 16:05:11 -0000 I've finally been able to take a look at the problem-statement-06 draft, primarily to check the iSCSI material, but I also took a look at the main portion of the draft. I have a few comments, and greatly appreciate the patience of the authors and WG chairs in being willing to look at these after WG Last Call. Everything I found here is minor. -- Section 2: A single Unicode code point in this memo is denoted by "U+" followed by four to six hexadecimal digits. Compare to [Unicode61], Appendix A. I don't understand what is intended by "Compare". Is this representation the same as, similar to or different from the cited reference? -- Section 3 During IETF 77, a BOF discussed the current state of the protocols that have defined Stringprep profiles [NEWPREP]. I'd suggest adding the month and year of IETF 77 in parens after the 77. o Stringprep is bound to version 3.2 of Unicode. Stringprep has not been updated to new versions of Unicode. Therefore, the protocols using Stringprep are stuck to Unicode 3.2. o The protocols need to be updated to support new versions of Unicode. The protocols would like to not be bound to a specific version of Unicode, but rather have better Unicode agility in the way of IDNA2008. This is important partly because it is usually impossible for an application to require Unicode 3.2; the application gets whatever version of Unicode is available on the host. I suggest merging first sentence of second bullet into the first bullet so that the second bullet focuses on Unicode version agility. The last sentence of the first bullet could then be: Therefore, the protocols using Stringprep are stuck at Unicode 3.2, and their specifications need to be updated to support newer versions of Unicode. Also, "Unicode agility" -> "Unicode version agility". The following iSCSI bullet is incorrect: o iSCSI uses a Stringprep profile for the IQN, which is very similar to (often is) a DNS domain name. with o iSCSI uses a Stringprep profile for the names of protocol participant= s (called initiators and targets). The IQN format of iSCSI names contains a reversed DNS domain name. -- Appendix A The User entry for RFC 3722 (iSCSI) should be "b", not "a". The iSCSI name strings are part of host and storage system configuration; these strings are entered by and are visible to administrators. -- Appendix B.1 iSCSI Stringprep Profiles: RFC3722, RFC3721, RFC3720 There is one profile, and it's specified by RFC 3722. The other two RFCs describe the naming design and how the strings are used. It may not b appropriate to list the other two RFCs in the section name. Description: An iSCSI session consists of an Initiator (i.e., host or server that uses storage) communicating with a target (i.e., a storage array or other system that provides storage). Both the iSCSI initiator and target are named by iSCSI Names. The iSCSI stringprep profile is used for iSCSI names. Initiator -> initiator in first line. What is the impact if the comparison results in a false positive? Potential access to the wrong storage. - If the initiator has no access to the wrong storage, an authentication failure is the probable result. - If the initiator has access to the worng storage, the resulting mis-identificaiton could result in use of the wrong data and possible corruption of stored data. Correct two spelling errors: - worng -> wrong - identificaiton -> identification. What are the security impacts? iSCSI names are often used as the authentication identities for storage systems. Comparison problems could result in authentication problems, although note that authentication failure ameliorates some of the false positive cases. Change "are often used" to "may be used" in the first line. How much tolerance for change from existing stringprep approach? Good tolerance; the community would prefer that internationalization experts solve internationalization problems ;-). Remove the smiley. Thanks, --David ---------------------------------------------------- David L. Black, Distinguished Engineer EMC Corporation, 176 South St., Hopkinton, MA=A0 01748 +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778= 6 david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754 ---------------------------------------------------- From david.black@emc.com Fri Aug 3 09:43:12 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 091A421F8E75 for ; Fri, 3 Aug 2012 09:43:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.471 X-Spam-Level: X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.128, 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 pL9uFX4yvbKC for ; Fri, 3 Aug 2012 09:43:11 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id EA91021F8E6F for ; Fri, 3 Aug 2012 09:43:10 -0700 (PDT) Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q73GhAjH025500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 3 Aug 2012 12:43:10 -0400 Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for ; Fri, 3 Aug 2012 12:42:48 -0400 Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q73GgmX4021209 for ; Fri, 3 Aug 2012 12:42:48 -0400 Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Fri, 3 Aug 2012 12:42:48 -0400 From: To: , Date: Fri, 3 Aug 2012 12:42:46 -0400 Thread-Topic: Late comments on problem-statement-06 [NFSv4] Thread-Index: Ac1xHW6s7JXycQe3TH+1GM95krtj8QAd4Otg Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208E8018F@MX15A.corp.emc.com> References: <8D3D17ACE214DC429325B2B98F3AE71208E80169@MX15A.corp.emc.com> In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208E80169@MX15A.corp.emc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: Re: [precis] Late comments on problem-statement-06 [NFSv4] 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, 03 Aug 2012 16:43:12 -0000 NFS also contains some stringprep profiles: - NFSv4: RFC 3530, Section 11 - NFSv4.1: RFC 5661, Section 14 There are also concerns that the stringprep approach doesn't work well for = NFSv4. See section 12 of draft-ietf-nfsv4-rfc3530bis-18.txt for some current think= ing on this topic. Thanks, --David > -----Original Message----- > From: Black, David > Sent: Friday, August 03, 2012 12:05 PM > To: precis@ietf.org > Cc: Black, David > Subject: Late comments on problem-statement-06 >=20 > I've finally been able to take a look at the problem-statement-06 draft, > primarily to check the iSCSI material, but I also took a look at the main > portion of the draft. I have a few comments, and greatly appreciate the > patience of the authors and WG chairs in being willing to look at these > after WG Last Call. Everything I found here is minor. >=20 > -- Section 2: >=20 > A single Unicode code point in this memo is denoted by "U+" followed > by four to six hexadecimal digits. Compare to [Unicode61], Appendix > A. >=20 > I don't understand what is intended by "Compare". Is this representation > the same as, similar to or different from the cited reference? >=20 > -- Section 3 >=20 > During IETF 77, a BOF discussed the current state of the protocols > that have defined Stringprep profiles [NEWPREP]. >=20 > I'd suggest adding the month and year of IETF 77 in parens after the 77. >=20 > o Stringprep is bound to version 3.2 of Unicode. Stringprep has not > been updated to new versions of Unicode. Therefore, the protocols > using Stringprep are stuck to Unicode 3.2. >=20 > o The protocols need to be updated to support new versions of > Unicode. The protocols would like to not be bound to a specific > version of Unicode, but rather have better Unicode agility in the > way of IDNA2008. This is important partly because it is usually > impossible for an application to require Unicode 3.2; the > application gets whatever version of Unicode is available on the > host. >=20 > I suggest merging first sentence of second bullet into the first bullet > so that the second bullet focuses on Unicode version agility. The last > sentence of the first bullet could then be: >=20 > Therefore, the protocols using Stringprep are stuck at Unicode 3.2, > and their specifications need to be updated to support newer versio= ns > of Unicode. >=20 > Also, "Unicode agility" -> "Unicode version agility". >=20 > The following iSCSI bullet is incorrect: >=20 > o iSCSI uses a Stringprep profile for the IQN, which is very similar > to (often is) a DNS domain name. >=20 > with >=20 > o iSCSI uses a Stringprep profile for the names of protocol participa= nts > (called initiators and targets). The IQN format of iSCSI names contains > a reversed DNS domain name. >=20 > -- Appendix A >=20 > The User entry for RFC 3722 (iSCSI) should be "b", not "a". The iSCSI na= me > strings are part of host and storage system configuration; these strings > are entered by and are visible to administrators. >=20 > -- Appendix B.1 iSCSI Stringprep Profiles: RFC3722, RFC3721, RFC3720 >=20 > There is one profile, and it's specified by RFC 3722. The other two RFCs > describe the naming design and how the strings are used. It may not b > appropriate to list the other two RFCs in the section name. >=20 > Description: An iSCSI session consists of an Initiator (i.e., host > or server that uses storage) communicating with a target (i.e., a > storage array or other system that provides storage). Both the > iSCSI initiator and target are named by iSCSI Names. The iSCSI > stringprep profile is used for iSCSI names. >=20 > Initiator -> initiator in first line. >=20 > What is the impact if the comparison results in a false positive? > Potential access to the wrong storage. - If the initiator has no > access to the wrong storage, an authentication failure is the > probable result. - If the initiator has access to the worng > storage, the resulting mis-identificaiton could result in use of > the wrong data and possible corruption of stored data. >=20 > Correct two spelling errors: > - worng -> wrong > - identificaiton -> identification. >=20 > What are the security impacts? iSCSI names are often used as the > authentication identities for storage systems. Comparison > problems could result in authentication problems, although note > that authentication failure ameliorates some of the false positive > cases. >=20 > Change "are often used" to "may be used" in the first line. >=20 > How much tolerance for change from existing stringprep approach? > Good tolerance; the community would prefer that > internationalization experts solve internationalization problems > ;-). >=20 > Remove the smiley. >=20 > Thanks, > --David > ---------------------------------------------------- > David L. Black, Distinguished Engineer > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748 > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7= 786 > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754 > ---------------------------------------------------- From t.nemo10@kmd.keio.ac.jp Fri Aug 3 10:14:53 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 55FFC21F8E13 for ; Fri, 3 Aug 2012 10:14:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] 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 8+nUSaK+IquY for ; Fri, 3 Aug 2012 10:14:52 -0700 (PDT) Received: from mail.kmd.keio.ac.jp (mail.kmd.keio.ac.jp [IPv6:2001:200:167:2e90::164]) by ietfa.amsl.com (Postfix) with ESMTP id 1218921F8E0F for ; Fri, 3 Aug 2012 10:14:51 -0700 (PDT) Received: from [IPv6:2001:df8::64:e4be:7a45:1f39:83cc] (unknown [IPv6:2001:df8:0:64:e4be:7a45:1f39:83cc]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kmd.keio.ac.jp (Postfix) with ESMTPSA id E75117FBE6; Sat, 4 Aug 2012 02:14:44 +0900 (JST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) From: Takahiro Nemoto In-Reply-To: Date: Fri, 3 Aug 2012 10:14:42 -0700 Content-Transfer-Encoding: 7bit Message-Id: <2FA538E6-17BC-46DF-980B-87AAC3D582DA@kmd.keio.ac.jp> References: To: "precis@ietf.org" X-Mailer: Apple Mail (2.1485) Subject: Re: [precis] SpecialCasing 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, 03 Aug 2012 17:14:53 -0000 Thank you very much for your helpful suggestions. I read section 3.13 of the Unicode Standard. I'll reflect comments and update the draft to add a reference to the section to section4.3. immediately. Nemo On 2012/08/02, at 9:24, Joe Hildebrand (jhildebr) wrote: > After looking at this table, I think it captures precisely the sort of > information that I was trying to describe for the registry. > > Therefore, I agree with Peter. > > Can we add a reference to section 3.13 of the Unicode Standard to section > 4.3 of the draft, please? > > > On 8/1/12 8:27 PM, "Peter Saint-Andre" wrote: > >> We spent a lot of time today discussing Section 4.3 of >> draft-yoneya-precis-mappings, including the possibility of creating an >> IANA registry. As I mentioned during the meeting, I really do think that >> this section is simply citing a few examples from the SpecialCasing.txt >> file in the Unicode character database. I suggest that we make the >> connection explicit and just re-use the SpecialCasing rules. They might >> not be "complete" in some sense, but they are well-defined and thus >> easily used in PRECIS mappings. >> >> Peter >> >> -- >> Peter Saint-Andre >> https://stpeter.im/ >> >> >> _______________________________________________ >> precis mailing list >> precis@ietf.org >> https://www.ietf.org/mailman/listinfo/precis >> > > > > -- > Joe Hildebrand > > > > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis -- Takahiro Nemoto t.nemo10@kmd.keio.ac.jp From internet-drafts@ietf.org Fri Aug 3 10:33:44 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 1E74121F8D80; Fri, 3 Aug 2012 10:33:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.47 X-Spam-Level: X-Spam-Status: No, score=-102.47 tagged_above=-999 required=5 tests=[AWL=0.129, 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 OIM+pYAVRelr; Fri, 3 Aug 2012 10:33:43 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F97E21F8DA2; Fri, 3 Aug 2012 10:33:43 -0700 (PDT) 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.33 Message-ID: <20120803173343.3477.78706.idtracker@ietfa.amsl.com> Date: Fri, 03 Aug 2012 10:33:43 -0700 Cc: precis@ietf.org Subject: [precis] I-D Action: draft-ietf-precis-problem-statement-07.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, 03 Aug 2012 17:33:44 -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 : Stringprep Revision and PRECIS Problem Statement Author(s) : Marc Blanchet Andrew Sullivan Filename : draft-ietf-precis-problem-statement-07.txt Pages : 30 Date : 2012-08-03 Abstract: If a protocol expects to compare two strings and is prepared only for those strings to be ASCII, then using Unicode codepoints in those strings requires they be prepared somehow. Internationalizing Domain Names in Applications (here called 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 datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-precis-problem-statement There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-precis-problem-statement-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-problem-statement-07 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From stpeter@stpeter.im Fri Aug 3 10:44: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 50EAE21F8DE8 for ; Fri, 3 Aug 2012 10:44:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.569 X-Spam-Level: X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 IFsigOtjbcvr for ; Fri, 3 Aug 2012 10:44:24 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C36C521F8DE5 for ; Fri, 3 Aug 2012 10:44:24 -0700 (PDT) Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B0C094044F; Fri, 3 Aug 2012 12:04:17 -0600 (MDT) Message-ID: <501C0DF6.6030204@stpeter.im> Date: Fri, 03 Aug 2012 11:44:22 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: david.black@emc.com References: <8D3D17ACE214DC429325B2B98F3AE71208E80169@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71208E8018F@MX15A.corp.emc.com> In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208E8018F@MX15A.corp.emc.com> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: precis@ietf.org Subject: Re: [precis] Late comments on problem-statement-06 [NFSv4] 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, 03 Aug 2012 17:44:25 -0000 On 8/3/12 10:42 AM, david.black@emc.com wrote: > NFS also contains some stringprep profiles: > > - NFSv4: RFC 3530, Section 11 > - NFSv4.1: RFC 5661, Section 14 > > There are also concerns that the stringprep approach doesn't work well for NFSv4. > See section 12 of draft-ietf-nfsv4-rfc3530bis-18.txt for some current thinking > on this topic. I see that they devote over 20 pages to internationalization issues. I looked at the first 5 pages and then realized I'd need to spend significant time grokking it all... Peter -- Peter Saint-Andre https://stpeter.im/ From marc.blanchet@viagenie.ca Fri Aug 3 10:48:57 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 0FF2F21F8E24 for ; Fri, 3 Aug 2012 10:48:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 P7ox+pTds6pX for ; Fri, 3 Aug 2012 10:48:56 -0700 (PDT) Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 32FFF21F8D60 for ; Fri, 3 Aug 2012 10:48:56 -0700 (PDT) Received: from [IPv6:2001:df8::80:7574:39d6:261a:a9ca] (unknown [IPv6:2001:df8:0:80:7574:39d6:261a:a9ca]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2E36F415AC; Fri, 3 Aug 2012 13:48:55 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Marc Blanchet In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208E80169@MX15A.corp.emc.com> Date: Fri, 3 Aug 2012 10:48:54 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <51BB69C6-08AD-40DA-944E-8919539BCBF8@viagenie.ca> References: <8D3D17ACE214DC429325B2B98F3AE71208E80169@MX15A.corp.emc.com> To: X-Mailer: Apple Mail (2.1278) Cc: precis@ietf.org Subject: Re: [precis] Late comments on problem-statement-06 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, 03 Aug 2012 17:48:57 -0000 -08 now includes all your changes. However, for: "-- Appendix B.1 iSCSI Stringprep Profiles: RFC3722, RFC3721, RFC3720 >=20 >=20 > There is one profile, and it's specified by RFC 3722. The other two = RFCs > describe the naming design and how the strings are used. It may not b > appropriate to list the other two RFCs in the section name." I wanted to keep the three RFCs in the list since they had been = identified as to be reviewed during our stringprep customers review = process. (so that we show the coverage we made). So I rewrote as: iSCSI Stringprep Profile: RFC3722 (and RFC3721, RFC3720). hope this is acceptable to you. Marc. Le 2012-08-03 =E0 09:04, a =E9crit : > I've finally been able to take a look at the problem-statement-06 = draft, > primarily to check the iSCSI material, but I also took a look at the = main > portion of the draft. I have a few comments, and greatly appreciate = the > patience of the authors and WG chairs in being willing to look at = these > after WG Last Call. Everything I found here is minor. >=20 > -- Section 2: >=20 > A single Unicode code point in this memo is denoted by "U+" followed > by four to six hexadecimal digits. Compare to [Unicode61], Appendix > A. >=20 > I don't understand what is intended by "Compare". Is this = representation > the same as, similar to or different from the cited reference? >=20 > -- Section 3 >=20 > During IETF 77, a BOF discussed the current state of the protocols > that have defined Stringprep profiles [NEWPREP]. >=20 > I'd suggest adding the month and year of IETF 77 in parens after the = 77. >=20 > o Stringprep is bound to version 3.2 of Unicode. Stringprep has = not > been updated to new versions of Unicode. Therefore, the = protocols > using Stringprep are stuck to Unicode 3.2. >=20 > o The protocols need to be updated to support new versions of > Unicode. The protocols would like to not be bound to a specific > version of Unicode, but rather have better Unicode agility in the > way of IDNA2008. This is important partly because it is usually > impossible for an application to require Unicode 3.2; the > application gets whatever version of Unicode is available on the > host. >=20 > I suggest merging first sentence of second bullet into the first = bullet > so that the second bullet focuses on Unicode version agility. The = last > sentence of the first bullet could then be: >=20 > Therefore, the protocols using Stringprep are stuck at Unicode = 3.2, > and their specifications need to be updated to support newer = versions > of Unicode. >=20 > Also, "Unicode agility" -> "Unicode version agility". >=20 > The following iSCSI bullet is incorrect: >=20 > o iSCSI uses a Stringprep profile for the IQN, which is very = similar > to (often is) a DNS domain name. >=20 > with >=20 > o iSCSI uses a Stringprep profile for the names of protocol = participants > (called initiators and targets). The IQN format of iSCSI names = contains > a reversed DNS domain name. >=20 > -- Appendix A >=20 > The User entry for RFC 3722 (iSCSI) should be "b", not "a". The iSCSI = name > strings are part of host and storage system configuration; these = strings > are entered by and are visible to administrators. >=20 > -- Appendix B.1 iSCSI Stringprep Profiles: RFC3722, RFC3721, RFC3720 >=20 > There is one profile, and it's specified by RFC 3722. The other two = RFCs > describe the naming design and how the strings are used. It may not b > appropriate to list the other two RFCs in the section name. >=20 > Description: An iSCSI session consists of an Initiator (i.e., host > or server that uses storage) communicating with a target (i.e., a > storage array or other system that provides storage). Both the > iSCSI initiator and target are named by iSCSI Names. The iSCSI > stringprep profile is used for iSCSI names. >=20 > Initiator -> initiator in first line. >=20 > What is the impact if the comparison results in a false positive? > Potential access to the wrong storage. - If the initiator has no > access to the wrong storage, an authentication failure is the > probable result. - If the initiator has access to the worng > storage, the resulting mis-identificaiton could result in use of > the wrong data and possible corruption of stored data. >=20 > Correct two spelling errors: > - worng -> wrong > - identificaiton -> identification. >=20 > What are the security impacts? iSCSI names are often used as the > authentication identities for storage systems. Comparison > problems could result in authentication problems, although note > that authentication failure ameliorates some of the false = positive > cases. >=20 > Change "are often used" to "may be used" in the first line. >=20 > How much tolerance for change from existing stringprep approach? > Good tolerance; the community would prefer that > internationalization experts solve internationalization problems > ;-). >=20 > Remove the smiley. >=20 > Thanks, > --David > ---------------------------------------------------- > David L. Black, Distinguished Engineer > EMC Corporation, 176 South St., Hopkinton, MA 01748 > +1 (508) 293-7953 FAX: +1 (508) 293-7786 > david.black@emc.com Mobile: +1 (978) 394-7754 > ---------------------------------------------------- >=20 > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis From marc.blanchet@viagenie.ca Fri Aug 3 10:50: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 EF41621F8D55 for ; Fri, 3 Aug 2012 10:50:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 6kwe25VNQ6zA for ; Fri, 3 Aug 2012 10:50:17 -0700 (PDT) Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 0E16E21F8D0C for ; Fri, 3 Aug 2012 10:50:17 -0700 (PDT) Received: from [IPv6:2001:df8::80:7574:39d6:261a:a9ca] (unknown [IPv6:2001:df8:0:80:7574:39d6:261a:a9ca]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 81321415AC; Fri, 3 Aug 2012 13:50:13 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Marc Blanchet In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208E8018F@MX15A.corp.emc.com> Date: Fri, 3 Aug 2012 10:50:12 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <0C2ADF5C-802F-4C2A-AA11-CEC6910BC063@viagenie.ca> References: <8D3D17ACE214DC429325B2B98F3AE71208E80169@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71208E8018F@MX15A.corp.emc.com> To: X-Mailer: Apple Mail (2.1278) Cc: precis@ietf.org Subject: Re: [precis] Late comments on problem-statement-06 [NFSv4] 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, 03 Aug 2012 17:50:18 -0000 Le 2012-08-03 =E0 09:42, a =E9crit : > NFS also contains some stringprep profiles: >=20 > - NFSv4: RFC 3530, Section 11 > - NFSv4.1: RFC 5661, Section 14 >=20 > There are also concerns that the stringprep approach doesn't work well = for NFSv4. > See section 12 of draft-ietf-nfsv4-rfc3530bis-18.txt for some current = thinking > on this topic. ok. but I'm not sure what to do or include into the problem statement.=20= Do you want to sketch something? Marc. >=20 > Thanks, > --David >=20 >=20 >> -----Original Message----- >> From: Black, David >> Sent: Friday, August 03, 2012 12:05 PM >> To: precis@ietf.org >> Cc: Black, David >> Subject: Late comments on problem-statement-06 >>=20 >> I've finally been able to take a look at the problem-statement-06 = draft, >> primarily to check the iSCSI material, but I also took a look at the = main >> portion of the draft. I have a few comments, and greatly appreciate = the >> patience of the authors and WG chairs in being willing to look at = these >> after WG Last Call. Everything I found here is minor. >>=20 >> -- Section 2: >>=20 >> A single Unicode code point in this memo is denoted by "U+" = followed >> by four to six hexadecimal digits. Compare to [Unicode61], = Appendix >> A. >>=20 >> I don't understand what is intended by "Compare". Is this = representation >> the same as, similar to or different from the cited reference? >>=20 >> -- Section 3 >>=20 >> During IETF 77, a BOF discussed the current state of the protocols >> that have defined Stringprep profiles [NEWPREP]. >>=20 >> I'd suggest adding the month and year of IETF 77 in parens after the = 77. >>=20 >> o Stringprep is bound to version 3.2 of Unicode. Stringprep has = not >> been updated to new versions of Unicode. Therefore, the = protocols >> using Stringprep are stuck to Unicode 3.2. >>=20 >> o The protocols need to be updated to support new versions of >> Unicode. The protocols would like to not be bound to a specific >> version of Unicode, but rather have better Unicode agility in = the >> way of IDNA2008. This is important partly because it is usually >> impossible for an application to require Unicode 3.2; the >> application gets whatever version of Unicode is available on the >> host. >>=20 >> I suggest merging first sentence of second bullet into the first = bullet >> so that the second bullet focuses on Unicode version agility. The = last >> sentence of the first bullet could then be: >>=20 >> Therefore, the protocols using Stringprep are stuck at Unicode = 3.2, >> and their specifications need to be updated to support newer = versions >> of Unicode. >>=20 >> Also, "Unicode agility" -> "Unicode version agility". >>=20 >> The following iSCSI bullet is incorrect: >>=20 >> o iSCSI uses a Stringprep profile for the IQN, which is very = similar >> to (often is) a DNS domain name. >>=20 >> with >>=20 >> o iSCSI uses a Stringprep profile for the names of protocol = participants >> (called initiators and targets). The IQN format of iSCSI names = contains >> a reversed DNS domain name. >>=20 >> -- Appendix A >>=20 >> The User entry for RFC 3722 (iSCSI) should be "b", not "a". The = iSCSI name >> strings are part of host and storage system configuration; these = strings >> are entered by and are visible to administrators. >>=20 >> -- Appendix B.1 iSCSI Stringprep Profiles: RFC3722, RFC3721, RFC3720 >>=20 >> There is one profile, and it's specified by RFC 3722. The other two = RFCs >> describe the naming design and how the strings are used. It may not = b >> appropriate to list the other two RFCs in the section name. >>=20 >> Description: An iSCSI session consists of an Initiator (i.e., host >> or server that uses storage) communicating with a target (i.e., = a >> storage array or other system that provides storage). Both the >> iSCSI initiator and target are named by iSCSI Names. The iSCSI >> stringprep profile is used for iSCSI names. >>=20 >> Initiator -> initiator in first line. >>=20 >> What is the impact if the comparison results in a false positive? >> Potential access to the wrong storage. - If the initiator has no >> access to the wrong storage, an authentication failure is the >> probable result. - If the initiator has access to the worng >> storage, the resulting mis-identificaiton could result in use of >> the wrong data and possible corruption of stored data. >>=20 >> Correct two spelling errors: >> - worng -> wrong >> - identificaiton -> identification. >>=20 >> What are the security impacts? iSCSI names are often used as the >> authentication identities for storage systems. Comparison >> problems could result in authentication problems, although note >> that authentication failure ameliorates some of the false = positive >> cases. >>=20 >> Change "are often used" to "may be used" in the first line. >>=20 >> How much tolerance for change from existing stringprep approach? >> Good tolerance; the community would prefer that >> internationalization experts solve internationalization problems >> ;-). >>=20 >> Remove the smiley. >>=20 >> Thanks, >> --David >> ---------------------------------------------------- >> David L. Black, Distinguished Engineer >> EMC Corporation, 176 South St., Hopkinton, MA 01748 >> +1 (508) 293-7953 FAX: +1 (508) 293-7786 >> david.black@emc.com Mobile: +1 (978) 394-7754 >> ---------------------------------------------------- >=20 > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis From marc.blanchet@viagenie.ca Fri Aug 3 10:51:13 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 ADBD121F8DB9 for ; Fri, 3 Aug 2012 10:51:12 -0700 (PDT) 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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, 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 gudE0uhnCk-D for ; Fri, 3 Aug 2012 10:51:12 -0700 (PDT) Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id EE10921F8D65 for ; Fri, 3 Aug 2012 10:51:11 -0700 (PDT) Received: from [IPv6:2001:df8::80:7574:39d6:261a:a9ca] (unknown [IPv6:2001:df8:0:80:7574:39d6:261a:a9ca]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 545C2415AC for ; Fri, 3 Aug 2012 13:51:11 -0400 (EDT) From: Marc Blanchet Content-Type: multipart/alternative; boundary="Apple-Mail=_C43CC106-A30D-49FC-9F79-67444E08209F" Date: Fri, 3 Aug 2012 10:51:11 -0700 References: <20120803173343.3477.78706.idtracker@ietfa.amsl.com> To: precis@ietf.org Message-Id: <5669CFD0-C2C6-4717-8955-414555480009@viagenie.ca> Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Subject: [precis] Fwd: I-D Action: draft-ietf-precis-problem-statement-07.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, 03 Aug 2012 17:51:13 -0000 --Apple-Mail=_C43CC106-A30D-49FC-9F79-67444E08209F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 new rev including David Black comments. (see other email for details) Marc. D=E9but du message r=E9exp=E9di=E9 : > De : internet-drafts@ietf.org > Objet : [precis] I-D Action: = draft-ietf-precis-problem-statement-07.txt > Date : 3 ao=FBt 2012 10:33:43 HAP > =C0 : i-d-announce@ietf.org > Cc : precis@ietf.org >=20 >=20 > 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. >=20 > Title : Stringprep Revision and PRECIS Problem = Statement > Author(s) : Marc Blanchet > Andrew Sullivan > Filename : draft-ietf-precis-problem-statement-07.txt > Pages : 30 > Date : 2012-08-03 >=20 > Abstract: > If a protocol expects to compare two strings and is prepared only = for > those strings to be ASCII, then using Unicode codepoints in those > strings requires they be prepared somehow. Internationalizing = Domain > Names in Applications (here called 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. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-precis-problem-statement >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-precis-problem-statement-07 >=20 > A diff from the previous version is available at: > = http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-problem-statement-07 >=20 >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > precis mailing list > precis@ietf.org > https://www.ietf.org/mailman/listinfo/precis --Apple-Mail=_C43CC106-A30D-49FC-9F79-67444E08209F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 new = rev including David Black comments. (see other email for = details)

Marc.

D=E9but du message = r=E9exp=E9di=E9 :

De : internet-drafts@ietf.org
<= /span>

Objet : [precis] I-D Action: = draft-ietf-precis-problem-statement-07.txt

Date : 3 ao=FBt 2012 = 10:33:43 HAP

=C0 : i-d-announce@ietf.org
=

Cc : precis@ietf.org

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 =           : Stringprep = Revision and PRECIS Problem Statement
Author(s) =       : Marc Blanchet
=             &n= bsp;           &nbs= p;Andrew Sullivan
Filename =        : = draft-ietf-precis-problem-statement-07.txt
Pages =           : = 30
= Date =            : = 2012-08-03

Abstract:
  If a protocol expects to = compare two strings and is prepared only for
  those = strings to be ASCII, then using Unicode codepoints in those
=   strings requires they be prepared somehow. = Internationalizing Domain
  Names in Applications = (here called 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 datatracker status page for = this draft is:
https://datatracker.ietf.org/doc/draft-ietf-precis-problem-statement

There's also a htmlized version available = at:
http://tools.ietf.org/html/draft-ietf-precis-problem-statement-07
A diff from the previous version is available = at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-precis-problem-statem= ent-07

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