BCP 64, RFC 3383 on Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)

[rfc-editor@rfc-editor.org]

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


        BCP 64
        RFC 3383

        Title:	    Internet Assigned Numbers Authority (IANA)
                    Considerations for the Lightweight Directory
                    Access Protocol (LDAP) 
        Author(s):  K. Zeilenga
        Status:	    Best Current Practice
	Date:       September 2002
        Mailbox:    Kurt@OpenLDAP.org
        Pages:      22
        Characters: 45893
        SeeAlso:    BCP 64

        I-D Tag:    draft-ietf-ldapbis-iana-09.txt

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


This document provides procedures for registering extensible elements
of the Lightweight Directory Access Protocol (LDAP).  This document
also provides guidelines to the Internet Assigned Numbers Authority
(IANA) describing conditions under which new values can be assigned.

This document is a product of the LDAP (v3) Revision Working Group of
the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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/rfc3383.txt>