[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RFC 4515 on Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters
A new Request for Comments is now available in online RFC libraries.
RFC 4515
Title: Lightweight Directory Access Protocol (LDAP):
String Representation of Search Filters
Author: M. Smith, Ed., T. Howes
Status: Standards Track
Date: June 2006
Mailbox: mcs@pearlcrescent.com,
howes@opsware.com
Pages: 12
Characters: 23885
Obsoletes: RFC2254
See-Also:
I-D Tag: draft-ietf-ldapbis-filter-09.txt
URL: http://www.rfc-editor.org/rfc/rfc4515.txt
Lightweight Directory Access Protocol (LDAP) search filters are
transmitted in the LDAP protocol using a binary representation that is
appropriate for use on the network. This document defines a
human-readable string representation of LDAP search filters that is
appropriate for use in LDAP URLs (RFC 4516) and in other applications.
[STANDARDS TRACK]
This document is a product of the LDAP (v3) Revision
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: 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.
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
...