draft-ietf-ldapbis-bcp64-02.txt   draft-ietf-ldapbis-bcp64-03.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 15 February 2004 Expires in six months 4 June 2004
Obsoletes: RFC 3383 Obsoletes: RFC 3383
IANA Considerations for LDAP IANA Considerations for LDAP
<draft-ietf-ldapbis-bcp64-02.txt> <draft-ietf-ldapbis-bcp64-03.txt>
Status of Memo 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 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. This document is intended to replace RFC 3383.
discussion of this document will take place on the IETF LDAP Revision Distribution of this memo is unlimited. Technical discussion of this
Working Group (LDAPBIS) mailing list <ietf-ldapbis@openldap.org>. document will take place on the IETF LDAP Revision Working Group
Please send editorial comments directly to the document editor (LDAPBIS) mailing list <ietf-ldapbis@openldap.org>. Please send
editorial comments directly to the document editor
<Kurt@OpenLDAP.org>. <Kurt@OpenLDAP.org>.
By submitting this Internet-Draft, I accept the provisions of Section
4 of RFC 3667. By submitting this Internet-Draft, I certify that any
applicable patent or other IPR claims of which I am aware have been
disclosed, and any of which I become aware will be disclosed, in
accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as groups may also distribute working documents as Internet-Drafts.
Internet-Drafts. Internet-Drafts are draft documents valid for a
maximum of six months and may be updated, replaced, or obsoleted by Internet-Drafts are draft documents valid for a maximum of six months
other documents at any time. It is inappropriate to use and may be updated, replaced, or obsoleted by other documents at any
Internet-Drafts as reference material or to cite them other than as time. It is inappropriate to use Internet-Drafts as reference
``work in progress.'' material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
<http://www.ietf.org/ietf/1id-abstracts.txt>. The list of http://www.ietf.org/ietf/1id-abstracts.txt. The list of
Internet-Draft Shadow Directories can be accessed at Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>. http://www.ietf.org/shadow.html.
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Please see the Full Copyright section near the end of this document Please see the Full Copyright section near the end of this document
for more information. for more information.
Abstract Abstract
This document provides procedures for registering extensible elements This document provides procedures for registering extensible elements
of Lightweight Directory Access Protocol (LDAP). The document also of Lightweight Directory Access Protocol (LDAP). The document also
skipping to change at page 3, line 48 skipping to change at page 4, line 8
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) [X.680]. Specifications which assign OIDs to Identifiers (OIDs) [X.680]. Specifications which assign OIDs to
elements 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). For elements developed
arc will be assigned upon Expert Review with Specification Required. by others, any properly delegated OID can be used, including those
Only one OID per specification will be assigned. The specification under "Internet Directory Numbers" (1.3.6.1.1.x) or "Internet Private
MAY then assign any number of OIDs within this arc without further Enterprise Numbers" (1.3.6.1.4.1.x).
coordination with IANA.
For elements developed by others, any properly delegated OID can be Internet Directory Numbers (1.3.6.1.1.x) will be assigned upon Expert
used, including those under "Internet Private Enterprise Numbers" Review with Specification Required. Only one OID per specification
(1.3.6.1.4.1.x) assigned by IANA will be assigned. The specification MAY then assign any number of
<http://www.iana.org/cgi-bin/enterprise.pl>. OIDs within this arc without further coordination with IANA.
Internet Private Enterprise Numbers (1.3.6.1.4.1.x) are assigned by
IANA <http://www.iana.org/cgi-bin/enterprise.pl>.
To avoid interoperability problems between early implementations of a To avoid interoperability problems between early implementations of a
"work in progress" and implementations of the published specification "work in progress" and implementations 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" and early implementations. OIDs under the Internet progress" and early implementations. OIDs under the Internet
Experimental OID arc (1.3.6.1.3.x) may be used for this purpose. Experimental OID arc (1.3.6.1.3.x) may be used for this purpose.
Experimental OIDs SHALL NOT be used in published specifications (e.g. Experimental OIDs SHALL NOT be used in published specifications (e.g.
RFCs). RFCs).
skipping to change at page 10, line 32 skipping to change at page 10, line 39
IANA Considerations Section in RFCs" [RFC2434] by Thomas Narten and IANA Considerations Section in RFCs" [RFC2434] by Thomas Narten and
Harald Alvestrand. Harald 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. Normative References 9. References
[[Note to the RFC Editor: please replace the citation tags used in
referencing Internet-Drafts with tags of the form RFCnnnn.]]
9.1. Normative References
[RFC1155] Rose, M. and K. McCloghrie, "Structure and [RFC1155] Rose, M. and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP- Identification of Management Information for TCP/IP-
based Internets", STD 16 (also RFC 1155), May 1990. based Internets", STD 16 (also RFC 1155), May 1990.
[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 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26 (also RFC IANA Considerations Section in RFCs", BCP 26 (also RFC
2434), October 1998. 2434), October 1998.
[RFC3639] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", RFC 3639 (also STD 63), November 2003. 10646", RFC 3629 (also STD 63), November 2003.
[Features] Zeilenga, K., "Feature Discovery in LDAP", RFC 3674, [Features] Zeilenga, K., "Feature Discovery in LDAP", RFC 3674,
December 2003. December 2003.
[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.
skipping to change at page 11, line 38 skipping to change at page 12, line 5
as amended by the "Unicode Standard Annex #27: Unicode as amended by the "Unicode Standard Annex #27: Unicode
3.1" (http://www.unicode.org/reports/tr27/) and by the 3.1" (http://www.unicode.org/reports/tr27/) and by the
"Unicode Standard Annex #28: Unicode 3.2" "Unicode Standard Annex #28: Unicode 3.2"
(http://www.unicode.org/reports/tr28/). (http://www.unicode.org/reports/tr28/).
[X.680] International Telecommunication Union - [X.680] International Telecommunication Union -
Telecommunication Standardization Sector, "Abstract Telecommunication Standardization Sector, "Abstract
Syntax Notation One (ASN.1) - Specification of Basic Syntax Notation One (ASN.1) - Specification of Basic
Notation", X.680(1997) (also ISO/IEC 8824-1:1998). Notation", X.680(1997) (also ISO/IEC 8824-1:1998).
10. Informative References 9.2. 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.
[IANADSN] IANA, "Directory Systems Names", [IANADSN] IANA, "Directory Systems Names",
http://www.iana.org/assignments/directory-system-names. http://www.iana.org/assignments/directory-system-names.
[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.
skipping to change at page 15, line 22 skipping to change at page 15, line 36
- References to ISO 10646 have been replaced with [Unicode]. - References to ISO 10646 have been replaced with [Unicode].
- The "Assigned Values" appendix providing initial registry values - The "Assigned Values" appendix providing initial registry values
was removed. was removed.
- Numerous editorial changes were made. - Numerous editorial changes were made.
Full Copyright Full Copyright
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published and OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
distributed, in whole or in part, without restriction of any kind, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Intellectual Property Rights
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed, The IETF takes no position regarding the validity or scope of any
or as required to translate it into languages other than English. Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be found
in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this specification
can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 

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