[rfc-dist] RFC 3671 on Collective Attributes in the Lightweight Directory Access Protocol (LDAP)

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Wed, 24 Dec 2003 12:42:52 -0800


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

        RFC 3671

        Title:      Collective Attributes in
                    the Lightweight Directory Access Protocol (LDAP)
        Author(s):  K. Zeilenga
        Status:     Standards Track
        Date:       December 2003
        Mailbox:    Kurt@OpenLDAP.org
        Pages:      10
        Characters: 17912
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-zeilenga-ldap-collective-08.txt

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

X.500 collective attributes allow common characteristics to be shared
between collections of entries.  This document summarizes the X.500
information model for collective attributes and describes use of
collective attributes in LDAP (Lightweight Directory Access Protocol).
This document provides schema definitions for collective attributes
for use in 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: <031224124146.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3671

Content-Type:   Message/External-body;

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