draft-ietf-ldapbis-dn-15.txt   draft-ietf-ldapbis-dn-16.txt 
INTERNET-DRAFT Editor: Kurt D. Zeilenga INTERNET-DRAFT Editor: Kurt D. Zeilenga
Intended Category: Standard Track OpenLDAP Foundation Intended Category: Standard Track OpenLDAP Foundation
Expires in six months 24 October 2004 Expires in six months 10 February 2005
Obsoletes: 2253 Obsoletes: RFC 2253
LDAP: String Representation of Distinguished Names LDAP: String Representation of Distinguished Names
<draft-ietf-ldapbis-dn-15.txt> <draft-ietf-ldapbis-dn-16.txt>
Status of Memo Status of Memo
This document is intended to be, after appropriate review and This document is intended to be, after appropriate review and
revision, submitted to the RFC Editor as a Standard Track document revision, submitted to the RFC Editor as a Standard Track document
replacing RFC 2253. Distribution of this memo is unlimited. replacing RFC 2253. Distribution of this memo is unlimited.
Technical discussion of this document will take place on the IETF LDAP Technical discussion of this document will take place on the IETF LDAP
Revision (LDAPBIS) Working Group mailing list Revision (LDAPBIS) Working Group mailing list
<ietf-ldapbis@openldap.org>. Please send editorial comments directly <ietf-ldapbis@openldap.org>. Please send editorial comments directly
to the document editor <Kurt@OpenLDAP.org>. to the document editor <Kurt@OpenLDAP.org>.
skipping to change at page 1, line 36 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress." or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
<http://www.ietf.org/ietf/1id-abstracts.txt>. The list of http://www.ietf.org/1id-abstracts.html
Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>.
Copyright (C) The Internet Society (2004). All Rights Reserved. The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright (C) The Internet Society (2005). All Rights Reserved.
Please see the Full Copyright section near the end of this document Please see the Full Copyright section near the end of this document
for more information. for more information.
Abstract Abstract
The X.500 Directory uses distinguished names (DNs) as primary keys to The X.500 Directory uses distinguished names (DNs) as primary keys to
entries in the directory. This document defines the string entries in the directory. This document defines the string
representation used in the Lightweight Directory Access Protocol representation used in the Lightweight Directory Access Protocol
(LDAP) to transfer distinguished names. The string representation is (LDAP) to transfer distinguished names. The string representation is
skipping to change at page 2, line 50 skipping to change at page 2, line 50
ASN.1 structured representation. ASN.1 structured representation.
While other documents may define other algorithms for converting a DN While other documents may define other algorithms for converting a DN
from its ASN.1 structured representation to a string, all algorithms from its ASN.1 structured representation to a string, all algorithms
MUST produce strings which adhere to the requirements of Section 3. MUST produce strings which adhere to the requirements of Section 3.
This document does not define a canonical string representation for This document does not define a canonical string representation for
DNs. Comparison of DNs for equality is to be performed in accordance DNs. Comparison of DNs for equality is to be performed in accordance
with the distinguishedNameMatch matching rule [Syntaxes]. with the distinguishedNameMatch matching rule [Syntaxes].
This document is an integral part of the LDAP Technical Specification This document is a integral part of the LDAP technical specification
[Roadmap]. This document obsoletes RFC 2253. Changes since RFC 2253 [Roadmap] which obsoletes the previously defined LDAP technical
are summarized in Appendix B. specification, RFC 3377, in its entirety. This document obsoletes RFC
2253. Changes since RFC 2253 are summarized in Appendix B.
This specification assumes familiarity with X.500 [X.500] and the This specification assumes familiarity with X.500 [X.500] and the
concept of Distinguished Name [X.501][Models]. concept of Distinguished Name [X.501][Models].
1.1. Conventions 1.1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 [RFC2119]. document are to be interpreted as described in BCP 14 [RFC2119].
skipping to change at page 4, line 32 skipping to change at page 4, line 32
AttributeTypeAndValues are separated by a plus sign ('+' U+002B) AttributeTypeAndValues are separated by a plus sign ('+' U+002B)
character. character.
2.3. Converting AttributeTypeAndValue 2.3. Converting AttributeTypeAndValue
The AttributeTypeAndValue is encoded as the string representation of The AttributeTypeAndValue is encoded as the string representation of
the AttributeType, followed by an equals sign ('=' U+003D) character, the AttributeType, followed by an equals sign ('=' U+003D) character,
followed by the string representation of the AttributeValue. The followed by the string representation of the AttributeValue. The
encoding of the AttributeValue is given in Section 2.4. encoding of the AttributeValue is given in Section 2.4.
If the AttributeType is defined to have a short name and that short If the AttributeType is defined to have a short name (descriptor)
name is known to be registered [REGISTRY][BCP64bis] as identifying the [Models] and that short name is known to be registered
AttributeType, that short name, a <descr>, is used. Otherwise the [REGISTRY][BCP64bis] as identifying the AttributeType, that short
AttributeType is encoded as the dotted-decimal encoding, a name, a <descr>, is used. Otherwise the AttributeType is encoded as
<numericoid>, of its OBJECT IDENTIFIER. The <descr> and <numericoid> the dotted-decimal encoding, a <numericoid>, of its OBJECT IDENTIFIER.
is defined in [Models]. The <descr> and <numericoid> is defined in [Models].
Implementations are not expected to dynamically update their knowledge Implementations are not expected to dynamically update their knowledge
of registered short names. However, implementations SHOULD provide a of registered short names. However, implementations SHOULD provide a
mechanism to allow its knowledge of registered short names to be mechanism to allow its knowledge of registered short names to be
updated. updated.
2.4. Converting an AttributeValue from ASN.1 to a String 2.4. Converting an AttributeValue from ASN.1 to a String
If the AttributeType is of the dotted-decimal form, the AttributeValue If the AttributeType is of the dotted-decimal form, the AttributeValue
is represented by an number sign ('#' U+0023) character followed by is represented by an number sign ('#' U+0023) character followed by
skipping to change at page 5, line 42 skipping to change at page 5, line 42
Each octet of the character to be escaped is replaced by a backslash Each octet of the character to be escaped is replaced by a backslash
and two hex digits, which form a single octet in the code of the and two hex digits, which form a single octet in the code of the
character. Alternatively, if and only if the character to be escaped character. Alternatively, if and only if the character to be escaped
is one of is one of
' ', '"', '#', '+', ',', ';', '<', '=', '>', or '\' ' ', '"', '#', '+', ',', ';', '<', '=', '>', or '\'
(U+0020, U+0022, U+0023, U+002B, U+002C, U+003B, (U+0020, U+0022, U+0023, U+002B, U+002C, U+003B,
U+003C, U+003D, U+003E, U+005C respectively) U+003C, U+003D, U+003E, U+005C respectively)
it can be prefixed by a backslash ('\' U+0005C). it can be prefixed by a backslash ('\' U+005C).
Examples of the escaping mechanism are shown in Section 4. Examples of the escaping mechanism are shown in Section 4.
3. Parsing a String back to a Distinguished Name 3. Parsing a String back to a Distinguished Name
The string representation of Distinguished Names is restricted to The string representation of Distinguished Names is restricted to
UTF-8 [RFC3629] encoded Unicode [Unicode] characters. The structure UTF-8 [RFC3629] encoded Unicode [Unicode] characters. The structure
of this string representation is specified using the following of this string representation is specified using the following
Augmented BNF [RFC2234] grammar: Augmented BNF [RFC2234] grammar:
skipping to change at page 9, line 10 skipping to change at page 9, line 10
Distinguished Names typically consist of descriptive information about Distinguished Names typically consist of descriptive information about
the entries they name, which can be people, organizations, devices or the entries they name, which can be people, organizations, devices or
other real-world objects. This frequently includes some of the other real-world objects. This frequently includes some of the
following kinds of information: following kinds of information:
- the common name of the object (i.e. a person's full name) - the common name of the object (i.e. a person's full name)
- an email or TCP/IP address - an email or TCP/IP address
- its physical location (country, locality, city, street address) - its physical location (country, locality, city, street address)
- organizational attributes (such as department name or affiliation) - organizational attributes (such as department name or affiliation)
Most countries have privacy laws regarding the publication of In some cases, such information can be considered sensitive. In many
information about people. countries, privacy laws exist which prohibit disclosure of certain
kinds of descriptive information (e.g., email addresses). Hence,
servers implementors are encouraged to support DIT structural rules
and name forms [Models] as these provide a mechanism for
administrators to select appropriate naming attributes for entries.
Administrators are encouraged to use these mechanisms, access
controls, and other administrative controls which may be available to
restrict use of attributes containing sensitive information in naming
of entries. Additionally, use of authentication and data security
services in LDAP [AuthMeth][Protocol] should be considered.
5.2. Use of Distinguished Names in Security Applications 5.2. Use of Distinguished Names in Security Applications
The transformations of an AttributeValue value from its X.501 form to The transformations of an AttributeValue value from its X.501 form to
an LDAP string representation are not always reversible back to the an LDAP string representation are not always reversible back to the
same BER (Basic Encoding Rules) or DER (Distinguished Encoding rules) same BER (Basic Encoding Rules) or DER (Distinguished Encoding rules)
form. An example of a situation which requires the DER form of a form. An example of a situation which requires the DER form of a
distinguished name is the verification of an X.509 certificate. distinguished name is the verification of an X.509 certificate.
For example, a distinguished name consisting of one RDN with one AVA, For example, a distinguished name consisting of one RDN with one AVA,
skipping to change at page 9, line 45 skipping to change at page 10, line 9
This document is an update to RFC 2253, by Mark Wahl, Tim Howes, and This document is an update to RFC 2253, by Mark Wahl, Tim Howes, and
Steve Kille. RFC 2253 was a product of the IETF ASID Working Group. Steve Kille. RFC 2253 was a product of the IETF ASID Working Group.
This document is a product of the IETF LDAPBIS Working Group. This document is a product of the IETF LDAPBIS Working Group.
7. Document Editor's Address 7. Document Editor's Address
Kurt D. Zeilenga Kurt D. Zeilenga
OpenLDAP Foundation OpenLDAP Foundation
<Kurt@OpenLDAP.org>
Email: Kurt@OpenLDAP.org
8. References 8. References
[[Note to the RFC Editor: please replace the citation tags used in [[Note to the RFC Editor: please replace the citation tags used in
referencing Internet-Drafts with tags of the form RFCnnnn.]] referencing Internet-Drafts with tags of the form RFCnnnn where
possible.]]
8.1. Normative References 8.1. Normative References
[X.501] International Telecommunication Union - [X.501] International Telecommunication Union -
Telecommunication Standardization Sector, "The Directory Telecommunication Standardization Sector, "The Directory
-- Models," X.501(1993) (also ISO/IEC 9594-2:1994). -- Models," X.501(1993) (also ISO/IEC 9594-2:1994).
[X.680] International Telecommunication Union - [X.680] International Telecommunication Union -
Telecommunication Standardization Sector, "Abstract Telecommunication Standardization Sector, "Abstract
Syntax Notation One (ASN.1) - Specification of Basic Syntax Notation One (ASN.1) - Specification of Basic
skipping to change at page 14, line 42 skipping to change at page 15, line 7
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Full Copyright Full Copyright
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/