INTERNET-DRAFT                          Editor:  Kurt D. Zeilenga
Intended Category: BCP                        OpenLDAP Foundation
Expires: 1 10 October 2001                              1                            10 April 2001

                       IANA Considerations for LDAP

Status of Memo

  This document is an Internet-Draft and is in full conformance with all
  provisions of Section 10 of RFC2026.

  This document is intended to be, after appropriate review and
  revision, submitted to the RFC Editor as a Best Current Practice
  document.  Distribution of this memo is unlimited.  Technical
  discussion of this document will take place on the IETF LDAP Revision
  Working Group (LDAPbis) mailing list <>.
  Please send editorial comments directly to the document editor

  Internet-Drafts are working documents of the Internet Engineering Task
  Force (IETF), its areas, and its working groups.  Note that other
  groups may also distribute working documents as Internet-Drafts.
  Internet-Drafts are draft documents valid for a maximum of six months
  and may be updated, replaced, or obsoleted by other documents at any
  time.  It is inappropriate to use Internet-Drafts as reference
  material or to cite them other than as ``work in progress.''

  The list of current Internet-Drafts can be accessed at
  <>. The list of
  Internet-Draft Shadow Directories can be accessed at

  Copyright 2001, The Internet Society.  All Rights Reserved.

  Please see the Copyright section near the end of this document for
  more information.


  This document provides procedures for registering extensible elements
  of LDAP.  The document also provides guidelines to IANA describing
  conditions under which new values can be assigned.

1. Introduction

  The Lightweight Directory Access Protocol [RFC2251] [LDAPTS] (LDAP) is an
  extensible protocol.  LDAP supports:
    - addition of new operations,
    - extension of existing operations, and
    - extensible schema.

  This document details procedures for registering with values of used
  to unambiguously identify extensible elements of the protocol with IANA
    - LDAP message types,
    - LDAP result codes,
    - LDAP authentication methods,
    - LDAP attribute description options, and
    - Object Identifiers descriptive names

  This names.

  These registries are maintained by the Internet Assigned Numbers
  Authority (IANA).

  In addition, this document also provides guidelines to IANA describing the
  conditions under which new values can be assigned.

2. Terms Terminology and Conventions

  This section details terms and conventions are used in this document.

2.1. Policy terms Terminology

  The terms "IESG Approval", "Standards Action", "IETF Consensus",
  "Specification Required", "First Come First Served", "Expert Review",
  and "Private Use" are used as defined in [RFC2434].

2.2. Requirement terms Terminology

  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
  document are to be interpreted as described in [RFC2119].

2.3. Common ABNF productions Productions

  A number of syntaxes in this document are described using ABNF
  [RFC2234].  These syntaxes rely on the following common productions:


       ALPHA = %x41-5A / %61-7A     ; A-Z / a-z


       LDIGIT = %x31-39             ; 1-9

       DIGIT = %x30 / ld            ; 0-9


       HYPHEN = %x2D                ; "-"


       PERIOD = %x2E                ; "."

       number = DIGIT / ( LDIGIT 1*DIGIT )

       keychar = ( a ALPHA / d DIGIT / hyphen HYPHEN )
       leadkeychar = ( a / d ) ALPHA

       keystring = leadkeychar *keychar

  A keyword is case-insensitive UTF-8 [RFC2279] string restricted to the
  keystring production.

3.  IANA Considerations for LDAP

  This section details each of the types kind of protocol values which can be
  registered and provides IANA guidelines on how to assign new values.

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" ( assigned
  by IANA <>.

  For IETF developed protocol and schema items, OIDS under "Internet
  Directory Numbers" ( 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
  Object Identifier to identify protocol extensions [RFC2251], schema
  elements [RFC2252], protocol extensions, LDAP URL [RFC2255]
  extensions, and other objects.  These names SHALL be restricted to
  case-insensitive UTF-8 strings limited by the following ABNF:

       name = keystring

  Multiple names MAY be assigned to a given OID.  For purposes of
  registration, an OID SHALL be represented in numeric OID form
  conforming to the ABNF:

       numericoid = number *( period PERIOD number ) ; e.g.

       number = d / ( ld 1*d )

  While the protocol places no maximum length restriction upon
  descriptive names, they SHOULD be short.  IANA MAY refuse to register
  any name over 48 characters in length.  IANA MAY reject obviously
  bogus registrations.

  Names beginning with "x-" are for Private Use.  IANA Use and SHALL NOT
  register any name beginning with "x-". be

  Names beginning with "e-" are reserved for experiments.  IANA SHALL
  register any name beginning with "e-" on a First Come First Served

  Expert Review is REQUIRED before accepting registration of all other

  IANA SHALL NOT verify the registrant "owns" the OID being named.

  The OID namespace is managed by The ISO/IEC Joint Technical Committee
  1 - Subcommittee 6.


