The answer is yes. There is a companion RFC to the LDAP RFC1777 - which is
RFC1778 that spells out the attribute names. You seem to have reaad 1777 and
1779, but missed 1778! However, both the LDAP v2 and the attribute paper are
being revised and the latest drafts are:
draft-ietf-asid-ldapv2-protocol-00.txt and
draft-ietf-asid-ldapv2-attributes-00.txt
Hope this helps.
-- -sri (Srinivas Sataluri, 908-949-7782, sri@qsun.att.com or sataluri@attmail.com-- --- Forwarded mail from Russell Fulton <r.fulton@auckland.ac.nz>From: Russell Fulton <r.fulton@auckland.ac.nz> Subject: attribute naming standards To: ldap@umich.edu Date: Fri, 21 Jun 1996 10:36:06 +1200 (NZT)
Greetings all.
Next silly question:
Are the attribute names cn, sn, ou, mail, etc standardised?
I ask this because I have now got Simeon mail client to work with the UM ldap server by changing the attribute names to: commonname, surname and department. Not surprisingly now none of the UM clients find the attributes they are looking for.
It seems to me that if various implementations are to interopereate then there needs to be agreement on a core set of attributes.
RFC1779 on distinguishing names gives a standard set of names for use in dns including cn, ou and o.
Are ther any other 'standard' names?
Can a client that uses commonname instead of cn rightly claim to be an LDAP client since it appears to be at least in violation of 1779?
Alternatively is there anything I can set up in the configuration file that maps cn to commonname and vise versa?
Cheers, Russell.
+-------------------------------------------------------------------+ | Russell Fulton 'phone +64 9 373-7599 x 8955 | | ITSS fax +64 9 373-7425 | | University of Auckland email r.fulton@auckland.ac.nz | | Private Bag 92019 time gmt -12 (-13 oct - mar) | | Auckland, New Zealand. | +-------------------------------------------------------------------+
--- End of forwarded mail from Russell Fulton <r.fulton@auckland.ac.nz>