7 INTERNET-DRAFT Kurt D. Zeilenga
8 Intended Category: Standard Track OpenLDAP Foundation
9 Expires in six months 5 March 2006
13 The LDAP Don't Use Copy Control
14 <draft-zeilenga-ldap-dontusecopy-02.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 (2006). 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-02 5 March 2006
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 MUST be TRUE. There is no corresponding response control.
101 The control is appropriate for both LDAP interrogation operations,
102 including Compare and Search operations [Protocol]. It is
103 inappropriate for all other operations, including Abandon, Bind,
104 Delete, Modify, ModifyDN, StartTLS, and Unbind operations [Protocol].
106 When the control is attached to an LDAP request, the requested
107 operation MUST NOT be performed on copied information. That is, the
108 requested operation MUST be performed on original information.
110 If original information for the target or base object of the operation
114 Zeilenga LDAP Don't Use Copy Control [Page 2]
116 INTERNET-DRAFT draft-zeilenga-ldap-dontusecopy-02 5 March 2006
119 is not available (either locally or through chaining), the server MUST
120 either return a referral directing the client to a server believed to
121 be better able to service the request or return an appropriate result
122 code (e.g., unwillingToPerform).
125 4. Security Considerations
127 This control is intended to be provided where providing service using
128 copied information might lead to unexpected application behavior.
129 Designers of directory applications should consider where it is
130 appropriate for clients to provide this control. Designers should
131 consider whether use of copied information, in particular security and
132 policy information, may result insecure behavior.
134 Security considerations for the base operations [Protocol] extended by
135 this control, as well as general LDAP security considerations
136 [Roadmap], generally apply to implementation and use of this
140 5. IANA Considerations
142 5.1. Object Identifier
144 It is requested that IANA assign upon Standards Action an LDAP Object
145 Identifier [BCP64bis] to identify the LDAP Don't Use Copy Control
146 defined in this document.
148 Subject: Request for LDAP Object Identifier Registration
149 Person & email address to contact for further information:
150 Kurt Zeilenga <kurt@OpenLDAP.org>
151 Specification: RFC XXXX
152 Author/Change Controller: IESG
154 Identifies the LDAP Don't Use Copy Control
156 5.2 LDAP Protocol Mechanism
158 Registration of this protocol mechanism [BCP64bis] is requested.
160 Subject: Request for LDAP Protocol Mechanism Registration
161 Object Identifier: IANA-ASSIGNED-OID
162 Description: Don't Use Copy Control
163 Person & email address to contact for further information:
164 Kurt Zeilenga <kurt@openldap.org>
166 Specification: RFC XXXX
170 Zeilenga LDAP Don't Use Copy Control [Page 3]
172 INTERNET-DRAFT draft-zeilenga-ldap-dontusecopy-02 5 March 2006
175 Author/Change Controller: IESG
185 Email: Kurt@OpenLDAP.org
190 [[Note to the RFC Editor: please replace the citation tags used in
191 referencing Internet-Drafts with tags of the form RFCnnnn where
195 7.1. Normative References
197 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
198 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
200 [Roadmap] Zeilenga, K. (editor), "LDAP: Technical Specification
201 Road Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in
204 [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol",
205 draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
208 7.2. Informative References
210 [X.500] International Telecommunication Union -
211 Telecommunication Standardization Sector, "The Directory
212 -- Overview of concepts, models and services,"
213 X.500(1993) (also ISO/IEC 9594-1:1994).
215 [X.511] International Telecommunication Union -
216 Telecommunication Standardization Sector, "The
217 Directory: Abstract Service Definition", X.511(1993)
218 (also ISO/IEC 9594-3:1993).
220 [BCP64bis] Zeilenga, K., "IANA Considerations for LDAP",
221 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-02 5 March 2006
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 (2006).
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]