3383
BEST CURRENT PRACTICE
Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP) (Obsoleted)
Authors: K. Zeilenga
Date: September 2002
Area: app
Working Group: ldapbis
Stream: IETF
Obsoleted by:
RFC 4520
RFC 3383
Obsoleted by: 4520 BEST CURRENT PRACTICE
Network Working Group K. Zeilenga
Request for Comments: 3383 OpenLDAP Foundation
BCP: 64 September 2002
Category: Best Current Practice
<span class="h1">Internet Assigned Numbers Authority (IANA) Considerations</span>
<span class="h1">for the Lightweight Directory Access Protocol (LDAP)</span>
Status of this Memo
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.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract
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.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Lightweight Directory Access Protocol (LDAP) [<a href="./rfc3377" title=""Lightweight Directory Access Protocol (v3): Technical Specification"">RFC3377</a>] is an
extensible protocol. LDAP supports:
- addition of new operations,
- extension of existing operations, and
- extensible schema.
This document details procedures for registering values of used to
unambiguously identify extensible elements of the protocol including:
- LDAP message types;
- LDAP extended operations and controls;
- LDAP result codes;
- LDAP authentication methods;
- LDAP attribute description options; and
- Object Identifier descriptors.
These registries are maintained by the Internet Assigned Numbers
Authority (IANA).
<span class="grey">Zeilenga Best Current Practice [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
In addition, this document provides guidelines to IANA describing the
conditions under which new values can be assigned.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology and Conventions</span>
This section details terms and conventions used in this document.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Policy Terminology</span>
The terms "IESG Approval", "Standards Action", "IETF Consensus",
"Specification Required", "First Come First Served", "Expert Review",
and "Private Use" are used as defined in <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a> [<a href="./rfc2434" title="">RFC2434</a>].
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Requirement Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. In
this case, "the specification" as used by <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> refers to the
processing of protocols being submitted to the IETF standards
process.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Common ABNF Productions</span>
A number of syntaxes in this document are described using ABNF
[<a href="./rfc2234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC2234</a>]. These syntaxes rely on the following common productions:
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
LDIGIT = %x31-39 ; 1-9
DIGIT = %x30 / LDIGIT ; 0-9
HYPHEN = %x2D ; "-"
DOT = %x2E ; "."
number = DIGIT / ( LDIGIT 1*DIGIT )
keychar = ALPHA / DIGIT / HYPHEN
leadkeychar = ALPHA
keystring = leadkeychar *keychar
A keyword is a case-insensitive string of UTF-8 [<a href="./rfc2279" title=""UTF-8, a transformation format of ISO 10646"">RFC2279</a>] encoded
characters from the Universal Character Set (UCS) [<a href="#ref-ISO10646">ISO10646</a>]
restricted to the <keystring> production.
<span class="grey">Zeilenga Best Current Practice [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations for LDAP</span>
This section details each kind of protocol value which can be
registered and provides IANA guidelines on how to assign new values.
IANA may reject obviously bogus registration requests.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Object Identifiers</span>
Numerous LDAP schema and protocol elements are identified by Object
Identifiers. Specifications which assign OIDs to elements SHOULD
state who delegated the OIDs for its use.
For IETF developed elements, specifications SHOULD use OIDs under
"Internet Directory Numbers" (1.3.6.1.1.x). Numbers under this OID
arc will be assigned upon Expert Review with Specification Required.
Only one OID per specification will be assigned. The specification
MAY then assign any number of OIDs within this arc without further
coordination with IANA.
For elements developed by others, any properly delegated OID can
be used, including those under "Internet Private Enterprise
Numbers" (1.3.6.1.4.1.x) assigned by IANA
<<a href="http://www.iana.org/cgi-bin/enterprise.pl">http://www.iana.org/cgi-bin/enterprise.pl</a>>.
To avoid interoperability problems between early implementations of
"works in progress" and implementations of the published
specification (e.g., the RFC), experimental OIDs SHOULD be used in
"works in progress" and early implementations. OIDs under the
Internet Experimental OID arc (1.3.6.1.3.x) may be used for this
purpose.
Experimental OIDs are not to used in published specifications (e.g.,
RFCs).
Practices for IANA assignment of Internet Enterprise and Experimental
OIDs are detailed in STD 16 [<a href="./rfc1155" title=""Structure and Identification of Management Information for TCP/IP-based Internets"">RFC1155</a>].
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Protocol Mechanisms</span>
LDAP provides a number of Root DSE attributes for discovery of
protocol mechanisms identified by OIDs, including:
- supportedControl [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>] and
- supportedExtension [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>].
<span class="grey">Zeilenga Best Current Practice [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
A registry of OIDs used for discover of protocol mechanisms is
provided to allow implementors and others to locate the technical
specification for these protocol mechanisms. Future specifications
of additional Root DSE attributes holding values identifying protocol
mechanisms MAY extend this registry for their values.
OIDs associated with discoverable protocol mechanisms SHOULD be
registered. These are be considered on a First Come First Served
with Specification Required basis.
OIDs associated with Standard Track mechanisms MUST be registered and
require Standards Action.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Object Identifier Descriptors</span>
LDAP allows short descriptive names (or descriptors) to be used
instead of a numeric Object Identifier to identify protocol
extensions [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>], schema elements [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>], LDAP URL [<a href="./rfc2255" title=""The LDAP URL Format"">RFC2255</a>]
extensions, and other objects. Descriptors are restricted to strings
of UTF-8 encoded UCS characters restricted by the following ABNF:
name = keystring
Descriptors are case-insensitive.
Multiple names may be assigned to a given OID. For purposes of
registration, an OID is to be represented in numeric OID form
conforming to the ABNF:
numericoid = number *( DOT number ) ; e.g., 1.1.0.23.40
While the protocol places no maximum length restriction upon
descriptors, they should be short. Descriptors longer than 48
characters may be viewed as too long to register.
A values ending with a hyphen ("-") reserve all descriptors which
start with the value. For example, the registration of the option
"descrFamily-" reserves all options which start with "descrFamily-"
for some related purpose.
Descriptors beginning with "x-" are for Private Use and cannot be
registered.
Descriptors beginning with "e-" are reserved for experiments and will
be registered on a First Come First Served basis.
All other descriptors require Expert Review to be registered.
<span class="grey">Zeilenga Best Current Practice [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
The registrant need not "own" the OID being named.
The OID namespace is managed by The ISO/IEC Joint Technical Committee
1 - Subcommittee 6.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. AttributeDescription Options</span>
An AttributeDescription [RFC2251, <a href="#section-4.1.5">Section 4.1.5</a>] can contain zero or
more options specifying additional semantics. An option SHALL be
restricted to a string UTF-8 encoded UCS characters limited by the
following ABNF:
option = keystring
Options are case-insensitive.
While the protocol places no maximum length restriction upon option
strings, they should be short. Options longer than 24 characters may
be viewed as too long to register.
Values ending with a hyphen ("-") reserve all option names which
start with the name. For example, the registration of the option
"optionFamily-" reserves all options which start with "optionFamily-"
for some related purpose.
Options beginning with "x-" are for Private Use and cannot be
registered.
Options beginning with "e-" are reserved for experiments and will be
registered on a First Come First Served basis.
All other options require Standards Action or Expert Review with
Specification Required to be registered.
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. LDAP Message Types</span>
Each protocol message is encapsulated in an LDAPMessage envelope
[RFC2251, <a href="#section-4.1.1">Section 4.1.1</a>]. The protocolOp CHOICE indicates the type
of message encapsulated. Each message type consists of a keyword and
a non-negative choice number is combined with the class (APPLICATION)
and data type (CONSTRUCTED or PRIMITIVE) to construct the BER tag in
the message's encoding. The choice numbers for existing protocol
messages are implicit in the protocol's ASN.1 defined in [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>].
New values will be registered upon Standards Action.
Note: LDAP provides extensible messages which reduces, but does not
eliminate, the need to add new message types.
<span class="grey">Zeilenga Best Current Practice [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. LDAP Result Codes</span>
LDAP result messages carry an resultCode enumerated value to indicate
the outcome of the operation [RFC2251, <a href="#section-4.1.10">Section 4.1.10</a>]. Each result
code consists of a keyword and a non-negative integer.
New resultCodes integers in the range 0-1023 require Standards Action
to be registered. New resultCode integers in the range 1024-4095
require Expert Review with Specification Required. New resultCode
integers in the range 4096-16383 will be registered on a First Come
First Served basis. Keywords associated with integers in the range
0-4095 SHALL NOT start with "e-" or "x-". Keywords associated with
integers in the range 4096-16383 SHALL start with "e-". Values
greater than or equal to 16384 and keywords starting with "x-" are
for Private Use and cannot be registered.
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. LDAP Authentication Method</span>
The LDAP Bind operation supports multiple authentication methods
[RFC2251, <a href="#section-4.2">Section 4.2</a>]. Each authentication choice consists of a
keyword and a non-negative integer.
The registrant SHALL classify the authentication method usage using
one of the following terms:
COMMON - method is appropriate for common use on the
Internet,
LIMITED USE - method is appropriate for limited use,
OBSOLETE - method has been deprecated or otherwise found to be
inappropriate for any use.
Methods without publicly available specifications SHALL NOT be
classified as COMMON. New registrations of class OBSOLETE cannot be
registered.
New authentication method integers in the range 0-1023 require
Standards Action to be registered. New authentication method
integers in the range 1024-4095 require Expert Review with
Specification Required. New authentication method integers in the
range 4096-16383 will be registered on a First Come First Served
basis. Keywords associated with integers in the range 0-4095 SHALL
NOT start with "e-" or "x-". Keywords associated with integers in
the range 4096-16383 SHALL start with "e-". Values greater than or
equal to 16384 and keywords starting with "x-" are for Private Use
and cannot be registered.
Note: LDAP supports SASL [<a href="./rfc2222" title=""Simple Authentication and Security Layer (SASL)"">RFC2222</a>] as an Authentication CHOICE.
SASL is an extensible LDAP authentication method.
<span class="grey">Zeilenga Best Current Practice [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Directory Systems Names</span>
The IANA-maintained "Directory Systems Names" registry [<a href="#ref-IANADSN" title=""Directory Systems Names"">IANADSN</a>] of
valid keywords for well known attributes used in the LDAPv2 string
representation of a distinguished name [<a href="./rfc1779" title=""A String Representation of Distinguished Names"">RFC1779</a>]. <a href="./rfc1779">RFC 1779</a> was
obsoleted by <a href="./rfc2253">RFC 2253</a>.
Directory systems names are not known to be used in any other
context. LDAPv3 uses Object Identifier Descriptors [<a href="#section-3.2">Section 3.2</a>]
(which have a different syntax than directory system names).
New Directory System Names will no longer be accepted. For
historical purposes, the current list of registered names should
remain publicly available.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Registration Procedure</span>
The procedure given here MUST be used by anyone who wishes to use a
new value of a type described in <a href="#section-3">Section 3</a> of this document.
The first step is for the requester to fill out the appropriate form.
Templates are provided in <a href="#appendix-A">Appendix A</a>.
If the policy is Standards Action, the completed form SHOULD be
provided to the IESG with the request for Standards Action. Upon
approval of the Standards Action, the IESG SHALL forward the request
(possibly revised) to IANA. The IESG SHALL be viewed as the owner of
all values requiring Standards Action.
If the policy is Expert Review, the requester SHALL post the
completed form to the <directory@apps.ietf.org> mailing list for
public review. The review period is two (2) weeks. If a revised
form is later submitted, the review period is restarted. Anyone
may subscribe to this list by sending a request to
<directory-request@apps.ietf.org>. During the review, objections
may be raised by anyone (including the Expert) on the list. After
completion of the review, the Expert, based upon public comments,
SHALL either approve the request and forward it to the IESG OR deny
the request. In either case, the Expert SHALL promptly notify the
requester of the action. Actions of the Expert may be appealed
[<a href="./rfc2026" title=""The Internet Standards Process -- Revision 3"">RFC2026</a>]. The Expert is appointed by Applications Area Director(s).
The requester is viewed as the owner of values registered under
Expert Review.
If the policy is First Come First Served, the requester SHALL submit
the completed form directly to the IANA: <iana@iana.org>. The
requester is viewed as the owner of values registered under First
Come First Served.
<span class="grey">Zeilenga Best Current Practice [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
Neither the Expert nor IANA will take position on the claims of
copyright or trademarks issues regarding completed forms.
Prior to submission of the Internet Draft (I-D) to the RFC Editor but
after IESG review and tentative approval, the document editor SHOULD
revise the I-D to use registered values.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Registration Maintenance</span>
This section discusses maintenance of registrations.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Lists of Registered Values</span>
IANA makes lists of registered values readily available to the
Internet community on their web site: <<a href="http://www.iana.org/">http://www.iana.org/</a>>.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Change Control</span>
The registration owner MAY update the registration subject to the
same constraints and review as with new registrations. In cases
where the owner is not unable or unwilling to make necessary updates,
the IESG MAY assert ownership in order to update the registration.
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Comments</span>
For cases where others (anyone other than the owner) have significant
objections to the claims in a registration and the owner does not
agree to change the registration, comments MAY be attached to a
registration upon Expert Review. For registrations owned by the
IESG, the objections SHOULD be addressed by initiating a request for
Expert Review.
The form of these requests is ad hoc, but MUST include the specific
objections to be reviewed and SHOULD contain (directly or by
reference) materials supporting the objections.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
The security considerations detailed in [<a href="./rfc2434" title="">RFC2434</a>] are generally
applicable to this document. Additional security considerations
specific to each namespace are discussed in <a href="#section-3">Section 3</a> where
appropriate.
Security considerations for LDAP are discussed in documents
comprising the technical specification [<a href="./rfc3377" title=""Lightweight Directory Access Protocol (v3): Technical Specification"">RFC3377</a>].
<span class="grey">Zeilenga Best Current Practice [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgment</span>
This document is a product of the IETF LDAP Revision (LDAPbis)
Working Group. Some text was borrowed from "Guidelines for Writing
an IANA Considerations Section in RFCs" [<a href="./rfc2434" title="">RFC2434</a>] by Thomas Narten
and Harald Alvestrand.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span>
[<a id="ref-RFC1155">RFC1155</a>] Rose, M. and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD
16, <a href="./rfc1155">RFC 1155</a>, May 1990.
[<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process -- Revision
3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2234">RFC2234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", <a href="./rfc2234">RFC 2234</a>, November 1997.
[<a id="ref-RFC2251">RFC2251</a>] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory
Access Protocol (v3)", <a href="./rfc2251">RFC 2251</a>, December 1997.
[<a id="ref-RFC2252">RFC2252</a>] Wahl, M., Coulbeck, A., Howes, T. and S. Kille,
"Lightweight Directory Access Protocol (v3): Attribute
Syntax Definitions", <a href="./rfc2252">RFC 2252</a>, December 1997.
[<a id="ref-RFC2255">RFC2255</a>] Howes, T. and M. Smith, "The LDAP URL Format", <a href="./rfc2255">RFC 2255</a>,
December, 1997.
[<a id="ref-RFC2256">RFC2256</a>] Wahl, M., "A Summary of the X.500(96) User Schema for use
with LDAPv3", <a href="./rfc2256">RFC 2256</a>, December 1997.
[<a id="ref-RFC2279">RFC2279</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", <a href="./rfc2279">RFC 2279</a>, January 1998.
[<a id="ref-RFC2434">RFC2434</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>,
October 1998.
[<a id="ref-RFC3377">RFC3377</a>] Hodges, J. and R. Morgan, "Lightweight Directory Access
Protocol (v3): Technical Specification", <a href="./rfc3377">RFC 3377</a>,
September 2002.
[<a id="ref-IANADSN">IANADSN</a>] IANA, "Directory Systems Names",
<a href="http://www.iana.org/assignments/directory-system-names">http://www.iana.org/assignments/directory-system-names</a>
<span class="grey">Zeilenga Best Current Practice [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
[<a id="ref-ISO10646">ISO10646</a>] Universal Multiple-Octet Coded Character Set (UCS) -
Architecture and Basic Multilingual Plane, ISO/IEC
10646-1: 1993.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Informative References</span>
[<a id="ref-RFC1779">RFC1779</a>] Kille, S., "A String Representation of Distinguished
Names", <a href="./rfc1779">RFC 1779</a>, March 1995.
[<a id="ref-RFC2222">RFC2222</a>] Myers, J., "Simple Authentication and Security Layer
(SASL)", <a href="./rfc2222">RFC 2222</a>, October 1997.
<span class="grey">Zeilenga Best Current Practice [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Registration Templates</span>
This appendix provides registration templates for registering new
LDAP values.
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. LDAP Object Identifier Registration Template</span>
Subject: Request for LDAP OID Registration
Person & email address to contact for further information:
Specification: (I-D)
Author/Change Controller:
Comments:
(Any comments that the requester deems relevant to the request)
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. LDAP Protocol Mechanism Registration Template</span>
Subject: Request for LDAP Protocol Mechanism Registration
Object Identifier:
Description:
Person & email address to contact for further information:
Usage: (One of Control or Extension)
Specification: (I-D)
Author/Change Controller:
Comments:
(Any comments that the requester deems relevant to the request)
<span class="grey">Zeilenga Best Current Practice [Page 11]</span><span id="page-12" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>. LDAP Descriptor Registration Template</span>
Subject: Request for LDAP Descriptor Registration
Descriptor (short name):
Object Identifier:
Person & email address to contact for further information:
Usage: (One of attribute type, URL extension,
object class, or other)
Specification: (RFC, I-D, URI)
Author/Change Controller:
Comments:
(Any comments that the requester deems relevant to the request)
<span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a>. LDAP Attribute Description Option Registration Template</span>
Subject: Request for LDAP Attribute Description Option Registration
Option Name:
Family of Options: (YES or NO)
Person & email address to contact for further information:
Specification: (RFC, I-D, URI)
Author/Change Controller:
Comments:
(Any comments that the requester deems relevant to the request)
<span class="grey">Zeilenga Best Current Practice [Page 12]</span><span id="page-13" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h3"><a class="selflink" id="appendix-A.5" href="#appendix-A.5">A.5</a>. LDAP Message Type Registration Template</span>
Subject: Request for LDAP Message Type Registration
LDAP Message Name:
Person & email address to contact for further information:
Specification: (Approved I-D)
Comments:
(Any comments that the requester deems relevant to the request)
<span class="h3"><a class="selflink" id="appendix-A.6" href="#appendix-A.6">A.6</a>. LDAP Result Code Registration Template</span>
Subject: Request for LDAP Result Code Registration
Result Code Name:
Person & email address to contact for further information:
Specification: (RFC, I-D, URI)
Author/Change Controller:
Comments:
(Any comments that the requester deems relevant to the request)
<span class="h3"><a class="selflink" id="appendix-A.7" href="#appendix-A.7">A.7</a>. LDAP Authentication Method Registration Template</span>
Subject: Request for LDAP Authentication Method Registration
Authentication Method Name:
Person & email address to contact for further information:
Specification: (RFC, I-D, URI)
Intended Usage: (One of COMMON, LIMITED-USE, OBSOLETE)
Author/Change Controller:
Comments:
(Any comments that the requester deems relevant to the request)
<span class="grey">Zeilenga Best Current Practice [Page 13]</span><span id="page-14" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Assigned Values</span>
The following values are currently assigned.
<span class="h3"><a class="selflink" id="appendix-B.1" href="#appendix-B.1">B.1</a>. Object Identifiers</span>
Currently registered "Internet Private Enterprise Numbers" can be
found at <<a href="http://www.iana.org/assignments/enterprise-numbers">http://www.iana.org/assignments/enterprise-numbers</a>>.
Currently registered "Internet Directory Numbers" can be found at
<<a href="http://www.iana.org/assignments/smi-numbers">http://www.iana.org/assignments/smi-numbers</a>>.
<span class="h3"><a class="selflink" id="appendix-B.2" href="#appendix-B.2">B.2</a>. Protocol Mechanisms</span>
Object Identifier Type Description Reference
-------------------------- ---- -------------- ---------
<span class="h6"><a class="selflink" id="section-1.2.840.113556.1.4.473" href="#section-1.2.840.113556.1.4.473">1.2.840.113556.1.4.473</a> C </span> Sort Request [<a href="./rfc2891">RFC2891</a>]
<span class="h6"><a class="selflink" id="section-1.2.840.113556.1.4.474" href="#section-1.2.840.113556.1.4.474">1.2.840.113556.1.4.474</a> C </span> Sort Response [<a href="./rfc2891">RFC2891</a>]
<span class="h6"><a class="selflink" id="section-1.3.6.1.4.1.1466.101.119.1" href="#section-1.3.6.1.4.1.1466.101.119.1">1.3.6.1.4.1.1466.101.119.1</a> E </span> Dynamic Refresh [<a href="./rfc2589">RFC2589</a>]
<span class="h6"><a class="selflink" id="section-1.3.6.1.4.1.1466.20037" href="#section-1.3.6.1.4.1.1466.20037">1.3.6.1.4.1.1466.20037</a> E </span> Start TLS [<a href="./rfc2830">RFC2830</a>]
<span class="h6"><a class="selflink" id="section-1.3.6.1.4.1.4203.1.11.1" href="#section-1.3.6.1.4.1.4203.1.11.1">1.3.6.1.4.1.4203.1.11.1</a> E </span> Modify Password [<a href="./rfc3062">RFC3062</a>]
<span class="h6"><a class="selflink" id="section-2.16.840.1.113730.3.4.2" href="#section-2.16.840.1.113730.3.4.2">2.16.840.1.113730.3.4.2</a> C </span> ManageDsaIT [<a href="./rfc3296">RFC3296</a>]
Legend
------------------------
C => supportedControl
E => supportedExtension
<span class="h3"><a class="selflink" id="appendix-B.3" href="#appendix-B.3">B.3</a>. Object Identifier Descriptors</span>
NAME Type OID [REF]
------------------------ ---- -----------------
account O 0.9.2342.19200300.100.4.5 [<a href="./rfc1274">RFC1274</a>]
alias O 2.5.6.1 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
aliasedEntryName A 2.5.4.1 [X.501]
aliasedObjectName A 2.5.4.1 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
altServer A 1.3.6.1.4.1.1466.101.120.6 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
applicationEntity O 2.5.6.12 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
applicationProcess O 2.5.6.11 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
aRecord A 0.9.2342.19200300.100.1.26 [<a href="./rfc1274">RFC1274</a>]
associatedDomain A 0.9.2342.19200300.100.1.37 [<a href="./rfc1274">RFC1274</a>]
associatedInternetGateway A 1.3.6.1.4.1.453.7.2.8 [<a href="./rfc2164">RFC2164</a>]
associatedName A 0.9.2342.19200300.100.1.38 [<a href="./rfc1274">RFC1274</a>]
associatedORAddress A 1.3.6.1.4.1.453.7.2.6 [<a href="./rfc2164">RFC2164</a>]
associatedX400Gateway A 1.3.6.1.4.1.453.7.2.3 [<a href="./rfc2164">RFC2164</a>]
attributeTypes A 2.5.21.5 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
audio A 0.9.2342.19200300.100.1.55 [<a href="./rfc1274">RFC1274</a>]
authorityRevocationList A 2.5.4.38 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
<span class="grey">Zeilenga Best Current Practice [Page 14]</span><span id="page-15" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
bitStringMatch M 2.5.13.16 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
buildingName A 0.9.2342.19200300.100.1.48 [<a href="./rfc1274">RFC1274</a>]
businessCategory A 2.5.4.15 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
C A 2.5.4.6 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
cACertificate A 2.5.4.37 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
calCalAdrURI A 1.2.840.113556.1.4.481 [<a href="./rfc2739">RFC2739</a>]
calCalURI A 1.2.840.113556.1.4.478 [<a href="./rfc2739">RFC2739</a>]
calCAPURI A 1.2.840.113556.1.4.480 [<a href="./rfc2739">RFC2739</a>]
calEntry O 1.2.840.113556.1.5.87 [<a href="./rfc2739">RFC2739</a>]
calFBURL A 1.2.840.113556.1.4.479 [<a href="./rfc2739">RFC2739</a>]
calOtherCalAdrURIs A 1.2.840.113556.1.4.485 [<a href="./rfc2739">RFC2739</a>]
calOtherCalURIs A 1.2.840.113556.1.4.482 [<a href="./rfc2739">RFC2739</a>]
calOtherCAPURIs A 1.2.840.113556.1.4.484 [<a href="./rfc2739">RFC2739</a>]
calOtherFBURLs A 1.2.840.113556.1.4.483 [<a href="./rfc2739">RFC2739</a>]
caseExactIA5Match M 1.3.6.1.4.1.1466.109.114.1 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
caseIgnoreIA5Match M 1.3.6.1.4.1.1466.109.114.2 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
caseIgnoreListMatch M 2.5.13.11 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
caseIgnoreMatch M 2.5.13.2 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
caseIgnoreOrderingMatch M 2.5.13.3 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
caseIgnoreSubstringsMatch M 2.5.13.4 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
certificateRevocationList A 2.5.4.39 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
certificationAuthority O 2.5.6.16 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
certificationAuthority-V2 O 2.5.6.16.2 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
CN A 2.5.4.3 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
cNAMERecord A 0.9.2342.19200300.100.1.31 [<a href="./rfc1274">RFC1274</a>]
co A 0.9.2342.19200300.100.1.43 [<a href="./rfc1274">RFC1274</a>]
commonName A 2.5.4.3 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
country O 2.5.6.2 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
countryName A 2.5.4.6 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
createTimestamp A 2.5.18.1 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
creatorsName A 2.5.18.3 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
cRLDistributionPoint O 2.5.6.19 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
crossCertificatePair A 2.5.4.40 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
DC A 0.9.2342.19200300.100.1.25 [<a href="./rfc2247">RFC2247</a>]
dcObject O 1.3.6.1.4.1.1466.344 [<a href="./rfc2247">RFC2247</a>]
deltaCRL O 2.5.6.23 [<a href="./rfc2587">RFC2587</a>]
deltaRevocationList A 2.5.4.53 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
description A 2.5.4.13 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
destinationIndicator A 2.5.4.27 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
device O 2.5.6.14 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
distinguishedName A 2.5.4.49 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
distinguishedNameMatch M 2.5.13.1 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
distinguishedNameTableEntry O 1.3.6.1.4.1.453.7.1.5 [<a href="./rfc2293">RFC2293</a>]
distinguishedNameTableKey A 1.3.6.1.4.1.453.7.2.3 [<a href="./rfc2293">RFC2293</a>]
dITContentRules A 2.5.21.2 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
dITRedirect A 0.9.2342.19200300.100.1.54 [<a href="./rfc1274">RFC1274</a>]
dITStructureRules A 2.5.21.1 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
dmd O 2.5.6.20 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
<span class="grey">Zeilenga Best Current Practice [Page 15]</span><span id="page-16" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
dmdName A 2.5.4.54 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
dnQualifier A 2.5.4.46 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
dNSDomain O 0.9.2342.19200300.100.4.15 [<a href="./rfc1274">RFC1274</a>]
document O 0.9.2342.19200300.100.4.6 [<a href="./rfc1274">RFC1274</a>]
documentAuthor A 0.9.2342.19200300.100.1.14 [<a href="./rfc1274">RFC1274</a>]
documentIdentifier A 0.9.2342.19200300.100.1.11 [<a href="./rfc1274">RFC1274</a>]
documentLocation A 0.9.2342.19200300.100.1.15 [<a href="./rfc1274">RFC1274</a>]
documentPublisher A 0.9.2342.19200300.100.1.56 [<a href="./rfc1274">RFC1274</a>]
documentSeries O 0.9.2342.19200300.100.4.8 [<a href="./rfc1274">RFC1274</a>]
documentTitle A 0.9.2342.19200300.100.1.12 [<a href="./rfc1274">RFC1274</a>]
documentVersion A 0.9.2342.19200300.100.1.13 [<a href="./rfc1274">RFC1274</a>]
domain O 0.9.2342.19200300.100.4.13 [<a href="./rfc2247">RFC2247</a>]
domainComponent A 0.9.2342.19200300.100.1.25 [<a href="./rfc2247">RFC2247</a>]
domainNameForm N 1.3.6.1.4.1.1466.345 [<a href="./rfc2247">RFC2247</a>]
domainRelatedObject O 0.9.2342.19200300.100.4.17 [<a href="./rfc1274">RFC1274</a>]
drink A 0.9.2342.19200300.100.1.5 [<a href="./rfc1274">RFC1274</a>]
dSA O 2.5.6.13 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
dSAQuality A 0.9.2342.19200300.100.1.49 [<a href="./rfc1274">RFC1274</a>]
dynamicObject O 1.3.6.1.4.1.1466.101.119.2 [<a href="./rfc2589">RFC2589</a>]
dynamicSubtrees A 1.3.6.1.4.1.1466.101.119.4 [<a href="./rfc2589">RFC2589</a>]
enhancedSearchGuide A 2.5.4.47 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
entryTtl A 1.3.6.1.4.1.1466.101.119.3 [<a href="./rfc2589">RFC2589</a>]
extensibleObject O 1.3.6.1.4.1.1466.101.120.111 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
facsimileTelephoneNumber A 2.5.4.23 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
favouriteDrink A 0.9.2342.19200300.100.1.5 [<a href="./rfc1274">RFC1274</a>]
friendlyCountry O 0.9.2342.19200300.100.4.18 [<a href="./rfc1274">RFC1274</a>]
friendlyCountryName A 0.9.2342.19200300.100.1.43 [<a href="./rfc1274">RFC1274</a>]
generalizedTimeMatch M 2.5.13.27 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
generalizedTimeOrderingMatch M 2.5.13.28 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
generationQualifier A 2.5.4.44 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
givenName A 2.5.4.42 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
GN A 2.5.4.42 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
groupOfNames O 2.5.6.9 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
groupOfUniqueNames O 2.5.6.17 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
homePhone A 0.9.2342.19200300.100.1.20 [<a href="./rfc1274">RFC1274</a>]
homePostalAddress A 0.9.2342.19200300.100.1.39 [<a href="./rfc1274">RFC1274</a>]
homeTelephone A 0.9.2342.19200300.100.1.20 [<a href="./rfc1274">RFC1274</a>]
host A 0.9.2342.19200300.100.1.9 [<a href="./rfc1274">RFC1274</a>]
houseIdentifier A 2.5.4.51 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
info A 0.9.2342.19200300.100.1.4 [<a href="./rfc1274">RFC1274</a>]
initials A 2.5.4.43 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
integerFirstComponentMatch M 2.5.13.29 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
integerMatch M 2.5.13.14 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
internationaliSDNNumber A 2.5.4.25 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
janetMailbox A 0.9.2342.19200300.100.1.46 [<a href="./rfc1274">RFC1274</a>]
jpegPhoto A 0.9.2342.19200300.100.1.60 [<a href="./rfc1488">RFC1488</a>]
knowledgeInformation A 2.5.4.2 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
L A 2.5.4.7 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
<span class="grey">Zeilenga Best Current Practice [Page 16]</span><span id="page-17" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
labeledURI A 1.3.6.1.4.1.250.1.57 [<a href="./rfc2079">RFC2079</a>]
labeledURIObject A 1.3.6.1.4.1.250.3.15 [<a href="./rfc2079">RFC2079</a>]
lastModifiedBy A 0.9.2342.19200300.100.1.24 [<a href="./rfc1274">RFC1274</a>]
lastModifiedTime A 0.9.2342.19200300.100.1.23 [<a href="./rfc1274">RFC1274</a>]
ldapSyntaxes A 1.3.6.1.4.1.1466.101.120.16 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
locality O 2.5.6.3 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
localityName A 2.5.4.7 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
mail A 0.9.2342.19200300.100.1.3 [<a href="./rfc2798">RFC2798</a>]
mailPreferenceOption A 0.9.2342.19200300.100.1.47 [<a href="./rfc1274">RFC1274</a>]
manager A 0.9.2342.19200300.100.1.10 [<a href="./rfc1274">RFC1274</a>]
matchingRules A 2.5.21.4 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
matchingRuleUse A 2.5.21.8 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
mcgamTables A 1.3.6.1.4.1.453.7.2.9 [<a href="./rfc2164">RFC2164</a>]
mDRecord A 0.9.2342.19200300.100.1.27 [<a href="./rfc1274">RFC1274</a>]
member A 2.5.4.31 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
mixerGateway O 1.3.6.1.4.1.453.7.1.4 [<a href="./rfc2164">RFC2164</a>]
mobile A 0.9.2342.19200300.100.1.41 [<a href="./rfc1274">RFC1274</a>]
mobileTelephoneNumber A 0.9.2342.19200300.100.1.41 [<a href="./rfc1274">RFC1274</a>]
modifiersName A 2.5.18.4 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
modifyTimestamp A 2.5.18.2 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
mXRecord A 0.9.2342.19200300.100.1.28 [<a href="./rfc1274">RFC1274</a>]
name A 2.5.4.41 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
nameForms A 2.5.21.7 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
namingContexts A 1.3.6.1.4.1.1466.101.120.5 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
nSRecord A 0.9.2342.19200300.100.1.29 [<a href="./rfc1274">RFC1274</a>]
numericStringMatch M 2.5.13.8 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
numericStringSubstringsMatch M 2.5.13.10 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
O A 2.5.4.10 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
objectClass A 2.5.4.0 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
objectClasses A 2.5.21.6 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
objectIdentifierFirstComponentMatch M 2.5.13.30 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
objectIdentifiersMatch M 2.5.13.0 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
octetStringMatch M 2.5.13.17 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
omittedORAddressComponent O 1.3.6.1.4.1.453.7.1.3 [<a href="./rfc2164">RFC2164</a>]
oRAddressComponentType A 1.3.6.1.4.1.453.7.2.7 [<a href="./rfc2164">RFC2164</a>]
organization O 2.5.6.4 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
organizationalPerson O 2.5.6.7 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
organizationalRole O 2.5.6.8 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
organizationalStatus A 0.9.2342.19200300.100.1.45 [<a href="./rfc1274">RFC1274</a>]
organizationalUnit O 2.5.6.5 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
organizationalUnitName A 2.5.4.11 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
organizationName A 2.5.4.10 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
otherMailbox A 0.9.2342.19200300.100.1.22 [<a href="./rfc1274">RFC1274</a>]
OU A 2.5.4.11 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
owner A 2.5.4.32 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
pager A 0.9.2342.19200300.100.1.42 [<a href="./rfc1274">RFC1274</a>]
pagerTelephoneNumber A 0.9.2342.19200300.100.1.42 [<a href="./rfc1274">RFC1274</a>]
person O 2.5.6.6 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
<span class="grey">Zeilenga Best Current Practice [Page 17]</span><span id="page-18" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
personalSignature A 0.9.2342.19200300.100.1.53 [<a href="./rfc1274">RFC1274</a>]
personalTitle A 0.9.2342.19200300.100.1.40 [<a href="./rfc1274">RFC1274</a>]
photo A 0.9.2342.19200300.100.1.7 [<a href="./rfc1274">RFC1274</a>]
physicalDeliveryOfficeName A 2.5.4.19 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
pilotDSA O 0.9.2342.19200300.100.4.21 [<a href="./rfc1274">RFC1274</a>]
pilotObject O 0.9.2342.19200300.100.4.3 [<a href="./rfc1274">RFC1274</a>]
pilotOrganization O 0.9.2342.19200300.100.4.20 [<a href="./rfc1274">RFC1274</a>]
pilotPerson O 0.9.2342.19200300.100.4.4 [<a href="./rfc1274">RFC1274</a>]
pkiCA O 2.5.6.22 [<a href="./rfc2587">RFC2587</a>]
pkiUser O 2.5.6.21 [<a href="./rfc2587">RFC2587</a>]
postalAddress A 2.5.4.16 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
postalCode A 2.5.4.17 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
postOfficeBox A 2.5.4.18 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
preferredDeliveryMethod A 2.5.4.28 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
presentationAddress A 2.5.4.29 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
presentationAddressMatch M 2.5.13.22 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
protocolInformation A 2.5.4.48 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
protocolInformationMatch M 2.5.13.24 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
qualityLabelledData O 0.9.2342.19200300.100.4.22 [<a href="./rfc1274">RFC1274</a>]
ref A 2.16.840.1.113730.3.1.34 [<a href="./rfc3296">RFC3296</a>]
referral 0 2.16.840.1.113730.3.2.6 [<a href="./rfc3296">RFC3296</a>]
registeredAddress A 2.5.4.26 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
residentialPerson O 2.5.6.10 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
RFC822LocalPart O 0.9.2342.19200300.100.4.14 [<a href="./rfc1274">RFC1274</a>]
RFC822Mailbox A 0.9.2342.19200300.100.1.3 [<a href="./rfc1274">RFC1274</a>]
rFC822ToX400Mapping O 1.3.6.1.4.1.453.7.1.1 [<a href="./rfc2164">RFC2164</a>]
roleOccupant A 2.5.4.33 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
room O 0.9.2342.19200300.100.4.7 [<a href="./rfc1274">RFC1274</a>]
roomNumber A 0.9.2342.19200300.100.1.6 [<a href="./rfc1274">RFC1274</a>]
searchGuide A 2.5.4.14 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
secretary A 0.9.2342.19200300.100.1.21 [<a href="./rfc1274">RFC1274</a>]
seeAlso A 2.5.4.34 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
serialNumber A 2.5.4.5 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
simpleSecurityObject O 0.9.2342.19200300.100.4.19 [<a href="./rfc1274">RFC1274</a>]
singleLevelQuality A 0.9.2342.19200300.100.1.50 [<a href="./rfc1274">RFC1274</a>]
SN A 2.5.4.4 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
sOARecord A 0.9.2342.19200300.100.1.30 [<a href="./rfc1274">RFC1274</a>]
ST A 2.5.4.8 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
stateOrProvinceName A 2.5.4.8 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
street A 2.5.4.9 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
streetAddress A 2.5.4.9 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
strongAuthenticationUser O 2.5.6.15 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
subschema O 2.5.20.1 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
subschemaSubentry A 2.5.18.10 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
subtree O 1.3.6.1.4.1.453.7.1.1 [<a href="./rfc2293">RFC2293</a>]
subtreeMaximumQuality A 0.9.2342.19200300.100.1.52 [<a href="./rfc1274">RFC1274</a>]
subtreeMinimumQuality A 0.9.2342.19200300.100.1.51 [<a href="./rfc1274">RFC1274</a>]
supportedAlgorithms A 2.5.4.52 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
<span class="grey">Zeilenga Best Current Practice [Page 18]</span><span id="page-19" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
supportedApplicationContext A 2.5.4.30 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
supportedControl A 1.3.6.1.4.1.1466.101.120.13 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
supportedExtension A 1.3.6.1.4.1.1466.101.120.7 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
supportedLDAPVersion A 1.3.6.1.4.1.1466.101.120.15 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
supportedSASLMechanisms A 1.3.6.1.4.1.1466.101.120.14 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
surname A 2.5.4.4 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
table O 1.3.6.1.4.1.453.7.1.2 [<a href="./rfc2293">RFC2293</a>]
tableEntry O 1.3.6.1.4.1.453.7.1.3 [<a href="./rfc2293">RFC2293</a>]
telephoneNumber A 2.5.4.20 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
telephoneNumberMatch M 2.5.13.20 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
telephoneNumberSubstringsMatch M 2.5.13.21 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
teletexTerminalIdentifier A 2.5.4.22 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
telexNumber A 2.5.4.21 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
textEncodedORAddress A 0.9.2342.19200300.100.1.2 [<a href="./rfc1274">RFC1274</a>]
textTableEntry O 1.3.6.1.4.1.453.7.1.4 [<a href="./rfc2293">RFC2293</a>]
textTableKey A 1.3.6.1.4.1.453.7.2.1 [<a href="./rfc2293">RFC2293</a>]
textTableValue A 1.3.6.1.4.1.453.7.2.2 [<a href="./rfc2293">RFC2293</a>]
title A 2.5.4.12 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
top O 2.5.6.0 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
uid A 0.9.2342.19200300.100.1.1 [<a href="./rfc2253">RFC2253</a>]
uniqueIdentifier A 0.9.2342.19200300.100.1.44 [<a href="./rfc1274">RFC1274</a>]
uniqueMember A 2.5.4.50 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
uniqueMemberMatch M 2.5.13.23 [<a href="./rfc2252" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">RFC2252</a>]
userCertificate A 2.5.4.36 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
userClass A 0.9.2342.19200300.100.1.8 [<a href="./rfc1274">RFC1274</a>]
userId A 0.9.2342.19200300.100.1.1 [<a href="./rfc1274">RFC1274</a>]
userPassword A 2.5.4.35 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
userSecurityInformation O 2.5.6.18 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
x121Address A 2.5.4.24 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
x400ToRFC822Mapping O 1.3.6.1.4.1.453.7.1.2 [<a href="./rfc2164">RFC2164</a>]
x500UniqueIdentifier A 2.5.4.45 [<a href="./rfc2256" title=""A Summary of the X.500(96) User Schema for use with LDAPv3"">RFC2256</a>]
Legend
------------------------
A => Attribute Type
C => DIT Content Rule
E => LDAP URL Extension
M => Matching Rule
N => Name Form
O => Object Class
<span class="grey">Zeilenga Best Current Practice [Page 19]</span><span id="page-20" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h3"><a class="selflink" id="appendix-B.4" href="#appendix-B.4">B.4</a>. Attribute Description Options</span>
Option Owner Reference
---------------- ----- ---------
binary IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
lang-* IESG [<a href="./rfc2596">RFC2596</a>]
* family of options
<span class="h3"><a class="selflink" id="appendix-B.5" href="#appendix-B.5">B.5</a>. LDAPMessage types</span>
Name Code Owner Reference
--------------------------- ---- ----- ---------
bindRequest 0 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
bindResponse 1 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
unbindRequest 2 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
searchRequest 3 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
searchResEntry 4 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
searchResDone 5 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
modifyRequest 6 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
modifyResponse 7 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
addRequest 8 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
addResponse 9 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
delRequest 10 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
delResponse 11 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
modDNRequest 12 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
modDNResponse 13 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
compareRequest 14 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
compareResponse 15 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
abandonRequest 16 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved 17-18 IESG
searchResRef 19 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved 20-22 IESG
extendedReq 23 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
extendedResp 24 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
<span class="h3"><a class="selflink" id="appendix-B.6" href="#appendix-B.6">B.6</a>. resultCode values</span>
Name Code Owner Reference
--------------------------- ---- ----- ---------
success 0 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
operationsError 1 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
protocolError 2 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
timeLimitExceeded 3 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
sizeLimitExceeded 4 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
compareFalse 5 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
compareTrue 6 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
authMethodNotSupported 7 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
<span class="grey">Zeilenga Best Current Practice [Page 20]</span><span id="page-21" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
strongAuthRequired 8 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved (partialResults) 9 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
referral 10 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
adminLimitExceeded 11 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
unavailableCriticalExtension 12 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
confidentialityRequired 13 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
saslBindInProgress 14 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
noSuchAttribute 16 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
undefinedAttributeType 17 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
inappropriateMatching 18 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
constraintViolation 19 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
attributeOrValueExists 20 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
invalidAttributeSyntax 21 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
noSuchObject 32 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
aliasProblem 33 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
invalidDNSyntax 34 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved (isLeaf) 35 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
aliasDereferencingProblem 36 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved 37-47 IESG
inappropriateAuthentication 48 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
invalidCredentials 49 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
insufficientAccessRights 50 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
busy 51 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
unavailable 52 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
unwillingToPerform 53 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
loopDetect 54 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved 55-63 IESG
namingViolation 64 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
objectClassViolation 65 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
notAllowedOnNonLeaf 66 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
notAllowedOnRDN 67 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
entryAlreadyExists 68 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
objectClassModsProhibited 69 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved (resultsTooLarge) 70 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved 71-79 IESG
other 80 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
reserved (APIs) 81-90 IESG [<a href="./rfc2251" title=""Lightweight Directory Access Protocol (v3)"">RFC2251</a>]
<span class="grey">Zeilenga Best Current Practice [Page 21]</span><span id="page-22" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
<span class="h3"><a class="selflink" id="appendix-B.7" href="#appendix-B.7">B.7</a>. Bind Authentication Method</span>
Method Value Owner Usage Reference
------ ----- ----- ----------- -----------------
simple 0 IESG LIMITED USE [RFC2251,<a href="./rfc2829">RFC2829</a>]
krbv42LDAP 1 IESG OBSOLETE* [<a href="./rfc1777">RFC1777</a>]
krbv42DSA 2 IESG OBSOLETE* [<a href="./rfc1777">RFC1777</a>]
sasl 3 IESG COMMON [RFC2251,<a href="./rfc2829">RFC2829</a>]
* These LDAPv2-only mechanisms were deprecated in favor of the
LDAPv3 SASL authentication method, specifically the GSSAPI mechanism.
Author's Address
Kurt D. Zeilenga
OpenLDAP Foundation
EMail: [email protected]
<span class="grey">Zeilenga Best Current Practice [Page 22]</span><span id="page-23" ></span>
<span class="grey"><a href="./rfc3383">RFC 3383</a> IANA Considerations for LDAP September 2002</span>
Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Zeilenga Best Current Practice [Page 23]
Annotations
Select text to annotate