[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Revised Matched Values Draft
David,
> -----Original Message-----
> From: David Chadwick [mailto:d.w.chadwick@salford.ac.uk]
> Sent: Wednesday, 12 July 2000 8:36
> To: Kurt D. Zeilenga
> Cc: ietf-ldapext@netscape.com
> Subject: Re: Revised Matched Values Draft
>
>
> Kurt
>
[snip]
> > >An LDAP search operation is specified with a baseObject
> set to the DN
> > >of the entry, a subtree scope, a filter set to
> >
> >"(|(mail=sean.mullan@sun.com)(mail=d.w.chadwick@salford.ac.uk))", and
> > > the list of attributes to be returned set to "mail
> telephoneNumber".
> > > In addition, a ValuesReturnFilter control is set to
> > >"mail=sean.mullan@sun.com, mail=d.w.chadwick@salford.ac.uk,
> > >telephoneNumber=*"
> >
> > Please use parentheses. In fact, you may want to define a string
> > format for ValuesReturnFilter. I suggest something like:
> >
> >
> (:(mail=sean.mullan@sun.com)(mail=d.w.chadwick@salford.ac.uk)(teleph
> > oneNumber=*))
> >
> > or if that looks too much like a search filter:
> >
> >
> {(mail=sean.mullan@sun.com)(mail=d.w.chadwick@salford.ac.uk)(telepho
> > neNumber=*)}
>
> I think it would be a good idea for the LDAP group to settle on a
> character that can represent the ASN.1 type SEQUENCE, and
> another that can represent a SET.
I think it would be a good idea for the LDAP group to settle on a
uniform predictable way of encoding any ASN.1 type (I volunteer to
write an I-D on it if there's any support) but that is another story.
> I need this also for my PKI and
> PMI schema document. Steven Legg is working on this at the
> moment, but lets assume for now that comma , represents
> SEQUENCE and + represents SET. Unfortunately we have not
> been too consistent in this in the past, as comma has represented
> both, and + has also represented SET (e.g. as in DNs)
I don't see any need to distinguished between SET and SEQUENCE in a
string encoding. They can just as well use the same separator, or if
the components of the SET/SEQUENCE are self-contained as in Kurt's
suggestion above then no separators are necessary.
ASN.1 value notation also treats SET & SEQUENCE the same, and I suspect
the comma separators there are cosmetic anyway.
[snip]
Regards,
Steven
> ***************************************************
>
> David Chadwick
> IS Institute, University of Salford, Salford M5 4WT
> Tel +44 161 295 5351 Fax +44 161 745 8169
> Mobile +44 790 167 0359
> Email D.W.Chadwick@salford.ac.uk
> Home Page http://www.salford.ac.uk/its024/chadwick.htm
> Understanding X.500 http://www.salford.ac.uk/its024/X500.htm
> X.500/LDAP Seminars http://www.salford.ac.uk/its024/seminars.htm
> Entrust key validation string MLJ9-DU5T-HV8J
>
> ***************************************************
>
>