Network Working Group M. Schleiff
Internet-Draft NAC
Intended status: Informational September 19, 2006
Expires: March 23, 2007
LDAP Schema for eXtensible Resource Identifier (XRI)
draft-schleiff-ldap-xri-01
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 23, 2007.
Copyright Notice
Copyright (C) The Internet Society (2006).
Schleiff Expires March 23, 2007 [Page 1]
Internet-Draft LDAP Schema for XRI September 2006
Abstract
This document describes Attribute Types and an Object Class for use
in representing XRI (eXtensible Resource Identifier) values in LDAP
(Lightweight Directory Access Protocol) and X.500 directory services.
Schleiff Expires March 23, 2007 [Page 2]
Internet-Draft LDAP Schema for XRI September 2006
1. Background and Intended Use
This document specifies particular LDAP schema objects pertinent to
XRI. It is intended as an Internet-Draft to be referenced in a
subsequent request for assignment of OID numbers for each schema
object, according to processes described in [RFC4520]. Technical
discussion of this document will take place on the
<directory@apps.ietf.org> mailing list as specified in section 4 of
[RFC4520]. Please send editorial comments directly to the author
<marty.schleiff@boeing.com>.
The OASIS XRI Technical Committee develops specifications for
representation of various types of resource identifiers within a
standard framework called XRI (eXtensible Resource Identifier). XRIs
identify resources independent of any specific network location,
domain, application, or protocol. The OASIS XRI Technical Committee
homepage is at the following location:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xri
Conventions for representing an object's XRI(s) in Lightweight
Directory Access Protocol (LDAP) and X.500 directory services will
simplify deployment of XRI-aware directory client applications and
interoperability among such applications.
This document defines an Object Class and several Attribute Types for
conventional representation of XRIs in directory services.
Schema definitions are provided using LDAP description formats
[RFC4512]. Definitions provided here are formatted (line wrapped)
for readability. The characters "IANA-ASSIGNED-OID" will appear in
the LDAP definitions until an OID (Object IDentifier) is obtained via
procedures described in [RFC4520], under which OIDs will be assigned
for each schema object.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119.
Schleiff Expires March 23, 2007 [Page 3]
Internet-Draft LDAP Schema for XRI September 2006
2. Definition of the xRIObject Object Class
The xRIObject is an auxiliary object class that MAY be added to any
directory entry for purposes of associating eXtensible Resource
Identifiers with that object.
( IANA-ASSIGNED-OID.1
NAME 'xRIObject'
SUP top
AUXILIARY
DESC 'objectClass for XRI attribute types'
MAY ( xRI $ altXRI ) )
Schleiff Expires March 23, 2007 [Page 4]
Internet-Draft LDAP Schema for XRI September 2006
3. Definition of the xRI Attribute Type
The xRI attribute type MAY be present on a directory entry with
objectClass = xRIObject. Although a directory entry may be
associated with many XRIs, the xRI Attribute Type contains just a
single value representing the preferred or primary XRI value for that
entry. When displaying an entry, especially within a one-line
summary list, it is useful to be able to identify which of
potentially several XRIs should be displayed. If present, the value
in xRI is the value that should be displayed. When a search is done
to find the XRI for a subject, this is the single value that should
be returned.
( IANA-ASSIGNED-OID.2
NAME ( 'xRI' 'extensibleResourceIdentifier' )
DESC 'The preferred or primary XRI for the subject.'
EQUALITY caseExactMatch
SUBSTR caseExactSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE )
Schleiff Expires March 23, 2007 [Page 5]
Internet-Draft LDAP Schema for XRI September 2006
4. Definition of the altXRI Attribute Type
The altXRI attribute type MAY be present on a directory entry with
objectClass = xRIObject. A directory entry may be associated with
many XRIs. To facilitate successful directory searches, the multiple
XRIs identifying a subject SHOULD be included in the altXRI Attribute
Type of that subject's directory entry.
( IANA-ASSIGNED-OID.3
NAME ( 'altXRI' 'alternateExtensibleResourceIdentifer' )
DESC 'A list of XRIs that are synonymns for the same subject.'
EQUALITY caseExactMatch
SUBSTR caseExactSubstringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
Schleiff Expires March 23, 2007 [Page 6]
Internet-Draft LDAP Schema for XRI September 2006
5. Matching Rule Considerations
Many kinds of identifiers can be expressed within the XRI framework,
such as UUIDs, distinguishedName, OID, case insensitive string, case
sensitive string, numeric, and others. Because these identifiers
have differing matching rules, XRI values being stored into directory
attributes, and those being compared against values in a directory,
SHOULD be normalized by the LDAP client to a point that
caseExactMatch will yield desired results. The xRI and altXRI
attribute types are defined with caseExactMatch equality matching.
In contexts where identifiers are known to be XRIs, the "xri:" scheme
name and following slashes is sometimes omitted; however, successful
matching will be more achievable with consistent treatment of the
"xri:" scheme name and following slashes as follows:
o When an XRI appears within an XRI cross reference (i.e., within
parentheses) the "xri://" SHOULD be ommitted.
o Otherwise the "xri://" SHOULD be explicitly included.
Schleiff Expires March 23, 2007 [Page 7]
Internet-Draft LDAP Schema for XRI September 2006
6. Security Considerations
Introduction of these schema objects is not believed to introduce new
security considerations beyond those described in the OASIS XRI suite
of specifications.
Schleiff Expires March 23, 2007 [Page 8]
Internet-Draft LDAP Schema for XRI September 2006
7. IANA Considerations
7.1. Object Identifier Registration
It is requested that IANA register upon Expert Review an LDAP Object
Identifier [RFC4520] under "Internet Directory Numbers"
(1.3.6.1.1.x).
Subject: Request for LDAP OID Registration
Person & email address to contact for further information:
Marty Schleiff <marty.schleiff@boeing.com>
Specification: Internet-Draft
Author/Change Controller: NAC (Network Applications Consortium -
see http://www.netapps.org)
Comments:
Please register an OID for definition of eXtensible Resource
Identifier (XRI) schema objects. Schema objects pertaining
to XRIs may be assigned OIDs under the IANA-ASSIGNED-OID.
7.2. 'xRIObject' Descriptor Registration
It is requested that IANA register upon Expert Review the LDAP
'xRIObject' descriptor following processes detailed in [RFC4520].
Subject: Request for LDAP Descriptor Registration
Descriptor (short name): xRIObject
Object Identifier: IANA-ASSIGNED-OID.1
Person & email address to contact for further information:
Marty Schleiff <marty.schleiff@boeing.com>
Usage: Object Class
7.3. 'xRI' Descriptor Registration
It is requested that IANA register upon Expert Review the LDAP 'xRI'
descriptor following processes detailed in [RFC4520].
Subject: Request for LDAP Descriptor Registration
Descriptor (short name): xRI
Object Identifier: IANA-ASSIGNED-OID.2
Person & email address to contact for further information:
Marty Schleiff <marty.schleiff@boeing.com>
Usage: Attribute Type
7.4. 'altXRI' Descriptor Registration
It is requested that IANA register upon Expert Review the LDAP
'altXRI' descriptor following processes detailed in [RFC4520].
Schleiff Expires March 23, 2007 [Page 9]
Internet-Draft LDAP Schema for XRI September 2006
Subject: Request for LDAP Descriptor Registration
Descriptor (short name): altXRI
Object Identifier: IANA-ASSIGNED-OID.3
Person & email address to contact for further information:
Marty Schleiff <marty.schleiff@boeing.com>
Usage: Attribute Type
Schleiff Expires March 23, 2007 [Page 10]
Internet-Draft LDAP Schema for XRI September 2006
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14 (also RFC 2119), March 1997.
8.2. Informative References
[RFC4512] Zeilenga, K. (editor), "LDAP: Directory Information
Models", RFC 4512, June 2006.
[RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority
(IANA) Considerations for the Lightweight Directory
Access Protocol (LDAP)", RFC 4520, BCP 64, June 2006.
Schleiff Expires March 23, 2007 [Page 11]
Internet-Draft LDAP Schema for XRI September 2006
Author's Address
Marty Schleiff
Network Applications Consortium
Email: marty.schleiff@boeing.com
URI: http://www.netapps.org
Schleiff Expires March 23, 2007 [Page 12]
Internet-Draft LDAP Schema for XRI September 2006
Full Copyright Statement
Copyright (C) The Internet Society (2006).
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 the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
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.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Schleiff Expires March 23, 2007 [Page 13]