Network Working Group N. Klasen Internet-Draft Avinci Updates: RFC2256 (if approved) May 2003 Expires: Oktober 30, 2003 LDAP: matching rules for facsimile telephone numbers draft-klasen-ldap-facs-tel-number-matching-01.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This document is intended to be, after appropriate review and revision, submitted to the RFC Editor as a Standards Track document. Distribution of this memo is unlimited. Technical discussion of this document will take place on the IETF LDAP Revision Working Group (LDAPbis) mailing list . Please send editorial comments directly to the author . This Internet-Draft will expire on Oktober 30, 2003. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract Based on changes to the 4th edition of X.500, this document updates the Lightweight Directory Access Protocol (LDAP). It defines an equality and a substrings matching rule for the 'Facsimile Telephone Number' syntax and updates the 'facsimileTelephoneNumber' attribute type to use them. Klasen Expires Oktober 30, 2003 [Page 1] Internet-Draft facsimile telephone number matching May 2003 Conventions used in this document Schema definitions are provided using LDAP description formats [RFC2252]. Definitions provided here are formatted (line wrapped) for readability. 1. Introduction The Lightweight Directory Access Protocol (LDAP) [RFC3377] is based on the 2nd edition of X.500 [ITU.X500.1993]. This edition of X.500 did not define any matching rules for the 'Facsimile Telephone Number' syntax. This omission was corrected by Technical Corrigendum 1 [ITU.X520.2001.TC.1] to the 4th edition of X.520 [ITU.X520.2001]. This document updates LDAP accordingly. It defines the 'facsimileNumberMatch' and 'facsimileNumberSubstringsMatch' matching rules and replaces section 5.24 of [RFC2256] by redefining the 'facsimileTelephoneNumber' attribute type to use them. 2. Schema Elements for Facsimile Telephone Numbers 2.1 'Facsimile Telephone Number' Syntax The 'FacsimileTelephoneNumber' ASN.1 type [ITU.X520.2001] specifies a telephone number for a facsimile terminal and optionally its parameters: FacsimileTelephoneNumber ::= SEQUENCE { telephoneNumber TelephoneNumber, parameters G3FacsimileNonBasicParameters OPTIONAL } TelephoneNumber ::= PrintableString (SIZE(1..ub-telephone-number)) -- String complying with ITU-T Rec. E.123 only The LDAP Syntax ('Facsimile Telephone Number' ) for this ASN.1 type is defined in [RFC2252]. Its LDAP specific string representation is given in by the following BNF: fax-number = printablestring [ "$" faxparameters ] faxparameters = faxparm / ( faxparm "$" faxparameters ) faxparm = "twoDimensional" / "fineResolution" / "unlimitedLength" / "b4Length" / "a3Width" / "b4Width" / "uncompressed" In the above, the printablestring is the 'telephoneNumber' and the faxparm tokens represent the fax 'parameters'. Klasen Expires Oktober 30, 2003 [Page 2] Internet-Draft facsimile telephone number matching May 2003 The matching rules defined in the following sections only act upon the 'telephoneNumber' component. So any characters in an attribute value which occur after the first '$' (and including the first '$') are ignored when matching. 2.2 'facsimileNumberMatch' Matching Rule The 'facsimileNumberMatch' rule compares an assertion value of the 'Telephone Number' syntax to the 'telephoneNumber' component of an attribute value of the 'Facsimile Telephone Number' syntax. The corresponding ASN.1 type of this component is a PrintableString representing a telephone number. The rule evaluates to TRUE if and only if the 'telephoneNumber' component of the attribute value and the assertion value have the same number of characters and corresponding characters are the same, ignoring the case of letters, and ignoring space and `-' characters. The LDAP definition for the 'facsimileNumberMatch' matching rule is: ( 2.5.13.63 NAME 'facsimileNumberMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 ) The 'facsimileNumberMatch' rule is an equality matching rule. The OID 1.3.6.1.4.1.1466.115.121.1.50 refers to the 'Telephone Number' syntax [RFC2252]. 2.3 'facsimileNumberSubstringsMatch' Matching Rule The 'facsimileNumberSubstringsMatch' rule compares an assertion value of the 'Substring Assertion' syntax to the first component of an attribute value of the 'Facsimile Telephone Number' syntax. The corresponding ASN.1 type of this component is a PrintableString representing a telephone number. The rule evaluates to TRUE if and only if the substrings of the assertion value match disjoint portions of the 'telephoneNumber' component of the attribute value in the order of the substrings in the assertion value, and an substring, if present, matches the beginning of the attribute value, and a substring, if present, matches the end of the attribute value. A substring matches a portion of the attribute value if corresponding characters are the same, ignoring the case of letters, and ignoring space and `-' characters. The LDAP definition for the 'facsimileNumberSubstringsMatch' matching rule is: Klasen Expires Oktober 30, 2003 [Page 3] Internet-Draft facsimile telephone number matching May 2003 ( 2.5.13.64 NAME 'facsimileNumberSubstringsMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 ) The 'facsimileNumberSubstringsMatch' rule is a substrings matching rule. The OID 1.3.6.1.4.1.1466.115.121.1.58 refers to the 'Substring Assertion' syntax [RFC2252]. 2.4 'facsimileTelephoneNumber' Attribute Type A value of this attribute type is a telephone number for a facsimile terminal and optionally its parameters. ( 2.5.4.23 NAME 'facsimileTelephoneNumber' EQUALITY facsimileNumberMatch SUBSTR facsimileNumberSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 ) The OID 1.3.6.1.4.1.1466.115.121.1.22 refers to the Facsimile Telephone Number Syntax [RFC2252]. 3. IANA Considerations This document make no OID assignments, it only associates LDAP schema descriptions with existing elements of X.500 schema. It is requested that the Internet Assigned Numbers Authority (IANA) update the LDAP descriptors registry as indicated in the following templates: Subject: Request for LDAP Descriptor Registration Descriptor (short name): facsimileNumberMatch Object Identifier: 2.5.13.63 Person & email address to contact for further information: Norbert Klasen Usage: Matching Rule Specification: RFC XXXX Author/Change Controller: IESG Subject: Request for LDAP Descriptor Registration Descriptor (short name): facsimileNumberSubstringsMatch Object Identifier: 2.5.13.64 Person & email address to contact for further information: Norbert Klasen Usage: Matching Rule Specification: RFC XXXX Author/Change Controller: IESG Klasen Expires Oktober 30, 2003 [Page 4] Internet-Draft facsimile telephone number matching May 2003 Subject: Request for LDAP Descriptor Registration Update Descriptor (short name): facsimileTelephoneNumber Object Identifier: 2.5.4.23 Person & email address to contact for further information: Norbert Klasen Usage: Attribute Type Specification: RFC XXXX Author/Change Controller: IESG 4. Security Considerations Security considerations for LDAP are discussed in documents comprising the technical specification [RFC3377]. 5. Acknowledgements This document borrows text from [I-D.ietf-ldapbis-syntaxes] and [I-D.ietf-ldapbis-user-schema]. This document is based upon input of the IETF LDAPBIS working group. The author wishes to thank S. Legg and K. Zeilenga for their contributions to this document. This document has been prepared using xml2rfc. Normative References [ITU.X520.2001] International Telecommunication Union, "Information Technology - Open Systems Interconnection - The Directory: Authentication Framework", ITU-T Recommendation X.520, 2001. [ITU.X520.2001.TC.1] International Telecommunication Union, "Information Technology - Open Systems Interconnection - The Directory: Authentication Framework - Technical Corrigendum 1", ITU-T Recommendation X.520 Technical Cor.1, 2002. [RFC2252] Wahl, M., Coulbeck, A., Howes, T. and S. Kille, "Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 2252, December 1997. [RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use with LDAPv3", RFC 2256, December 1997. [RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access Protocol (v3): Technical Specification", RFC 3377, September 2002. Klasen Expires Oktober 30, 2003 [Page 5] Internet-Draft facsimile telephone number matching May 2003 Informative References [I-D.ietf-ldapbis-syntaxes] Dally, K. and S. Legg, "LDAP: Syntaxes and Matching Rules", draft-ietf-ldapbis-syntaxes-05 (work in progress), March 2003. [I-D.ietf-ldapbis-user-schema] Dally, K., "LDAP: User Schema", draft-ietf-ldapbis-user-schema-05 (work in progress), May 2003. [ITU.E123.1988] International Telecommunication Union, "Notation for national and international telephone numbers", ITU-T Recommendation E.123, November 1988. [ITU.X500.1993] International Telecommunication Union, "Information Technology - Open Systems Interconnection - The Directory: Overview of Concepts, Models and Services", ITU-T Recommendation X.500, 1993. Author's Address Norbert Klasen Avinci Region West GmbH Halskestr. 38 40880 Ratingen Germany Phone: +49 2102 124 500 Fax: +49 2102 124 555 EMail: norbert.klasen@avinci.de URI: http://www.avinci.biz Klasen Expires Oktober 30, 2003 [Page 6] Internet-Draft facsimile telephone number matching May 2003 Appendix A. Examples Take as example the following entry: dn: o=avinci,c=de objectclass: organization o: avinci facsimileTelephoneNumber: +49 2102 124 555 $fineResolution$a3Width Now, searching for (facsimileTelephoneNumber=+49-2102-124-555) would match this entry, as o only the telephoneNumber component, ie. '+49 2102 124 555 ' of the attribute value is taken into account o and the assertion value '+49-2102-124-555' matches '+49 2102 124 555 ' according to the telephone number matching rule, ie. ignoring the case of letters, and ignoring space and '-' characters. Likewise, the entry specified above would be matched by the following filter which uses the substring matching rule: (facsimileTelephoneNumber=*-555) Appendix B. Change Log B.1 Changes from -00 o Added section reiterating the Facsimile Telephone Number syntax. o Corrected OIDs for assertion syntaxes in definition of matching rules. o Added examples. o Various editorial updates. Klasen Expires Oktober 30, 2003 [Page 7] Internet-Draft facsimile telephone number matching May 2003 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (C) The Internet Society (2003). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Klasen Expires Oktober 30, 2003 [Page 8] Internet-Draft facsimile telephone number matching May 2003 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Klasen Expires Oktober 30, 2003 [Page 9]