idnits 2.17.1 draft-hoehrmann-cp-collation-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 15, 2010) is 4965 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Hoehrmann 3 Internet-Draft September 15, 2010 4 Intended status: Informational 5 Expires: March 19, 2011 7 The i;codepoint collation 8 draft-hoehrmann-cp-collation-01 10 Abstract 12 This memo describes the "i;codepoint" collation. Character strings 13 are compared based on the Unicode scalar values of the characters. 14 The collation supports equality, substring, and ordering operations. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on March 19, 2011. 33 Copyright Notice 35 Copyright (c) 2010 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 1. Introduction 50 The i;codepoint collation operates on Unicode strings and treats any 51 and all differences between two strings as significant. Ordering of 52 different strings is determined by the Unicode scalar values of the 53 characters. It produces usable results where further information is 54 unavailable. In that it is suitable as default collation. 56 The equality operation determines if two strings are identical. This 57 makes the collation suitable for use with strings known to be in some 58 canonical form. Similarily, applications that require strings to be 59 in a canonical but otherwise arbitrary order may find this collation 60 the most efficient as it requires no transformations. 62 2. Definition 64 The i;codepoint collation is the same as the i;octet collation except 65 that it operates on sequences of Unicode scalar values, not octets. 66 Note that by definition the set of Unicode scalar values excludes the 67 surrogate code points and as such they do not occur in valid input. 69 3. Security Considerations 71 None beyond those in RFC 4790 [RFC4790]. 73 4. IANA Considerations 75 This document defines the i;codepoint collation as per [RFC4790]. 77 5. Registration document 79 80 81 82 i;codepoint 83 Unicode identity 84 equality order substring 85 RFC XXXX 86 IETF 87 bjoern@hoehrmann.de 88 90 6. References 92 [RFC4790] Newman, C., Duerst, M., and A. Gulbrandsen, "Internet 93 Application Protocol Collation Registry", RFC 4790, 94 March 2007. 96 Author's Address 98 Bjoern Hoehrmann 99 Mittelstrasse 50 100 39114 Magdeburg 101 Germany 103 EMail: mailto:bjoern@hoehrmann.de 104 URI: http://bjoern.hoehrmann.de 106 Note: Please write "Bjoern Hoehrmann" with o-umlaut (U+00F6) wherever 107 possible, e.g., as "Björn Höhrmann" in HTML and XML.