draft-ietf-ldapbis-iana-06.txt   draft-ietf-ldapbis-iana-07.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 12 May 2002 Expires in six months 17 May 2002
IANA Considerations for LDAP IANA Considerations for LDAP
<draft-ietf-ldapbis-iana-06.txt> <draft-ietf-ldapbis-iana-07.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 4, line 6 skipping to change at page 4, line 6
IANA. 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 implementors of
''works in progress'' and implementors of the published specification ''works in progress'' and implementors 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. progress''. Experimental OIDs MUST replaced before publication. OIDs
OIDs under the Internet Experimental OID arc (1.3.6.1.3.x) may be used under the Internet Experimental OID arc (1.3.6.1.3.x) may be used for
for this purpose. this purpose.
Practices for IANA assignment of Internet Enterprise and Experimental Practices for IANA assignment of Internet Enterprise and Experimental
OIDs are detailed in STD15 [RFC1157]. 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 SHALL be restricted to strings of
UTF-8 encoded UCS characters restricted by the following ABNF: UTF-8 encoded UCS characters restricted by the following ABNF:
name = keystring name = keystring
skipping to change at page 9, line 21 skipping to change at page 9, line 21
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. Normative References
[RFC1157] J. Case, M. Fedor, M. Schoffstall, J. Davin, "A Simple [RFC1155] M. Rose, K. McCloghrie, "Structure and Identification of
Network Management Protocol (SNMP)", STD 15 (also RFC Management Information for TCP/IP-based Internets", STD 16
1157), May 1990. (also RFC 1155), May 1990.
[RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", [RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3",
BCP 9 (also 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", BCP 14 (also RFC 2119), March 1997. Requirement Levels", BCP 14 (also RFC 2119), March 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.
skipping to change at page 13, line 20 skipping to change at page 13, line 20
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]
aRecord A 0.9.2342.19200300.100.1.26 [RFC1274] aRecord A 0.9.2342.19200300.100.1.26 [RFC1274]
associatedDomain A 0.9.2342.19200300.100.1.37 [RFC2164] associatedDomain A 0.9.2342.19200300.100.1.37 [RFC1274]
associatedInternetGateway A 1.3.6.1.4.1.453.7.2.8 [RFC2164] associatedInternetGateway A 1.3.6.1.4.1.453.7.2.8 [RFC2164]
associatedName A 0.9.2342.19200300.100.1.38 [RFC1274] associatedName A 0.9.2342.19200300.100.1.38 [RFC1274]
associatedORAddress A 1.3.6.1.4.1.453.7.2.6 [RFC2164] associatedORAddress A 1.3.6.1.4.1.453.7.2.6 [RFC2164]
associatedX400Gateway A 1.3.6.1.4.1.453.7.2.3 [RFC2164] associatedX400Gateway A 1.3.6.1.4.1.453.7.2.3 [RFC2164]
attributeTypes A 2.5.21.5 [RFC2252] attributeTypes A 2.5.21.5 [RFC2252]
audio A 0.9.2342.19200300.100.1.55 [RFC1274] audio A 0.9.2342.19200300.100.1.55 [RFC1274]
authorityRevocationList A 2.5.4.38 [RFC2256] authorityRevocationList A 2.5.4.38 [RFC2256]
bitStringMatch M 2.5.13.16 [RFC2252] bitStringMatch M 2.5.13.16 [RFC2252]
buildingName A 0.9.2342.19200300.100.1.48 [RFC1274] buildingName A 0.9.2342.19200300.100.1.48 [RFC1274]
businessCategory A 2.5.4.15 [RFC2256] businessCategory A 2.5.4.15 [RFC2256]
 End of changes. 

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