3.3. AttributeDescription Options

  An AttributeDescription [RFC2251, Section 4.1.5] can contain zero or
  options specifying additional semantics.  An option SHALL be
  restricted to case-insensitive UTF-8 string limited by the following

       option = keystring

  While the protocol places no maximum length restriction upon option
  strings, they SHOULD be short.  IANA MAY refuse to register any option
  over 16 characters in length.  IANA MAY reject obviously bogus

  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.  IANA Use and SHALL NOT
  register any option beginning with "x-".

  Options beginning with "e-" are reserved for experiments.  IANA SHALL
  register any option beginning with "e-" on a First Come First Served

  IANA SHALL register other options by either Standards Action or Expert
  Review with Specification Required.


3.4. LDAP Message Types

  Each protocol message is encapsulated in an LDAPMessage envelope
  [RFC2251, Section 4.1.1].  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 [RFC2251].

  New values SHALL only be registered by Standards Track action.

  Note: LDAP provides extensible messages which reduces, but does not
        eliminate, the need to add new message types.


3.5. LDAP Result Codes

  LDAP result messages carry an resultCode enumerated value to indicate
  the outcome of the operation [RFC2251, Section 4.1.10].  Each result
  code consists of a keyword and a non-negative integer.

  IANA SHALL register new resultCode integers from in the range 0-255 upon
  Standards Action, in the range 256-1023 with Expert Review, 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-".  IANA MAY reject obviously bogus
  Values greater than or equal to 8192 are for Private Use.

3.5. Use and SHALL NOT
  be registered.

  IANA MAY reject obviously bogus registrations.

3.6. LDAP Authentication Method

  The LDAP Bind operation supports multiple authentication methods
  [RFC2251, Section 4.2].  Each authentication choice consists of a
  keyword and a non-negative integer.

  Authentication methods usage SHALL be classified using one of the
  following terms:

    COMMON      - method is appropriate for common use on the Internet,
    LIMITED USE - method is appropriate for limited uses. use.
    OBSOLETE    - method has been deprecated or other otherwise found to be
                  inappropriate for any use.

  IANA SHALL NOT register new OBSOLETE mechanisms. authentication methods.  Methods
  without publicly available specifications SHALL NOT be classified as
  COMMON.  IANA MAY reject obviously bogus registrations.

  IANA SHALL register new authentication method integers from 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-".
  IANA MAY reject obviously bogus registrations.  Values greater than or equal
  to 8192 are for Private Use. Use and SHALL NOT be registered.

  Note: LDAP supports SASL [RFC2222] as an Authentication CHOICE.  SASL
        is an extensible LDAP authentication method.

  Developers of new authentication methods are SHOULD seek appropriate

3.6. Other values?

  Other LDAP name spaces?

4. Registration Procedure

  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
  currently registered with IANA.

  The first step is for the request to fill out the appropriate form.
  Templates are provided in Appendix 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 <> 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 my sending a request to <>.
  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 [RFC2026].  The Expert is appointed by
  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
  the completed form directly to the IESG <>.  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

  This section needs to be flushed out.

  5.1. Location discusses maintenance of List registrations.

5.1. Lists of Registered Values

  IANA makes lists of registered values readily available to the
  Internet community on their web site <>.

5.2. Comments Change Control

  The registration owner MAY update the specification subject to the
  same constraints and review as with new registrations.


  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

  The security considerations detailed in [RFC2434] are generally
  applicable to this document.  Security considerations to each
  namespace are discussed in Section 3.

  Security considerations for LDAP are detailed in documents comprising
  the technical specification [LDAPTS].

7. Acknowledgment

  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

