draft-ietf-ldapbis-iana-00.txt   draft-ietf-ldapbis-iana-01.txt 
INTERNET-DRAFT Editor: Kurt D. Zeilenga INTERNET-DRAFT Editor: Kurt D. Zeilenga
Intended Category: BCP OpenLDAP Foundation Intended Category: BCP OpenLDAP Foundation
Expires: 1 October 2001 1 April 2001 Expires: 10 October 2001 10 April 2001
IANA Considerations for LDAP IANA Considerations for LDAP
<draft-ietf-ldapbis-iana-00.txt> <draft-ietf-ldapbis-iana-01.txt>
Status of Memo Status of Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
This document is intended to be, after appropriate review and This document is intended to be, after appropriate review and
revision, submitted to the RFC Editor as a Best Current Practice revision, submitted to the RFC Editor as a Best Current Practice
document. Distribution of this memo is unlimited. Technical document. Distribution of this memo is unlimited. Technical
discussion of this document will take place on the IETF LDAP Revision discussion of this document will take place on the IETF LDAP Revision
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>.
Copyright 2001, The Internet Society. All Rights Reserved. Copyright 2001, The Internet Society. All Rights Reserved.
Please see the Copyright section near the end of this document for Please see the Copyright section near the end of this document for
more information. more information.
Abstract Abstract
This document provides procedures for registering extensible elements This document provides procedures for registering extensible elements
of LDAP. The document also provides guidelines to IANA describing of LDAP. The document also provides guidelines to IANA describing
conditions under which new values can be assigned. conditions under which new values can be assigned.
1. Introduction 1. Introduction
The Lightweight Directory Access Protocol [RFC2251] (LDAP) is an The Lightweight Directory Access Protocol [LDAPTS] (LDAP) is an
extensible protocol. LDAP supports: extensible protocol. LDAP supports:
- addition of new operations, - addition of new operations,
- extension of existing operations, and - extension of existing operations, and
- extensible schema. - extensible schema.
This document details procedures for registering values of used to This document details procedures for registering with values of used
unambiguously identify extensible elements of the protocol with IANA to unambiguously identify extensible elements of the protocol
including: including:
- LDAP message types, - LDAP message types,
- LDAP result codes, - LDAP result codes,
- LDAP authentication methods, - LDAP authentication methods,
- LDAP attribute description options, and - LDAP attribute description options, and
- Object Identifiers descriptive names - Object Identifiers descriptive names.
This document also provides guidelines to IANA describing the These registries are maintained by the Internet Assigned Numbers
Authority (IANA).
In addition, this document provides guidelines to IANA describing the
conditions under which new values can be assigned. conditions under which new values can be assigned.
2. Terms and Conventions 2. Terminology and Conventions
This section details terms and conventions are used in this document. This section details terms and conventions are used in this document.
2.1. Policy terms 2.1. Policy Terminology
The terms "IESG Approval", "Standards Action", "IETF Consensus", The terms "IESG Approval", "Standards Action", "IETF Consensus",
"Specification Required", "First Come First Served", "Expert Review", "Specification Required", "First Come First Served", "Expert Review",
and "Private Use" are used as defined in [RFC2434]. and "Private Use" are used as defined in [RFC2434].
2.2. Requirement terms 2.2. Requirement Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2.3. Common ABNF productions 2.3. Common ABNF Productions
A number of syntaxes in this document are described using ABNF A number of syntaxes in this document are described using ABNF
[RFC2324]. These syntaxes rely on the following common productions: [RFC2234]. These syntaxes rely on the following common productions:
a = %x41-5A / %61-7A ; A-Z / a-z ALPHA = %x41-5A / %61-7A ; A-Z / a-z
ld = %x31-39 ; 1-9 LDIGIT = %x31-39 ; 1-9
d = %x30 / ld ; 0-9
hyphen = %x2D ; "-" DIGIT = %x30 / ld ; 0-9
period = %x2E ; "." HYPHEN = %x2D ; "-"
keychar = ( a / d / hyphen ) PERIOD = %x2E ; "."
leadkeychar = ( a / d )
number = DIGIT / ( LDIGIT 1*DIGIT )
keychar = ( ALPHA / DIGIT / HYPHEN )
leadkeychar = ALPHA
keystring = leadkeychar *keychar keystring = leadkeychar *keychar
A keyword is case-insensitive UTF-8 [RFC2279] string restricted to the A keyword is case-insensitive UTF-8 [RFC2279] string restricted to the
keystring production. keystring production.
3. IANA Considerations for LDAP 3. IANA Considerations for LDAP
This section details each of the types of protocol values which can be This section details each kind of protocol values which can be
registered and provides IANA guidelines on how to assign new values. registered and provides IANA guidelines on how to assign new values.
3.1. Object Identifiers Descriptive Names 3.1. Object Identifiers
Numerous LDAP schema and protocol elements are identified by Object
Identifiers. Any properly delegated OID may be used including those
under "Internet Private Enterprise Numbers" (1.3.5.1.4.1.x) assigned
by IANA <http://www.iana.org/cgi-bin/enterprise.pl>.
For IETF developed protocol and schema items, OIDS under "Internet
Directory Numbers" (1.3.6.1.1.x) MAY be used. IANA will assign
numbers under this OID arc upon Expert Review with Specification
Required. In general, only one OID per specification SHOULD be
assigned. The specification may then assign any number of OIDs within
this arc without further coordination with IANA.
3.2. Object Identifiers Descriptive Names
LDAP allows short descriptive names to be used instead of an numeric LDAP allows short descriptive names to be used instead of an numeric
Object Identifier to identify protocol extensions [RFC2251], schema Object Identifier to identify protocol extensions [RFC2251], schema
elements [RFC2252], protocol extensions, LDAP URL [RFC2255] elements [RFC2252], protocol extensions, LDAP URL [RFC2255]
extensions, and other objects. These names SHALL be restricted to extensions, and other objects. These names SHALL be restricted to
case-insensitive UTF-8 strings limited by the following ABNF: case-insensitive UTF-8 strings limited by the following ABNF:
name = keystring name = keystring
Multiple names MAY be assigned to a given OID. For purposes of Multiple names MAY be assigned to a given OID. For purposes of
registration, an OID SHALL be represented in numeric OID form registration, an OID SHALL be represented in numeric OID form
conforming to the ABNF: conforming to the ABNF:
numericoid = number *( period number ) ; e.g. 1.1.23.4 numericoid = number *( PERIOD number ) ; e.g. 1.1.0.23.40
number = d / ( ld 1*d )
While the protocol places no maximum length restriction upon While the protocol places no maximum length restriction upon
descriptive names, they SHOULD be short. IANA MAY refuse to register descriptive names, they SHOULD be short. IANA MAY refuse to register
any name over 48 characters in length. IANA MAY reject obviously any name over 48 characters in length. IANA MAY reject obviously
bogus registrations. bogus registrations.
Names beginning with "x-" are for Private Use. IANA SHALL NOT Names beginning with "x-" are for Private Use and SHALL NOT be
register any name beginning with "x-". registered.
Names beginning with "e-" are reserved for experiments. IANA SHALL Names beginning with "e-" are reserved for experiments. IANA SHALL
register any name beginning with "e-" on a First Come First Served register any name beginning with "e-" on a First Come First Served
basis. basis.
Expert Review is REQUIRED before accepting registration of all other Expert Review is REQUIRED before accepting registration of all other
names. names.
IANA SHALL NOT verify the registrant "owns" the OID being named. IANA SHALL NOT verify the registrant "owns" the OID being named.
The OID namespace is managed by The ISO/IEC Joint Technical Committee The OID namespace is managed by The ISO/IEC Joint Technical Committee
1 - Subcommittee 6. 1 - Subcommittee 6.
3.2. AttributeDescription Options 3.3. AttributeDescription Options
An AttributeDescription [RFC2251, Section 4.1.5] can contain zero or An AttributeDescription [RFC2251, Section 4.1.5] can contain zero or
options specifying additional semantics. An option SHALL be options specifying additional semantics. An option SHALL be
restricted to case-insensitive UTF-8 string limited by the following restricted to case-insensitive UTF-8 string limited by the following
ABNF: ABNF:
option = keystring option = keystring
While the protocol places no maximum length restriction upon option While the protocol places no maximum length restriction upon option
strings, they SHOULD be short. IANA MAY refuse to register any option strings, they SHOULD be short. IANA MAY refuse to register any option
over 16 characters in length. IANA MAY reject obviously bogus over 16 characters in length. IANA MAY reject obviously bogus
registrations. registrations.
Values ending with a hyphen ("-") reserve all option names which start Values ending with a hyphen ("-") reserve all option names which start
with the name. For example, the registration of the option with the name. For example, the registration of the option
"optionFamily-" reserves all options which start with "optionFamily-" "optionFamily-" reserves all options which start with "optionFamily-"
for some related purpose. for some related purpose.
Options beginning with "x-" are for Private Use. IANA SHALL NOT Options beginning with "x-" are for Private Use and SHALL NOT
register any option beginning with "x-". registered.
Options beginning with "e-" are reserved for experiments. IANA SHALL Options beginning with "e-" are reserved for experiments. IANA SHALL
register any option beginning with "e-" on a First Come First Served register any option beginning with "e-" on a First Come First Served
basis. basis.
IANA SHALL register other options by either Standards Action or Expert IANA SHALL register other options by either Standards Action or Expert
Review with Specification Required. Review with Specification Required.
3.3. LDAP Message Types 3.4. LDAP Message Types
Each protocol message is encapsulated in an LDAPMessage envelope Each protocol message is encapsulated in an LDAPMessage envelope
[RFC2251, Section 4.1.1]. The protocolOp CHOICE indicates the type of [RFC2251, Section 4.1.1]. The protocolOp CHOICE indicates the type of
message encapsulated. Each message type consists of a keyword and a message encapsulated. Each message type consists of a keyword and a
non-negative choice number is combined with the class (APPLICATION) non-negative choice number is combined with the class (APPLICATION)
and data type (CONSTRUCTED or PRIMITIVE) to construct the BER tag in and data type (CONSTRUCTED or PRIMITIVE) to construct the BER tag in
the message's encoding. The choice numbers for existing protocol the message's encoding. The choice numbers for existing protocol
messages are implicit in the protocol's ASN.1 defined in [RFC2251]. messages are implicit in the protocol's ASN.1 defined in [RFC2251].
New values SHALL only be registered by Standards Track action. New values SHALL only be registered by Standards Track action.
Note: LDAP provides extensible messages which reduces, but does not Note: LDAP provides extensible messages which reduces, but does not
eliminate, the need to add new message types. eliminate, the need to add new message types.
3.4. LDAP Result Codes 3.5. LDAP Result Codes
LDAP result messages carry an resultCode enumerated value to indicate LDAP result messages carry an resultCode enumerated value to indicate
the outcome of the operation [RFC2251, Section 4.1.10]. Each result the outcome of the operation [RFC2251, Section 4.1.10]. Each result
code consists of a keyword and a non-negative integer. code consists of a keyword and a non-negative integer.
IANA SHALL register resultCode integers from 0-255 upon Standards IANA SHALL register new resultCode integers in the range 0-255 upon
Action, 256-1023 with Expert Review, and 1024-8191 on a First Come Standards Action, in the range 256-1023 with Expert Review, and in the
First Served basis. Keywords associated with integers in the range range 1024-8191 on a First Come First Served basis. Keywords
1024-8191 SHALL start with "e-". IANA MAY reject obviously bogus associated with integers in the range 1024-8191 SHALL start with "e-".
registrations. Values greater than or equal to 8192 are for Private Use and SHALL NOT
be registered.
Values greater than or equal to 8192 are for Private Use. IANA MAY reject obviously bogus registrations.
3.5. LDAP Authentication Method 3.6. LDAP Authentication Method
The LDAP Bind operation supports multiple authentication methods The LDAP Bind operation supports multiple authentication methods
[RFC2251, Section 4.2]. Each authentication choice consists of a [RFC2251, Section 4.2]. Each authentication choice consists of a
keyword and a non-negative integer. keyword and a non-negative integer.
Authentication methods usage SHALL be classified using one of the Authentication methods usage SHALL be classified using one of the
following terms: following terms:
COMMON - method is appropriate for common use on the Internet, COMMON - method is appropriate for common use on the Internet,
LIMITED USE - method is appropriate for limited uses. LIMITED USE - method is appropriate for limited use.
OBSOLETE - method has been deprecated or other found to be OBSOLETE - method has been deprecated or otherwise found to be
inappropriate for any use. inappropriate for any use.
IANA SHALL NOT register new OBSOLETE mechanisms. Methods without IANA SHALL NOT register new OBSOLETE authentication methods. Methods
publicly available specifications SHALL NOT be classified as COMMON. without publicly available specifications SHALL NOT be classified as
COMMON. IANA MAY reject obviously bogus registrations.
IANA SHALL register authentication method integers from 0-255 upon
Standards Action, 256-1023 with Expert Review with Specification
Required, and 1024-8191 on a First Come First Served basis. Keywords
associated with integers in the range 1024-8191 SHALL start with "e-".
IANA MAY reject obviously bogus registrations.
Values greater than or equal to 8192 are for Private Use. IANA SHALL register new authentication method integers in the range
0-255 upon Standards Action, in the range 256-1023 with Expert Review
with Specification Required, and in the range 1024-8191 on a First
Come First Served basis. Keywords associated with integers in the
range 1024-8191 SHALL start with "e-". Values greater than or equal
to 8192 are for Private Use and SHALL NOT be registered.
Note: LDAP supports SASL [RFC2222] as an Authentication CHOICE. SASL Note: LDAP supports SASL [RFC2222] as an Authentication CHOICE. SASL
is an extensible LDAP authentication method. is an extensible LDAP authentication method.
Developers of new authentication methods are SHOULD seek appropriate
review.
3.6. Other values?
Other LDAP name spaces?
4. Registration Procedure 4. Registration Procedure
The procedure given here MUST be used by anyone who to use a new value The procedure given here MUST be used by anyone who to use a new value
of a type described in Section 3 of this document which is not of a type described in Section 3 of this document which is not
currently registered with IANA. currently registered with IANA.
The first step is for the request to fill out the appropriate form. The first step is for the request to fill out the appropriate form.
Templates are provided in Appendix A. Templates are provided in Appendix A.
If the policy is Standards Action, the completed form SHOULD be If the policy is Standards Action, the completed form SHOULD be
provided to the IESG with the request for Standards Action. Upon provided to the IESG with the request for Standards Action. Upon
approval of the Standards Action, the IESG SHALL forward the request approval of the Standards Action, the IESG SHALL forward the request
(possibly revised) to IANA. (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 If the policy is Expert Review, the requester SHALL post the completed
form to the <directory@apps.ietf.org> mailing list for public review. 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 The review period is two (2) weeks. If a revised form is later
submitted, the review period is restarted. Anyone may subscribe to submitted, the review period is restarted. Anyone may subscribe to
this list my sending a request to <directory-request@apps.ietf.org>. this list my sending a request to <directory-request@apps.ietf.org>.
During the review, objections may be raised by anyone (including the During the review, objections may be raised by anyone (including the
Expert) on the list. After completion of the review, the Expert, Expert) on the list. After completion of the review, the Expert,
based upon public comments, SHALL either approve the request and based upon public comments, SHALL either approve the request and
forward it to the IESG OR deny the request. In either case, the forward it to the IESG OR deny the request. In either case, the
Expert SHALL promptly notify the requester of the action . Actions of Expert SHALL promptly notify the requester of the action . Actions of
the Expert may be appealed [RFC2026]. The Expert is appointed by the Expert may be appealed [RFC2026]. The Expert is appointed by
Applications Area Director(s). Applications Area Director(s). The requestor is viewed is the owner
of values registered under Expert Review, but the IESG MAY assert
ownership in cases where the owner is not willing or able to make
necessary updates.
If the policy is First Come First Served, the requester SHALL submit If the policy is First Come First Served, the requester SHALL submit
the completed form directly to the IESG <iesg@iesg.org>. the completed form directly to the IESG <iesg@iesg.org>. The
requestor is viewed is the owner of values registered under First Come
First Served, but the IESG MAY assert ownership in cases where the
owner is not willing or able to make necessary updates.
5. Registration Maintenance 5. Registration Maintenance
This section needs to be flushed out. This section discusses maintenance of registrations.
5.1. Location of List of Registered Values 5.1. Lists of Registered Values
5.2. Comments IANA makes lists of registered values readily available to the
Internet community on their web site <http://www.iana.org/>.
5.3. Change Control 5.2. Change Control
The registration owner MAY update the specification subject to the
same constraints and review as with new registrations.
5.3. Comments
For cases where others have significant objectiions to the claims in a
registration and the author does not agree to change the registration,
comments MAY be attached to registrations after Expert Review. For
registrations owned by the IESG, the objections SHOULD be addressed by
initiating a Change Control request.
6. Security Considerations 6. Security Considerations
The security considerations detailed in [RFC2434] are generally The security considerations detailed in [RFC2434] are generally
applicable to this document. Security considerations to each applicable to this document. Security considerations to each
namespace are discussed in Section 3. namespace are discussed in Section 3.
Security considerations for LDAP are detailed in documents comprising
the technical specification [LDAPTS].
7. Acknowledgment 7. Acknowledgment
This document is a product of the IETF LDAP Revision (LDAPbis) WG. This document is a product of the IETF LDAP Revision (LDAPbis) WG.
Some text was borrowed from "Guidelines for Writing an IANA
Considerations Section in RFCs" [RFC2434] by Thomas Narten and Harald
Alvestrand.
8. Author's Address 8. Author's Address
Kurt D. Zeilenga Kurt D. Zeilenga
OpenLDAP Foundation OpenLDAP Foundation
Email: Kurt@OpenLDAP.org Email: Kurt@OpenLDAP.org
9. References 9. References
[RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3",
RFC 2026, October 1996.
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC2222] J. Myers, "Simple Authentication and Security Layer (SASL)",
RFC 2222, October 1997.
[RFC2234] D. Crocker, P. Overell, "Augmented BNF for Syntax [RFC2234] D. Crocker, P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
[RFC2279] F. Yergeau, "UTF-8, a transformation format of ISO 10646",
RFC 2279, January 1998.
[RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access [RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access
Protocol (v3)", RFC 2251, December 1997. Protocol (v3)", RFC 2251, December 1997.
[RFC2252] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight [RFC2252] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight
Directory Access Protocol (v3): Attribute Syntax Directory Access Protocol (v3): Attribute Syntax
Definitions", RFC 2252, December 1997. Definitions", RFC 2252, December 1997.
[RFC2255] T. Howes, M. Smith, "The LDAP URL Format", RFC 2255, [RFC2255] T. Howes, M. Smith, "The LDAP URL Format", RFC 2255,
December, 1997. December, 1997.
[RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use [RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use
with LDAPv3", RFC 2256, December 1997. with LDAPv3", RFC 2256, December 1997.
[RFC2279] F. Yergeau, "UTF-8, a transformation format of ISO 10646",
RFC 2279, January 1998.
[RFC2434] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA [RFC2434] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", RFC 2119, October 1998. Considerations Section in RFCs", RFC 2119, October 1998.
Appendix A. Registration Templates Appendix A. Registration Templates
This appendix provides registration templates for registering new LDAP This appendix provides registration templates for registering new LDAP
values. <<add templates>> values. <<add templates>>
Appendix B. Assigned Values Appendix B. Assigned Values
The following values are currently assigned. The following values are currently assigned.
B.1. Object Identifiers Descriptive Names B.1. Object Identifiers
Currently registered "Internet Private Enterprise Numbers" can be
found at:
ftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbers
Currently registered "Internet Directory Numbers" can be found at:
ftp://ftp.isi.edu/in-notes/iana/assignments/smi-numbers
B.2. Object Identifiers Descriptive Names
NAME Type OID [REF] NAME Type OID [REF]
------------------------ ---- ----------------- ------------------------ ---- -----------------
account O 0.9.2342.19200300.100.4.5 [RFC1274]
alias O 2.5.6.1 [RFC2256] alias O 2.5.6.1 [RFC2256]
aliasedObjectName T 2.5.4.1 [RFC2256] aliasedObjectName T 2.5.4.1 [RFC2256]
altServer T 1.3.6.1.4.1.1466.101.120.6 [RFC2252] altServer T 1.3.6.1.4.1.1466.101.120.6 [RFC2252]
applicationEntity O 2.5.6.12 [RFC2256] applicationEntity O 2.5.6.12 [RFC2256]
applicationProcess O 2.5.6.11 [RFC2256] applicationProcess O 2.5.6.11 [RFC2256]
aRecord T 0.9.2342.19200300.100.1.26 [RFC1274]
associatedDomain T 0.9.2342.19200300.100.1.37 [RFC2164] associatedDomain T 0.9.2342.19200300.100.1.37 [RFC2164]
associatedInternetGateway T 1.3.6.1.4.1.453.7.2.8 [RFC2164]
associatedName T 0.9.2342.19200300.100.1.38 [RFC1274]
associatedORAddress T 1.3.6.1.4.1.453.7.2.6 [RFC2164]
associatedX400Gateway T 1.3.6.1.4.1.453.7.2.3 [RFC2164]
attributeTypes T 2.5.21.5 [RFC2252] attributeTypes T 2.5.21.5 [RFC2252]
audio T 0.9.2342.19200300.100.1.55 [RFC1274]
authorityRevocationList T 2.5.4.38 [RFC2256] authorityRevocationList T 2.5.4.38 [RFC2256]
bitStringMatch M 2.5.13.16 [RFC2252]
buildingName T 0.9.2342.19200300.100.1.48 [RFC1274]
businessCategory T 2.5.4.15 [RFC2256] businessCategory T 2.5.4.15 [RFC2256]
c T 2.5.4.6 [RFC2256] C T 2.5.4.6 [RFC2256]
cACertificate T 2.5.4.37 [RFC2256] cACertificate T 2.5.4.37 [RFC2256]
caseExactIA5Match M 1.3.6.1.4.1.1466.109.114.1 [RFC2252]
caseIgnoreIA5Match M 1.3.6.1.4.1.1466.109.114.2 [RFC2252]
caseIgnoreListMatch M 2.5.13.11 [RFC2252]
caseIgnoreMatch M 2.5.13.2 [RFC2252]
caseIgnoreOrderingMatch M 2.5.13.3 [RFC2252]
caseIgnoreSubstringsMatch M 2.5.13.4 [RFC2252]
certificateRevocationList T 2.5.4.39 [RFC2256] certificateRevocationList T 2.5.4.39 [RFC2256]
certificationAuthority O 2.5.6.16 [RFC2256] certificationAuthority O 2.5.6.16 [RFC2256]
certificationAuthority-V2 O 2.5.6.16.2 [RFC2256] certificationAuthority-V2 O 2.5.6.16.2 [RFC2256]
cn T 2.5.4.3 [RFC2256] CN T 2.5.4.3 [RFC2256]
cNAMERecord T 0.9.2342.19200300.100.1.31 [RFC1274]
co T 0.9.2342.19200300.100.1.43 [RFC1274]
commonName T 2.5.4.3 [RFC2256] commonName T 2.5.4.3 [RFC2256]
country O 2.5.6.2 [RFC2256] country O 2.5.6.2 [RFC2256]
countryName T 2.5.4.6 [RFC2256] countryName T 2.5.4.6 [RFC2256]
createTimestamp T 2.5.18.1 [RFC2252] createTimestamp T 2.5.18.1 [RFC2252]
creatorsName T 2.5.18.3 [RFC2252] creatorsName T 2.5.18.3 [RFC2252]
cRLDistributionPoint O 2.5.6.19 [RFC2256] cRLDistributionPoint O 2.5.6.19 [RFC2256]
crossCertificatePair T 2.5.4.40 [RFC2256] crossCertificatePair T 2.5.4.40 [RFC2256]
dc T 0.9.2342.19200300.100.1.25 [RFC2247] DC T 0.9.2342.19200300.100.1.25 [RFC2247]
dcObject O 1.3.6.1.4.1.1466.344 [RFC2247] dcObject O 1.3.6.1.4.1.1466.344 [RFC2247]
deltaCRL O 2.5.6.23 [RFC2587] deltaCRL O 2.5.6.23 [RFC2587]
deltaRevocationList T 2.5.4.53 [RFC2256] deltaRevocationList T 2.5.4.53 [RFC2256]
description T 2.5.4.13 [RFC2256] description T 2.5.4.13 [RFC2256]
destinationIndicator T 2.5.4.27 [RFC2256] destinationIndicator T 2.5.4.27 [RFC2256]
device O 2.5.6.14 [RFC2256] device O 2.5.6.14 [RFC2256]
distinguishedName T 2.5.4.49 [RFC2256] distinguishedName T 2.5.4.49 [RFC2256]
distinguishedNameMatch M 2.5.13.1 [RFC2252]
distinguishedNameTableEntry O 1.3.6.1.4.1.453.7.1.5 [RFC2293]
distinguishedNameTableKey T 1.3.6.1.4.1.453.7.2.3 [RFC2293]
dITContentRules T 2.5.21.2 [RFC2252] dITContentRules T 2.5.21.2 [RFC2252]
dITRedirect T 0.9.2342.19200300.100.1.54 [RFC1274]
dITStructureRules T 2.5.21.1 [RFC2252] dITStructureRules T 2.5.21.1 [RFC2252]
dmd O 2.5.6.20 [RFC2256] dmd O 2.5.6.20 [RFC2256]
dmdName T 2.5.4.54 [RFC2256] dmdName T 2.5.4.54 [RFC2256]
dnQualifier T 2.5.4.46 [RFC2256] dnQualifier T 2.5.4.46 [RFC2256]
dNSDomain O 0.9.2342.19200300.100.4.15 [RFC1274]
document O 0.9.2342.19200300.100.4.6 [RFC1274]
documentAuthor T 0.9.2342.19200300.100.1.14 [RFC1274]
documentIdentifier T 0.9.2342.19200300.100.1.11 [RFC1274]
documentLocation T 0.9.2342.19200300.100.1.15 [RFC1274]
documentPublisher T 0.9.2342.19200300.100.1.56 [RFC1274]
documentSeries O 0.9.2342.19200300.100.4.8 [RFC1274]
documentTitle T 0.9.2342.19200300.100.1.12 [RFC1274]
documentVersion T 0.9.2342.19200300.100.1.13 [RFC1274]
domain O 0.9.2342.19200300.100.4.13 [RFC2247]
domainComponent T 0.9.2342.19200300.100.1.25 [RFC2247] domainComponent T 0.9.2342.19200300.100.1.25 [RFC2247]
domainNameForm N 1.3.6.1.4.1.1466.345 [RFC2247]
domainRelatedObject O 0.9.2342.19200300.100.4.17 [RFC1274]
drink T 0.9.2342.19200300.100.1.5 [RFC1274]
dSA O 2.5.6.13 [RFC2256] dSA O 2.5.6.13 [RFC2256]
dSAQuality T 0.9.2342.19200300.100.1.49 [RFC1274]
dynamicObject O 1.3.6.1.4.1.1466.101.119.2 [RFC2589] dynamicObject O 1.3.6.1.4.1.1466.101.119.2 [RFC2589]
dynamicSubtrees T 1.3.6.1.4.1.1466.101.119.4 [RFC2589] dynamicSubtrees T 1.3.6.1.4.1.1466.101.119.4 [RFC2589]
enhancedSearchGuide T 2.5.4.47 [RFC2256] enhancedSearchGuide T 2.5.4.47 [RFC2256]
entryTtl T 1.3.6.1.4.1.1466.101.119.3 [RFC2589] entryTtl T 1.3.6.1.4.1.1466.101.119.3 [RFC2589]
extensibleObject O 1.3.6.1.4.1.1466.101.120.111 [RFC2252] extensibleObject O 1.3.6.1.4.1.1466.101.120.111 [RFC2252]
facsimileTelephoneNumber T 2.5.4.23 [RFC2256] facsimileTelephoneNumber T 2.5.4.23 [RFC2256]
fax T 2.5.4.23 [RFC2256] favouriteDrink T 0.9.2342.19200300.100.1.5 [RFC1274]
friendlyCountry O 0.9.2342.19200300.100.4.18 [RFC1274]
friendlyCountryName T 0.9.2342.19200300.100.1.43 [RFC1274]
generalizedTimeMatch M 2.5.13.27 [RFC2252]
generalizedTimeOrderingMatch M 2.5.13.28 [RFC2252]
generationQualifier T 2.5.4.44 [RFC2256] generationQualifier T 2.5.4.44 [RFC2256]
givenName T 2.5.4.42 [RFC2256] givenName T 2.5.4.42 [RFC2256]
GN T 2.5.4.42 [RFC2256]
groupOfNames O 2.5.6.9 [RFC2256] groupOfNames O 2.5.6.9 [RFC2256]
groupOfUniqueNames O 2.5.6.17 [RFC2256] groupOfUniqueNames O 2.5.6.17 [RFC2256]
homePhone T 0.9.2342.19200300.100.1.20 [RFC1274]
homePostalAddress T 0.9.2342.19200300.100.1.39 [RFC1274]
homeTelephone T 0.9.2342.19200300.100.1.20 [RFC1274]
host T 0.9.2342.19200300.100.1.9 [RFC1274]
houseIdentifier T 2.5.4.51 [RFC2256] houseIdentifier T 2.5.4.51 [RFC2256]
info T 0.9.2342.19200300.100.1.4 [RFC1274]
initials T 2.5.4.43 [RFC2256] initials T 2.5.4.43 [RFC2256]
integerFirstComponentMatch M 2.5.13.29 [RFC2252]
integerMatch M 2.5.13.14 [RFC2252]
internationaliSDNNumber T 2.5.4.25 [RFC2256] internationaliSDNNumber T 2.5.4.25 [RFC2256]
janetMailbox T 0.9.2342.19200300.100.1.46 [RFC1274]
jpegPhoto T 0.9.2342.19200300.100.1.60 [RFC1488]
knowledgeInformation T 2.5.4.2 [RFC2256] knowledgeInformation T 2.5.4.2 [RFC2256]
l T 2.5.4.7 [RFC2256] L T 2.5.4.7 [RFC2256]
labeledURI T 1.3.6.1.4.1.250.1.57 [RFC2079] labeledURI T 1.3.6.1.4.1.250.1.57 [RFC2079]
labeledURIObject O 1.3.6.1.4.1.250.3.15 [RFC2079] labeledURIObject T 1.3.6.1.4.1.250.3.15 [RFC2079]
LDAPsubEntry O 2.16.840.1.113719.2.142.6.1.1 [SUBENTRY] lastModifiedBy T 0.9.2342.19200300.100.1.24 [RFC1274]
lastModifiedTime T 0.9.2342.19200300.100.1.23 [RFC1274]
ldapSyntaxes T 1.3.6.1.4.1.1466.101.120.16 [RFC2251] ldapSyntaxes T 1.3.6.1.4.1.1466.101.120.16 [RFC2251]
locality O 2.5.6.3 [RFC2256] locality O 2.5.6.3 [RFC2256]
localityName T 2.5.4.7 [RFC2256] localityName T 2.5.4.7 [RFC2256]
mail T 0.9.2342.19200300.100.1.3 [RFC2798] mail T 0.9.2342.19200300.100.1.3 [RFC2798]
mailPreferenceOption T 0.9.2342.19200300.100.1.47 [RFC1274]
manager T 0.9.2342.19200300.100.1.10 [RFC1274]
matchingRules T 2.5.21.4 [RFC2252] matchingRules T 2.5.21.4 [RFC2252]
matchingRuleUse T 2.5.21.8 [RFC2252] matchingRuleUse T 2.5.21.8 [RFC2252]
mcgamTables T 1.3.6.1.4.1.453.7.2.9 [RFC2164]
mDRecord T 0.9.2342.19200300.100.1.27 [RFC1274]
member T 2.5.4.31 [RFC2256] member T 2.5.4.31 [RFC2256]
mixerGateway O 1.3.6.1.4.1.453.7.1.4 [RFC2164]
mobile T 0.9.2342.19200300.100.1.41 [RFC1274]
mobileTelephoneNumber T 0.9.2342.19200300.100.1.41 [RFC1274]
modifiersName T 2.5.18.4 [RFC2252] modifiersName T 2.5.18.4 [RFC2252]
modifyTimestamp T 2.5.18.2 [RFC2252] modifyTimestamp T 2.5.18.2 [RFC2252]
mXRecord T 0.9.2342.19200300.100.1.28 [RFC1274]
name T 2.5.4.41 [RFC2256] name T 2.5.4.41 [RFC2256]
nameForms T 2.5.21.7 [RFC2252] nameForms T 2.5.21.7 [RFC2252]
namingContexts T 1.3.6.1.4.1.1466.101.120.5 [RFC2252] namingContexts T 1.3.6.1.4.1.1466.101.120.5 [RFC2252]
o T 2.5.4.10 [RFC2256] nSRecord T 0.9.2342.19200300.100.1.29 [RFC1274]
numericStringMatch M 2.5.13.8 [RFC2252]
numericStringSubstringsMatch M 2.5.13.10 [RFC2252]
O T 2.5.4.10 [RFC2256]
objectClass T 2.5.4.0 [RFC2256] objectClass T 2.5.4.0 [RFC2256]
objectClasses T 2.5.21.6 [RFC2252] objectClasses T 2.5.21.6 [RFC2252]
objectIdentifierFirstComponentMatch M 2.5.13.30 [RFC2252]
objectIdentifiersMatch M 2.5.13.0 [RFC2252]
octetStringMatch M 2.5.13.17 [RFC2252]
omittedORAddressComponent O 1.3.6.1.4.1.453.7.1.3 [RFC2164]
oRAddressComponentType T 1.3.6.1.4.1.453.7.2.7 [RFC2164]
organization O 2.5.6.4 [RFC2256] organization O 2.5.6.4 [RFC2256]
organizationalPerson O 2.5.6.7 [RFC2256] organizationalPerson O 2.5.6.7 [RFC2256]
organizationalRole O 2.5.6.8 [RFC2256] organizationalRole O 2.5.6.8 [RFC2256]
organizationalStatus T 0.9.2342.19200300.100.1.45 [RFC1274]
organizationalUnit O 2.5.6.5 [RFC2256] organizationalUnit O 2.5.6.5 [RFC2256]
organizationalUnitName T 2.5.4.11 [RFC2256] organizationalUnitName T 2.5.4.11 [RFC2256]
organizationName T 2.5.4.10 [RFC2256] organizationName T 2.5.4.10 [RFC2256]
ou T 2.5.4.11 [RFC2256] otherMailbox T 0.9.2342.19200300.100.1.22 [RFC1274]
OU T 2.5.4.11 [RFC2256]
owner T 2.5.4.32 [RFC2256] owner T 2.5.4.32 [RFC2256]
pager T 0.9.2342.19200300.100.1.42 [RFC1274]
pagerTelephoneNumber T 0.9.2342.19200300.100.1.42 [RFC1274]
person O 2.5.6.6 [RFC2256] person O 2.5.6.6 [RFC2256]
personalSignature T 0.9.2342.19200300.100.1.53 [RFC1274]
personalTitle T 0.9.2342.19200300.100.1.40 [RFC1274]
photo T 0.9.2342.19200300.100.1.7 [RFC1274]
physicalDeliveryOfficeName T 2.5.4.19 [RFC2256] physicalDeliveryOfficeName T 2.5.4.19 [RFC2256]
pilotDSA O 0.9.2342.19200300.100.4.21 [RFC1274]
pilotObject O 0.9.2342.19200300.100.4.3 [RFC1274]
pilotOrganization O 0.9.2342.19200300.100.4.20 [RFC1274]
pilotPerson O 0.9.2342.19200300.100.4.4 [RFC1274]
pkiCA O 2.5.6.22 [RFC2587]
pkiUser O 2.5.6.21 [RFC2587]
postalAddress T 2.5.4.16 [RFC2256] postalAddress T 2.5.4.16 [RFC2256]
postalCode T 2.5.4.17 [RFC2256] postalCode T 2.5.4.17 [RFC2256]
postOfficeBox T 2.5.4.18 [RFC2256] postOfficeBox T 2.5.4.18 [RFC2256]
preferredDeliveryMethod T 2.5.4.28 [RFC2256] preferredDeliveryMethod T 2.5.4.28 [RFC2256]
presentationAddress T 2.5.4.29 [RFC2256] presentationAddress T 2.5.4.29 [RFC2256]
presentationAddressMatch M 2.5.13.22 [RFC2252]
protocolInformation T 2.5.4.48 [RFC2256] protocolInformation T 2.5.4.48 [RFC2256]
protocolInformationMatch M 2.5.13.24 [RFC2252]
qualityLabelledData O 0.9.2342.19200300.100.4.22 [RFC1274]
registeredAddress T 2.5.4.26 [RFC2256] registeredAddress T 2.5.4.26 [RFC2256]
residentialPerson O 2.5.6.10 [RFC2256] residentialPerson O 2.5.6.10 [RFC2256]
rfc822Mailbox T 0.9.2342.19200300.100.1.3 [RFC1274] RFC822LocalPart O 0.9.2342.19200300.100.4.14 [RFC1274]
RFC822Mailbox T 0.9.2342.19200300.100.1.3 [RFC1274]
rFC822ToX400Mapping O 1.3.6.1.4.1.453.7.1.1 [RFC2164]
roleOccupant T 2.5.4.33 [RFC2256] roleOccupant T 2.5.4.33 [RFC2256]
room O 0.9.2342.19200300.100.4.7 [RFC1274]
roomNumber T 0.9.2342.19200300.100.1.6 [RFC1274]
searchGuide T 2.5.4.14 [RFC2256] searchGuide T 2.5.4.14 [RFC2256]
secretary T 0.9.2342.19200300.100.1.21 [RFC1274]
seeAlso T 2.5.4.34 [RFC2256] seeAlso T 2.5.4.34 [RFC2256]
serialNumber T 2.5.4.5 [RFC2256] serialNumber T 2.5.4.5 [RFC2256]
simpleSecurityObject O 0.9.2342.19200300.100.4.19 [RFC1274] simpleSecurityObject O 0.9.2342.19200300.100.4.19 [RFC1274]
sn T 2.5.4.4 [RFC2256] singleLevelQuality T 0.9.2342.19200300.100.1.50 [RFC1274]
st T 2.5.4.8 [RFC2256] SN T 2.5.4.4 [RFC2256]
sOARecord T 0.9.2342.19200300.100.1.30 [RFC1274]
ST T 2.5.4.8 [RFC2256]
stateOrProvinceName T 2.5.4.8 [RFC2256] stateOrProvinceName T 2.5.4.8 [RFC2256]
street T 2.5.4.9 [RFC2256] street T 2.5.4.9 [RFC2256]
streetAddress T 2.5.4.9 [RFC2256] streetAddress T 2.5.4.9 [RFC2256]
strongAuthenticationUser O 2.5.6.15 [RFC2256] strongAuthenticationUser O 2.5.6.15 [RFC2256]
subschema O 2.5.20.1 [RFC2252] subschema O 2.5.20.1 [RFC2252]
subschemaSubentry T 2.5.18.10 [RFC2252] subschemaSubentry T 2.5.18.10 [RFC2252]
subtree O 1.3.6.1.4.1.453.7.1.1 [RFC2293]
subtreeMaximumQuality T 0.9.2342.19200300.100.1.52 [RFC1274]
subtreeMinimumQuality T 0.9.2342.19200300.100.1.51 [RFC1274]
supportedAlgorithms T 2.5.4.52 [RFC2256] supportedAlgorithms T 2.5.4.52 [RFC2256]
supportedApplicationContext T 2.5.4.30 [RFC2256] supportedApplicationContext T 2.5.4.30 [RFC2256]
supportedControl T 1.3.6.1.4.1.1466.101.120.13 [RFC2252] supportedControl T 1.3.6.1.4.1.1466.101.120.13 [RFC2252]
supportedExtension T 1.3.6.1.4.1.1466.101.120.7 [RFC2252] supportedExtension T 1.3.6.1.4.1.1466.101.120.7 [RFC2252]
supportedLDAPVersion T 1.3.6.1.4.1.1466.101.120.15 [RFC2252] supportedLDAPVersion T 1.3.6.1.4.1.1466.101.120.15 [RFC2252]
supportedSASLMechanisms T 1.3.6.1.4.1.1466.101.120.14 [RFC2252] supportedSASLMechanisms T 1.3.6.1.4.1.1466.101.120.14 [RFC2252]
surname T 2.5.4.4 [RFC2256] surname T 2.5.4.4 [RFC2256]
table O 1.3.6.1.4.1.453.7.1.2 [RFC2293]
tableEntry O 1.3.6.1.4.1.453.7.1.3 [RFC2293]
telephoneNumber T 2.5.4.20 [RFC2256] telephoneNumber T 2.5.4.20 [RFC2256]
telephoneNumberMatch M 2.5.13.20 [RFC2252]
telephoneNumberSubstringsMatch M 2.5.13.21 [RFC2252]
teletexTerminalIdentifier T 2.5.4.22 [RFC2256] teletexTerminalIdentifier T 2.5.4.22 [RFC2256]
telexNumber T 2.5.4.21 [RFC2256] telexNumber T 2.5.4.21 [RFC2256]
textEncodedORAddress T 0.9.2342.19200300.100.1.2 [RFC1274]
textTableEntry O 1.3.6.1.4.1.453.7.1.4 [RFC2293]
textTableKey T 1.3.6.1.4.1.453.7.2.1 [RFC2293]
textTableValue T 1.3.6.1.4.1.453.7.2.2 [RFC2293]
title T 2.5.4.12 [RFC2256] title T 2.5.4.12 [RFC2256]
top O 2.5.6.0 [RFC2256] top O 2.5.6.0 [RFC2256]
uid T 0.9.2342.19200300.100.1.1 [RFC2253] uid T 0.9.2342.19200300.100.1.1 [RFC2253]
uniqueIdentifier T 0.9.2342.19200300.100.1.44 [RFC1274]
uniqueMember T 2.5.4.50 [RFC2256] uniqueMember T 2.5.4.50 [RFC2256]
uniqueMemberMatch M 2.5.13.23 [RFC2252]
userCertificate T 2.5.4.36 [RFC2256] userCertificate T 2.5.4.36 [RFC2256]
userid T 0.9.2342.19200300.100.1.1 [RFC1274] userClass T 0.9.2342.19200300.100.1.8 [RFC1274]
userId T 0.9.2342.19200300.100.1.1 [RFC1274]
userPassword T 2.5.4.35 [RFC2256] userPassword T 2.5.4.35 [RFC2256]
userSecurityInformation O 2.5.6.18 [RFC2256] userSecurityInformation O 2.5.6.18 [RFC2256]
x121Address T 2.5.4.24 [RFC2256] x121Address T 2.5.4.24 [RFC2256]
x400ToRFC822Mapping O 1.3.6.1.4.1.453.7.1.2 [RFC2164]
x500UniqueIdentifier T 2.5.4.45 [RFC2256] x500UniqueIdentifier T 2.5.4.45 [RFC2256]
B.2. Attribute Description Options
Legend
-----------------------
M => Matching Rule
O => Object Class
U => LDAP URL Extension
T => Attribute Type
B.3. Attribute Description Options
Option Owner Reference Option Owner Reference
------ ----- --------- ------ ----- ---------
binary IESG [RFC2251] binary IESG [RFC2251]
lang-* IESG [RFC2596] lang-* IESG [RFC2596]
B.3. LDAPMessage types * family of options
B.4. LDAPMessage types
Name Code Owner Reference Name Code Owner Reference
--------------------------- ---- ----- --------- --------------------------- ---- ----- ---------
bindRequest 0 IESG [RFC2251] bindRequest 0 IESG [RFC2251]
bindResponse 1 IESG [RFC2251] bindResponse 1 IESG [RFC2251]
unbindRequest 2 IESG [RFC2251] unbindRequest 2 IESG [RFC2251]
searchRequest 3 IESG [RFC2251] searchRequest 3 IESG [RFC2251]
searchResEntry 4 IESG [RFC2251] searchResEntry 4 IESG [RFC2251]
searchResDone 5 IESG [RFC2251] searchResDone 5 IESG [RFC2251]
modifyRequest 6 IESG [RFC2251] modifyRequest 6 IESG [RFC2251]
skipping to change at page 11, line 38 skipping to change at page 15, line 21
modDNResponse 13 IESG [RFC2251] modDNResponse 13 IESG [RFC2251]
compareRequest 14 IESG [RFC2251] compareRequest 14 IESG [RFC2251]
compareResponse 15 IESG [RFC2251] compareResponse 15 IESG [RFC2251]
abandonRequest 16 IESG [RFC2251] abandonRequest 16 IESG [RFC2251]
reserved 17-18 IESG reserved 17-18 IESG
searchResRef 19 IESG [RFC2251] searchResRef 19 IESG [RFC2251]
reserved 20-22 IESG reserved 20-22 IESG
extendedReq 23 IESG [RFC2251] extendedReq 23 IESG [RFC2251]
extendedResp 24 IESG [RFC2251] extendedResp 24 IESG [RFC2251]
B.4. resultCode values B.5. resultCode values
Name Code Owner Reference Name Code Owner Reference
--------------------------- ---- ----- --------- --------------------------- ---- ----- ---------
success 0 IESG [RFC2251] success 0 IESG [RFC2251]
operationsError 1 IESG [RFC2251] operationsError 1 IESG [RFC2251]
protocolError 2 IESG [RFC2251] protocolError 2 IESG [RFC2251]
timeLimitExceeded 3 IESG [RFC2251] timeLimitExceeded 3 IESG [RFC2251]
sizeLimitExceeded 4 IESG [RFC2251] sizeLimitExceeded 4 IESG [RFC2251]
compareFalse 5 IESG [RFC2251] compareFalse 5 IESG [RFC2251]
compareTrue 6 IESG [RFC2251] compareTrue 6 IESG [RFC2251]
skipping to change at page 13, line 5 skipping to change at page 16, line 33
reserved (APIs) 82 IESG [RFC2251] reserved (APIs) 82 IESG [RFC2251]
reserved (APIs) 83 IESG [RFC2251] reserved (APIs) 83 IESG [RFC2251]
reserved (APIs) 84 IESG [RFC2251] reserved (APIs) 84 IESG [RFC2251]
reserved (APIs) 85 IESG [RFC2251] reserved (APIs) 85 IESG [RFC2251]
reserved (APIs) 86 IESG [RFC2251] reserved (APIs) 86 IESG [RFC2251]
reserved (APIs) 87 IESG [RFC2251] reserved (APIs) 87 IESG [RFC2251]
reserved (APIs) 88 IESG [RFC2251] reserved (APIs) 88 IESG [RFC2251]
reserved (APIs) 89 IESG [RFC2251] reserved (APIs) 89 IESG [RFC2251]
reserved (APIs) 90 IESG [RFC2251] reserved (APIs) 90 IESG [RFC2251]
B.5. Bind Authentication Method B.6. Bind Authentication Method
Method Value Owner Usage Reference Method Value Owner Usage Reference
------ ----- ----- ----------- ----------------- ------ ----- ----- ----------- -----------------
simple 0 IESG LIMITED USE [RFC2251,RFC2829] simple 0 IESG LIMITED USE [RFC2251,RFC2829]
krbv42LDAP 1 IESG OBSOLETE* [RFC1777] krbv42LDAP 1 IESG OBSOLETE* [RFC1777]
krbv42DSA 2 IESG OBSOLETE* [RFC1777] krbv42DSA 2 IESG OBSOLETE* [RFC1777]
sasl 3 IESG COMMON [RFC2251,RFC2829] sasl 3 IESG COMMON [RFC2251,RFC2829]
* These LDAPv2-only mechanisms were deprecated in favor LDAPv3 SASL * These LDAPv2-only mechanisms were deprecated in favor LDAPv3 SASL
authentication method, specifically when used with the KERBEROS_IV authentication method, specifically the GSSAPI mechanism.
mechanism or the GSSAPI mechanism.
Copyright 2001, The Internet Society. All Rights Reserved. Copyright 2001, The Internet Society. All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/