LDAP Series Part III - The Historical Secrets
The origins of LDAP begin with the International Telecommunication Union (ITU) based in Geneva. ITU began setting email standards which required a directory of names (and other information) that could be accessed across networks in a hierarchical fashion not dissimilar to DNS. The result of their work resulted in the X.500 series of standards which defined DAP (Directory Access Protocol), the protocol for accessing a networked directory service.
Tim Howes, Steve Kille and Wengyik Yeong saw a better way to achieve the aims of ITU and published a proposal entitled X.500 Lightweight Directory Access Protocol in RFC 1487 during July 1993. Their abstract read as follows:
The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the Directory, and is intended to be a complement to the DAP itself.
Tim Howes of the University of Michigan led the development of LDAP supported by the National Science Foundation. From 1993 to 1997, the Internet Engineering Task Force (IETF) published 13 RFCs related to LDAP and dozens since. In essence, the University of Michigan invented and created LDAP. Two open source projects resulted from the work at the University of Michigan – OpenLDAP and the Fedora Directory Server.
On April 22, 1996, in a press release, the University of Michigan announced that "Netscape (would) incorporate Lightweight Directory Access Protocol (LDAP) directory service technology developed at the U-M into its World-Wide Web software." The University felt they had taken "a giant step toward having (a) global directory service on the Internet."
Netscape and the University partnered to create the Netscape Directory Server (NDS), which became the leading LDAP application in commercial use. Interestingly enough, Red Hat purchased NDS from AOL and open sourced its code. That resulted in delivery of Fedora Directory Server (FDS) to the Linux community.
The OpenLDAP Project was started in 1998 by Kurt Zeilenga. The project started by cloning the LDAP source code from the University Of Michigan. When attempting to access the original LDAP project, the page redirects you to the OpenLDAP project.
In essence, one could speculate that the OpenLDAP project became the successor of the University of Michigan project.
Subsequent Internet protocols have their origins in LDAP including the XML Enabled Directory (XED), Directory Services Markup Language (DSML), the Service Location Protocol (SLP) and the Service Provisioning Markup Language (SPML).
Of course, this short discussion requires mention of one other subsequent development - Active Directory (AD). Redmond utilized LDAP protocols to create AD, which demonstrates the remarkable potential of the founders' (Tim Howes, Steve Kille and Wengyik Yeong) work, which began back in 1993.
If you haven't delved into AD, you owe it to yourself to do so. The Linux community could use the AD blueprint to manage enterprises. That could extend the historical discussion of LDAP even further.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Keeping track of IP address
43 min 12 sec ago - Roll your own dynamic dns
5 hours 56 min ago - Please correct the URL for Salt Stack's web site
9 hours 8 min ago - Android is Linux -- why no better inter-operation
11 hours 23 min ago - Connecting Android device to desktop Linux via USB
11 hours 51 min ago - Find new cell phone and tablet pc
12 hours 50 min ago - Epistle
14 hours 18 min ago - Automatically updating Guest Additions
15 hours 27 min ago - I like your topic on android
16 hours 13 min ago - This is the easiest tutorial
22 hours 49 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
LDAP begin with the International Telecommunication Union
I think recently linux more intresting directions and all works make that more convient.
Don't touch Active Directory, let alone learn something!
AD is all wrong and some of it isn't even standards based. Just keep using it for your Windows Domain Authentications and leave the real Directory servers to it ;-)
Gavin.
History of LDAP is missing...
The history of LDAP is missing something unless the contributions of Novell and their legendary NDS are recognized. Ahead of the curve in it's day and which subsequently became an LDAP v3 implementation that runs on NetWare, Linux, Solaris, Windoze, etc...surely a conversation starter!
The Historical Secrets
I love history..especially when its related to OSS. Hope all is well.