8. Author's Address

  Kurt D. Zeilenga
  OpenLDAP Foundation


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
            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
            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
            Protocol (v3)", RFC 2251, December 1997.

  [RFC2252] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight
            Directory Access Protocol (v3):  Attribute Syntax
            Definitions", RFC 2252, December 1997.

  [RFC2255] T. Howes, M. Smith, "The LDAP URL Format", RFC 2255,
            December, 1997.

  [RFC2256]  Wahl, M., "A Summary of the X.500(96) User Schema for use
            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
            Considerations Section in RFCs", RFC 2119, October 1998.

Appendix A.  Registration Templates

  This appendix provides registration templates for registering new LDAP
  values.  <<add templates>>

Appendix B.  Assigned Values

  The following values are currently assigned.

B.1.  Object Identifiers

  Currently registered "Internet Private Enterprise Numbers" can be
  found at:

  Currently registered "Internet Directory Numbers" can be found at:

B.2.  Object Identifiers Descriptive Names

  NAME                         Type OID [REF]
  ------------------------     ---- -----------------
  account                         O 0.9.2342.19200300.100.4.5 [RFC1274]
  alias                           O [RFC2256]
  aliasedObjectName               T [RFC2256]
  altServer                       T [RFC2252]
  applicationEntity               O [RFC2256]
  applicationProcess              O [RFC2256]
  aRecord                         T 0.9.2342.19200300.100.1.26 [RFC1274]
  associatedDomain                T 0.9.2342.19200300.100.1.37 [RFC2164]
  associatedInternetGateway       T [RFC2164]
  associatedName                  T 0.9.2342.19200300.100.1.38 [RFC1274]
  associatedORAddress             T [RFC2164]
  associatedX400Gateway           T [RFC2164]
  attributeTypes                  T [RFC2252]
  audio                           T 0.9.2342.19200300.100.1.55 [RFC1274]
  authorityRevocationList         T [RFC2256]
  bitStringMatch                  M [RFC2252]
  buildingName                    T 0.9.2342.19200300.100.1.48 [RFC1274]
  businessCategory                T [RFC2256]
  C                               T [RFC2256]
  cACertificate                   T [RFC2256]
  caseExactIA5Match               M [RFC2252]
  caseIgnoreIA5Match              M [RFC2252]
  caseIgnoreListMatch             M [RFC2252]
  caseIgnoreMatch                 M [RFC2252]
  caseIgnoreOrderingMatch         M [RFC2252]
  caseIgnoreSubstringsMatch       M [RFC2252]
  certificateRevocationList       T [RFC2256]
  certificationAuthority          O [RFC2256]
  certificationAuthority-V2       O [RFC2256]
  CN                              T [RFC2256]
  cNAMERecord                     T 0.9.2342.19200300.100.1.31 [RFC1274]
  co                              T 0.9.2342.19200300.100.1.43 [RFC1274]
  commonName                      T [RFC2256]
  country                         O [RFC2256]
  countryName                     T [RFC2256]
  createTimestamp                 T [RFC2252]
  creatorsName                    T [RFC2252]
  cRLDistributionPoint            O [RFC2256]
  crossCertificatePair            T [RFC2256]
  DC                              T 0.9.2342.19200300.100.1.25 [RFC2247]
  dcObject                        O [RFC2247]
  deltaCRL                        O [RFC2587]
  deltaRevocationList             T [RFC2256]
  description                     T [RFC2256]
  destinationIndicator            T [RFC2256]
  device                          O [RFC2256]
  distinguishedName               T [RFC2256]
  distinguishedNameMatch          M [RFC2252]
  distinguishedNameTableEntry     O [RFC2293]
  distinguishedNameTableKey       T [RFC2293]
  dITContentRules                 T [RFC2252]
  dITRedirect                     T 0.9.2342.19200300.100.1.54 [RFC1274]
  dITStructureRules               T [RFC2252]
  dmd                             O [RFC2256]
  dmdName                         T [RFC2256]
  dnQualifier                     T [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]
  domainNameForm                  N [RFC2247]
  domainRelatedObject             O 0.9.2342.19200300.100.4.17 [RFC1274]
  drink                           T 0.9.2342.19200300.100.1.5 [RFC1274]
  dSA                             O [RFC2256]
  dSAQuality                      T 0.9.2342.19200300.100.1.49 [RFC1274]
  dynamicObject                   O [RFC2589]
  dynamicSubtrees                 T [RFC2589]
  enhancedSearchGuide             T [RFC2256]
  entryTtl                        T [RFC2589]
  extensibleObject                O [RFC2252]
  facsimileTelephoneNumber        T [RFC2256]
  favouriteDrink                  T [RFC2256] 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 [RFC2252]
  generalizedTimeOrderingMatch    M [RFC2252]
  generationQualifier             T [RFC2256]
  givenName                       T [RFC2256]
  GN                              T [RFC2256]
  groupOfNames                    O [RFC2256]
  groupOfUniqueNames              O [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 [RFC2256]
  info                            T 0.9.2342.19200300.100.1.4 [RFC1274]
  initials                        T [RFC2256]
  integerFirstComponentMatch      M [RFC2252]
  integerMatch                    M [RFC2252]
  internationaliSDNNumber         T [RFC2256]
  janetMailbox                    T 0.9.2342.19200300.100.1.46 [RFC1274]
  jpegPhoto                       T 0.9.2342.19200300.100.1.60 [RFC1488]
  knowledgeInformation            T [RFC2256]
  L                               T [RFC2256]
  labeledURI                      T [RFC2079]
  labeledURIObject             O                T [RFC2079]
  LDAPsubEntry                 O 2.16.840.1.113719. [SUBENTRY]
  lastModifiedBy                  T 0.9.2342.19200300.100.1.24 [RFC1274]
  lastModifiedTime                T 0.9.2342.19200300.100.1.23 [RFC1274]
  ldapSyntaxes                    T [RFC2251]
  locality                        O [RFC2256]
  localityName                    T [RFC2256]
  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 [RFC2252]
  matchingRuleUse                 T [RFC2252]
  mcgamTables                     T [RFC2164]
  mDRecord                        T 0.9.2342.19200300.100.1.27 [RFC1274]
  member                          T [RFC2256]
  mixerGateway                    O [RFC2164]
  mobile                          T 0.9.2342.19200300.100.1.41 [RFC1274]
  mobileTelephoneNumber           T 0.9.2342.19200300.100.1.41 [RFC1274]
  modifiersName                   T [RFC2252]
  modifyTimestamp                 T [RFC2252]
  mXRecord                        T 0.9.2342.19200300.100.1.28 [RFC1274]
  name                            T [RFC2256]
  nameForms                       T [RFC2252]
  namingContexts                  T [RFC2252]
  nSRecord                        T 0.9.2342.19200300.100.1.29 [RFC1274]
  numericStringMatch              M [RFC2252]
  numericStringSubstringsMatch    M [RFC2252]
  O                               T [RFC2256]
  objectClass                     T [RFC2256]
  objectClasses                   T [RFC2252]
  objectIdentifierFirstComponentMatch M [RFC2252]
  objectIdentifiersMatch          M [RFC2252]
  octetStringMatch                M [RFC2252]
  omittedORAddressComponent       O [RFC2164]
  oRAddressComponentType          T [RFC2164]
  organization                    O [RFC2256]
  organizationalPerson            O [RFC2256]
  organizationalRole              O [RFC2256]
  organizationalStatus            T 0.9.2342.19200300.100.1.45 [RFC1274]
  organizationalUnit              O [RFC2256]
  organizationalUnitName          T [RFC2256]
  organizationName                T [RFC2256]
  otherMailbox                    T 0.9.2342.19200300.100.1.22 [RFC1274]
  OU                              T [RFC2256]
  owner                           T [RFC2256]
  pager                           T 0.9.2342.19200300.100.1.42 [RFC1274]
  pagerTelephoneNumber            T 0.9.2342.19200300.100.1.42 [RFC1274]
  person                          O [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 [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 [RFC2587]
  pkiUser                         O [RFC2587]
  postalAddress                   T [RFC2256]
  postalCode                      T [RFC2256]
  postOfficeBox                   T [RFC2256]
  preferredDeliveryMethod         T [RFC2256]
  presentationAddress             T [RFC2256]
  presentationAddressMatch        M [RFC2252]
  protocolInformation             T [RFC2256]
  protocolInformationMatch        M [RFC2252]
  qualityLabelledData             O 0.9.2342.19200300.100.4.22 [RFC1274]
  registeredAddress               T [RFC2256]
  residentialPerson               O [RFC2256]
  RFC822LocalPart                 O 0.9.2342.19200300.100.4.14 [RFC1274]
  RFC822Mailbox                   T 0.9.2342.19200300.100.1.3 [RFC1274]
  rFC822ToX400Mapping             O [RFC2164]
  roleOccupant                    T [RFC2256]
  room                            O 0.9.2342.19200300.100.4.7 [RFC1274]
  roomNumber                      T 0.9.2342.19200300.100.1.6 [RFC1274]
  searchGuide                     T [RFC2256]
  secretary                       T 0.9.2342.19200300.100.1.21 [RFC1274]
  seeAlso                         T [RFC2256]
  serialNumber                    T [RFC2256]
  simpleSecurityObject            O 0.9.2342.19200300.100.4.19 [RFC1274]
  singleLevelQuality              T 0.9.2342.19200300.100.1.50 [RFC1274]
  SN                              T [RFC2256]
  sOARecord                       T 0.9.2342.19200300.100.1.30 [RFC1274]
  ST                              T [RFC2256]
  stateOrProvinceName             T [RFC2256]
  street                          T [RFC2256]
  streetAddress                   T [RFC2256]
  strongAuthenticationUser        O [RFC2256]
  subschema                       O [RFC2252]
  subschemaSubentry               T [RFC2252]
  subtree                         O [RFC2293]
  subtreeMaximumQuality           T 0.9.2342.19200300.100.1.52 [RFC1274]
  subtreeMinimumQuality           T 0.9.2342.19200300.100.1.51 [RFC1274]
  supportedAlgorithms             T [RFC2256]
  supportedApplicationContext     T [RFC2256]
  supportedControl                T [RFC2252]
  supportedExtension              T [RFC2252]
  supportedLDAPVersion            T [RFC2252]
  supportedSASLMechanisms         T [RFC2252]
  surname                         T [RFC2256]
  table                           O [RFC2293]
  tableEntry                      O [RFC2293]
  telephoneNumber                 T [RFC2256]
  telephoneNumberMatch            M [RFC2252]
  telephoneNumberSubstringsMatch  M [RFC2252]
  teletexTerminalIdentifier       T [RFC2256]
  telexNumber                     T [RFC2256]
  textEncodedORAddress            T 0.9.2342.19200300.100.1.2 [RFC1274]
  textTableEntry                  O [RFC2293]
  textTableKey                    T [RFC2293]
  textTableValue                  T [RFC2293]
  title                           T [RFC2256]
  top                             O [RFC2256]
  uid                             T 0.9.2342.19200300.100.1.1 [RFC2253]
  uniqueIdentifier                T 0.9.2342.19200300.100.1.44 [RFC1274]
  uniqueMember                    T [RFC2256]
  uniqueMemberMatch               M [RFC2252]
  userCertificate                 T [RFC2256]
  userClass                       T 0.9.2342.19200300.100.1.8 [RFC1274]
  userId                          T 0.9.2342.19200300.100.1.1 [RFC1274]
  userPassword                    T [RFC2256]
  userSecurityInformation         O [RFC2256]
  x121Address                     T [RFC2256]
  x400ToRFC822Mapping             O [RFC2164]
  x500UniqueIdentifier            T [RFC2256]

  M => Matching Rule
  O => Object Class
  U => LDAP URL Extension
  T => Attribute Type

  B.3.  Attribute Description Options

  Option  Owner  Reference
  ------  -----  ---------
  binary  IESG   [RFC2251]
  lang-*  IESG   [RFC2596]


  * family of options

  B.4. LDAPMessage types

  Name                         Code Owner  Reference
  ---------------------------  ---- -----  ---------
  bindRequest                     0  IESG  [RFC2251]
  bindResponse                    1  IESG  [RFC2251]
  unbindRequest                   2  IESG  [RFC2251]
  searchRequest                   3  IESG  [RFC2251]
  searchResEntry                  4  IESG  [RFC2251]
  searchResDone                   5  IESG  [RFC2251]
  modifyRequest                   6  IESG  [RFC2251]
  modifyResponse                  7  IESG  [RFC2251]
  addRequest                      8  IESG  [RFC2251]
  addResponse                     9  IESG  [RFC2251]
  delRequest                     10  IESG  [RFC2251]
  delResponse                    11  IESG  [RFC2251]
  modDNRequest                   12  IESG  [RFC2251]
  modDNResponse                  13  IESG  [RFC2251]
  compareRequest                 14  IESG  [RFC2251]
  compareResponse                15  IESG  [RFC2251]
  abandonRequest                 16  IESG  [RFC2251]
  reserved                    17-18  IESG
  searchResRef                   19  IESG  [RFC2251]
  reserved                    20-22  IESG
  extendedReq                    23  IESG  [RFC2251]
  extendedResp                   24  IESG  [RFC2251]


  B.5. resultCode values

  Name                         Code Owner  Reference
  ---------------------------  ---- -----  ---------
  success                         0  IESG  [RFC2251]
  operationsError                 1  IESG  [RFC2251]
  protocolError                   2  IESG  [RFC2251]
  timeLimitExceeded               3  IESG  [RFC2251]
  sizeLimitExceeded               4  IESG  [RFC2251]
  compareFalse                    5  IESG  [RFC2251]
  compareTrue                     6  IESG  [RFC2251]
  authMethodNotSupported          7  IESG  [RFC2251]
  strongAuthRequired              8  IESG  [RFC2251]
  reserved (partialResults)       9  IESG  [RFC2251]
  referral                       10  IESG  [RFC2251]
  adminLimitExceeded             11  IESG  [RFC2251]
  unavailableCriticalExtension   12  IESG  [RFC2251]
  confidentialityRequired        13  IESG  [RFC2251]
  saslBindInProgress             14  IESG  [RFC2251]
  noSuchAttribute                16  IESG  [RFC2251]
  undefinedAttributeType         17  IESG  [RFC2251]
  inappropriateMatching          18  IESG  [RFC2251]
  constraintViolation            19  IESG  [RFC2251]
  attributeOrValueExists         20  IESG  [RFC2251]
  invalidAttributeSyntax         21  IESG  [RFC2251]
  noSuchObject                   32  IESG  [RFC2251]
  aliasProblem                   33  IESG  [RFC2251]
  invalidDNSyntax                34  IESG  [RFC2251]
  reserved (isLeaf)              35  IESG  [RFC2251]
  aliasDereferencingProblem      36  IESG  [RFC2251]
  reserved                    37-47  IESG
  inappropriateAuthentication    48  IESG  [RFC2251]
  invalidCredentials             49  IESG  [RFC2251]
  insufficientAccessRights       50  IESG  [RFC2251]
  busy                           51  IESG  [RFC2251]
  unavailable                    52  IESG  [RFC2251]
  unwillingToPerform             53  IESG  [RFC2251]
  loopDetect                     54  IESG  [RFC2251]
  reserved                    55-63  IESG
  namingViolation                64  IESG  [RFC2251]
  objectClassViolation           65  IESG  [RFC2251]
  notAllowedOnNonLeaf            66  IESG  [RFC2251]
  notAllowedOnRDN                67  IESG  [RFC2251]
  entryAlreadyExists             68  IESG  [RFC2251]
  objectClassModsProhibited      69  IESG  [RFC2251]
  reserved (resultsTooLarge)     70  IESG  [RFC2251]
  reserved                    71-79  IESG
  other                          80  IESG  [RFC2251]
  reserved (APIs)                81  IESG  [RFC2251]
  reserved (APIs)                82  IESG  [RFC2251]
  reserved (APIs)                83  IESG  [RFC2251]
  reserved (APIs)                84  IESG  [RFC2251]
  reserved (APIs)                85  IESG  [RFC2251]
  reserved (APIs)                86  IESG  [RFC2251]
  reserved (APIs)                87  IESG  [RFC2251]
  reserved (APIs)                88  IESG  [RFC2251]
  reserved (APIs)                89  IESG  [RFC2251]
  reserved (APIs)                90  IESG  [RFC2251]


B.6. Bind Authentication Method

  Method      Value  Owner  Usage        Reference
  ------      -----  -----  -----------  -----------------
  simple          0  IESG   LIMITED USE  [RFC2251,RFC2829]
  krbv42LDAP      1  IESG   OBSOLETE*    [RFC1777]
  krbv42DSA       2  IESG   OBSOLETE*    [RFC1777]
  sasl            3  IESG   COMMON       [RFC2251,RFC2829]

  * These LDAPv2-only mechanisms were deprecated in favor LDAPv3 SASL
    authentication method, specifically when used with the KERBEROS_IV
    mechanism or the GSSAPI mechanism.

Copyright 2001, The Internet Society.  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