Red Hat Bugzilla – Bug 21701
RFCs should be packaged in openldap, not openldap-devel
Last modified: 2007-03-26 23:38:02 EDT
In order to know what to put in your ldap database, and how to structure
it, many of the RFC's packaged in openldap-devel should be available to the
openldap user. Minimally, they should go in openldap-server but many of
them may also be necessary in order to know how to formulate queries, so
you might consider putting them in openldap.
Here's my list of openldap-devel RFC numbers (possibly) needed to run/query
Some of these are only needed for those who are attempting some sort of
x500 compatibiltiy, which is probably not most people. Although just
because the RFC talks about x500 it dosen't mean that it's not really
useful in setting up ldap. I found the x500 executive and techincal
overviews key. Others, like the ones titled "A String Representation of
LDAP Search Filters" are really handy when querying with a client and may
not really be necessary to set up a server.
In any case, they don't belong in openldap-devel as they are of much wider
use. Considering that the ldap documentation is so weak, I don't know how
people could set up a server without them.
My list is the result of a quick look-see. Somebody who knows what they
are doing would surely do a better job.
Um, okay, I'll stick them in the base package (it might be better for -clients,
but I could see the search filter and other things being useful if you're using
nss_ldap, which doesn't need -clients). This change will be made in 2.0.7-7 and