[turba] First shot at a new ldap schema.

[Adam Tauno Williams]

>>Please let me know what changes should be made and how we might want to
>>maintain this in the future as new applications are added.
>should we be making a smimepublickey?  Why not use userSMIMECertificate
>(2.16.840.1.113730.3.1.40) in inetOrgPerson?  

My understanding is that a SMIMECertificate != pgp public key.  This was
thrashed out on the OpenLDAP list a while back.  There are public LDAP-backed
PGP key exchanges, so there must be a schema somewhere, but I haven't found it yet.

I did find a note on the syntax, it should always be ASCII.  The key is encoded
as a hex string and prefixed with a "0x".  No OIDs or attribute names yet,  I'll
look some more on my lunch.


>And for free/busy info I think
>there is some stuff already out there.  I'm using calFBURL
>(1.2.840.113556.1.4.479) which was mentioned by someone a couple weeks ago. 
>We can rename the attribute names to something more friendly, but keep the
>existing OIDs.  However, there could be limitations that I don't know about. 

Since many applications use calFBURL, etc..., and may place the information in
the Dit as such, I think we should just go with the rfc2839 attributes.


Adam Tauno Williams
Network & Systems Administrator
Morrison Industries
Grand Rapids, Mi. USA