response, without affecting its application to any subsequent
SearchResultEntry response.
- This control is totally unrelated to alias dereferencing [RFC4511].
-
-
-
+ Servers implementing this technical specification SHOULD publish the
+ object identifier deref-oid (IANA assigned; see Section 6) as a value
+ of the 'supportedControl' attribute [RFC4512] in their root DSE.
+ This control is totally unrelated to alias dereferencing [RFC4511].
2.2. Control Request
- The specification of the Dereference Control request is:
+ The control type is deref-oid (IANA assigned; see Section 6). The
+ specification of the Dereference Control request is:
controlValue ::= SEQUENCE OF derefSpec DerefSpec
2.3. Control Response
- The specification of the Dereference Control response is:
+ The control type is deref-oid (IANA assigned; see Section 6). The
+ specification of the Dereference Control response is:
controlValue ::= SEQUENCE OF derefRes DerefRes
-
-
Masarati & Chu Expires April 4, 2009 [Page 5]
\f
Internet-Draft LDAP Deref October 2008
response.
</t>
+ <t>
+Servers implementing this technical specification SHOULD publish
+the object identifier deref-oid (IANA assigned;
+see <xref target="iana_considerations" />) as a value
+of the 'supportedControl' attribute <xref target="RFC4512" />
+in their root DSE.
+ </t>
+
<t>
This control is totally unrelated to alias dereferencing
<xref target="RFC4511" />.
<section anchor="control_request" title="Control Request">
<figure>
<preamble>
+The control type is deref-oid (IANA assigned;
+see <xref target="iana_considerations" />).
The specification of the Dereference Control request is:
</preamble>
<artwork>
<section anchor="control_response" title="Control Response">
<figure>
<preamble>
+The control type is deref-oid (IANA assigned;
+see <xref target="iana_considerations" />).
The specification of the Dereference Control response is:
</preamble>
<artwork>
</t>
</section>
- <section title="IANA Considerations">
+ <section anchor="iana_considerations" title="IANA Considerations">
<section title="Object Identifier Registration">
<figure>
<preamble>
2. LDAP "What Failed?" Control . . . . . . . . . . . . . . . . . 4
2.1. Control Semantics . . . . . . . . . . . . . . . . . . . . 4
2.2. Control Request . . . . . . . . . . . . . . . . . . . . . 4
- 2.3. Control Response . . . . . . . . . . . . . . . . . . . . . 4
- 3. Implementation Notes . . . . . . . . . . . . . . . . . . . . . 5
- 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
- 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
- 5.1. Object Identifier Registration . . . . . . . . . . . . . . 7
- 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
- 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
- 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
- 7.2. Informative References . . . . . . . . . . . . . . . . . . 9
- Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10
- Intellectual Property and Copyright Statements . . . . . . . . . . 11
+ 2.3. Control Response . . . . . . . . . . . . . . . . . . . . . 5
+ 3. Implementation Notes . . . . . . . . . . . . . . . . . . . . . 6
+ 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
+ 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
+ 5.1. Object Identifier Registration . . . . . . . . . . . . . . 8
+ 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
+ 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
+ 7.1. Normative References . . . . . . . . . . . . . . . . . . . 10
+ 7.2. Informative References . . . . . . . . . . . . . . . . . . 10
+ Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11
+ Intellectual Property and Copyright Statements . . . . . . . . . . 12
ordering of controls handling when requesting the "What Failed?"
control.
+ Servers implementing this technical specification SHOULD publish the
+ object identifier whatFailed-oid (IANA assigned; see Section 5) as a
+ value of the 'supportedControl' attribute [RFC4512] in their root
+ DSE.
+
2.2. Control Request
- The controlType is whatFailed-oid; the controlValue MUST be absent;
- the criticality SHOULD be FALSE.
+ The controlType is whatFailed-oid (IANA assigned; see Section 5); the
+ controlValue MUST be absent; the criticality SHOULD be FALSE.
+
+
+
+
+
+
+
+
+
+
+Masarati Expires April 4, 2009 [Page 4]
+\f
+Internet-Draft LDAP WHATFAILED October 2008
+
2.3. Control Response
- The controlType is whatFailed-oid; the controlValue is:
+ The controlType is whatFailed-oid (IANA assigned; see Section 5); the
+ controlValue is:
controlValue ::= SET OF oid LDAPOID
-Masarati Expires April 4, 2009 [Page 4]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Masarati Expires April 4, 2009 [Page 5]
\f
Internet-Draft LDAP WHATFAILED October 2008
-Masarati Expires April 4, 2009 [Page 5]
+Masarati Expires April 4, 2009 [Page 6]
\f
Internet-Draft LDAP WHATFAILED October 2008
-Masarati Expires April 4, 2009 [Page 6]
+Masarati Expires April 4, 2009 [Page 7]
\f
Internet-Draft LDAP WHATFAILED October 2008
-Masarati Expires April 4, 2009 [Page 7]
+Masarati Expires April 4, 2009 [Page 8]
\f
Internet-Draft LDAP WHATFAILED October 2008
-Masarati Expires April 4, 2009 [Page 8]
+Masarati Expires April 4, 2009 [Page 9]
\f
Internet-Draft LDAP WHATFAILED October 2008
[RFC4511] Sermersheim, J., "Lightweight Directory Access Protocol
(LDAP): The Protocol", RFC 4511, June 2006.
+ [RFC4512] Zeilenga, K., "Lightweight Directory Access Protocol
+ (LDAP): Directory Information Models", RFC 4512,
+ June 2006.
+
7.2. Informative References
[RFC4526] Zeilenga, K., "Lightweight Directory Access Protocol
-
-
-
-
-Masarati Expires April 4, 2009 [Page 9]
+Masarati Expires April 4, 2009 [Page 10]
\f
Internet-Draft LDAP WHATFAILED October 2008
-Masarati Expires April 4, 2009 [Page 10]
+Masarati Expires April 4, 2009 [Page 11]
\f
Internet-Draft LDAP WHATFAILED October 2008
-Masarati Expires April 4, 2009 [Page 11]
+Masarati Expires April 4, 2009 [Page 12]
\f
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4510.xml'>
<!ENTITY rfc4511 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4511.xml'>
+ <!ENTITY rfc4512 PUBLIC ''
+ 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4512.xml'>
<!ENTITY rfc4526 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4526.xml'>
<!ENTITY rfc4529 PUBLIC ''
Clients SHOULD NOT rely on any specific ordering of controls handling
when requesting the "What Failed?" control.
</t>
+
+ <t>
+Servers implementing this technical specification SHOULD publish
+the object identifier whatFailed-oid (IANA assigned;
+see <xref target="iana_considerations" />) as a value
+of the 'supportedControl' attribute <xref target="RFC4512" />
+in their root DSE.
+ </t>
</section>
<section title="Control Request">
<t>
-The controlType is whatFailed-oid;
+The controlType is whatFailed-oid (IANA assigned;
+see <xref target="iana_considerations" />);
the controlValue MUST be absent;
the criticality SHOULD be FALSE.
</t>
<section title="Control Response">
<figure>
<preamble>
-The controlType is whatFailed-oid;
+The controlType is whatFailed-oid (IANA assigned;
+see <xref target="iana_considerations" />);
the controlValue is:
</preamble>
<artwork>
</t>
</section>
- <section title="IANA Considerations">
+ <section anchor="iana_considerations" title="IANA Considerations">
<section title="Object Identifier Registration">
<figure>
<preamble>
&rfc2119;
&rfc4510;
&rfc4511;
+ &rfc4512;
</references>
<references title='Informative References'>
&rfc4526;
projects / openldap / commitdiff