< draft-zeilenga-ldap-cosine-01.txt   draft-zeilenga-ldap-cosine-02.txt >
INTERNET-DRAFT Editor: Kurt D. Zeilenga INTERNET-DRAFT Editor: Kurt D. Zeilenga
Intended Category: Standard Track OpenLDAP Foundation Intended Category: Standard Track OpenLDAP Foundation
Expires in six months 23 October 2005 Expires in six months 6 February 2006
Obsoletes: RFC 1274, RFC 2247 Obsoletes: RFC 1274
Updates: RFC 2798 Updates: RFC 2247, RFC 2798
COSINE LDAP/X.500 Schema COSINE LDAP/X.500 Schema
<draft-zeilenga-ldap-cosine-01.txt> <draft-zeilenga-ldap-cosine-02.txt>
Status of this Memo Status of this Memo
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 Standard Track document. revision, submitted to the RFC Editor as a Standard Track document.
Distribution of this memo is unlimited. Technical discussion of this Distribution of this memo is unlimited. Technical discussion of this
document will take place on the IETF LDAPEXT mailing list document will take place on the IETF LDAPEXT mailing list
<ldapext@ietf.org>. Please send editorial comments directly to the <ldapext@ietf.org>. Please send editorial comments directly to the
author <Kurt@OpenLDAP.org>. author <Kurt@OpenLDAP.org>.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress." 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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of 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 (2005). All Rights Reserved. Copyright (C) The Internet Society (2006). 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 a collection of schema elements for use with This document provides a collection of schema elements for use with
the Lightweight Directory Access Protocol (LDAP) from the COSINE and the Lightweight Directory Access Protocol (LDAP) from the COSINE and
Internet X.500 pilot projects. Internet X.500 pilot projects.
This document obsoletes RFC 1274 and RFC 2247. This document obsoletes RFC 1274 and updates RFC 2247 and RFC 2798.
Table of Contents Table of Contents
Status of this Memo 1 Status of this Memo 1
Abstract 2 Abstract 2
Table of Contents Table of Contents
1. Background and Intended Use 3 1. Background and Intended Use 3
1.1. Relationship with Other Documents 1.1. Relationship with Other Documents
1.2. Terminology and Conventions 1.2. Terminology and Conventions
2. COSINE Attribute Types 4 2. COSINE Attribute Types 4
skipping to change at page 3, line 49 skipping to change at page 3, line 49
schema elements are in wide use today. As the old schema descriptions schema elements are in wide use today. As the old schema descriptions
cannot be used without adaptation, interoperabilty issues may arise cannot be used without adaptation, interoperabilty issues may arise
due to lack of standardized modern schema descriptions. due to lack of standardized modern schema descriptions.
This document addresses these issues by offering standardized schema This document addresses these issues by offering standardized schema
descriptions, where needed, for widely-used COSINE schema elements. descriptions, where needed, for widely-used COSINE schema elements.
1.1. Relationship to Other Documents 1.1. Relationship to Other Documents
This document, together with [Schema] and [Syntaxes], obsoletes RFC This document, together with [Schema] and [Syntaxes], obsoletes RFC
1274 in its entirety. [Schema] replaces Sections 9.3.1 (Userid) and 1274 in its entirety. [Schema] replaces sections 9.3.1 (Userid) and
Section 9.3.21 (Domain Component) of RFC 1274. [Syntaxes] replaces 9.3.21 (Domain Component) of RFC 1274. [Syntaxes] replaces section
section 9.4 (Generally useful syntaxes) of RFC 1274. 9.4 (Generally useful syntaxes) of RFC 1274.
This document replaces the remainder of RFC 1274. Appendix A. This document replaces the remainder of RFC 1274. Appendix A.
discusses changes since RFC 1274, as well as why certain schema discusses changes since RFC 1274, as well as why certain schema
elements were not brought forward in this revision of the COSINE elements were not brought forward in this revision of the COSINE
schema. All elements not brought are to be regarded as Historic. schema. All elements not brought are to be regarded as Historic.
This document, together with [NamingPlan] and [Schema], obsoletes RFC The description of the 'domain' object class provided in this document
2247 in its entirety. [Schema] replaces Section 4 (Attribute Type supercedes that found in RFC 2247. That is, section 3.4 of this
Definition) and Section 5.1 (The dcObject object class) of RFC 2247. document replaces section 5.2 of RFC 2247.
This document replaces Section 5.2 (The domain object class) of RFC
2247. The remainder of RFC 2247 is replaced by [NamingPlan].
Some of these items were described in RFC 2798 (inetOrgPerson schema). Some of schema elements specified here were described in RFC 2798
This document supersedes these descriptions. This document, together (inetOrgPerson schema). This document supersedes these descriptions.
with [Schema], replaces section 9.1.3 of RFC 2798. This document, together with [Schema], replaces section 9.1.3 of RFC
2798.
1.2. Terminology and Conventions 1.2. Terminology and Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 [RFC2119]. document are to be interpreted as described in BCP 14 [RFC2119].
DIT stands for Directory Information Tree. DIT stands for Directory Information Tree.
DN stands for Distinguished Name. DN stands for Distinguished Name.
DSA stands for Directory System Agent, a server. DSA stands for Directory System Agent, a server.
skipping to change at page 4, line 45 skipping to change at page 4, line 44
Schema definitions are provided using LDAP description formats Schema definitions are provided using LDAP description formats
[Models]. Definitions provided here are formatted (line wrapped) for [Models]. Definitions provided here are formatted (line wrapped) for
readability. readability.
2. COSINE Attribute Types 2. COSINE Attribute Types
This section details COSINE attribute types for use in LDAP. This section details COSINE attribute types for use in LDAP.
2.1. associatedDomain 2.1. associatedDomain
The 'associatedDomain' attribute specifies DNS domains [RFC1034] which The 'associatedDomain' attribute specifies DNS [RFC1034][RFC2181] host
are associated with an object. For example, the entry in the DIT with names [RFC1123] which are associated with an object. That is, values
a DN <DC=example,DC=com> might have an associated domain of of this attribute should conform to the following ABNF:
"example.com".
domain = root / label *( DOT label )
root = SPACE
label = LETDIG [ *61( LETDIG / HYPHEN ) LETDIG ]
LETDIG = %x30-39 / %x41-5A / %x61-7A ; "0" - "9" / "A"-"Z" / "a"-"z"
SPACE = %x20 ; space (" ")
HYPHEN = %x2D ; hyphen ("-")
DOT = %x2E ; period (".")
For example, the entry in the DIT with a DN <DC=example,DC=com> might
have an associated domain of "example.com".
( 0.9.2342.19200300.100.1.37 NAME 'associatedDomain' ( 0.9.2342.19200300.100.1.37 NAME 'associatedDomain'
EQUALITY caseIgnoreIA5Match EQUALITY caseIgnoreIA5Match
SUBSTR caseIgnoreIA5SubstringsMatch SUBSTR caseIgnoreIA5SubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
The IA5String (1.3.6.1.4.1.1466.115.121.1.26) syntax and the The IA5String (1.3.6.1.4.1.1466.115.121.1.26) syntax and the
'caseIgnoreIA5Match' and 'caseIgnoreIA5SubstringsMatch' rules are 'caseIgnoreIA5Match' and 'caseIgnoreIA5SubstringsMatch' rules are
described in [Syntaxes]. described in [Syntaxes].
It is noted that the directory will not ensure that values of this It is noted that the directory will not ensure that values of this
attribute conform to the <domain> production [RFC1034]. It is the attribute conform to the <domain> production provided above. It is
application responsibility to ensure domains it stores in this the application responsibility to ensure domains it stores in this
attribute are appropriately represented. attribute are appropriately represented.
It is also noted that applications supporting Internationalized Domain It is also noted that applications supporting Internationalized Domain
Names SHALL use the ToASCII method [RFC3490] to produce <label> Names SHALL use the ToASCII method [RFC3490] to produce <label>
components of the <domain> production. components of the <domain> production.
2.2. associatedName 2.2. associatedName
The 'associatedName' attribute specifies names of entries in the The 'associatedName' attribute specifies names of entries in the
organizational DIT associated with a DNS domain [RFC1034]. organizational DIT associated with a DNS domain [RFC1034][RFC2181].
( 0.9.2342.19200300.100.1.38 NAME 'associatedName' ( 0.9.2342.19200300.100.1.38 NAME 'associatedName'
EQUALITY distinguishedNameMatch EQUALITY distinguishedNameMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
The DistinguishedName (1.3.6.1.4.1.1466.115.121.1.12) syntax and the The DistinguishedName (1.3.6.1.4.1.1466.115.121.1.12) syntax and the
'distinguishedNameMatch' rule are described in [Syntaxes]. 'distinguishedNameMatch' rule are described in [Syntaxes].
2.3. buildingName 2.3. buildingName
skipping to change at page 21, line 33 skipping to change at page 21, line 43
[[Note to the RFC Editor: please replace the citation tags used in [[Note to the RFC Editor: please replace the citation tags used in
referencing Internet-Drafts with tags of the form RFCnnnn where referencing Internet-Drafts with tags of the form RFCnnnn where
possible.]] possible.]]
8.1. Normative References 8.1. Normative References
[RFC1034] Mockapetris, P., "Domain names - concepts [RFC1034] Mockapetris, P., "Domain names - concepts
and facilities", STD 13 (also RFC 1034), November 1987. and facilities", STD 13 (also RFC 1034), November 1987.
[RFC1123] Braden, R., "Requirements for Internet Hosts -
Application and Support", STD 3, RFC 1123, October 1989
[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.
[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
Specification", RFC 2181, July 1997.
[RFC2247] Kille, S., M. Wahl, A. Grimstad, R. Huber and S. [RFC2247] Kille, S., M. Wahl, A. Grimstad, R. Huber and S.
Sataluri, "Using Domains in LDAP/X.500 Distinguished Sataluri, "Using Domains in LDAP/X.500 Distinguished
Names", January 1998. Names", January 1998.
[RFC2821] Klensin, J. (editor), "Simple Mail Transfer Protocol", [RFC2821] Klensin, J. (editor), "Simple Mail Transfer Protocol",
RFC 2822, April 2001. RFC 2822, April 2001.
[RFC3490] Faltstrom, P., P. Hoffman, and A. Costello, [RFC3490] Faltstrom, P., P. Hoffman, and A. Costello,
"Internationalizing Domain Names in Applications "Internationalizing Domain Names in Applications
(INDA)", RFC 3490, March 2003. (INDA)", RFC 3490, March 2003.
skipping to change at page 25, line 8 skipping to change at page 25, line 24
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Full Copyright Full Copyright
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
 End of changes. 13 change blocks. 
25 lines changed or deleted 40 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/