7 INTERNET-DRAFT Kurt D. Zeilenga
8 Intended Category: Standard Track OpenLDAP Foundation
9 Expires in six months 17 July 2005
13 The LDAP Don't Use Copy Control
14 <draft-zeilenga-ldap-dontusecopy-01.txt>
19 This document is intended to be, after appropriate review and
20 revision, submitted to the IESG for consideration as a Standard Track
21 document. Distribution of this memo is unlimited. Technical
22 discussion of this document will take place on the IETF LDAP
23 Extensions mailing list <ldapext@ietf.org>. Please send editorial
24 comments directly to the author <Kurt@OpenLDAP.org>.
26 By submitting this Internet-Draft, each author represents that any
27 applicable patent or other IPR claims of which he or she is aware have
28 been or will be disclosed, and any of which he or she becomes aware
29 will be disclosed, in accordance with Section 6 of BCP 79.
31 Internet-Drafts are working documents of the Internet Engineering Task
32 Force (IETF), its areas, and its working groups. Note that other
33 groups may also distribute working documents as Internet-Drafts.
35 Internet-Drafts are draft documents valid for a maximum of six months
36 and may be updated, replaced, or obsoleted by other documents at any
37 time. It is inappropriate to use Internet-Drafts as reference material
38 or to cite them other than as "work in progress."
40 The list of current Internet-Drafts can be accessed at
41 http://www.ietf.org/1id-abstracts.html
43 The list of Internet-Draft Shadow Directories can be accessed at
44 http://www.ietf.org/shadow.html
47 Copyright (C) The Internet Society (2005). All Rights Reserved.
49 Please see the Full Copyright section near the end of this document
58 Zeilenga LDAP Don't Use Copy Control [Page 1]
60 INTERNET-DRAFT draft-zeilenga-ldap-dontusecopy-01 17 July 2005
65 This document defines the Lightweight Directory Access Protocol (LDAP)
66 Don't Use Copy control extension which allows a client to specify that
67 copied information should not be used in providing service. This
68 control is based upon the X.511 dontUseCopy service control option.
71 1. Background and Intended Usage
73 This document defines the Lightweight Directory Access Protocol (LDAP)
74 [Roadmap] Don't Use Copy control extension. The control may be
75 attached to request messages to indicate that copied (replicated or
76 cached) information [X.500] should not be used in providing service.
77 This control is based upon the X.511 [X.511] dontUseCopy service
80 The Don't Use Copy control is intended to be used where the client
81 requires the service be provided using original (master) information
87 DSA stands for Directory System Agent (or server).
88 DSE stands for DSA-specific Entry.
90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
92 document are to be interpreted as described in BCP 14 [RFC2119].
95 3. The Don't Use Copy Control
97 The Don't Use Copy control is an LDAP Control [Protocol] whose
98 controlType is IANA-ASSIGNED-OID and controlValue is absent. The
99 criticality may be TRUE or FALSE. There is no corresponding response
102 The control is appropriate for both LDAP interrogation operations,
103 including Compare and Search operations [Protocol]. It is
104 inappropriate for all other operations, including Abandon, Bind,
105 Delete, Modify, ModifyDN, StartTLS, and Unbind operations [Protocol].
107 When the control is attached to an LDAP request, the requested
108 operation MUST NOT be performed on copied information. That is, the
109 requested operation MUST be performed on original information.
114 Zeilenga LDAP Don't Use Copy Control [Page 2]
116 INTERNET-DRAFT draft-zeilenga-ldap-dontusecopy-01 17 July 2005
119 If original information for the target or base object of the operation
120 is not available (either locally or through chaining), the server MUST
121 either return a referral directing the client to a server believed to
122 be better able to service the request or return an appropriate result
123 code (e.g., unwillingToPerform).
126 4. Security Considerations
128 This control is intended to be provided where providing service using
129 copied information might lead to unexpected application behavior.
130 Designers of directory applications should consider where it is
131 appropriate for clients to provide this control. Designers should
132 consider whether use of copied information, in particular security and
133 policy information, may result insecure behavior.
135 Security considerations for the base operations [Protocol] extended by
136 this control, as well as general LDAP security considerations
137 [Roadmap], generally apply to implementation and use of this
141 5. IANA Considerations
143 5.1. Object Identifier
145 It is requested that IANA assign upon Standards Action an LDAP Object
146 Identifier [BCP64bis] to identify the LDAP Don't Use Copy Control
147 defined in this document.
149 Subject: Request for LDAP Object Identifier Registration
150 Person & email address to contact for further information:
151 Kurt Zeilenga <kurt@OpenLDAP.org>
152 Specification: RFC XXXX
153 Author/Change Controller: IESG
155 Identifies the LDAP Don't Use Copy Control
157 5.2 LDAP Protocol Mechanism
159 Registration of this protocol mechanism [BCP64bis] is requested.
161 Subject: Request for LDAP Protocol Mechanism Registration
162 Object Identifier: IANA-ASSIGNED-OID
163 Description: Don't Use Copy Control
164 Person & email address to contact for further information:
165 Kurt Zeilenga <kurt@openldap.org>
170 Zeilenga LDAP Don't Use Copy Control [Page 3]
172 INTERNET-DRAFT draft-zeilenga-ldap-dontusecopy-01 17 July 2005
175 Specification: RFC XXXX
176 Author/Change Controller: IESG
186 Email: Kurt@OpenLDAP.org
191 [[Note to the RFC Editor: please replace the citation tags used in
192 referencing Internet-Drafts with tags of the form RFCnnnn where
196 7.1. Normative References
198 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
199 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
201 [Roadmap] Zeilenga, K. (editor), "LDAP: Technical Specification
202 Road Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in
205 [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol",
206 draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
209 7.2. Informative References
211 [X.500] International Telecommunication Union -
212 Telecommunication Standardization Sector, "The Directory
213 -- Overview of concepts, models and services,"
214 X.500(1993) (also ISO/IEC 9594-1:1994).
216 [X.511] International Telecommunication Union -
217 Telecommunication Standardization Sector, "The
218 Directory: Abstract Service Definition", X.511(1993)
219 (also ISO/IEC 9594-3:1993).
221 [BCP64bis] Zeilenga, K., "IANA Considerations for LDAP",
222 draft-ietf-ldapbis-bcp64-xx.txt, a work in progress.
226 Zeilenga LDAP Don't Use Copy Control [Page 4]
228 INTERNET-DRAFT draft-zeilenga-ldap-dontusecopy-01 17 July 2005
231 Intellectual Property Rights
233 The IETF takes no position regarding the validity or scope of any
234 Intellectual Property Rights or other rights that might be claimed to
235 pertain to the implementation or use of the technology described in
236 this document or the extent to which any license under such rights
237 might or might not be available; nor does it represent that it has
238 made any independent effort to identify any such rights. Information
239 on the procedures with respect to rights in RFC documents can be found
240 in BCP 78 and BCP 79.
242 Copies of IPR disclosures made to the IETF Secretariat and any
243 assurances of licenses to be made available, or the result of an
244 attempt made to obtain a general license or permission for the use of
245 such proprietary rights by implementers or users of this specification
246 can be obtained from the IETF on-line IPR repository at
247 http://www.ietf.org/ipr.
249 The IETF invites any interested party to bring to its attention any
250 copyrights, patents or patent applications, or other proprietary
251 rights that may cover technology that may be required to implement
252 this standard. Please address the information to the IETF at
259 Copyright (C) The Internet Society (2005).
261 This document is subject to the rights, licenses and restrictions
262 contained in BCP 78, and except as set forth therein, the authors
263 retain all their rights.
265 This document and the information contained herein are provided on an
266 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
267 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
268 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
269 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
270 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
271 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
282 Zeilenga LDAP Don't Use Copy Control [Page 5]