TCP/IP Tutorial and Technical Overview - IBM Redbooks

RFC number Content
4519 Schema for User Applications
4520 Internet Assigned Numbers Authority (IANA) Considerations for
LDAP
4521 Considerations for LDAP
4522 The Binary Encoding Option
4523 Schema Definitions for X.509 Certificates
4524 COSINE/ LDAP X.500 Schema
4525 Modify-Increment Extension
4526 Absolute True and False Filters
4527 Read Entry Controls
4528 Assertion Control
4529 Requesting Attributes by Object Class in LDAP
4530 entryUUID Operational Attribute
4531 Turn Operation
4532 “Who Am I” Operation
4533 Content Synchronization Operation
Though an application program interface (API) for previous versions of LDAP
was limited to specifications in RFC 1823, the LDAPv3 provides both a C API
and a Java Naming and Directory Interface (JNDI).
12.4.2 The LDAP directory server
LDAP defines a communication protocol. That is, it defines the transport and
format of messages used by a client to access data in an X.500-like directory.
LDAP does not define the directory service itself. An application client program
initiates an LDAP message by calling an LDAP API. But an X.500 directory
server does not understand LDAP messages. In fact, the LDAP client and X.500
server even use different communication protocols (TCP/IP versus OSI). The
LDAP client actually communicates with a gateway process (also called a proxy
or front end) that forwards requests to the X.500 directory server (see
Figure 12-14 on page 462), known as an LDAP server, which fulfils requests
from the LDAP client. It does this by becoming a client of the X.500 server. The
Chapter 12. Directory and naming protocols 461