Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)
RFC 3876
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2015-10-14 |
07 | (System) | Notify list changed from <d.w.chadwick@iti.salford.ac.uk>, <SEAN.MULLAN@SUN.COM> to <d.w.chadwick@iti.salford.ac.uk> |
2004-09-21 |
07 | Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2004-09-21 |
07 | Amy Vezza | [Note]: ' RFC 3876' added by Amy Vezza |
2004-09-14 |
07 | (System) | RFC published |
2004-05-17 |
07 | Amy Vezza | State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza |
2004-05-17 |
07 | Amy Vezza | IESG state changed to Approved-announcement sent |
2004-05-17 |
07 | Amy Vezza | IESG has approved the document |
2004-05-17 |
07 | Amy Vezza | Closed "Approve" ballot |
2004-05-17 |
07 | Amy Vezza | State Changes to Approved-announcement to be sent from IESG Evaluation::AD Followup by Amy Vezza |
2004-01-08 |
07 | Amy Vezza | Removed from agenda for telechat - 2004-01-08 by Amy Vezza |
2004-01-08 |
07 | Amy Vezza | State Changes to IESG Evaluation::AD Followup from IESG Evaluation - Defer by Amy Vezza |
2004-01-05 |
07 | Harald Alvestrand | [Ballot Position Update] New position, Yes, has been recorded for by Harald Alvestrand |
2003-12-18 |
07 | Amy Vezza | [Ballot Position Update] New position, No Objection, has been recorded for by Amy Vezza |
2003-12-18 |
07 | Amy Vezza | [Ballot Position Update] New position, No Objection, has been recorded for by Amy Vezza |
2003-12-18 |
07 | Harald Alvestrand | State Changes to IESG Evaluation - Defer from IESG Evaluation by Harald Alvestrand |
2003-12-18 |
07 | Alex Zinin | [Ballot Position Update] New position, No Objection, has been recorded for by Alex Zinin |
2003-12-18 |
07 | Bill Fenner | [Ballot Position Update] New position, No Objection, has been recorded for by Bill Fenner |
2003-12-18 |
07 | Bert Wijnen | [Ballot Position Update] Position for Bert Wijnen has been changed to No Objection from Undefined by Bert Wijnen |
2003-12-18 |
07 | Bert Wijnen | [Ballot comment] From OPS Directorate review: The editorial quality is not too good. As one nit, there should not be numbered references in the boilerplate … [Ballot comment] From OPS Directorate review: The editorial quality is not too good. As one nit, there should not be numbered references in the boilerplate to RFC2026, that'll go awry when rfc-editor remvoes the boilerplate.. Registrigration of the Matched Values control as an LDAP Protocol ==> s/Registrigration/Registration/ Bert adds: - IANA considerations: This document uses the OID 1.2.826.0.1.3344810.2.3 to identify the matchedValues control described here. This OID was assigned by TrueTrust Ltd, under its BSI assigned English/Welsh Registered Company number [13]. Probably OK? I am not sure. In any event we should decide consciously. - no IPR section. Would that not be usefull to have, to make sure that individual submitter understands that he needs to file any IPR that he/she may have? |
2003-12-18 |
07 | Bert Wijnen | [Ballot Position Update] New position, Undefined, has been recorded for by Bert Wijnen |
2003-12-18 |
07 | Jon Peterson | [Ballot Position Update] New position, No Objection, has been recorded for by Jon Peterson |
2003-12-17 |
07 | Margaret Cullen | [Ballot Position Update] New position, No Objection, has been recorded for by Margaret Wasserman |
2003-12-17 |
07 | Russ Housley | [Ballot comment] The document does not follow the guidelines for examples. It uses the author's phone numbers and email addresses. |
2003-12-17 |
07 | Russ Housley | [Ballot Position Update] New position, No Objection, has been recorded for by Russ Housley |
2003-12-17 |
07 | Ted Hardie | [Ballot comment] In reply to Ned's Discuss: AttributeDescriptionList is defined in RFC2251, and is part of the core LDAP spec. The RFC is referenced as … [Ballot comment] In reply to Ned's Discuss: AttributeDescriptionList is defined in RFC2251, and is part of the core LDAP spec. The RFC is referenced as [2] in this draft. I suspect the community of developers working won't have an issue with it, but just in case, would "(see [2])" at the first mention of AttributeDescriptionList solve the problem? |
2003-12-16 |
07 | Steven Bellovin | [Ballot Position Update] New position, No Objection, has been recorded for by Steve Bellovin |
2003-12-07 |
07 | Ned Freed | [Ballot discuss] The note at the end of section 2 says: Note. If the AttributeDescriptionList is empty or comprises "*" then the control … [Ballot discuss] The note at the end of section 2 says: Note. If the AttributeDescriptionList is empty or comprises "*" then the control MUST be applied against every user attribute. If the AttributeDescriptionList contains a "+" then the control MUST be applied against every operational attribute. But "AttributeDescriptionList" appears nowhere else in the document, nor is it part of any of any of the components of SimpleFilterItem. I assume this is referring to the attributes field of the search request this control is attached to, but this really needs to be made more explicit. More generally, an interesting side effect of this control is that it doesn't seem to be possible to say "return only the values of these attributes that match these criteria but return all values of all other attributes". Is this going to be a problem? And even if it isn't a problem, some text describing this limitation would seem to be in order. Nits: The first example uses the domains hotmail.com and sun.com. These should be changed to our customary example domains. Section 7. "Registrigration" -> "Registration". Copyright boilerplate has (date) rather than an actual date. Section 12 should be marked as needing to be removed prior to publication. Further discussion: We now have a number of LDAP controls that apply to searching (2891 - server side result sorting, 2696 - paged results, 2649 - signed results). I believe I can argue that the utility of being able to specify any of these in an LDAP URL is questionable, and that wanting paged results, sorted results, or signed results is a function of the underlying application and not of the URL the application is processing. But I cannot make the same argument stick for this document -- it seems quite reasonable to want to be able to construct an LDAP URL that says "return only the attribute values that match these criteria". As such, I wonder if it would not be appropriate to define an LDAP URL extension that allows this control to be specified. (Is this why ABNF for specifying a string version of this control was worked out so carefully?) |
2003-12-07 |
07 | Ned Freed | [Ballot Position Update] Position for Ned Freed has been changed to Discuss from Yes by Ned Freed |
2003-12-07 |
07 | Ned Freed | [Ballot Position Update] New position, Yes, has been recorded for by Ned Freed |
2003-12-04 |
07 | Ted Hardie | State Changes to IESG Evaluation from Waiting for Writeup by Ted Hardie |
2003-12-02 |
07 | Ted Hardie | Placed on agenda for telechat - 2003-12-18 by Ted Hardie |
2003-12-02 |
07 | Ted Hardie | [Ballot Position Update] New position, Yes, has been recorded for Ted Hardie |
2003-12-02 |
07 | Ted Hardie | Ballot has been issued by Ted Hardie |
2003-12-02 |
07 | Ted Hardie | Created "Approve" ballot |
2003-12-02 |
07 | (System) | Ballot writeup text was added |
2003-12-02 |
07 | (System) | Last call text was added |
2003-12-02 |
07 | (System) | Ballot approval text was added |
2003-07-23 |
07 | (System) | New version available: draft-ietf-ldapext-matchedval-07.txt |
2003-03-24 |
07 | Ted Hardie | Shepherding AD has been changed to Hardie, Ted from Faltstrom, Patrik |
2002-10-29 |
07 | Patrik Fältström | This is an individual submission. |
2002-10-29 |
07 | Patrik Fältström | by paf |
2002-10-29 |
07 | Patrik Fältström | State Changes to Waiting for Writeup from AD Evaluation by paf |
2002-10-29 |
07 | Patrik Fältström | I changed my mind. Let's keep this as a wg document for some days. |
2002-10-29 |
07 | Patrik Fältström | by paf |
2002-10-29 |
07 | Patrik Fältström | Should be an individual submission and not part of LDAPEXT wg. |
2002-10-29 |
07 | Patrik Fältström | by paf |
2002-10-29 |
07 | Patrik Fältström | Waiting for new version which takes care of references to new draft-ietf-ldapbis-iana. Responsible: Patrik |
2002-10-29 |
07 | Patrik Fältström | by paf |
2002-10-29 |
07 | Patrik Fältström | State Changes to AD Evaluation -- Revised ID Needed from AD Evaluation -- External Party by paf |
2002-09-02 |
07 | Patrik Fältström | Waiting for new version due to draft-ietf-ldapbis-iana being created. |
2002-09-02 |
07 | Patrik Fältström | A new comment added by paf |
2002-09-02 |
07 | Patrik Fältström | State Changes to New Version Needed (WG/Author) from Wait for Writeup by paf |
2002-08-30 |
07 | Stephen Coya | State Changes to Wait for Writeup from Last Call Issued by scoya |
2002-07-29 |
07 | Stephen Coya | responsible has been changed to Patrik from Area Directors |
2002-07-29 |
07 | Stephen Coya | State Changes to Last Call Issued from New Version … State Changes to Last Call Issued from New Version Needed (WG/Author) by scoya |
2002-07-29 |
07 | (System) | Last call sent |
2002-06-27 |
06 | (System) | New version available: draft-ietf-ldapext-matchedval-06.txt |
2002-05-01 |
07 | Patrik Fältström | After the new version is done, a 4 week call will be issued as this will be treated as an individual submission |
2002-05-01 |
07 | Patrik Fältström | Intended Status has been changed to Proposed Standard from Request |
2002-05-01 |
07 | Patrik Fältström | State Changes to New Version Needed (WG/Author) from AD Evaluation … State Changes to New Version Needed (WG/Author) from AD Evaluation by Patrik Faltstrom |
2002-04-29 |
07 | Patrik Fältström | I have sent a question to the LDAP directorate on suggestions on what to do with this draft. |
2002-03-08 |
07 | Harald Alvestrand | This (now expired) draft was submitted for publication as Proposed in April 2001. |
2002-03-08 |
07 | Harald Alvestrand | Draft Added by Harald Alvestrand |
2000-12-19 |
05 | (System) | New version available: draft-ietf-ldapext-matchedval-05.txt |
2000-10-16 |
04 | (System) | New version available: draft-ietf-ldapext-matchedval-04.txt |
2000-09-05 |
03 | (System) | New version available: draft-ietf-ldapext-matchedval-03.txt |
2000-07-06 |
02 | (System) | New version available: draft-ietf-ldapext-matchedval-02.txt |
1999-09-08 |
01 | (System) | New version available: draft-ietf-ldapext-matchedval-01.txt |
1999-08-20 |
00 | (System) | New version available: draft-ietf-ldapext-matchedval-00.txt |