Skip to main content

Lightweight Directory Access Protocol (LDAP) Read Entry Controls
draft-zeilenga-ldap-readentry-04

Revision differences

Document history

Date Rev. By Action
2005-07-12
04 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2005-06-27
04 Amy Vezza IESG state changed to Approved-announcement sent
2005-06-27
04 Amy Vezza IESG has approved the document
2005-06-27
04 Amy Vezza Closed "Approve" ballot
2005-06-27
04 Amy Vezza [Ballot Position Update] New position, No Objection, has been recorded for Allison Mankin by Amy Vezza
2005-06-24
04 Amy Vezza State Changes to Approved-announcement to be sent from IESG Evaluation by Amy Vezza
2005-06-23
04 Mark Townsley [Ballot Position Update] New position, No Objection, has been recorded for Mark Townsley by Mark Townsley
2005-06-23
04 Jon Peterson [Ballot Position Update] New position, No Objection, has been recorded for Jon Peterson by Jon Peterson
2005-06-22
04 David Kessens [Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens
2005-06-22
04 Bill Fenner [Ballot Position Update] New position, No Objection, has been recorded for Bill Fenner by Bill Fenner
2005-06-21
04 Russ Housley [Ballot Position Update] New position, No Objection, has been recorded for Russ Housley by Russ Housley
2005-06-21
04 Sam Hartman [Ballot Position Update] New position, No Objection, has been recorded for Sam Hartman by Sam Hartman
2005-06-17
04 Brian Carpenter
[Ballot comment]
Editorial points from review by Scott Brim:

...

Some text suggestions:

  If the update operation fails (in either normal or control
  …
[Ballot comment]
Editorial points from review by Scott Brim:

...

Some text suggestions:

  If the update operation fails (in either normal or control
  processing), no response control is provided.

I know this means that no response control is provided for the
post-read request, but as a naive reader I had to stop and think
whether that meant no response was provided to the update request at
all.  Not knowing the protocol well, it's hard for me to suggest an
improvement, but consider adding "to the post-read request control".

  The Pre-Read and Post-Read controls may be combined with each other
  and/or with a variety of other controls.  When combined with the
  assertion control [Assertion] and/or the manageDsaIT control
  [RFC3296], the semantics of each control included in the combination
  apply.  The Pre-Read and Post-Read controls may be combined with
  other controls as detailed in other technical specifications.

You could delete the last sentence, which is somewhat redundant, if
you added "as detailed in other specifications" to the first sentence.

  The controls defined in this document extend update operations to
  support read capabilities.  Servers MUST ensure that the client is
  authorized both for reading of the information provided in this
  control in addition to ensuring the client is authorized to perform
  the requested directory update.

That last sentence has too much in it and probably isn't English.  How
about "Servers MUST ensure that the client is authorized both to read
the information provided in this control and to perform the requested
directory update"?

A small nit: sometimes it says "a LDAP control" and sometimes "an LDAP
control".
2005-06-17
04 Brian Carpenter [Ballot Position Update] New position, No Objection, has been recorded for Brian Carpenter by Brian Carpenter
2005-06-16
04 Scott Hollenbeck [Ballot Position Update] New position, No Objection, has been recorded for Scott Hollenbeck by Scott Hollenbeck
2005-06-13
04 Ted Hardie [Ballot Position Update] New position, Yes, has been recorded for Ted Hardie
2005-06-13
04 Ted Hardie Ballot has been issued by Ted Hardie
2005-06-13
04 Ted Hardie Created "Approve" ballot
2005-06-13
04 Ted Hardie Telechat date was changed to 2005-06-23 from  by Ted Hardie
2005-06-13
04 Ted Hardie Placed on agenda for telechat - 2005-06-23 by Ted Hardie
2005-06-13
04 Ted Hardie State Changes to IESG Evaluation from Waiting for Writeup by Ted Hardie
2005-06-10
04 (System) State has been changed to Waiting for Writeup from In Last Call by system
2005-05-31
04 Michelle Cotton
IANA Last Call Comments:
Upon approval of this document the IANA will register a LDAP Object Identifier
in the following registr: SMI Network Management Directory …
IANA Last Call Comments:
Upon approval of this document the IANA will register a LDAP Object Identifier
in the following registr: SMI Network Management Directory Codes found at
http://www.iana.org/assignments/smi-numbers.
IANA will also register 2 LDAP Protocol Mechanisms found at
http://www.iana.org/assignments/ldap-parameters.
2005-05-13
04 Amy Vezza Last call sent
2005-05-13
04 Amy Vezza State Changes to In Last Call from Last Call Requested by Amy Vezza
2005-05-13
04 Ted Hardie State Changes to Last Call Requested from Publication Requested by Ted Hardie
2005-05-13
04 Ted Hardie Last Call was requested by Ted Hardie
2005-05-13
04 (System) Ballot writeup text was added
2005-05-13
04 (System) Last call text was added
2005-05-13
04 (System) Ballot approval text was added
2005-03-14
04 Scott Hollenbeck Draft Added by Scott Hollenbeck in state Publication Requested
2005-02-14
04 (System) New version available: draft-zeilenga-ldap-readentry-04.txt
2004-10-29
03 (System) New version available: draft-zeilenga-ldap-readentry-03.txt
2004-02-16
02 (System) New version available: draft-zeilenga-ldap-readentry-02.txt
2003-10-28
01 (System) New version available: draft-zeilenga-ldap-readentry-01.txt
2003-06-23
00 (System) New version available: draft-zeilenga-ldap-readentry-00.txt