draft-ietf-ldapbis-iana-02.txt   draft-ietf-ldapbis-iana-03.txt 
INTERNET-DRAFT Kurt D. Zeilenga INTERNET-DRAFT Kurt D. Zeilenga
Intended Category: BCP OpenLDAP Foundation Intended Category: BCP OpenLDAP Foundation
Expires: 26 December 2001 26 June 2001 Expires: 20 January 2002 20 July 2001
IANA Considerations for LDAP IANA Considerations for LDAP
<draft-ietf-ldapbis-iana-02.txt> <draft-ietf-ldapbis-iana-03.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' descriptive names. - Object Identifiers' 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.
skipping to change at page 3, line 41 skipping to change at page 3, line 41
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 Descriptive Names 3.2. Object Identifiers Descriptors
LDAP allows short descriptive names to be used instead of a numeric LDAP allows short descriptive names (or descriptors) to be used
Object Identifier to identify protocol extensions [RFC2251], schema instead of a numeric Object Identifier to identify protocol extensions
elements [RFC2252], protocol extensions, LDAP URL [RFC2255] [RFC2251], schema elements [RFC2252], protocol extensions, LDAP URL
extensions, and other objects. These names SHALL be restricted to [RFC2255] extensions, and other objects. Descriptors SHALL be
UTF-8 case-insensitive strings limited by the following ABNF: restricted to UTF-8 case-insensitive 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.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
descriptive names, they SHOULD be short. IANA MAY refuse to register descriptor, they SHOULD be short. IANA MAY refuse to register any
any name over 48 characters in length. IANA MAY reject obviously descriptor over 48 characters in length. IANA MAY reject obviously
bogus registrations. bogus registrations.
Names 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.
Names beginning with "e-" are reserved for experiments. IANA SHALL Descriptors beginning with "e-" are reserved for experiments. IANA
register any name beginning with "e-" on a First Come First Served SHALL register any descriptor beginning with "e-" on a First Come
basis. First Served basis.
Expert Review is REQUIRED before accepting registration of all other Expert Review is REQUIRED before accepting registration of all other
names. descriptors.
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.3. 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
more options specifying additional semantics. An option SHALL be more options specifying additional semantics. An option SHALL be
skipping to change at page 6, line 30 skipping to change at page 6, line 30
with Specification Required, and in the range 1024-8191 on a First with Specification Required, and in the range 1024-8191 on a First
Come First Served basis. Keywords associated with integers in the Come First Served basis. Keywords associated with integers in the
range 0-1023 SHALL NOT start with "e-" or "x-". Keywords associated range 0-1023 SHALL NOT start with "e-" or "x-". Keywords associated
with integers in the range 1024-8191 SHALL start with "e-". Values with integers in the range 1024-8191 SHALL start with "e-". Values
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
The IANA-maintained "Directory Systems Names" registry [IANADSN] of
valid keywords for well known attributes used in the LDAPv2 string
represention of a distinguished name [RFC 1779]. RFC 1779 was
obsoleted by RFC 2253.
Directory systems names are not known to be used in any other context.
LDAPv3 uses Object Identifier Descriptors [Section 3.2] (which have a
different syntax than directory system names).
IANA SHALL NOT register new Directory System Names. For historical
purposes, the current list of registrated names SHOULD be remain
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 which is new value of a type described in Section 3 of this document.
not currently registered with IANA.
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 7, line 46 skipping to change at page 8, line 16
For cases where others have significant objections to the claims in a For cases where others have significant objections to the claims in a
registration and the author does not agree to change the registration, registration and the author does not agree to change the registration,
comments MAY be attached to registrations after Expert Review. For comments MAY be attached to registrations after Expert Review. For
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. Security considerations to each applicable to this document. Additional security considerations
namespace are discussed in Section 3. specific to each namespace are discussed in Section 3 where
appropriate.
Security considerations for LDAP are detailed in documents comprising Security considerations for LDAP are detailed 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.
skipping to change at page 9, line 30 skipping to change at page 9, line 44
Person & email address to contact for further information: Person & email address to contact for further information:
Specification: (I-D) Specification: (I-D)
Author/Change Controller: Author/Change Controller:
Comments: Comments:
(Any comments that the requester deems relevant to the request) (Any comments that the requester deems relevant to the request)
A.2. LDAP Descriptive Name Registration Template A.2. LDAP Descriptor Registration Template
Subject: Request for LDAP Descriptive Name Registration Subject: Request for LDAP Descriptor Registration
Descriptive Name: Descriptor (short name):
Object Identifier: Object Identifier:
Person & email address to contact for further information: Person & email address to contact for further information:
Usage: (One of attribute type, URL extension, Usage: (One of attribute type, URL extension,
object class, or other) object class, or other)
Specification: (RFC, I-D, URI) Specification: (RFC, I-D, URI)
skipping to change at page 11, line 36 skipping to change at page 12, line 4
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:
ftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbers ftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbers
Currently registered "Internet Directory Numbers" can be found at: Currently registered "Internet Directory Numbers" can be found at:
ftp://ftp.isi.edu/in-notes/iana/assignments/smi-numbers ftp://ftp.isi.edu/in-notes/iana/assignments/smi-numbers
B.2. Object Identifiers Descriptive Names 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]
skipping to change at page 16, line 51 skipping to change at page 17, line 17
x500UniqueIdentifier A 2.5.4.45 [RFC2256] x500UniqueIdentifier A 2.5.4.45 [RFC2256]
Legend Legend
------------------------ ------------------------
A => Attribute Type A => Attribute Type
C => DIT Content Rule C => DIT Content Rule
E => LDAP URL Extension E => LDAP URL Extension
M => Matching Rule M => Matching Rule
N => Name Form N => Name Form
O => Object Class O => Object Class
S => DIT Structural Rule
B.3. Attribute Description Options B.3. Attribute Description Options
Option Owner Reference Option Owner Reference
---------------- ----- --------- ---------------- ----- ---------
binary IESG [RFC2251] binary IESG [RFC2251]
lang-* IESG [RFC2596] lang-* IESG [RFC2596]
* family of options * family of options
B.4. LDAPMessage types B.4. LDAPMessage types
skipping to change at page 18, line 42 skipping to change at page 19, line 9
reserved 55-63 IESG reserved 55-63 IESG
namingViolation 64 IESG [RFC2251] namingViolation 64 IESG [RFC2251]
objectClassViolation 65 IESG [RFC2251] objectClassViolation 65 IESG [RFC2251]
notAllowedOnNonLeaf 66 IESG [RFC2251] notAllowedOnNonLeaf 66 IESG [RFC2251]
notAllowedOnRDN 67 IESG [RFC2251] notAllowedOnRDN 67 IESG [RFC2251]
entryAlreadyExists 68 IESG [RFC2251] entryAlreadyExists 68 IESG [RFC2251]
objectClassModsProhibited 69 IESG [RFC2251] objectClassModsProhibited 69 IESG [RFC2251]
reserved (resultsTooLarge) 70 IESG [RFC2251] reserved (resultsTooLarge) 70 IESG [RFC2251]
reserved 71-79 IESG reserved 71-79 IESG
other 80 IESG [RFC2251] other 80 IESG [RFC2251]
reserved (APIs) 81 IESG [RFC2251] reserved (APIs) 81-90 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 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]
 End of changes. 

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