One document matched: draft-klasen-ldap-facs-tel-number-matching-00.txt
Network Working Group N. Klasen
Internet-Draft Avinci
Updates: RFC2256 (if approved) May 2003
Expires: Oktober 30, 2003
LDAPv3: matching rules for facsimile Telephone numbers
draft-klasen-ldap-facs-tel-number-matching-00.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 Extensions Working Group
mailing list <ldapext@ietf.org>. Please send editorial comments
directly to the author <norbert.klasen@avinci.de>.
This Internet-Draft will expire on Oktober 30, 2003.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document defines an equality and 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
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Matching Rules . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 facsimileNumberMatch . . . . . . . . . . . . . . . . . . . . . 3
2.2 facsimileNumberSubstringsMatch . . . . . . . . . . . . . . . . 3
3. The facsimilefacsimileNumber Attribute Type . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
Normative References . . . . . . . . . . . . . . . . . . . . 5
Informative References . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . 7
Klasen Expires Oktober 30, 2003 [Page 2]
Internet-Draft facsimile telephone number matching May 2003
1. Introduction
LDAPv3 as defined in [RFC3377] is based on [ITU.X500.1993]. This
version of X.500 does not define any matching rules for the Facsimile
Telephone Number syntax. This omission has been corrected in a
Technical Corrigendum [ITU.X520.2001.TC.1] to [ITU.X520.2001]. This
document updates LDAPv3 accordingly by adding the two newly defined
matching rules and updating the facsimileTelephoneNumber attribute
type to use them.
2. Matching Rules
2.1 facsimileNumberMatch
The facsimileNumberMatch rule compares an assertion value of the
Telephone Number syntax to the first part of an attribute value of
the Facsimile Telephone Number syntax. The corresponding ASN.1 type
of this part is a PrintableString representing a telephone number.
The rule evaluates to TRUE if and only if the telephone-number part
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.22 )
The facsimileNumberMatch rule is an equality matching rule.
2.2 facsimileNumberSubstringsMatch
The facsimileNumberSubstringsMatch rule compares an assertion value
of the Substring Assertion syntax to the first part of an attribute
value of the Facsimile Telephone Number syntax. The corresponding
ASN.1 type of this part 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 telephone-number part
of the attribute value in the order of the substrings in the
assertion value, and an <initial> substring, if present, matches the
beginning of the attribute value, and a <final> 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.
Klasen Expires Oktober 30, 2003 [Page 3]
Internet-Draft facsimile telephone number matching May 2003
The LDAP definition for the facsimileNumberSubstringsMatch matching
rule is:
( 2.5.13.64 NAME 'facsimileNumberSubstringsMatch'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 )
The facsimileNumberSubstringsMatch rule is a substrings matching
rule.
3. The facsimilefacsimileNumber Attribute Type
A value of this Attribute Type is a facsimile 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 SYNTAX oid indicates the Facsimile Telephone Number syntax.
4. IANA Considerations
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 <norbert.klasen@avinci.de>
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 <norbert.klasen@avinci.de>
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 <norbert.klasen@avinci.de>
Usage: Attribute Type
Specification: RFC XXXX
Author/Change Controller: IESG
5. Security Considerations
Security considerations for LDAP are discussed in documents
comprising the technical specification [RFC3377].
6. Acknowledgements
This document borrows text from [I-D.ietf-ldapbis-syntaxes] and
[I-D.ietf-ldapbis-user-schema].
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.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 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.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
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 7]
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 8]
| PAFTECH AB 2003-2026 | 2026-04-23 10:01:00 |