2 Extended Operations for Framing LDAP Operations
4 Intended Category: Standards Track
5 Expires: September 10, 2000
15 Netscape Communications Corp.
19 Extended Operations for Framing LDAP Operations
20 Filename: draft-ietf-ldup-framing-00.txt
24 1. Status of this Memo.............................................2
25 2. Abstract........................................................2
26 3. Overview........................................................2
27 4. Protocol element definitions....................................3
28 4.1 StartFramedProtocolRequest Extended Operation...................3
29 4.2 StartFramedProtocolResponse Extended Operation..................3
30 4.3 EndFramedProtocolRequest Extended Operation.....................4
31 4.4 EndFramedProtocolResponse Extended Operation....................4
32 5. Acknowledgments.................................................5
33 6. References......................................................5
34 7. Author's Addresses..............................................5
55 Stokes, Harrison and Good [Page 1]
57 Internet-Draft LDUP Workgroup March 10, 2000
60 1. Status of this Memo
62 This document is an Internet-Draft and is in full conformance with
63 all provisions of Section 10 of RFC2026.
65 Internet-Drafts are working documents of the Internet Engineering
66 Task Force (IETF), its areas, and its working groups. Note that other
67 groups may also distribute working documents as Internet-Drafts.
69 Internet-Drafts are draft documents valid for a maximum of six months
70 and may be updated, replaced, or obsoleted by other documents at any
71 time. It is inappropriate to use Internet- Drafts as reference
72 material or to cite them other than as "work in progress."
74 The list of current Internet-Drafts can be accessed at
75 http://www.ietf.org/ietf/1id-abstracts.txt
77 The list of Internet-Draft Shadow Directories can be accessed at
78 http://www.ietf.org/shadow.html.
82 This Internet Draft expires September 10, 2000.
87 Certain types of LDAP applications can benefit from the ability to
88 specify the beginning and end of a related group of operations. For
89 example, the LDUP multimaster update protocol [ARCHITECTURE] requires
90 that two servers agree to begin a session to transfer pending
91 replication updates. This document provides a framework for
92 constructing protocols that feature a framed set of related
93 operations. It defines a pair of LDAPv3 extended operations that
94 provide begin-end framing, and a pair of extended operations used to
95 respond the begin-end framing operations. The nature of the actual
96 LDAP operations carried inside these framing operations is not
97 specified in this document.
99 All protocol elements described here are LDAP Version 3 extended
100 operations. LDAP Version 3 is described in RFC 2251 [LDAPv3].
102 Certain terms used in this document are defined in the document "LDAP
103 Replication Architecture" [ARCHITECTURE].
105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
106 "SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are
107 to be interpreted as described in RFC 2119 [KEYWORDS].
111 This document describes two LDAPv3 Extended Operations that are used
112 to signal the beginning and end of a set of grouped operations, and
116 Stokes, Harrison and Good [Page 2]
118 Internet-Draft LDUP Workgroup March 10, 2000
121 two LDAPv3 extended operations that are used to respond to these
122 operations. These extended operations provide a framework that may be
123 used when developing a protocol that requires begin-end framing.
125 4. Protocol element definitions
127 4.1 StartFramedProtocolRequest Extended Operation
129 The StartFramedProtocolRequest extended operation indicates that the
130 initiator wishes to begin transmission of a set of related LDAP
131 operations. The requestValue of the StartFramedProtocolRequest
132 extended operation contains an OID that describes the specific framed
133 protocol being initiated, and a protocol-specific payload.
135 An LDAPv3 Extended Request is defined in [LDAPv3] as follows:
137 ExtendedRequest ::= [APPLICATION 23] SEQUENCE {
138 requestName [0] LDAPOID,
139 requestValue [1] OCTET STRING OPTIONAL
142 The requestName portion of the StartFramedProtocolRequest must be the
143 OID "2.16.840.1.113719.1.142.100.1".
145 The requestValue of the StartFramedProtocolRequest must be set to the
146 BER-encoding of the following:
148 StartFramedProtocolRequestValue ::= SEQUENCE {
149 framedProtocolOID LDAPOID,
150 framedProtocolPayload OPTIONAL OCTET STRING
153 The parameters in the requestValue of the StartFramedProtocolRequest
156 - framedProtocolOID: An OID that uniquely identifies the protocol
157 framed by this operation. - framedProtocolPayload: An octet
158 string that contains protocol-specific
162 4.2 StartFramedProtocolResponse Extended Operation
164 The StartFramedProtocolResponse extended operation is sent in
165 response to a StartFramedProtocolResponse extended operation.
167 An LDAPv3 Extended Response is defined in [LDAPv3] as follows:
172 Stokes, Harrison and Good [Page 3]
174 Internet-Draft LDUP Workgroup March 10, 2000
177 ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
178 COMPONENTS of LDAPResult,
179 responseName [10] LDAPOID OPTIONAL,
180 response [11] OCTET STRING OPTIONAL
183 The responseName of the StartFramedProtocolResponse must be the OID
184 "2.16.840.1.113719.1.142.100.2".
186 The response of the StartFramedProtocolResponse is set to the BER-
187 encoding of a protocol-specific response.
189 4.3 EndFramedProtocolRequest Extended Operation
191 The EndFramedProtocolRequest extended operation indicates the end a
192 set of related LDAP operations. The requestValue of the
193 EndFramedProtocolRequest extended operation contains a protocol-
196 An LDAPv3 Extended Request is defined in [LDAPv3] as follows:
198 ExtendedRequest ::= [APPLICATION 23] SEQUENCE {
199 requestName [0] LDAPOID,
200 requestValue [1] OCTET STRING OPTIONAL
203 The requestName of the EndFramedProtocolRequest must be the OID
204 "2.16.840.1.113719.1.142.100.4".
206 The requestValue of the EndFramedProtocolRequest is set to the BER-
207 encoding of a protocol-specific response.
209 4.4 EndFramedProtocolResponse Extended Operation
211 The EndFramedProtocolResponse extended operation is sent in response
212 to an EndFramedProtocolRequest.
214 An LDAPv3 Extended Response is defined in [LDAPv3] as follows:
216 ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
217 COMPONENTS of LDAPResult,
218 responseName [10] LDAPOID OPTIONAL,
219 response [11] OCTET STRING OPTIONAL
222 The responseName of the EndFramedProtocolResponse must be the OID
223 "2.16.840.1.113719.1.142.100.5".
228 Stokes, Harrison and Good [Page 4]
230 Internet-Draft LDUP Workgroup March 10, 2000
233 The response of the EndFramedProtocolResponse is set to the BER-
234 encoding of a protocol-specific response.
238 The authors gratefully acknowledge the contributions of the IETF LDUP
245 S. Bradner, "Key Words for use in RFCs to Indicate Requirement Lev-
246 els", Harvard University, RFC 2119, March 1997.
250 J. Merrells, E. Reed, U. Srinivasan, "LDAP Replication Architec-
251 ture", Internet-Draft, draft-ietf-ldup-model-02.txt, October 1999.
255 M. Wahl, S. Kille, T. Howes, "Lightweight Directory Access Protocol
256 (v3)", RFC 2251, December 1997.
258 7. Author's Addresses
265 EMail: stokes@austin.ibm.com
266 phone: +1 512 838 3725
274 EMail: roger_harrison@novell.com
275 Phone: +1 801 861 2642
278 Netscape Communications Corp.
279 501 E. Middlefield Rd.
284 Stokes, Harrison and Good [Page 5]
286 Internet-Draft LDUP Workgroup March 10, 2000
289 Mountain View, CA 94043
291 EMail: ggood@netscape.com
292 Phone: +1 650 937-3825
295 Appendix A - Complete ASN.1 Definition
297 StartFramedProtocolRequest ::= ExtendedRequest
299 StartFramedProtocolRequestValue ::= SEQUENCE {
300 framedProtocolOID LDAPOID,
301 framedProtocolPayload OPTIONAL OCTET STRING
304 StartFramedProtocolResponse ::= ExtendedResponse
306 EndFramedProtocolRequest ::= ExtendedRequest
308 EndFramedProtocolResponse ::= ExtendedResponse
310 Full Copyright Statement
312 Copyright (C) The Internet Society (1999). All Rights Reserved.
314 This document and translations of it may be copied and furnished to oth-
315 ers, and derivative works that comment on or otherwise explain it or
316 assist in its implementation may be prepared, copied, published and dis-
317 tributed, in whole or in part, without restriction of any kind, provided
318 that the above copyright notice and this paragraph are included on all
319 such copies and derivative works. However, this document itself may not
320 be modified in any way, such as by removing the copyright notice or
321 references to the Internet Society or other Internet organizations,
322 except as needed for the purpose of developing Internet standards in
323 which case the procedures for copyrights defined in the Internet Stan-
324 dards process must be followed, or as required to translate it into
325 languages other than English.
327 The limited permissions granted above are perpetual and will not be
328 revoked by the Internet Society or its successors or assigns.
330 This document and the information contained herein is provided on an "AS
331 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
332 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
333 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
334 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FIT-
335 NESS FOR A PARTICULAR PURPOSE.
340 Stokes, Harrison and Good [Page 6]