draft-ietf-ldapbis-bcp64-00.txt   draft-ietf-ldapbis-bcp64-01.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 20 June 2003 Obsoletes: Expires in six months 27 October 2003
Obsoletes: RFC 3383
IANA Considerations for LDAP IANA Considerations for LDAP
<draft-ietf-ldapbis-bcp64-00.txt> <draft-ietf-ldapbis-bcp64-01.txt>
Status of Memo Status of Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all 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 45 skipping to change at page 3, line 45
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.
IANA may reject obviously bogus registrations described. IANA may reject obviously bogus registrations described.
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 (OIDs). Specifications which assign OIDs to elements Identifiers (OIDs) [X.680]. Specifications which assign OIDs to
SHOULD state who delegated the OIDs for its use. elements SHOULD state who delegated the OIDs for its use.
For IETF developed elements, specifications SHOULD use OIDs under For IETF developed elements, specifications SHOULD use OIDs under
"Internet Directory Numbers" (1.3.6.1.1.x). Numbers under this OID "Internet Directory Numbers" (1.3.6.1.1.x). Numbers under this OID
arc will be assigned upon Expert Review with Specification Required. arc will be assigned upon Expert Review with Specification Required.
Only one OID per specification will be assigned. The specification Only one OID per specification will be assigned. The specification
MAY then assign any number of OIDs within this arc without further MAY then assign any number of OIDs within this arc without further
coordination with 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"
skipping to change at page 7, line 51 skipping to change at page 7, line 51
Standards Action to be registered. New authentication method Standards Action to be registered. New authentication method
integers in the range 1024-4095 require Expert Review with integers in the range 1024-4095 require Expert Review with
Specification Required. New authentication method integers in the Specification Required. New authentication method integers in the
range 4096-16383 will be registered on a First Come First Served range 4096-16383 will be registered on a First Come First Served
basis. Keywords associated with integers in the range 0-4095 SHALL basis. Keywords associated with integers in the range 0-4095 SHALL
NOT start with "e-" or "x-". Keywords associated with integers in NOT start with "e-" or "x-". Keywords associated with integers in
the range 4096-16383 SHALL start with "e-". Values greater than or the range 4096-16383 SHALL start with "e-". Values greater than or
equal to 16384 and keywords starting with "x-" are for Private Use equal to 16384 and keywords starting with "x-" are for Private Use
and cannot be registered. and cannot be registered.
Note: LDAP supports SASL [RFC2222] as an Authentication CHOICE. SASL Note: LDAP supports Simple Authentication and Security Layers [SASL]
is an extensible LDAP authentication method. as an authentication choice. SASL is an extensible LDAP
authentication method.
3.8. Directory Systems Names 3.8. 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], now Historic representation of a distinguished name [RFC1779], now Historic
[RFC3494]. [RFC3494].
Directory systems names are not known to be used in any other Directory systems names are not known to be used in any other
context. LDAPv3 uses Object Identifier Descriptors [Section 3.2] context. LDAPv3 uses Object Identifier Descriptors [Section 3.2]
skipping to change at page 10, line 44 skipping to change at page 10, line 44
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9 (also RFC 2026), October 1996. 3", BCP 9 (also RFC 2026), October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14 (also RFC 2119), March 1997. Requirement Levels", BCP 14 (also RFC 2119), March 1997.
[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26 (also RFC
2434), October 1998.
[Roadmap] Zeilenga, K. (editor), "LDAP: Technical Specification [Roadmap] Zeilenga, K. (editor), "LDAP: Technical Specification
Road Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in Road Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in
progress. progress.
[Protocol] Sermersheim, J. (editor), "LDAP: The Protocol", [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol",
draft-ietf-ldapbis-protocol-xx.txt, a work in progress. draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
[Models] Zeilenga, K. (editor), "LDAP: Directory Information [Models] Zeilenga, K. (editor), "LDAP: Directory Information
Models", draft-ietf-ldapbis-models-xx.txt, a work in Models", draft-ietf-ldapbis-models-xx.txt, a work in
progress. progress.
[LDAPURL] Smith, M. (editor), "LDAP: Uniform Resource Locator", [LDAPURL] Smith, M. (editor), "LDAP: Uniform Resource Locator",
draft-ietf-ldapbis-url-xx.txt, a work in progress. draft-ietf-ldapbis-url-xx.txt, a work in progress.
[UTF-8] Yergeau, F., "UTF-8, a transformation [UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO
format of ISO 10646", draft-yergeau-rfc2279bis, a work 10646", draft-yergeau-rfc2279bis-xx.txt, a work in
in progress. progress.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26 (also RFC
2434), October 1998.
[RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access
Protocol (v3): Technical Specification", RFC 3377,
September 2002.
[ISO10646] International Organization for Standardization, [ISO10646] International Organization for Standardization,
"Universal Multiple-Octet Coded Character Set (UCS) - "Universal Multiple-Octet Coded Character Set (UCS) -
Architecture and Basic Multilingual Plane", ISO/IEC Architecture and Basic Multilingual Plane", ISO/IEC
10646-1 : 1993. 10646-1 : 1993.
[X.680] International Telecommunication Union -
Telecommunication Standardization Sector, "Abstract
Syntax Notation One (ASN.1) - Specification of Basic
Notation", X.680(1997) (also ISO/IEC 8824-1:1998).
10. Informative References 10. Informative References
[RFC1779] Kille, S., "A String Representation of Distinguished [RFC1779] Kille, S., "A String Representation of Distinguished
Names", RFC 1779, March 1995. Names", RFC 1779, March 1995.
[RFC3494] Zeilenga, K., "Lightweight Directory Access Protocol [RFC3494] Zeilenga, K., "Lightweight Directory Access Protocol
version 2 (LDAPv2) to Historic Status", RFC 3494, March version 2 (LDAPv2) to Historic Status", RFC 3494, March
2003. 2003.
[RFC2222] Myers, J., "Simple Authentication and Security Layer [SASL] Melnikov, A. (Editor), "Simple Authentication and
(SASL)", RFC 2222, October 1997. Security Layer (SASL)",
draft-ietf-sasl-rfc2222bis-xx.txt, a work in progress.
Appendix A. Registration Templates Appendix A. Registration Templates
This appendix provides registration templates for registering new This appendix provides registration templates for registering new
LDAP values. LDAP 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
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)
 End of changes. 

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