RFC 3698 on Lightweight Directory Access Protocol (LDAP): Additional Matching Rules
rfc-editor@rfc-editor.org Thu, 26 February 2004 20:05 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05960 for <ietf-announce-archive@odin.ietf.org>; Thu, 26 Feb 2004 15:05:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AwRZW-0003vM-Uw for ietf-announce-list@asgard.ietf.org; Thu, 26 Feb 2004 14:53:26 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AwRUB-0003m2-3S for all-ietf@asgard.ietf.org; Thu, 26 Feb 2004 14:47:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05138 for <all-ietf@ietf.org>; Thu, 26 Feb 2004 14:47:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwRU9-0004cQ-00 for all-ietf@ietf.org; Thu, 26 Feb 2004 14:47:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwRTP-0004Wk-00 for all-ietf@ietf.org; Thu, 26 Feb 2004 14:47:08 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AwRSg-0004Pc-00 for all-ietf@ietf.org; Thu, 26 Feb 2004 14:46:22 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1QJkMk03407; Thu, 26 Feb 2004 11:46:22 -0800 (PST)
Message-Id: <200402261946.i1QJkMk03407@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3698 on Lightweight Directory Access Protocol (LDAP): Additional Matching Rules
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 26 Feb 2004 11:46:22 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3698 Title: Lightweight Directory Access Protocol (LDAP): Additional Matching Rules Author(s): K. Zeilenga, Ed. Status: Standards Track Date: February 2004 Mailbox: Kurt@OpenLDAP.org Pages: 9 Characters: 17562 Updates: 2798 I-D Tag: draft-zeilenga-ldap-user-schema-mr-00.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3698.txt This document provides a collection of matching rules for use with the Lightweight Directory Access Protocol (LDAP). As these matching rules are simple adaptations of matching rules specified for use with the X.500 Directory, most are already in wide use. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.