[rfc-dist] RFC 3672 on Subentries in the Lightweight Directory Access Protocol (LDAP)

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Wed, 24 Dec 2003 12:44:11 -0800


A new Request for Comments is now available in online RFC libraries.

        RFC 3672

        Title:      Subentries in the Lightweight Directory Access
                    Protocol (LDAP)
        Author(s):  K. Zeilenga, S. Legg
        Status:     Standards Track
        Date:       December 2003
        Mailbox:    Kurt@OpenLDAP.org, steven.legg@adacel.com.au
        Pages:      12
        Characters: 24447
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-zeilengaldap-subentry-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3672.txt

In X.500 directories, subentries are special entries used to hold
information associated with a subtree or subtree refinement.  This
document adapts X.500 subentries mechanisms for use with the
Lightweight Directory Access Protocol (LDAP).

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

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.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

Content-Type: text/plain
Content-ID: <031224124310.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3672

Content-Type:   Message/External-body;

Content-Type: text/plain
Content-ID: <031224124310.RFC@RFC-EDITOR.ORG>