draft-ietf-ldapbis-user-schema-09.txt   draft-ietf-ldapbis-user-schema-10.txt 
INTERNET-DRAFT Editor: A. Sciberras INTERNET-DRAFT Editor: A. Sciberras
Intended Category: Standard Track eB2Bcom Intended Category: Standard Track eB2Bcom
Updates: RFC 2247, RFC 2798, RFC 2377 April 4, 2005 Updates: RFC 2247, RFC 2798, RFC 2377 July 11, 2005
Obsoletes: RFC 2256 Obsoletes: RFC 2256
LDAP: Schema for User Applications LDAP: Schema for User Applications
draft-ietf-ldapbis-user-schema-09.txt draft-ietf-ldapbis-user-schema-10.txt
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of Section 3 of RFC 3978. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3979. By submitting this Internet-Draft, I accept the provisions of Section
3 of BCP 78.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as
Drafts. 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 time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress". material 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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
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.
Distribution of this memo is unlimited. Technical discussion of this Distribution of this document is unlimited. Technical discussion of
document will take place on the IETF LDAP Revision Working Group this document should take place on the IETF LDAP Revision Working
(LDAPbis) mailing list <ietf-ldapbis@openldap.org>. Please send Group (LDAPbis) mailing list <ietf-ldapbis@openldap.org>. Please
editorial comments directly to the editor send editorial comments directly to the editor
<andrew.sciberras@eb2bcom.com>. <andrew.sciberras@eb2bcom.com>.
This Internet-Draft expires on 4 October 2005. This Internet-Draft expires on 11 January 2006.
Copyright Notice
Copyright (C) The Internet Society 2005. All Rights Reserved.
Abstract Abstract
This document is an integral part of the Lightweight Directory Access This document is an integral part of the Lightweight Directory Access
Protocol (LDAP) technical specification [Roadmap]. It provides a Protocol (LDAP) technical specification [Roadmap]. It provides a
technical specification of attribute types and object classes technical specification of attribute types and object classes
intended for use by LDAP directory clients for many directory intended for use by LDAP directory clients for many directory
services, such as, White Pages. These objects are widely used as a services, such as, White Pages. These objects are widely used as a
basis for the schema in many LDAP directories. This document does basis for the schema in many LDAP directories. This document does
not cover attributes used for the administration of directory not cover attributes used for the administration of directory
skipping to change at page 4, line 42 skipping to change at page 4, line 42
6. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 29 6. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 29
7. References. . . . . . . . . . . . . . . . . . . . . . . . . . 30 7. References. . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.1 Normative. . . . . . . . . . . . . . . . . . . . . . . . 30 7.1 Normative. . . . . . . . . . . . . . . . . . . . . . . . 30
7.2 Informative. . . . . . . . . . . . . . . . . . . . . . . 31 7.2 Informative. . . . . . . . . . . . . . . . . . . . . . . 31
8. Author's Address. . . . . . . . . . . . . . . . . . . . . . . 31 8. Author's Address. . . . . . . . . . . . . . . . . . . . . . . 31
9. Intellectual Property Statement . . . . . . . . . . . . . . . 32 9. Intellectual Property Statement . . . . . . . . . . . . . . . 32
10. Disclaimer of Validity. . . . . . . . . . . . . . . . . . . . 32 10. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 32
1. Introduction 1. Introduction
This document provides an overview of attribute types and object This document provides an overview of attribute types and object
classes intended for use by Lightweight Directory Access Protocol classes intended for use by Lightweight Directory Access Protocol
(LDAP) directory clients for many directory services, such as, White (LDAP) directory clients for many directory services, such as, White
Pages. Originally specified in the X.500 [X.500] documents, these Pages. Originally specified in the X.500 [X.500] documents, these
objects are widely used as a basis for the schema in many LDAP objects are widely used as a basis for the schema in many LDAP
directories. This document does not cover attributes used for the directories. This document does not cover attributes used for the
administration of directory servers, nor does it include directory administration of directory servers, nor does it include directory
skipping to change at page 10, line 10 skipping to change at page 10, line 10
The 'enhancedSearchGuide' attribute type contains sets of information The 'enhancedSearchGuide' attribute type contains sets of information
for use by directory clients in constructing search filters. Each for use by directory clients in constructing search filters. Each
set is one value of this multi-valued attribute. set is one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.47 NAME 'enhancedSearchGuide' ( 2.5.4.47 NAME 'enhancedSearchGuide'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.21 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.21 )
1.3.6.1.4.1.1466.115.121.1.21 refers to the Enhanced Guide syntax 1.3.6.1.4.1.1466.115.121.1.21 refers to the Enhanced Guide syntax
[Syntaxes]. [Syntaxes].
Examples: "person#(sn$APPROX)#wholeSubtree" Examples: "person#(sn$APPROX)#wholeSubtree" and
"organizationalUnit#(ou$SUBSTR)#oneLevel" "organizationalUnit#(ou$SUBSTR)#oneLevel".
2.10 'facsimileTelephoneNumber' 2.10 'facsimileTelephoneNumber'
The 'facsimileTelephoneNumber' attribute type contains telephone The 'facsimileTelephoneNumber' attribute type contains telephone
numbers (and, optionally, the parameters) for facsimile terminals. numbers (and, optionally, the parameters) for facsimile terminals.
Each telephone number is one value of this multi-valued attribute. Each telephone number is one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.23 NAME 'facsimileTelephoneNumber' ( 2.5.4.23 NAME 'facsimileTelephoneNumber'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 )
1.3.6.1.4.1.1466.115.121.1.22 refers to the Facsimile Telephone 1.3.6.1.4.1.1466.115.121.1.22 refers to the Facsimile Telephone
Number syntax [Syntaxes]. Number syntax [Syntaxes].
Examples: "+61 3 9896 7801" and "+81 3 347 7418$fineResolution" Examples: "+61 3 9896 7801" and "+81 3 347 7418$fineResolution".
2.11 'generationQualifier' 2.11 'generationQualifier'
The 'generationQualifier' attribute type contains name strings that The 'generationQualifier' attribute type contains name strings that
are the part of a person's name which typically is the suffix. Each are the part of a person's name which typically is the suffix. Each
string is one value of this multi-valued attribute. string is one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.44 NAME 'generationQualifier' ( 2.5.4.44 NAME 'generationQualifier'
SUP name ) SUP name )
skipping to change at page 10, line 50 skipping to change at page 10, line 50
2.12 'givenName' 2.12 'givenName'
The 'givenName' attribute type contains name strings that are the The 'givenName' attribute type contains name strings that are the
part of a person's name which is not their surname. Each string is part of a person's name which is not their surname. Each string is
one value of this multi-valued attribute. one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.42 NAME 'givenName' ( 2.5.4.42 NAME 'givenName'
SUP name ) SUP name )
Examples: "Andrew", "Charles" and "Joanne" Examples: "Andrew", "Charles" and "Joanne".
2.13 'houseIdentifier' 2.13 'houseIdentifier'
The 'houseIdentifier' attribute type contains identifiers for a The 'houseIdentifier' attribute type contains identifiers for a
building within a location. Each identifier is one value of this building within a location. Each identifier is one value of this
multi-valued attribute. multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.51 NAME 'houseIdentifier' ( 2.5.4.51 NAME 'houseIdentifier'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
[Syntaxes]. [Syntaxes].
Examples: "20" to represent a the house number 20. Examples: "20" to represent the house number 20.
2.14 'initials' 2.14 'initials'
The 'initials' attribute type contains strings of initials of some or The 'initials' attribute type contains strings of initials of some or
all of an individual's names, except the surname(s). Each string is all of an individual's names, except the surname(s). Each string is
one value of this multi-valued attribute. one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.43 NAME 'initials' ( 2.5.4.43 NAME 'initials'
SUP name ) SUP name )
skipping to change at page 11, line 50 skipping to change at page 11, line 50
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.25 NAME 'internationalISDNNumber' ( 2.5.4.25 NAME 'internationalISDNNumber'
EQUALITY numericStringMatch EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.36 )
1.3.6.1.4.1.1466.115.121.1.36 refers to the Numeric String syntax 1.3.6.1.4.1.1466.115.121.1.36 refers to the Numeric String syntax
[Syntaxes]. [Syntaxes].
Example: "0198 333 333" Example: "0198 333 333".
2.16 'l' 2.16 'l'
The 'l' ('localityName' in X.500) attribute type contains names of a The 'l' ('localityName' in X.500) attribute type contains names of a
locality or place, such as a city, county or other geographic region. locality or place, such as a city, county or other geographic region.
Each name is one value of this multi-valued attribute. Each name is one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.7 NAME 'l' ( 2.5.4.7 NAME 'l'
SUP name ) SUP name )
skipping to change at page 12, line 28 skipping to change at page 12, line 28
The 'member' attribute type contains the Distinguished Names of The 'member' attribute type contains the Distinguished Names of
objects that are on a list or in a group. Each name is one value of objects that are on a list or in a group. Each name is one value of
this multi-valued attribute. this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.31 NAME 'member' ( 2.5.4.31 NAME 'member'
SUP distinguishedName ) SUP distinguishedName )
Examples: "cn=James Clarke,ou=Finance,o=Widget\, Inc." and Examples: "cn=James Clarke,ou=Finance,o=Widget\, Inc." and
"cn=John Xerri,ou=Finance,o=Widget\, Inc" may "cn=John Xerri,ou=Finance,o=Widget\, Inc." may
be two members of the financial team (group) at Widget, be two members of the financial team (group) at Widget,
Inc. In which case, both of these distinguished names would Inc. In which case, both of these distinguished names would
be present as individual values of the member attribute. be present as individual values of the member attribute.
2.18 'name' 2.18 'name'
The 'name' attribute type is the attribute supertype from which user The 'name' attribute type is the attribute supertype from which user
attribute types with the name syntax inherit. Such attribute types attribute types with the name syntax inherit. Such attribute types
are typically used for naming. The attribute type is multi-valued. are typically used for naming. The attribute type is multi-valued.
skipping to change at page 13, line 44 skipping to change at page 13, line 44
owned. Each owner's name is one value of this multi-valued owned. Each owner's name is one value of this multi-valued
attribute. attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.32 NAME 'owner' ( 2.5.4.32 NAME 'owner'
SUP distinguishedName ) SUP distinguishedName )
Example: The mailing list object, whose DN is "cn=All Employees, Example: The mailing list object, whose DN is "cn=All Employees,
ou=Mailing List,o=Widget\, Inc.", is owned by the Human ou=Mailing List,o=Widget\, Inc.", is owned by the Human
Resources Director. Resources Director.
Therefore, the value of the owner attribute within the Therefore, the value of the 'owner' attribute within the
mailing list object, would be the DN of the director (role): mailing list object, would be the DN of the director (role):
"cn=Human Resources Director,ou=employee,o=Widget\, Inc.". "cn=Human Resources Director,ou=employee,o=Widget\, Inc.".
2.22 'physicalDeliveryOfficeName' 2.22 'physicalDeliveryOfficeName'
The 'physicalDeliveryOfficeName' attribute type contains names that a The 'physicalDeliveryOfficeName' attribute type contains names that a
Postal Service uses to identify a post office. Postal Service uses to identify a post office.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.19 NAME 'physicalDeliveryOfficeName' ( 2.5.4.19 NAME 'physicalDeliveryOfficeName'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
skipping to change at page 15, line 33 skipping to change at page 15, line 33
( 2.5.4.28 NAME 'preferredDeliveryMethod' ( 2.5.4.28 NAME 'preferredDeliveryMethod'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.14 SYNTAX 1.3.6.1.4.1.1466.115.121.1.14
SINGLE-VALUE ) SINGLE-VALUE )
1.3.6.1.4.1.1466.115.121.1.14 refers to the Delivery Method syntax 1.3.6.1.4.1.1466.115.121.1.14 refers to the Delivery Method syntax
[Syntaxes]. [Syntaxes].
Example: If the mhs-delivery Delivery Method is preferred over Example: If the mhs-delivery Delivery Method is preferred over
telephone-delivery, which is preferred over all other telephone-delivery, which is preferred over all other
methods, the value would be: "mhs $ telephone" methods, the value would be: "mhs $ telephone".
2.27 'registeredAddress' 2.27 'registeredAddress'
The 'registeredAddress' attribute type contains postal addresses The 'registeredAddress' attribute type contains postal addresses
suitable for reception of telegrams or expedited documents, where it suitable for reception of telegrams or expedited documents, where it
is necessary to have the recipient accept delivery. Each address is is necessary to have the recipient accept delivery. Each address is
one value of this multi-valued attribute. one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.26 NAME 'registeredAddress' ( 2.5.4.26 NAME 'registeredAddress'
skipping to change at page 16, line 37 skipping to change at page 16, line 37
by clients in constructing search filters. It is superseded by by clients in constructing search filters. It is superseded by
'enhancedSearchGuide', described above in section 2.9. Each set is 'enhancedSearchGuide', described above in section 2.9. Each set is
one value of this multi-valued attribute. one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.14 NAME 'searchGuide' ( 2.5.4.14 NAME 'searchGuide'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.25 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.25 )
1.3.6.1.4.1.1466.115.121.1.25 refers to the Guide syntax [Syntaxes]. 1.3.6.1.4.1.1466.115.121.1.25 refers to the Guide syntax [Syntaxes].
Example: "person#sn$EQ" Example: "person#sn$EQ".
2.30 'seeAlso' 2.30 'seeAlso'
The 'seeAlso' attribute type contains Distinguished Names of objects The 'seeAlso' attribute type contains Distinguished Names of objects
that are related to the subject object. Each related object name is that are related to the subject object. Each related object name is
one value of this multi-valued attribute. one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.34 NAME 'seeAlso' ( 2.5.4.34 NAME 'seeAlso'
SUP distinguishedName ) SUP distinguishedName )
Example: The person object, "cn=James Brown,ou=employee,o=Widget\, Example: The person object, "cn=James Brown,ou=employee,o=Widget\,
Inc." is related to the role objects, "cn=Football Team Inc." is related to the role objects, "cn=Football Team
Captain,ou=sponsored activities,o=Widget\, Inc." and Captain,ou=sponsored activities,o=Widget\, Inc." and
"cn=Chess Team,ou=sponsored activities,o=Widget\, Inc.". "cn=Chess Team,ou=sponsored activities,o=Widget\, Inc.".
Since the role objects are related to the person object, the Since the role objects are related to the person object, the
'seeAlso' attribute will contain the distinguished name of 'seeAlso' attribute will contain the distinguished name of
each role object as separate values. each role object as separate values.
2.31 'serialNumber' 2.31 'serialNumber'
The 'serialNumber' attribute type contains the serial numbers of The 'serialNumber' attribute type contains the serial numbers of
devices. Each serial number is one value of this multi-valued devices. Each serial number is one value of this multi-valued
attribute. attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
skipping to change at page 17, line 36 skipping to change at page 17, line 36
2.32 'sn' 2.32 'sn'
The 'sn' ('surname' in X.500) attribute type contains name strings The 'sn' ('surname' in X.500) attribute type contains name strings
for the family names of a person. Each string is one value of this for the family names of a person. Each string is one value of this
multi-valued attribute. multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.4 NAME 'sn' ( 2.5.4.4 NAME 'sn'
SUP name ) SUP name )
Example: "Smith" Example: "Smith".
2.33 'st' 2.33 'st'
The 'st' ('stateOrProvinceName' in X.500) attribute type contains the The 'st' ('stateOrProvinceName' in X.500) attribute type contains the
full names of states or provinces. Each name is one value of this full names of states or provinces. Each name is one value of this
multi-valued attribute. multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.8 NAME 'st' ( 2.5.4.8 NAME 'st'
SUP name ) SUP name )
skipping to change at page 18, line 21 skipping to change at page 18, line 21
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.9 NAME 'street' ( 2.5.4.9 NAME 'street'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax
[Syntaxes]. [Syntaxes].
Example: "15 Main St." Example: "15 Main St.".
2.35 'telephoneNumber' 2.35 'telephoneNumber'
The 'telephoneNumber' attribute type contains telephone numbers that The 'telephoneNumber' attribute type contains telephone numbers that
comply with the ITU Recommendation E.123 [E.123]. Each number is one comply with the ITU Recommendation E.123 [E.123]. Each number is one
value of this multi-valued attribute. value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.20 NAME 'telephoneNumber' ( 2.5.4.20 NAME 'telephoneNumber'
EQUALITY telephoneNumberMatch EQUALITY telephoneNumberMatch
skipping to change at page 19, line 18 skipping to change at page 19, line 18
telex number, country code, and answerback code of a telex terminal. telex number, country code, and answerback code of a telex terminal.
Each set is one value of this multi-valued attribute. Each set is one value of this multi-valued attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.21 NAME 'telexNumber' ( 2.5.4.21 NAME 'telexNumber'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.52 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.52 )
1.3.6.1.4.1.1466.115.121.1.52 refers to the Telex Number syntax 1.3.6.1.4.1.1466.115.121.1.52 refers to the Telex Number syntax
[Syntaxes]. [Syntaxes].
Example: "12345$023$ABCDE" Example: "12345$023$ABCDE".
2.38 'title' 2.38 'title'
The 'title' attribute type contains the title of a person in their The 'title' attribute type contains the title of a person in their
organizational context. Each title is one value of this multi-valued organizational context. Each title is one value of this multi-valued
attribute. attribute.
(Source: X.520 [X.520]) (Source: X.520 [X.520])
( 2.5.4.12 NAME 'title' ( 2.5.4.12 NAME 'title'
SUP name ) SUP name )
skipping to change at page 20, line 29 skipping to change at page 20, line 27
would have a unique identifier value added, resulting in would have a unique identifier value added, resulting in
"ou=1st Battalion, o=Defense,c=US#'010101'B". "ou=1st Battalion, o=Defense,c=US#'010101'B".
2.41 'userPassword' 2.41 'userPassword'
The 'userPassword' attribute contains octet strings that are known The 'userPassword' attribute contains octet strings that are known
only to the user and the system to which the user has access. Each only to the user and the system to which the user has access. Each
string is one value of this multi-valued attribute. string is one value of this multi-valued attribute.
The application SHOULD prepare textual strings used as passwords by The application SHOULD prepare textual strings used as passwords by
transcoding them to Unicode, applying SASLprep [SASLprep], and transcoding them to Unicode, applying SASLprep [RFC4013], and
encoding as UTF-8. The determination of whether a password is encoding as UTF-8. The determination of whether a password is
textual is a local client matter. textual is a local client matter.
(Source: X.509 [X.509]) (Source: X.509 [X.509])
( 2.5.4.35 NAME 'userPassword' ( 2.5.4.35 NAME 'userPassword'
EQUALITY octetStringMatch EQUALITY octetStringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 )
1.3.6.1.4.1.1466.115.121.1.40 refers to the Octet String syntax 1.3.6.1.4.1.1466.115.121.1.40 refers to the Octet String syntax
[Syntaxes]. [Syntaxes].
skipping to change at page 29, line 12 skipping to change at page 29, line 10
Attributes of directory entries are used to provide descriptive Attributes of directory entries are used to provide descriptive
information about the real-world objects they represent, which can be information about the real-world objects they represent, which can be
people, organizations or devices. Most countries have privacy laws people, organizations or devices. Most countries have privacy laws
regarding the publication of information about people. regarding the publication of information about people.
Transfer of cleartext passwords is strongly discouraged where the Transfer of cleartext passwords is strongly discouraged where the
underlying transport service cannot guarantee confidentiality and may underlying transport service cannot guarantee confidentiality and may
result in disclosure of the password to unauthorized parties. result in disclosure of the password to unauthorized parties.
Multiple attribute values for the 'userPassword' needs to be used Multiple attribute values for the 'userPassword' attribute need to be
with care. Especially reset/deletion of a password by an admin used with care. Especially reset/deletion of a password by an admin
without knowing the old user password gets tricky or impossible if without knowing the old user password gets tricky or impossible if
multiple values for different applications are present. multiple values for different applications are present.
Certainly, applications which intend to replace the 'userPassword' Certainly, applications which intend to replace the 'userPassword'
value(s) with new value(s) should use modify/replaceValues (or value(s) with new value(s) should use modify/replaceValues (or
modify/deleteAttribute+addAttribute). Additionally, server modify/deleteAttribute+addAttribute). Additionally, server
implementations are encouraged to provide administrative controls implementations are encouraged to provide administrative controls
which, if enabled, restrict the 'userPassword' attributer to one which, if enabled, restrict the 'userPassword' attribute to one
value. value.
Note that when used for authentication purposes [AuthMeth], the user Note that when used for authentication purposes [AuthMeth], the user
need only prove knowledge of one of the values, not all of the need only prove knowledge of one of the values, not all of the
values. values.
6. Acknowledgements 6. Acknowledgements
The definitions, on which this document is based, have been developed The definitions, on which this document is based, have been developed
by committees for telecommunications and international standards. by committees for telecommunications and international standards.
skipping to change at page 29, line 46 skipping to change at page 29, line 44
The 'dc' attribute type definition and the 'dcObject' object class The 'dc' attribute type definition and the 'dcObject' object class
definition in this document supersede the specification in RFC 2247 definition in this document supersede the specification in RFC 2247
by S. Kille, M. Wahl, A. Grimstad, R. Huber, and S. Sataluri. by S. Kille, M. Wahl, A. Grimstad, R. Huber, and S. Sataluri.
The 'uid' attribute type definition in this document supersedes the The 'uid' attribute type definition in this document supersedes the
specification of the 'userid' in RFC 1274 by P. Barker and S. Kille specification of the 'userid' in RFC 1274 by P. Barker and S. Kille
and of the uid in RFC 2798 by M. Smith. and of the uid in RFC 2798 by M. Smith.
The 'uidObject' object class definition in this document supersedes The 'uidObject' object class definition in this document supersedes
the specification of the 'uidObject' in RFC 2377 by A. Grimstad, R. the specification of the 'uidObject' in RFC 2377 by A. Grimstad, R.
Huber, S, Sataluri and M. Smith. Huber, S. Sataluri and M. Smith.
This document is based upon input of the IETF LDAPBIS working group. This document is based upon input of the IETF LDAPBIS working group.
The author wishes to thank S. Legg and K. Zeilenga for their The author wishes to thank S. Legg and K. Zeilenga for their
significant contribution to this update. The author would also like significant contribution to this update. The author would also like
to thank Kathy Dally who edited early drafts of this document. to thank Kathy Dally who edited early drafts of this document.
7. References 7. References
7.1 Normative 7.1 Normative
skipping to change at page 30, line 41 skipping to change at page 30, line 41
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997 Requirement Levels", RFC 2119, March 1997
[RFC2234] Crocker, D., Overell P., "Augmented BNF for Syntax [RFC2234] Crocker, D., Overell P., "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997 Specifications: ABNF", RFC 2234, November 1997
[RFC3490] Faltstrom P., Hoffman P., Costello A., [RFC3490] Faltstrom P., Hoffman P., Costello A.,
"Internationalizing Domain Names in Applications "Internationalizing Domain Names in Applications
(IDNA)", RFC 3490, March 2003 (IDNA)", RFC 3490, March 2003
[RFC4013] Zeilenga K., "SASLprep: Stringprep profile for User
Names and Passwords", RFC 4013, February 2005.
[Roadmap] Zeilenga, K., "LDAP: Technical Specification Road [Roadmap] Zeilenga, K., "LDAP: Technical Specification Road
Map", draft-ietf-ldapbis-roadmap-xx (a work in Map", draft-ietf-ldapbis-roadmap-xx (a work in
progress) progress)
[SASLprep] Zeilenga K., "SASLprep: Stringprep profile for user
names and passwords", draft-ietf-sasl-saslprep-xx (a
work in progress)
[Syntaxes] S. Legg (editor), "LDAP: Syntaxes", draft-ietf-ldapbis- [Syntaxes] S. Legg (editor), "LDAP: Syntaxes", draft-ietf-ldapbis-
syntaxes-xx (a work in progress) syntaxes-xx (a work in progress)
[X.121] International numbering plan for public data networks, [X.121] International numbering plan for public data networks,
ITU-T Recommendation X.121, 1996 ITU-T Recommendation X.121, 1996
[X.509] The Directory: Authentication Framework, ITU-T [X.509] The Directory: Authentication Framework, ITU-T
Recommendation X.509, 1993 Recommendation X.509, 1993
[X.520] The Directory: Selected Attribute Types, ITU-T [X.520] The Directory: Selected Attribute Types, ITU-T
Recommendation X.520, 1993 Recommendation X.520, 1993
[X.521] The Directory: Selected Object Classes. ITU-T [X.521] The Directory: Selected Object Classes. ITU-T
Recommendation X.521, 1993 Recommendation X.521, 1993
7.2 Informative 7.2 Informative
skipping to change at page 31, line 39 skipping to change at page 31, line 37
Sataluri, S., "Using Domains in LDAP/X.500 Sataluri, S., "Using Domains in LDAP/X.500
Distinguished Names", RFC 2247, January 1998 Distinguished Names", RFC 2247, January 1998
[RFC2377] Grimstad, A., Huber, R., Sataluri, S., and Wahl, M., [RFC2377] Grimstad, A., Huber, R., Sataluri, S., and Wahl, M.,
"Naming Plan for Internet-Enabled Applications", RFC "Naming Plan for Internet-Enabled Applications", RFC
2377, September 1998. 2377, September 1998.
[RFC2798] Smith, M., "Definition of the inetOrgPerson LDAP Object [RFC2798] Smith, M., "Definition of the inetOrgPerson LDAP Object
Class", RFC 2798, April 2000 Class", RFC 2798, April 2000
[X.500] The Directory, ITU-T Recommendations X.501-X.525, 1993 [X.500] ITU-T Recommendations X.5000 (1993) | ISO/IEC
9594-1:1994, Information Technology - Open Systems
Interconnection - The Directory: Overview of concepts,
models and services.
8. Author's Address 8. Author's Address
Andrew Sciberras Andrew Sciberras
eB2Bcom eB2Bcom
Suite 3, Woodhouse Corporate Centre, Suite 3, Woodhouse Corporate Centre,
935 Station Street, 935 Station Street,
Box Hill North, Victoria 3129 Box Hill North, Victoria 3129
AUSTRALIA AUSTRALIA
skipping to change at page 32, line 29 skipping to change at page 32, line 30
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
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.
10. Disclaimer of Validity 10. Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and 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.
Copyright Statement Copyright (C) The Internet Society (2005). This
document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Appendix A Changes Made Since RFC 2256 Appendix A Changes Made Since RFC 2256
This appendix lists the changes that have been made from RFC 2256 to This appendix lists the changes that have been made from RFC 2256 to
this I-D. this I-D.
This appendix is not a normative part of this specification, which This appendix is not a normative part of this specification, which
has been provided for informational purposes only. has been provided for informational purposes only.
1. Replaced the document title. 1. Replaced the document title.
 End of changes. 

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