A new Request for Comments is now available in online RFC libraries.
RFC 3771
Title: The Lightweight Directory Access Protocol (LDAP)
Intermediate Response Message
Author(s): R. Harrison, K. Zeilenga
Status: Standards Track
Date: April 2004
Mailbox: roger_harrison@novell.com, Kurt@OpenLDAP.org
Pages: 8
Characters: 17114
Updates: 2251
I-D Tag: draft-rharrison-ldap-intermediate-resp-01.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3771.txt
This document defines and describes the IntermediateResponse
message, a general mechanism for defining
single-request/multiple-response operations in Lightweight Directory
Access Protocol (LDAP). The IntermediateResponse message is defined
in such a way that the protocol behavior of existing LDAP
operations is maintained. This message is intended to be used in
conjunction with the LDAP ExtendedRequest and ExtendedResponse to
define new single-request/multiple-response operations or in
conjunction with a control when extending existing LDAP operations in
a way that requires them to return intermediate response information.
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.
- <ftp://ftp.isi.edu/in-notes/rfc3771.txt>
-
