Skip to main content

Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: Internet Architecture Board <>,
    RFC Editor <>, 
    ldapbis mailing list <>, 
    ldapbis chair <>
Subject: Protocol Action: 'LDAP:String Representation of 
         Distinguished Names' to Proposed Standard 

The IESG has approved the following documents:

- 'LDAP:String Representation of Distinguished Names '
   <draft-ietf-ldapbis-dn-17.txt> as a Proposed Standard
- 'LDAP: String Representation of Search Filters '
   <draft-ietf-ldapbis-filter-10.txt> as a Proposed Standard
- 'LDAP: Directory Information Models '
   <draft-ietf-ldapbis-models-15.txt> as a Proposed Standard

These documents are products of the LDAP (v3) Revision Working Group. 

The IESG contact persons are Ted Hardie and Lisa Dusseault.

A URL of this Internet-Draft is:

Ballot Text

Technical Summary
This document defines the string representation used in the Lightweight
Directory Access Protocol
(LDAP) to transfer distinguished names.  The string representation is
designed to give a clean representation of commonly used distinguished
names, while being able to represent any distinguished name.
This document will replace RFC 2253; please refer to Appendix
B. for the changes since RFC 2253.
Working Group Summary
This doucment is the product of the LDAPBIS working group.  The working
group came to consensus on this document, and there were no comments
during the IETF-wide Last Call.

Protocol Quality
This document was reviewed for the IESG by Ted Hardie.

RFC Editor Note
RFC Editor, please move the following reference from Informative
to Normative and update the text as described below.

[BCP64bis]    Zeilenga, K., "IANA Considerations for LDAP",
                draft-ietf-ldapbis-bcp64-xx.txt, a work in progress.

In Section 3.


Implementations MAY recognize other DN string representations (such as
  that described in RFC 1779).  

Implementations MAY recognize other DN string representations.

RFC Editor Note