7 INTERNET-DRAFT Kurt D. Zeilenga
8 Intended Category: Standard Track OpenLDAP Foundation
9 Expires in six months 25 October 2003
12 The LDAP entryUUID operational attribute
13 <draft-zeilenga-ldap-uuid-02.txt>
18 This document is an Internet-Draft and is in full conformance with all
19 provisions of Section 10 of RFC2026.
21 This document is intended to be, after appropriate review and
22 revision, submitted to the RFC Editor as an Standard Track document.
23 Distribution of this memo is unlimited. Technical discussion of this
24 document will take place on the IETF LDAP Extensions mailing list
25 <ldapext@ietf.org>. Please send editorial comments directly to the
26 author <Kurt@OpenLDAP.org>.
28 Internet-Drafts are working documents of the Internet Engineering Task
29 Force (IETF), its areas, and its working groups. Note that other
30 groups may also distribute working documents as Internet-Drafts.
31 Internet-Drafts are draft documents valid for a maximum of six months
32 and may be updated, replaced, or obsoleted by other documents at any
33 time. It is inappropriate to use Internet-Drafts as reference
34 material or to cite them other than as ``work in progress.''
36 The list of current Internet-Drafts can be accessed at
37 <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
38 Internet-Draft Shadow Directories can be accessed at
39 <http://www.ietf.org/shadow.html>.
41 Copyright (C) The Internet Society (2003). All Rights Reserved.
43 Please see the Full Copyright section near the end of this document
49 This document describes the LDAP/X.500 'entryUUID' operational
50 attribute and associated matching rules and syntax. The attribute
51 holds a server-assigned Universally Unique Identifier (UUID) for the
52 object. Directory clients may use this attribute to distinguish
53 objects identified by a distinguished name or to locate an object
58 Zeilenga draft-zeilenga-ldap-uuid-02 [Page 1]
60 INTERNET-DRAFT LDAP entryUUID 25 October 2003
63 1. Background and Intended Use
65 In X.500 Directory Services [X.501], such as those accessible using
66 the the Lightweight Directory Access Protocol (LDAP) [RFC3377], an
67 object is identified by its distinguished name (DN). However, DNs are
68 not stable identifiers. That is, a new object may be identified by a
69 DN which previously identified another (now renamed or deleted)
72 This document describes the 'entryUUID' operational attribute which
73 holds the Universally Unique Identifier (UUID) [ISO11578] assigned to
74 the object by the server. Clients may use this attribute to
75 distinguish objects identified by a distinguished name or to locate an
76 object after renaming.
78 This document defines the UUID syntax, the 'uuidMatch' and
79 'uuidOrderingMatch' matching rules, the 'entryUUID' attribute type.
81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
83 document are to be interpreted as described in BCP 14 [RFC2119].
85 Schema definitions are provided using LDAP description formats
86 [RFC2252]. Definitions provided here are formatted (line wrapped) for
90 2. UUID Schema Elements
94 A Universally Unique Identifier (UUID) [ISO11578] is a 16-octet
95 (128-bit) value which identifies an object. The ASN.1 [X.690] type
96 UUID is defined to represent UUIDs.
98 UUID ::= OCTET STRING (SIZE(16))
99 -- constrained to an UUID [ISO 11578]
101 In LDAP, values of the UUID type are encoded using the [ASCII]
102 character string representation described in [ISO11578]. For example,
103 "597ae2f6-16a6-1027-98f4-d28b5365dc14".
105 The following is a LDAP syntax description [RFC2252] suitable for
106 publication in the subschema.
108 ( IANA-ASSIGNED-OID.1 DESC 'UUID' )
114 Zeilenga draft-zeilenga-ldap-uuid-02 [Page 2]
116 INTERNET-DRAFT LDAP entryUUID 25 October 2003
119 2.2 'uuidMatch' Matching Rule
121 The 'uuidMatch' matching rule compares an asserted UUID with a stored
122 UUID for equality. Its semantics are same as the octetStringMatch
123 [X.520][RFC2252] matching rule. The rule differs from
124 octetStringMatch in that the assertion value is encoded using the UUID
125 string representation instead of the normal OCTET STRING string
128 The following is a LDAP matching rule description [RFC2252] suitable
129 for publication in the subschema.
131 ( IANA-ASSIGNED-OID.2 NAME 'uuidMatch'
132 SYNTAX IANA-ASSIGNED-OID.1 )
135 2.3 'uuidOrderingMatch' Matching Rule
137 The 'uuidOrderingMatch' matching rule compares an asserted UUID
138 with a stored UUID for ordering. Its semantics are the same as the
139 octetStringOrderingMatch [X.520][RFC2252] matching rule. The rule
140 differs from octetStringOrderingMatch in that the assertion value
141 is encoded using the UUID string representation instead of the
142 normal OCTET STRING string representation.
144 The following is a LDAP matching rule description [RFC2252] suitable
145 for publication in the subschema.
147 ( IANA-ASSIGNED-OID.3 NAME 'uuidMatch'
148 SYNTAX IANA-ASSIGNED-OID.1 )
150 It is noted that not all UUID variants have a defined ordering and,
151 even where so, servers are not obligated to assign UUIDs in any
152 particular order. This matching rule is provided for completeness.
155 2.4. 'entryUUID' attribute
157 The 'entryUUID' operational attribute provides the Universally Unique
158 Identifier (UUID) [ISO11578] assigned to the entry.
160 The following is a LDAP attribute type description [RFC2252] suitable
161 for publication in the subschema.
163 ( IANA-ASSIGNED-OID.4 NAME 'entryUUID'
164 DESC 'UUID of the entry'
166 ORDERING uuidOrderingMatch
170 Zeilenga draft-zeilenga-ldap-uuid-02 [Page 3]
172 INTERNET-DRAFT LDAP entryUUID 25 October 2003
175 SYNTAX IANA-ASSIGNED-OID.1
178 USAGE directoryOperation )
180 Servers SHALL assign a UUID to each entry upon its addition to the
181 directory and provide the entry's UUID as the value of the
182 'entryUUID' operational attribute. An entry's UUID is immutable.
185 3. Security Considerations
187 Servers should ensure that components of UUID values are publicly
190 General LDAP security considerations [RFC3377] apply.
193 4. IANA Considerations
195 4.1. Object Identifier Registration
197 It is requested that IANA register upon Standards Action an LDAP
198 Object Identifier for use in this technical specification.
200 Subject: Request for LDAP OID Registration
201 Person & email address to contact for further information:
202 Kurt Zeilenga <kurt@OpenLDAP.org>
203 Specification: RFC XXXX
204 Author/Change Controller: IESG
206 Identifies the UUID schema elements
209 4.2. Registration of the uuidMatch descriptor
211 It is requested that IANA register upon Standards Action the LDAP
212 'uuidMatch' descriptor.
214 Subject: Request for LDAP Descriptor Registration
215 Descriptor (short name): uuidMatch
216 Object Identifier: IANA-ASSIGNED-OID.2
217 Person & email address to contact for further information:
218 Kurt Zeilenga <kurt@OpenLDAP.org>
220 Specification: RFC XXXX
221 Author/Change Controller: IESG
226 Zeilenga draft-zeilenga-ldap-uuid-02 [Page 4]
228 INTERNET-DRAFT LDAP entryUUID 25 October 2003
231 4.3. Registration of the uuidOrderingMatch descriptor
233 It is requested that IANA register upon Standards Action the LDAP
234 'uuidOrderingMatch' descriptor.
236 Subject: Request for LDAP Descriptor Registration
237 Descriptor (short name): uuidOrderingMatch
238 Object Identifier: IANA-ASSIGNED-OID.3
239 Person & email address to contact for further information:
240 Kurt Zeilenga <kurt@OpenLDAP.org>
242 Specification: RFC XXXX
243 Author/Change Controller: IESG
246 4.4. Registration of the entryUUID descriptor
248 It is requested that IANA register upon Standards Action the LDAP
249 'entryUUID' descriptor.
251 Subject: Request for LDAP Descriptor Registration
252 Descriptor (short name): entryUUID
253 Object Identifier: IANA-ASSIGNED-OID.4
254 Person & email address to contact for further information:
255 Kurt Zeilenga <kurt@OpenLDAP.org>
256 Usage: Attribute Type
257 Specification: RFC XXXX
258 Author/Change Controller: IESG
263 This document is based upon discussions in the LDAP Update and
264 Duplication Protocols (LDUP) WG. Members of the concluded LDAP
265 Extensions (LDAPEXT) Working Group provided review.
275 7. Normative References
277 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
278 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
282 Zeilenga draft-zeilenga-ldap-uuid-02 [Page 5]
284 INTERNET-DRAFT LDAP entryUUID 25 October 2003
287 [RFC2252] Wahl, M., A. Coulbeck, T. Howes, and S. Kille,
288 "Lightweight Directory Access Protocol (v3): Attribute
289 Syntax Definitions", RFC 2252, December 1997.
291 [RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access
292 Protocol (v3): Technical Specification", RFC 3377,
295 [ISO11578] International Organization for Standardization,
296 "Information technology - Open Systems Interconnection -
297 Remote Procedure Call", ISO/IEC 11578:1996.
299 [ASCII] Coded Character Set--7-bit American Standard Code for
300 Information Interchange, ANSI X3.4-1986.
302 [X.501] International Telecommunication Union -
303 Telecommunication Standardization Sector, "The Directory
304 -- Models," X.501(1993) (also ISO/IEC 9594-2:1994).
306 [X.520] International Telecommunication Union -
307 Telecommunication Standardization Sector, "The
308 Directory: Selected Attribute Types", X.520(1993) (also
309 ISO/IEC 9594-6:1994).
311 [X.680] International Telecommunication Union -
312 Telecommunication Standardization Sector, "Abstract
313 Syntax Notation One (ASN.1) - Specification of Basic
314 Notation", X.680(1997) (also ISO/IEC 8824-1:1998).
317 8. Informative References
319 [RFC3383] Zeilenga, K., "IANA Considerations for LDAP", BCP 64
320 (also RFC 3383), September 2002.
322 [UUIDinfo] The Open Group, "Universally Unique Identifier" appendix
323 of the CAE Specification "DCE 1.1: Remote Procedure
324 Calls", Document Number C706,
325 <http://www.opengroup.org/products/publications/catalog/c706.htm>
326 (appendix available at:
327 <http://www.opengroup.org/onlinepubs/9629399/apdxa.htm>),
332 Intellectual Property Rights
334 The IETF takes no position regarding the validity or scope of any
338 Zeilenga draft-zeilenga-ldap-uuid-02 [Page 6]
340 INTERNET-DRAFT LDAP entryUUID 25 October 2003
343 intellectual property or other rights that might be claimed to pertain
344 to the implementation or use of the technology described in this
345 document or the extent to which any license under such rights might or
346 might not be available; neither does it represent that it has made any
347 effort to identify any such rights. Information on the IETF's
348 procedures with respect to rights in standards-track and
349 standards-related documentation can be found in BCP-11. Copies of
350 claims of rights made available for publication and any assurances of
351 licenses to be made available, or the result of an attempt made to
352 obtain a general license or permission for the use of such proprietary
353 rights by implementors or users of this specification can be obtained
354 from the IETF Secretariat.
356 The IETF invites any interested party to bring to its attention any
357 copyrights, patents or patent applications, or other proprietary
358 rights which may cover technology that may be required to practice
359 this standard. Please address the information to the IETF Executive
366 Copyright (C) The Internet Society (2003). All Rights Reserved.
368 This document and translations of it may be copied and furnished to
369 others, and derivative works that comment on or otherwise explain it
370 or assist in its implmentation may be prepared, copied, published and
371 distributed, in whole or in part, without restriction of any kind,
372 provided that the above copyright notice and this paragraph are
373 included on all such copies and derivative works. However, this
374 document itself may not be modified in any way, such as by removing
375 the copyright notice or references to the Internet Society or other
376 Internet organizations, except as needed for the purpose of
377 developing Internet standards in which case the procedures for
378 copyrights defined in the Internet Standards process must be followed,
379 or as required to translate it into languages other than English.
394 Zeilenga draft-zeilenga-ldap-uuid-02 [Page 7]