draft-ietf-ldapbis-iana-07.txt   draft-ietf-ldapbis-iana-08.txt 
INTERNET-DRAFT Kurt D. Zeilenga INTERNET-DRAFT Kurt D. Zeilenga
Intended Category: BCP OpenLDAP Foundation Intended Category: BCP OpenLDAP Foundation
Expires in six months 17 May 2002 Expires in six months 29 July 2002
IANA Considerations for LDAP IANA Considerations for LDAP
<draft-ietf-ldapbis-iana-07.txt> <draft-ietf-ldapbis-iana-08.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 3, line 35 skipping to change at page 3, line 35
restricted to the <keystring> production. restricted to the <keystring> production.
3. IANA Considerations for LDAP 3. IANA Considerations for LDAP
This section details each kind of protocol value which can be This section details each kind of protocol value 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 3.1. Object Identifiers
Numerous LDAP schema and protocol elements are identified by Object Numerous LDAP schema and protocol elements are identified by Object
Identifiers. Specifications which assign OID to elements SHOULD state Identifiers. Specifications which assign OIDs to elements SHOULD
who delegated the OIDs for its use. state who delegated the OIDs for its use.
For IETF developed elements, OIDs under "Internet Directory Numbers" For IETF developed elements, specifications SHOULD use OIDs under
(1.3.6.1.1.x) SHOULD be used. IANA will assign numbers under this OID "Internet Directory Numbers" (1.3.6.1.1.x). Numbers under this OID
arc upon Expert Review with Specification Required. Only one OID per arc will be assigned upon Expert Review with Specification Required.
specification SHOULD be assigned. The specification MAY then assign Only one OID per specification will be assigned. The specification
any number of OIDs within this arc without further coordination with MAY then assign any number of OIDs within this arc without further
IANA. coordination with IANA.
For elements developed by others, any properly delegated OID can be For elements developed by others, any properly delegated OID can be
used, including those under "Internet Private Enterprise Numbers" used, including those under "Internet Private Enterprise Numbers"
(1.3.6.1.4.1.x) assigned by IANA (1.3.6.1.4.1.x) assigned by IANA
<http://www.iana.org/cgi-bin/enterprise.pl>. <http://www.iana.org/cgi-bin/enterprise.pl>.
To avoid interoperability problems between early implementors of To avoid interoperability problems between early implementions of
''works in progress'' and implementors of the published specification ''works in progress'' and implementions of the published specification
(e.g., the RFC), experimental OIDs SHOULD be used in ''works in (e.g., the RFC), experimental OIDs SHOULD be used in ''works in
progress''. Experimental OIDs MUST replaced before publication. OIDs progress'' and early implementations. OIDs under the Internet
under the Internet Experimental OID arc (1.3.6.1.3.x) may be used for Experimental OID arc (1.3.6.1.3.x) may be used for this purpose.
this purpose.
Experimental OIDs are not to used in published specifications (e.g.
RFCs).
Practices for IANA assignment of Internet Enterprise and Experimental Practices for IANA assignment of Internet Enterprise and Experimental
OIDs are detailed in STD 16 [RFC1155]. OIDs are detailed in STD 16 [RFC1155].
3.2. Object Identifier 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], LDAP URL [RFC2255] extensions, [RFC2251], schema elements [RFC2252], LDAP URL [RFC2255] extensions,
and other objects. Descriptors SHALL be restricted to strings of and other objects. Descriptors are restricted to strings of UTF-8
UTF-8 encoded UCS characters restricted by the following ABNF: encoded UCS characters restricted by the following ABNF:
name = keystring name = keystring
Descriptors are case-insensitive. Descriptors are case-insensitive.
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 is to be represented in numeric OID form
conforming to the ABNF: conforming to the ABNF:
numericoid = number *( DOT number ) ; e.g. 1.1.0.23.40 numericoid = number *( DOT 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
descriptors, they SHOULD be short. Descriptors longer than 48 descriptors, they should be short. Descriptors longer than 48
characters MAY be viewed as too long to register. IANA MAY reject characters may be viewed as too long to register. IANA may reject
obviously bogus registrations. obviously bogus registrations.
Descriptors beginning with "x-" are for Private Use and SHALL NOT be A values ending with a hyphen ("-") reserve all descriptors which
start with the value. For example, the registration of the option
"descrFamily-" reserves all options which start with "descrFamily-"
for some related purpose.
Descriptors beginning with "x-" are for Private Use and cannot be
registered. registered.
Descriptors beginning with "e-" are reserved for experiments. IANA Descriptors beginning with "e-" are reserved for experiments and will
SHALL register any descriptor beginning with "e-" on a First Come be registered on a First Come First Served basis.
First Served basis.
Expert Review is REQUIRED before accepting registration of all other All other descriptors require Expert Review to be registered.
descriptors.
IANA SHALL NOT verify the registrant "owns" the OID being named. The registrant need not "own" 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
restricted to a string UTF-8 encoded UCS characters limited by the restricted to a string UTF-8 encoded UCS characters limited by the
following ABNF: following ABNF:
option = keystring option = keystring
Options are case-insensitive. Options are case-insensitive.
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. Options longer than 24 characters MAY strings, they should be short. Options longer than 24 characters may
be viewed as too long to register. IANA MAY reject obviously bogus be viewed as too long to register. 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 and SHALL NOT Options beginning with "x-" are for Private Use and cannot be
registered. registered.
Options beginning with "e-" are reserved for experiments. IANA SHALL Options beginning with "e-" are reserved for experiments and will be
register any option beginning with "e-" on a First Come First Served registered on a First Come First Served basis.
basis.
IANA SHALL register other options by either Standards Action or Expert All other options require Standards Action or Expert Review with
Review with Specification Required. Specification Required to be registered.
3.4. 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 will be registered upon Standards 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.5. 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 new resultCode integers in the range 0-1023 upon New resultCodes integers in the range 0-1023 require Standards Action
Standards Action, in the range 1024-4095 with Expert Review with to be registered. New resultCode integers in the range 1024-4095
Specification Required, and in the range 4096-16383 on a First Come require Expert Review with Specification Required. New resultCode
integers in the range 4096-16383 will be registered on a First Come
First Served basis. Keywords associated with integers in the range First Served basis. Keywords associated with integers in the range
0-4095 SHALL NOT start with "e-" or "x-". Keywords associated with 0-4095 SHALL NOT start with "e-" or "x-". Keywords associated with
integers in the range 4096-16383 SHALL start with "e-". Values integers in the range 4096-16383 SHALL start with "e-". Values
greater than or equal to 16384 and keywords starting with "x-" are for greater than or equal to 16384 and keywords starting with "x-" are for
Private Use and SHALL NOT be registered. Private Use and cannot 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 The registrant SHALL classify the authentication method usage using
following terms: one of the 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 Methods without publicly available specifications SHALL NOT be
without publicly available specifications SHALL NOT be classified as classified as COMMON. New registrations of class OBSOLETE cannot be
COMMON. IANA MAY reject obviously bogus registrations. registered. IANA may reject obviously bogus registrations.
IANA SHALL register new authentication method integers in the range New authentication method integers in the range 0-1023 require
0-1023 upon Standards Action, in the range 1024-4095 with Expert Standards Action to be registered. New authentication method integers
Review with Specification Required, and in the range 4096-16383 on a in the range 1024-4095 require Expert Review with Specification
First Come First Served basis. Keywords associated with integers in Required. New authenticaiton method integers in the range 4096-16383
the range 0-4095 SHALL NOT start with "e-" or "x-". Keywords will be registered on a First Come First Served basis. Keywords
associated with integers in the range 4096-16383 SHALL start with associated with integers in the range 0-4095 SHALL NOT start with "e-"
"e-". Values greater than or equal to 16384 and keywords starting or "x-". Keywords associated with integers in the range 4096-16383
with "x-" are for Private Use and SHALL NOT be registered. SHALL start with "e-". Values greater than or equal to 16384 and
keywords starting with "x-" are for Private Use and cannot be
registered.
Note: LDAP supports SASL [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
representation of a distinguished name [RFC1779]. 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 New Directory System Names will no longer be accepted. For historical
purposes, the current list of registered names SHOULD remain purposes, the current list of registered names should remain
available. publically 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
skipping to change at page 8, line 8 skipping to change at page 8, line 16
of values registered under Expert Review. of values registered under Expert Review.
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 IANA <iana@iana.org>. The the completed form directly to the IANA <iana@iana.org>. The
requester is viewed as the owner of values registered under First Come requester is viewed as the owner of values registered under First Come
First Served. First Served.
Neither the Expert nor IANA will take position on the claims of Neither the Expert nor IANA will take position on the claims of
copyright or trademarks issues regarding completed forms. copyright or trademarks issues regarding completed forms.
Prior to submission of the Internet Draft (I-D) to the RFC Editor but
after IESG review and tentative approval, the document editor SHOULD
revise the I-D to use registered values.
5. Registration Maintenance 5. Registration Maintenance
This section discusses maintenance of registrations. This section discusses maintenance of registrations.
5.1. Lists of Registered Values 5.1. Lists of Registered Values
IANA makes lists of registered values readily available to the IANA makes lists of registered values readily available to the
Internet community on their web site <http://www.iana.org/>. Internet community on their web site <http://www.iana.org/>.
5.2. Change Control 5.2. Change Control
skipping to change at page 15, line 32 skipping to change at page 15, line 42
integerMatch M 2.5.13.14 [RFC2252] integerMatch M 2.5.13.14 [RFC2252]
internationaliSDNNumber A 2.5.4.25 [RFC2256] internationaliSDNNumber A 2.5.4.25 [RFC2256]
janetMailbox A 0.9.2342.19200300.100.1.46 [RFC1274] janetMailbox A 0.9.2342.19200300.100.1.46 [RFC1274]
jpegPhoto A 0.9.2342.19200300.100.1.60 [RFC1488] jpegPhoto A 0.9.2342.19200300.100.1.60 [RFC1488]
knowledgeInformation A 2.5.4.2 [RFC2256] knowledgeInformation A 2.5.4.2 [RFC2256]
L A 2.5.4.7 [RFC2256] L A 2.5.4.7 [RFC2256]
labeledURI A 1.3.6.1.4.1.250.1.57 [RFC2079] labeledURI A 1.3.6.1.4.1.250.1.57 [RFC2079]
labeledURIObject A 1.3.6.1.4.1.250.3.15 [RFC2079] labeledURIObject A 1.3.6.1.4.1.250.3.15 [RFC2079]
lastModifiedBy A 0.9.2342.19200300.100.1.24 [RFC1274] lastModifiedBy A 0.9.2342.19200300.100.1.24 [RFC1274]
lastModifiedTime A 0.9.2342.19200300.100.1.23 [RFC1274] lastModifiedTime A 0.9.2342.19200300.100.1.23 [RFC1274]
ldapSyntaxes A 1.3.6.1.4.1.1466.101.120.16 [RFC2251] ldapSyntaxes A 1.3.6.1.4.1.1466.101.120.16 [RFC2252]
locality O 2.5.6.3 [RFC2256] locality O 2.5.6.3 [RFC2256]
localityName A 2.5.4.7 [RFC2256] localityName A 2.5.4.7 [RFC2256]
mail A 0.9.2342.19200300.100.1.3 [RFC2798] mail A 0.9.2342.19200300.100.1.3 [RFC2798]
mailPreferenceOption A 0.9.2342.19200300.100.1.47 [RFC1274] mailPreferenceOption A 0.9.2342.19200300.100.1.47 [RFC1274]
manager A 0.9.2342.19200300.100.1.10 [RFC1274] manager A 0.9.2342.19200300.100.1.10 [RFC1274]
matchingRules A 2.5.21.4 [RFC2252] matchingRules A 2.5.21.4 [RFC2252]
matchingRuleUse A 2.5.21.8 [RFC2252] matchingRuleUse A 2.5.21.8 [RFC2252]
mcgamTables A 1.3.6.1.4.1.453.7.2.9 [RFC2164] mcgamTables A 1.3.6.1.4.1.453.7.2.9 [RFC2164]
mDRecord A 0.9.2342.19200300.100.1.27 [RFC1274] mDRecord A 0.9.2342.19200300.100.1.27 [RFC1274]
member A 2.5.4.31 [RFC2256] member A 2.5.4.31 [RFC2256]
skipping to change at page 16, line 47 skipping to change at page 17, line 9
pkiUser O 2.5.6.21 [RFC2587] pkiUser O 2.5.6.21 [RFC2587]
postalAddress A 2.5.4.16 [RFC2256] postalAddress A 2.5.4.16 [RFC2256]
postalCode A 2.5.4.17 [RFC2256] postalCode A 2.5.4.17 [RFC2256]
postOfficeBox A 2.5.4.18 [RFC2256] postOfficeBox A 2.5.4.18 [RFC2256]
preferredDeliveryMethod A 2.5.4.28 [RFC2256] preferredDeliveryMethod A 2.5.4.28 [RFC2256]
presentationAddress A 2.5.4.29 [RFC2256] presentationAddress A 2.5.4.29 [RFC2256]
presentationAddressMatch M 2.5.13.22 [RFC2252] presentationAddressMatch M 2.5.13.22 [RFC2252]
protocolInformation A 2.5.4.48 [RFC2256] protocolInformation A 2.5.4.48 [RFC2256]
protocolInformationMatch M 2.5.13.24 [RFC2252] protocolInformationMatch M 2.5.13.24 [RFC2252]
qualityLabelledData O 0.9.2342.19200300.100.4.22 [RFC1274] qualityLabelledData O 0.9.2342.19200300.100.4.22 [RFC1274]
ref A 2.16.840.1.113730.3.1.34 [RFC3296]
referral 0 2.16.840.1.113730.3.2.6 [RFC3296]
registeredAddress A 2.5.4.26 [RFC2256] registeredAddress A 2.5.4.26 [RFC2256]
residentialPerson O 2.5.6.10 [RFC2256] residentialPerson O 2.5.6.10 [RFC2256]
RFC822LocalPart O 0.9.2342.19200300.100.4.14 [RFC1274] RFC822LocalPart O 0.9.2342.19200300.100.4.14 [RFC1274]
RFC822Mailbox A 0.9.2342.19200300.100.1.3 [RFC1274] RFC822Mailbox A 0.9.2342.19200300.100.1.3 [RFC1274]
rFC822ToX400Mapping O 1.3.6.1.4.1.453.7.1.1 [RFC2164] rFC822ToX400Mapping O 1.3.6.1.4.1.453.7.1.1 [RFC2164]
roleOccupant A 2.5.4.33 [RFC2256] roleOccupant A 2.5.4.33 [RFC2256]
room O 0.9.2342.19200300.100.4.7 [RFC1274] room O 0.9.2342.19200300.100.4.7 [RFC1274]
roomNumber A 0.9.2342.19200300.100.1.6 [RFC1274] roomNumber A 0.9.2342.19200300.100.1.6 [RFC1274]
searchGuide A 2.5.4.14 [RFC2256] searchGuide A 2.5.4.14 [RFC2256]
secretary A 0.9.2342.19200300.100.1.21 [RFC1274] secretary A 0.9.2342.19200300.100.1.21 [RFC1274]
 End of changes. 

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