draft-ietf-ldapbis-iana-03.txt   draft-ietf-ldapbis-iana-04.txt 
INTERNET-DRAFT Kurt D. Zeilenga INTERNET-DRAFT Kurt D. Zeilenga
Intended Category: BCP OpenLDAP Foundation Intended Category: BCP OpenLDAP Foundation
Expires: 20 January 2002 20 July 2001 Expires: 20 May 2002 20 November 2001
IANA Considerations for LDAP IANA Considerations for LDAP
<draft-ietf-ldapbis-iana-03.txt> <draft-ietf-ldapbis-iana-04.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 2, line 19 skipping to change at page 2, line 19
- 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 values of used to
unambiguously identify extensible elements of the protocol including: unambiguously identify extensible elements of the protocol 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' descriptors. - Object Identifier descriptors.
These registries are maintained by the Internet Assigned Numbers These registries are maintained by the Internet Assigned Numbers
Authority (IANA). Authority (IANA).
In addition, this document provides guidelines to IANA describing the 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. Terminology and Conventions 2. Terminology and Conventions
This section details terms and conventions used in this document. This section details terms and conventions used in this document.
2.1. Policy Terminology 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 BCP 26 [RFC2434].
2.2. Requirement Terminology 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 BCP 14 [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
[RFC2234]. These syntaxes rely on the following common productions: [RFC2234]. These syntaxes rely on the following common productions:
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
LDIGIT = %x31-39 ; 1-9 LDIGIT = %x31-39 ; 1-9
DIGIT = %x30 / LDIGIT ; 0-9 DIGIT = %x30 / LDIGIT ; 0-9
HYPHEN = %x2D ; "-" HYPHEN = %x2D ; "-"
PERIOD = %x2E ; "." PERIOD = %x2E ; "."
number = DIGIT / ( LDIGIT 1*DIGIT ) number = DIGIT / ( LDIGIT 1*DIGIT )
skipping to change at page 3, line 41 skipping to change at page 3, line 44
under "Internet Private Enterprise Numbers" (1.3.5.1.4.1.x) assigned under "Internet Private Enterprise Numbers" (1.3.5.1.4.1.x) assigned
by IANA <http://www.iana.org/cgi-bin/enterprise.pl>. by IANA <http://www.iana.org/cgi-bin/enterprise.pl>.
For IETF developed protocol and schema elements, OIDs under "Internet For IETF developed protocol and schema elements, OIDs under "Internet
Directory Numbers" (1.3.6.1.1.x) MAY be used. IANA will assign Directory Numbers" (1.3.6.1.1.x) MAY be used. IANA will assign
numbers under this OID arc upon Expert Review with Specification numbers under this OID arc upon Expert Review with Specification
Required. In general, only one OID per specification SHOULD be Required. In general, only one OID per specification SHOULD be
assigned. The specification may then assign any number of OIDs within assigned. The specification may then assign any number of OIDs within
this arc without further coordination with IANA. this arc without further coordination with IANA.
3.2. Object Identifiers Descriptors 3.2. Object Identifier Descriptors
LDAP allows short descriptive names (or descriptors) to be used LDAP allows short descriptive names (or descriptors) to be used
instead of a numeric Object Identifier to identify protocol extensions instead of a numeric Object Identifier to identify protocol extensions
[RFC2251], schema elements [RFC2252], protocol extensions, LDAP URL [RFC2251], schema elements [RFC2252], LDAP URL [RFC2255] extensions,
[RFC2255] extensions, and other objects. Descriptors SHALL be and other objects. Descriptors SHALL be restricted to UTF-8
restricted to UTF-8 case-insensitive strings limited by the following case-insensitive strings limited by the following ABNF:
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.0.23.40 numericoid = number *( PERIOD number ) ; e.g. 1.1.0.23.40
While the protocol places no maximum length restriction upon While the protocol places no maximum length restriction upon
descriptor, they SHOULD be short. IANA MAY refuse to register any descriptors, they SHOULD be short. IANA MAY refuse to register any
descriptor over 48 characters in length. IANA MAY reject obviously descriptor over 48 characters in length. IANA MAY reject obviously
bogus registrations. bogus registrations.
Descriptors beginning with "x-" are for Private Use and SHALL NOT be Descriptors beginning with "x-" are for Private Use and SHALL NOT be
registered. registered.
Descriptors beginning with "e-" are reserved for experiments. IANA Descriptors beginning with "e-" are reserved for experiments. IANA
SHALL register any descriptor beginning with "e-" on a First Come SHALL register any descriptor beginning with "e-" on a First Come
First Served basis. First Served basis.
skipping to change at page 5, line 47 skipping to change at page 6, line 4
Standards Action, in the range 256-1023 with Expert Review, and in the Standards Action, in the range 256-1023 with Expert Review, and in the
range 1024-8191 on a First Come First Served basis. Keywords range 1024-8191 on a First Come First Served basis. Keywords
associated with integers in the range 0-1023 SHALL NOT start with "e-" associated with integers in the range 0-1023 SHALL NOT start with "e-"
or "x- the range 1024-8191 SHALL start with "e-". Values greater than or "x- the range 1024-8191 SHALL start with "e-". Values greater than
or equal to 8192 and keywords starting with "x-" are for Private Use or equal to 8192 and keywords starting with "x-" are for Private Use
and SHALL NOT be registered. and SHALL NOT be registered.
IANA MAY reject obviously bogus registrations. IANA MAY reject obviously bogus registrations.
3.6. 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 use. LIMITED USE - method is appropriate for limited use,
OBSOLETE - method has been deprecated or otherwise 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 authentication methods. Methods IANA SHALL NOT register new OBSOLETE authentication methods. Methods
without publicly available specifications SHALL NOT be classified as without publicly available specifications SHALL NOT be classified as
COMMON. IANA MAY reject obviously bogus registrations. COMMON. IANA MAY reject obviously bogus registrations.
IANA SHALL register new authentication method integers in the range IANA SHALL register new authentication method integers in the range
0-255 upon Standards Action, in the range 256-1023 with Expert Review 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 with Specification Required, and in the range 1024-8191 on a First
skipping to change at page 6, line 34 skipping to change at page 6, line 36
greater than or equal to 8192 and keywords starting with "x-" are for greater than or equal to 8192 and keywords starting with "x-" are for
Private Use and SHALL NOT be registered. 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.
3.7. Directory Systems Names 3.7. Directory Systems Names
The IANA-maintained "Directory Systems Names" registry [IANADSN] of The IANA-maintained "Directory Systems Names" registry [IANADSN] of
valid keywords for well known attributes used in the LDAPv2 string valid keywords for well known attributes used in the LDAPv2 string
represention of a distinguished name [RFC 1779]. RFC 1779 was representation of a distinguished name [RFC1779]. RFC 1779 was
obsoleted by RFC 2253. obsoleted by RFC 2253.
Directory systems names are not known to be used in any other context. Directory systems names are not known to be used in any other context.
LDAPv3 uses Object Identifier Descriptors [Section 3.2] (which have a LDAPv3 uses Object Identifier Descriptors [Section 3.2] (which have a
different syntax than directory system names). different syntax than directory system names).
IANA SHALL NOT register new Directory System Names. For historical IANA SHALL NOT register new Directory System Names. For historical
purposes, the current list of registrated names SHOULD be remain purposes, the current list of registered names SHOULD be remain
available. available.
4. Registration Procedure 4. Registration Procedure
The procedure given here MUST be used by anyone who wishes to use a The procedure given here MUST be used by anyone who wishes to use a
new value of a type described in Section 3 of this document. new value of a type described in Section 3 of this document.
The first step is for the requester to fill out the appropriate form. The first step is for the requester 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. The IESG SHALL be viewed as the owner of (possibly revised) to IANA. The IESG SHALL be viewed as the owner of
all values requiring Standards Action. 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.
skipping to change at page 8, line 20 skipping to change at page 8, line 21
registrations owned by the IESG, the objections SHOULD be addressed by registrations owned by the IESG, the objections SHOULD be addressed by
initiating a Change Control request. 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. Additional security considerations applicable to this document. Additional security considerations
specific to each namespace are discussed in Section 3 where specific to each namespace are discussed in Section 3 where
appropriate. appropriate.
Security considerations for LDAP are detailed in documents comprising Security considerations for LDAP are discussed in documents comprising
the technical specification [LDAPTS]. the technical specification [LDAPTS].
7. Acknowledgment 7. Acknowledgment
This document is a product of the IETF LDAP Revision (LDAPbis) Working This document is a product of the IETF LDAP Revision (LDAPbis) Working
Group. Some text was borrowed from "Guidelines for Writing an IANA Group. Some text was borrowed from "Guidelines for Writing an IANA
Considerations Section in RFCs" [RFC2434] by Thomas Narten and Harald Considerations Section in RFCs" [RFC2434] by Thomas Narten and Harald
Alvestrand. 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. Normative References
[RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", [RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3",
RFC 2026, October 1996. BCP 9 (also 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", BCP 14 (also 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.
[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.
skipping to change at page 9, line 23 skipping to change at page 9, line 23
[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", [RFC2279] F. Yergeau, "UTF-8, a transformation format of ISO 10646",
RFC 2279, January 1998. 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", BCP 26 (also RFC 2434),
October 1998.
[LDAPTS] J. Hodges, R.L. Morgan, "Lightweight Directory Access
Protocol (v3): Technical Specification", draft-ietf-ldapbis-
ldapv3-ts-00.txt (a work in progress).
10. Informative References
[RFC2222] J. Myers, "Simple Authentication and Security Layer (SASL)",
RFC 2222, October 1997.
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. values.
A.1. LDAP Object Identifier Registration Template A.1. LDAP Object Identifier Registration Template
Subject: Request for LDAP OID Registration Subject: Request for LDAP OID Registration
skipping to change at page 11, line 46 skipping to change at page 12, line 12
(Any comments that the requester deems relevant to the request) (Any comments that the requester deems relevant to the request)
Appendix B. Assigned Values Appendix B. Assigned Values
The following values are currently assigned. The following values are currently assigned.
B.1. Object Identifiers B.1. Object Identifiers
Currently registered "Internet Private Enterprise Numbers" can be Currently registered "Internet Private Enterprise Numbers" can be
found at: found at: http://www.isi.edu/in-notes/iana/assignments/enterprise-
ftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbers numbers
Currently registered "Internet Directory Numbers" can be found at: Currently registered "Internet Directory Numbers" can be found at:
http://www.iana.org/assignments/smi-numbers
ftp://ftp.isi.edu/in-notes/iana/assignments/smi-numbers B.2. Object Identifier Descriptors
B.2. Object Identifiers Descriptors
NAME Type OID [REF] NAME Type OID [REF]
------------------------ ---- ----------------- ------------------------ ---- -----------------
account O 0.9.2342.19200300.100.4.5 [RFC1274] account O 0.9.2342.19200300.100.4.5 [RFC1274]
alias O 2.5.6.1 [RFC2256] alias O 2.5.6.1 [RFC2256]
aliasedEntryName A 2.5.4.1 [X.501] aliasedEntryName A 2.5.4.1 [X.501]
aliasedObjectName A 2.5.4.1 [RFC2256] aliasedObjectName A 2.5.4.1 [RFC2256]
altServer A 1.3.6.1.4.1.1466.101.120.6 [RFC2252] altServer A 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]
 End of changes. 

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