Re: Protocol Action: 'LDAP: Internationalized String Preparation' to Proposed Standard
Frank Ellermann <nobody@xyzzy.claranet.de> Thu, 26 January 2006 17:43 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2B9D-0003dM-18; Thu, 26 Jan 2006 12:43:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2B97-0003bm-G9 for ietf@megatron.ietf.org; Thu, 26 Jan 2006 12:42:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07864 for <ietf@ietf.org>; Thu, 26 Jan 2006 12:41:22 -0500 (EST)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F2BDQ-0006El-7I for ietf@ietf.org; Thu, 26 Jan 2006 12:47:28 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1F2B29-0004z2-RV for ietf@ietf.org; Thu, 26 Jan 2006 18:35:45 +0100
Received: from 1cust143.tnt8.hbg2.deu.da.uu.net ([149.225.138.143]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Thu, 26 Jan 2006 18:35:45 +0100
Received: from nobody by 1cust143.tnt8.hbg2.deu.da.uu.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Thu, 26 Jan 2006 18:35:45 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Thu, 26 Jan 2006 18:31:04 +0100
Organization: <URL:http://purl.net/xyzzy>
Lines: 71
Message-ID: <43D90758.7229@xyzzy.claranet.de>
References: <E1F1qFn-0004h3-L8__29378.9512863897$1138217891$gmane$org@newodin.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 1cust143.tnt8.hbg2.deu.da.uu.net
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
Subject: Re: Protocol Action: 'LDAP: Internationalized String Preparation' to Proposed Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
The IESG wrote: > <draft-ietf-ldapbis-strprep-07.txt> as a Proposed Standard Mostly editorial nits: | presented and stored values are first prepared for comparison | and so that a character-by-character comparison yields the | "correct" result. s/and// (?) | The following six-step process SHALL be applied to each | presented and attribute value in preparation for character | string matching rule evaluation. s/and// (?) | The input string is be normalized to Unicode Form KC | (compatibility composed) as described in [UAX15]. s/is be/is/ Maybe s/KC/NFKC/ as used in 3454. Or better s/Form KC/NFKC/g (more than one occurence). | Characters which, per Section 5.8 of [Stringprep], change | display properties or are deprecated are prohibited. s/[Stringprep]/[RFC3454]/g Something with the indentation in appendices A and B is odd. | Otherwise, if the string being prepared is an initial, any, | or final substring, then the output string is exactly one | SPACE character, else the output string is exactly two | SPACEs. Apparently 'initial substring', 'any substring', and 'final substring' are terms here, and not simply the same as any substring, also used later in appendix B: | That is, if a prepared any substring matches a partition of | the attribute value, then an assertion constructed by | subdividing that substring into multiple substrings should | also match. How about quoting these terms: '"initial", "any", or "final substring"' in the first case, 'if a prepared "any substring" matches' in the second case (?) For an xml2rfc source that could be done with <spanx style="verb">any substring</spanx>. Actually only the unquoted "any" confused me, normally "any" should include initial and final. | All spaces are regarded as insignificant and are to be | removed. s/are to be// (?) More than one occurence. For the "Security Considerations" a note about mixing tables for different Unicode versions might help: RFC 3454 is 3.2, using an Unicode 5 table to figure out say "unassigned" might be a bad idea. | However, only leading and trailing (as well as multiple | consecutive spaces) of the string (as a whole) are | insignificant. s/consecutive spaces)/consecutive) spaces/ Bye, Frank _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Protocol Action: 'LDAP: Internationalized Str… Frank Ellermann
- Re: Protocol Action: 'LDAP: Internationalized Str… Kurt D. Zeilenga
- Re: Protocol Action: 'LDAP: Internationalized Str… Frank Ellermann