[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: protocol: compare operation
- To: "Hallvard B Furuseth" <h.b.furuseth@usit.uio.no>, <ietf-ldapbis@OpenLDAP.org>
- Subject: RE: protocol: compare operation
- From: "Ramsay, Ron" <Ron.Ramsay@ca.com>
- Date: Mon, 5 Jan 2004 11:46:44 +1100
- Content-class: urn:content-classes:message
- Thread-index: AcPQcpPEgAQlZ3oMRdWxf9WZ21ilCgCspXKw
- Thread-topic: protocol: compare operation
By undefined, do you mean the attribute is unknown or not present in the entry? If so, return an attribute error. The compare will return true if ANY value matches.
-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Hallvard B Furuseth
Sent: Friday, 2 January 2004 01:15
To: ietf-ldapbis@OpenLDAP.org
Subject: protocol: compare operation
The Compare operation is under-specified. What is the result if:
- The match evaluates to Undefined?
- Match against one attribute value evaluates to FALSE and against
another evaluates to TRUE or Undefined?
- The attribute has no EQUALITY matching rule? Maybe return
inappropriateMatching? (Not sure if this needs to be specified.)
Also, as I mentioned earlier, section 4.10 should mention
compareTrue and compareFalse.
--
Hallvard