draft-ietf-asid-ldapv3-attributes-07.txt   rfc2252.txt 
Network Working Group M. Wahl Network Working Group M. Wahl
INTERNET-DRAFT Critical Angle Inc. Request for Comments: 2252 Critical Angle Inc.
Obsoletes: RFC 1778 A. Coulbeck Category: Standards Track A. Coulbeck
Isode Inc. Isode Inc.
T. Howes T. Howes
Netscape Communications Corp. Netscape Communications Corp.
S. Kille S. Kille
Isode Limited Isode Limited
Intended Category: Standards Track 5 August 1997 December 1997
Lightweight Directory Access Protocol (v3): Lightweight Directory Access Protocol (v3):
Attribute Syntax Definitions Attribute Syntax Definitions
<draft-ietf-asid-ldapv3-attributes-07.txt>
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its areas, and Internet community, and requests discussion and suggestions for
its working groups. Note that other groups may also distribute working improvements. Please refer to the current edition of the "Internet
documents as Internet-Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months Copyright Notice
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress."
To learn the current status of any Internet-Draft, please check the Copyright (C) The Internet Society (1997). All Rights Reserved.
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), IESG Note
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
This document describes a directory access protocol that provides
both read and update access. Update access requires secure
authentication, but this document does not mandate implementation of
any satisfactory authentication mechanisms.
In accordance with RFC 2026, section 4.4.1, this specification is
being approved by IESG as a Proposed Standard despite this
limitation, for the following reasons:
a. to encourage implementation and interoperability testing of
these protocols (with or without update access) before they
are deployed, and
b. to encourage deployment and use of these protocols in read-only
applications. (e.g. applications where LDAPv3 is used as
a query language for directories which are updated by some
secure mechanism other than LDAP), and
c. to avoid delaying the advancement and deployment of other Internet
standards-track protocols which require the ability to query, but
not update, LDAPv3 directory servers.
Readers are hereby warned that until mandatory authentication
mechanisms are standardized, clients and servers written according to
this specification which make use of update functionality are
UNLIKELY TO INTEROPERATE, or MAY INTEROPERATE ONLY IF AUTHENTICATION
IS REDUCED TO AN UNACCEPTABLY WEAK LEVEL.
Implementors are hereby discouraged from deploying LDAPv3 clients or
servers which implement the update functionality, until a Proposed
Standard for mandatory authentication in LDAPv3 has been approved and
published as an RFC.
2. Abstract 2. Abstract
The Lightweight Directory Access Protocol (LDAP) [1] requires that The Lightweight Directory Access Protocol (LDAP) [1] requires that
the contents of AttributeValue fields in protocol elements be octet the contents of AttributeValue fields in protocol elements be octet
strings. This document defines a set of syntaxes for LDAPv3, and the strings. This document defines a set of syntaxes for LDAPv3, and the
rules by which attribute values of these syntaxes are represented as rules by which attribute values of these syntaxes are represented as
octet strings for transmission in the LDAP protocol. The syntaxes octet strings for transmission in the LDAP protocol. The syntaxes
defined in this document are referenced by this and other documents defined in this document are referenced by this and other documents
that define attribute types. This document also defines the set of that define attribute types. This document also defines the set of
skipping to change at page 2, line 16 skipping to change at page 3, line 10
classes. classes.
Additional documents define schemas for representing real-world Additional documents define schemas for representing real-world
objects as directory entries. objects as directory entries.
4. General Issues 4. General Issues
This document describes encodings used in an Internet protocol. This document describes encodings used in an Internet protocol.
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 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
this document are to be interpreted as described in RFC 2119 [4]. document are to be interpreted as described in RFC 2119 [4].
Attribute Type and Object Class definitions are written in a Attribute Type and Object Class definitions are written in a string
string representation of the AttributeTypeDescription and representation of the AttributeTypeDescription and
ObjectClassDescription data types defined in X.501(93) [3]. ObjectClassDescription data types defined in X.501(93) [3].
Implementors are strongly advised to first read the description Implementors are strongly advised to first read the description of
of how schema is represented in X.500 before reading the rest of how schema is represented in X.500 before reading the rest of this
this document. document.
4.1. Common Encoding Aspects 4.1. Common Encoding Aspects
For the purposes of defining the encoding rules for attribute For the purposes of defining the encoding rules for attribute
syntaxes, the following BNF definitions will be used. They are syntaxes, the following BNF definitions will be used. They are based
based on the BNF styles of RFC 822 [13]. on the BNF styles of RFC 822 [13].
a = "a" / "b" / "c" / "d" / "e" / "f" / "g" / "h" / "i" / a = "a" / "b" / "c" / "d" / "e" / "f" / "g" / "h" / "i" /
"j" / "k" / "l" / "m" / "n" / "o" / "p" / "q" / "r" / "j" / "k" / "l" / "m" / "n" / "o" / "p" / "q" / "r" /
"s" / "t" / "u" / "v" / "w" / "x" / "y" / "z" / "A" / "s" / "t" / "u" / "v" / "w" / "x" / "y" / "z" / "A" /
"B" / "C" / "D" / "E" / "F" / "G" / "H" / "I" / "J" / "B" / "C" / "D" / "E" / "F" / "G" / "H" / "I" / "J" /
"K" / "L" / "M" / "N" / "O" / "P" / "Q" / "R" / "S" / "K" / "L" / "M" / "N" / "O" / "P" / "Q" / "R" / "S" /
"T" / "U" / "V" / "W" / "X" / "Y" / "Z" "T" / "U" / "V" / "W" / "X" / "Y" / "Z"
d = "0" / "1" / "2" / "3" / "4" / d = "0" / "1" / "2" / "3" / "4" /
"5" / "6" / "7" / "8" / "9" "5" / "6" / "7" / "8" / "9"
hex-digit = d / "a" / "b" / "c" / "d" / "e" / "f" / hex-digit = d / "a" / "b" / "c" / "d" / "e" / "f" /
"A" / "B" / "C" / "D" / "E" / "F" "A" / "B" / "C" / "D" / "E" / "F"
k = a / d / "-" k = a / d / "-" / ";"
p = a / d / """ / "(" / ")" / "+" / "," / p = a / d / """ / "(" / ")" / "+" / "," /
"-" / "." / "/" / ":" / "?" / " " "-" / "." / "/" / ":" / "?" / " "
letterstring = 1*a letterstring = 1*a
numericstring = 1*d numericstring = 1*d
anhstring = 1*k anhstring = 1*k
keystring = a [ anhstring ] keystring = a [ anhstring ]
printablestring = 1*p printablestring = 1*p
space = 1*" " space = 1*" "
whsp = [ space ] whsp = [ space ]
utf8 = <any sequence of octets formed from the UTF-8 [9] utf8 = <any sequence of octets formed from the UTF-8 [9]
transformation of a character from ISO10646 [10]> transformation of a character from ISO10646 [10]>
dstring = 1*utf8 dstring = 1*utf8
qdstring = whsp "'" dstring "'" whsp qdstring = whsp "'" dstring "'" whsp
qdstringlist = [ qdstring *( qdstring ) ] qdstringlist = [ qdstring *( qdstring ) ]
qdstrings = qdstring / ( whsp "(" qdstringlist ")" whsp ) qdstrings = qdstring / ( whsp "(" qdstringlist ")" whsp )
In the following BNF for the string representation of OBJECT In the following BNF for the string representation of OBJECT
IDENTIFIERs, descr is the syntactic representation of an object IDENTIFIERs, descr is the syntactic representation of an object
descriptor, which consists of letters and digits, starting with a descriptor, which consists of letters and digits, starting with a
letter. An OBJECT IDENTIFIER in the numericoid format should not letter. An OBJECT IDENTIFIER in the numericoid format should not
have leading zeroes (e.g. "0.9.3" is permitted but "0.09.3" should have leading zeroes (e.g. "0.9.3" is permitted but "0.09.3" should
not be generated). not be generated).
When encoding 'oid' elements in a value, the descr encoding option When encoding 'oid' elements in a value, the descr encoding option
SHOULD be used in preference to the numericoid. An object descriptor is SHOULD be used in preference to the numericoid. An object descriptor
a more readable alias for a number OBJECT IDENTIFIER, and these is a more readable alias for a number OBJECT IDENTIFIER, and these
(where assigned and known by the implementation) SHOULD be used in (where assigned and known by the implementation) SHOULD be used in
preference to numeric oids to the greatest extent possible. preference to numeric oids to the greatest extent possible. Examples
Examples of object descriptors in LDAP are attribute type, object of object descriptors in LDAP are attribute type, object class and
class and matching rule names. matching rule names.
oid = descr / numericoid oid = descr / numericoid
descr = keystring descr = keystring
numericoid = numericstring *( "." numericstring ) numericoid = numericstring *( "." numericstring )
woid = whsp oid whsp woid = whsp oid whsp
; set of oids of either form ; set of oids of either form
skipping to change at page 4, line 14 skipping to change at page 5, line 15
4.2. Attribute Types 4.2. Attribute Types
The attribute types are described by sample values for the subschema The attribute types are described by sample values for the subschema
"attributeTypes" attribute, which is written in the "attributeTypes" attribute, which is written in the
AttributeTypeDescription syntax. While lines have been folded for AttributeTypeDescription syntax. While lines have been folded for
readability, the values transferred in protocol would not contain readability, the values transferred in protocol would not contain
newlines. newlines.
The AttributeTypeDescription is encoded according to the following The AttributeTypeDescription is encoded according to the following
BNF, and the productions for oid, qdescrs and qdstring are given BNF, and the productions for oid, qdescrs and qdstring are given in
in section 4.1. Implementors should note that future versions of section 4.1. Implementors should note that future versions of this
this document may have expanded this BNF to include additional terms. document may have expanded this BNF to include additional terms.
Terms which begin with the characters "X-" are reserved for private Terms which begin with the characters "X-" are reserved for private
experiments. experiments, and MUST be followed by a <qdstrings>.
AttributeTypeDescription = "(" whsp AttributeTypeDescription = "(" whsp
numericoid whsp ; AttributeType identifier numericoid whsp ; AttributeType identifier
[ "NAME" qdescrs ] ; name used in AttributeType [ "NAME" qdescrs ] ; name used in AttributeType
[ "DESC" qdstring ] ; description [ "DESC" qdstring ] ; description
[ "OBSOLETE" whsp ] [ "OBSOLETE" whsp ]
[ "SUP" woid ] ; derived from this other [ "SUP" woid ] ; derived from this other
; AttributeType ; AttributeType
[ "EQUALITY" woid ; Matching Rule name [ "EQUALITY" woid ; Matching Rule name
[ "ORDERING" woid ; Matching Rule name [ "ORDERING" woid ; Matching Rule name
skipping to change at page 4, line 43 skipping to change at page 5, line 44
[ "NO-USER-MODIFICATION" whsp ]; default user modifiable [ "NO-USER-MODIFICATION" whsp ]; default user modifiable
[ "USAGE" whsp AttributeUsage ]; default userApplications [ "USAGE" whsp AttributeUsage ]; default userApplications
whsp ")" whsp ")"
AttributeUsage = AttributeUsage =
"userApplications" / "userApplications" /
"directoryOperation" / "directoryOperation" /
"distributedOperation" / ; DSA-shared "distributedOperation" / ; DSA-shared
"dSAOperation" ; DSA-specific, value depends on server "dSAOperation" ; DSA-specific, value depends on server
Servers are not required to provide the same or any text Servers are not required to provide the same or any text in the
in the description part of the subschema values they maintain. description part of the subschema values they maintain. Servers
Servers SHOULD provide at least one of the "SUP" and "SYNTAX" fields SHOULD provide at least one of the "SUP" and "SYNTAX" fields for each
for each AttributeTypeDescription. AttributeTypeDescription.
Servers MUST implement all the attribute types referenced in Servers MUST implement all the attribute types referenced in sections
sections 5.1, 5.2 and 5.3. 5.1, 5.2 and 5.3.
Servers MAY recognize additional names and attributes not listed in Servers MAY recognize additional names and attributes not listed in
this document, and if they do so, MUST publish the definitions of this document, and if they do so, MUST publish the definitions of the
the types in the attributeTypes attribute of their subschema types in the attributeTypes attribute of their subschema entries.
entries.
Schema developers MUST NOT create attribute definitions whose names Schema developers MUST NOT create attribute definitions whose names
conflict with attributes defined for use with LDAP in existing conflict with attributes defined for use with LDAP in existing
standards-track RFCs. standards-track RFCs.
An AttributeDescription can be used as the value in a NAME part of an An AttributeDescription can be used as the value in a NAME part of an
AttributeTypeDescription. Note that these are case insensitive. AttributeTypeDescription. Note that these are case insensitive.
Note that the AttributeTypeDescription does not list the matching Note that the AttributeTypeDescription does not list the matching
rules which can can be used with that attribute type in an rules which can can be used with that attribute type in an
extensibleMatch search filter. This is done using the matchingRuleUse extensibleMatch search filter. This is done using the
attribute described in section 4.5. matchingRuleUse attribute described in section 4.5.
This document refines the schema description of X.501 by requiring This document refines the schema description of X.501 by requiring
that the syntax field in an AttributeTypeDescription be a string that the syntax field in an AttributeTypeDescription be a string
representation of an OBJECT IDENTIFIER for the LDAP string syntax representation of an OBJECT IDENTIFIER for the LDAP string syntax
definition, and an optional indication of the maximum length of definition, and an optional indication of the maximum length of a
a value of this attribute. value of this attribute (defined in section 4.3.2).
4.3. Syntaxes 4.3. Syntaxes
This section defines general requirements for LDAP attribute value This section defines general requirements for LDAP attribute value
syntax encodings. All documents defining attribute syntax encodings syntax encodings. All documents defining attribute syntax encodings
for use with LDAP are expected to conform to these requirements. for use with LDAP are expected to conform to these requirements.
The encoding rules defined for a given attribute syntax must produce The encoding rules defined for a given attribute syntax must produce
octet strings. To the greatest extent possible, encoded octet octet strings. To the greatest extent possible, encoded octet
strings should be usable in their native encoded form for display strings should be usable in their native encoded form for display
purposes. In particular, encoding rules for attribute syntaxes purposes. In particular, encoding rules for attribute syntaxes
defining non-binary values should produce strings that can be defining non-binary values should produce strings that can be
displayed with little or no translation by clients implementing displayed with little or no translation by clients implementing LDAP.
LDAP. There are a few cases (e.g. audio) however, when it is not There are a few cases (e.g. audio) however, when it is not sensible
sensible to produce a printable representation, and clients MUST NOT to produce a printable representation, and clients MUST NOT assume
assume that an unrecognized syntax is a string representation. that an unrecognized syntax is a string representation.
In encodings where an arbitrary string, not a Distinguished Name, is In encodings where an arbitrary string, not a Distinguished Name, is
used as part of a larger production, and other than as part of a used as part of a larger production, and other than as part of a
Distinguished Name, a backslash quoting mechanism is used to escape Distinguished Name, a backslash quoting mechanism is used to escape
the following separator symbol character (such as "'", "$" or "#") if the following separator symbol character (such as "'", "$" or "#") if
it should occur in that string. The backslash is followed by a pair it should occur in that string. The backslash is followed by a pair
of hexadecimal digits representing the next character. A backslash of hexadecimal digits representing the next character. A backslash
itself in the string which forms part of a larger syntax is always itself in the string which forms part of a larger syntax is always
transmitted as '\5C' or '\5c'. An example is given in section 6.27. transmitted as '\5C' or '\5c'. An example is given in section 6.27.
Syntaxes are also defined for matching rules whose assertion value Syntaxes are also defined for matching rules whose assertion value
syntax is different from the attribute value syntax. syntax is different from the attribute value syntax.
4.3.1 Binary Transfer of Values 4.3.1 Binary Transfer of Values
This encoding format is used if the binary encoding is requested by This encoding format is used if the binary encoding is requested by
the client for an attribute, or if the attribute syntax name is the client for an attribute, or if the attribute syntax name is
"1.3.6.1.4.1.1466.115.121.1.5". The value, an instance of the ASN.1 "1.3.6.1.4.1.1466.115.121.1.5". The contents of the LDAP
AttributeValue type, is BER-encoded, and the result is used as the AttributeValue or AssertionValue field is a BER-encoded instance of
value: the first byte inside the OCTET STRING wrapper is a tag byte. the attribute value or a matching rule assertion value ASN.1 data
However the OCTET STRING is still encoded in primitive form.) type as defined for use with X.500. (The first byte inside the OCTET
STRING wrapper is a tag octet. However, the OCTET STRING is still
encoded in primitive form.)
All servers MUST implement this form for both generating attribute All servers MUST implement this form for both generating attribute
values in search responses, and parsing attribute values in add, values in search responses, and parsing attribute values in add,
compare and modify requests, if the attribute type is recognized and compare and modify requests, if the attribute type is recognized and
the attribute syntax name is that of Binary. Clients which request the attribute syntax name is that of Binary. Clients which request
that all attributes be returned from entries MUST be prepared that all attributes be returned from entries MUST be prepared to
to receive values in binary (e.g. userCertificate), and SHOULD NOT receive values in binary (e.g. userCertificate;binary), and SHOULD
simply display binary or unrecognized values to users. NOT simply display binary or unrecognized values to users.
4.3.2. Syntax Object Identifiers 4.3.2. Syntax Object Identifiers
Syntaxes for use with LDAP are named by OBJECT IDENTIFIERs, which Syntaxes for use with LDAP are named by OBJECT IDENTIFIERs, which are
are dotted-decimal strings. These are not intended to be displayed dotted-decimal strings. These are not intended to be displayed to
to users. users.
noidlen = numericoid [ "{" len "}" ] noidlen = numericoid [ "{" len "}" ]
len = numericstring len = numericstring
The following table lists some of the syntaxes that have been defined The following table lists some of the syntaxes that have been defined
for LDAP thus far. The H-R column suggests whether a value in that for LDAP thus far. The H-R column suggests whether a value in that
syntax would likely be a human readable string. Clients and servers syntax would likely be a human readable string. Clients and servers
need not implement all the syntaxes listed here, and MAY implement need not implement all the syntaxes listed here, and MAY implement
other syntaxes. other syntaxes.
skipping to change at page 7, line 12 skipping to change at page 8, line 36
DSE Type Y 1.3.6.1.4.1.1466.115.121.1.20 DSE Type Y 1.3.6.1.4.1.1466.115.121.1.20
Enhanced Guide Y 1.3.6.1.4.1.1466.115.121.1.21 Enhanced Guide Y 1.3.6.1.4.1.1466.115.121.1.21
Facsimile Telephone Number Y 1.3.6.1.4.1.1466.115.121.1.22 Facsimile Telephone Number Y 1.3.6.1.4.1.1466.115.121.1.22
Fax N 1.3.6.1.4.1.1466.115.121.1.23 Fax N 1.3.6.1.4.1.1466.115.121.1.23
Generalized Time Y 1.3.6.1.4.1.1466.115.121.1.24 Generalized Time Y 1.3.6.1.4.1.1466.115.121.1.24
Guide Y 1.3.6.1.4.1.1466.115.121.1.25 Guide Y 1.3.6.1.4.1.1466.115.121.1.25
IA5 String Y 1.3.6.1.4.1.1466.115.121.1.26 IA5 String Y 1.3.6.1.4.1.1466.115.121.1.26
INTEGER Y 1.3.6.1.4.1.1466.115.121.1.27 INTEGER Y 1.3.6.1.4.1.1466.115.121.1.27
JPEG N 1.3.6.1.4.1.1466.115.121.1.28 JPEG N 1.3.6.1.4.1.1466.115.121.1.28
LDAP Syntax Description Y 1.3.6.1.4.1.1466.115.121.1.54 LDAP Syntax Description Y 1.3.6.1.4.1.1466.115.121.1.54
LDAP Schema Definition Y 1.3.6.1.4.1.1466.115.121.1.56
LDAP Schema Description Y 1.3.6.1.4.1.1466.115.121.1.57
Master And Shadow Access Points Y 1.3.6.1.4.1.1466.115.121.1.29 Master And Shadow Access Points Y 1.3.6.1.4.1.1466.115.121.1.29
Matching Rule Description Y 1.3.6.1.4.1.1466.115.121.1.30 Matching Rule Description Y 1.3.6.1.4.1.1466.115.121.1.30
Matching Rule Use Description Y 1.3.6.1.4.1.1466.115.121.1.31 Matching Rule Use Description Y 1.3.6.1.4.1.1466.115.121.1.31
Mail Preference Y 1.3.6.1.4.1.1466.115.121.1.32 Mail Preference Y 1.3.6.1.4.1.1466.115.121.1.32
MHS OR Address Y 1.3.6.1.4.1.1466.115.121.1.33 MHS OR Address Y 1.3.6.1.4.1.1466.115.121.1.33
Modify Rights Y 1.3.6.1.4.1.1466.115.121.1.55 Modify Rights Y 1.3.6.1.4.1.1466.115.121.1.55
Name And Optional UID Y 1.3.6.1.4.1.1466.115.121.1.34 Name And Optional UID Y 1.3.6.1.4.1.1466.115.121.1.34
Name Form Description Y 1.3.6.1.4.1.1466.115.121.1.35 Name Form Description Y 1.3.6.1.4.1.1466.115.121.1.35
Numeric String Y 1.3.6.1.4.1.1466.115.121.1.36 Numeric String Y 1.3.6.1.4.1.1466.115.121.1.36
Object Class Description Y 1.3.6.1.4.1.1466.115.121.1.37 Object Class Description Y 1.3.6.1.4.1.1466.115.121.1.37
Octet String Y 1.3.6.1.4.1.1466.115.121.1.40 Octet String Y 1.3.6.1.4.1.1466.115.121.1.40
OID Y 1.3.6.1.4.1.1466.115.121.1.38 OID Y 1.3.6.1.4.1.1466.115.121.1.38
Other Mailbox Y 1.3.6.1.4.1.1466.115.121.1.39 Other Mailbox Y 1.3.6.1.4.1.1466.115.121.1.39
Postal Address Y 1.3.6.1.4.1.1466.115.121.1.41 Postal Address Y 1.3.6.1.4.1.1466.115.121.1.41
Protocol Information Y 1.3.6.1.4.1.1466.115.121.1.42 Protocol Information Y 1.3.6.1.4.1.1466.115.121.1.42
Presentation Address Y 1.3.6.1.4.1.1466.115.121.1.43 Presentation Address Y 1.3.6.1.4.1.1466.115.121.1.43
Printable String Y 1.3.6.1.4.1.1466.115.121.1.44 Printable String Y 1.3.6.1.4.1.1466.115.121.1.44
Substring Assertion Y 1.3.6.1.4.1.1466.115.121.1.58
Subtree Specification Y 1.3.6.1.4.1.1466.115.121.1.45 Subtree Specification Y 1.3.6.1.4.1.1466.115.121.1.45
Supplier Information Y 1.3.6.1.4.1.1466.115.121.1.46 Supplier Information Y 1.3.6.1.4.1.1466.115.121.1.46
Supplier Or Consumer Y 1.3.6.1.4.1.1466.115.121.1.47 Supplier Or Consumer Y 1.3.6.1.4.1.1466.115.121.1.47
Supplier And Consumer Y 1.3.6.1.4.1.1466.115.121.1.48 Supplier And Consumer Y 1.3.6.1.4.1.1466.115.121.1.48
Supported Algorithm N 1.3.6.1.4.1.1466.115.121.1.49 Supported Algorithm N 1.3.6.1.4.1.1466.115.121.1.49
Telephone Number Y 1.3.6.1.4.1.1466.115.121.1.50 Telephone Number Y 1.3.6.1.4.1.1466.115.121.1.50
Teletex Terminal Identifier Y 1.3.6.1.4.1.1466.115.121.1.51 Teletex Terminal Identifier Y 1.3.6.1.4.1.1466.115.121.1.51
Telex Number Y 1.3.6.1.4.1.1466.115.121.1.52 Telex Number Y 1.3.6.1.4.1.1466.115.121.1.52
UTC Time Y 1.3.6.1.4.1.1466.115.121.1.53 UTC Time Y 1.3.6.1.4.1.1466.115.121.1.53
A suggested minimum upper bound on the number of characters in value A suggested minimum upper bound on the number of characters in value
with a string-based syntax, or the number of bytes in a value for all with a string-based syntax, or the number of bytes in a value for all
other syntaxes, may be indicated by appending this bound count inside other syntaxes, may be indicated by appending this bound count inside
of curly braces following the syntax name's OBJECT IDENTIFIER in an of curly braces following the syntax name's OBJECT IDENTIFIER in an
Attribute Type Description. This bound is not part of the syntax name Attribute Type Description. This bound is not part of the syntax
itself. For instance, "1.3.6.4.1.1466.0{64}" suggests that server name itself. For instance, "1.3.6.4.1.1466.0{64}" suggests that
implementations should allow a string to be 64 characters long, server implementations should allow a string to be 64 characters
although they may allow longer strings. Note that a single character long, although they may allow longer strings. Note that a single
of the Directory String syntax may be encoded in more than one byte character of the Directory String syntax may be encoded in more than
since UTF-8 is a variable-length encoding. one byte since UTF-8 is a variable-length encoding.
4.3.3. Syntax Description 4.3.3. Syntax Description
The following BNF may be used to associate a short description with The following BNF may be used to associate a short description with a
a syntax OBJECT IDENTIFIER. Implementors should note that future syntax OBJECT IDENTIFIER. Implementors should note that future
versions of this document may expand this definition to include versions of this document may expand this definition to include
additional terms. Terms whose identifier begins with "X-" are additional terms. Terms whose identifier begins with "X-" are
reserved for private experiments. reserved for private experiments, and MUST be followed by a
<qdstrings>.
SyntaxDescription = "(" whsp SyntaxDescription = "(" whsp
numericoid whsp numericoid whsp
[ "DESC" qdstring ] [ "DESC" qdstring ]
whsp ")" whsp ")"
4.4. Object Classes 4.4. Object Classes
The format for representation of object classes is defined in X.501 The format for representation of object classes is defined in X.501
[3]. In general every entry will contain an abstract class ("top" or [3]. In general every entry will contain an abstract class ("top" or
"alias"), at least one structural object class, and zero or more "alias"), at least one structural object class, and zero or more
auxiliary object classes. Whether an object class is abstract, auxiliary object classes. Whether an object class is abstract,
structural or auxiliary is defined when the object class identifier structural or auxiliary is defined when the object class identifier
is assigned. An object class definition should not be changed is assigned. An object class definition should not be changed
without having a new identifier assigned to it. without having a new identifier assigned to it.
Object class descriptions are written according to the following BNF. Object class descriptions are written according to the following BNF.
Implementors should note that future versions of this document may Implementors should note that future versions of this document may
expand this definition to include additional terms. Terms whose expand this definition to include additional terms. Terms whose
identifier begins with "X-" are reserved for private experiments. identifier begins with "X-" are reserved for private experiments, and
MUST be followed by a <qdstrings> encoding.
ObjectClassDescription = "(" whsp ObjectClassDescription = "(" whsp
numericoid whsp ; ObjectClass identifier numericoid whsp ; ObjectClass identifier
[ "NAME" qdescrs ] [ "NAME" qdescrs ]
[ "DESC" qdstring ] [ "DESC" qdstring ]
[ "OBSOLETE" whsp ] [ "OBSOLETE" whsp ]
[ "SUP" oids ] ; Superior ObjectClasses [ "SUP" oids ] ; Superior ObjectClasses
[ ( "ABSTRACT" / "STRUCTURAL" / "AUXILIARY" ) whsp ] [ ( "ABSTRACT" / "STRUCTURAL" / "AUXILIARY" ) whsp ]
; default structural ; default structural
[ "MUST" oids ] ; AttributeTypes [ "MUST" oids ] ; AttributeTypes
[ "MAY" oids ] ; AttributeTypes [ "MAY" oids ] ; AttributeTypes
whsp ")" whsp ")"
These are described as sample values for the subschema These are described as sample values for the subschema
"objectClasses" attribute for a server which implements the LDAP "objectClasses" attribute for a server which implements the LDAP
schema. While lines have been folded for readability, the values schema. While lines have been folded for readability, the values
transferred in protocol would not contain newlines. transferred in protocol would not contain newlines.
Servers SHOULD implement all the object classes referenced in Servers SHOULD implement all the object classes referenced in section
section 7, except for extensibleObject, which is optional. 7, except for extensibleObject, which is optional. Servers MAY
implement additional object classes not listed in this document, and
Servers MAY implement additional object classes not listed in this if they do so, MUST publish the definitions of the classes in the
document, and if they do so, MUST publish the definitions of the objectClasses attribute of their subschema entries.
classes in the objectClasses attribute of their subschema entries.
Later documents may define additional object classes.
Schema developers MUST NOT create object class definitions whose Schema developers MUST NOT create object class definitions whose
names conflict with attributes defined for use with LDAP in existing names conflict with attributes defined for use with LDAP in existing
standards-track RFCs. standards-track RFCs.
4.5. Matching Rules 4.5. Matching Rules
Matching rules are used by servers to compare attribute values Matching rules are used by servers to compare attribute values
against assertion values when performing Search and Compare against assertion values when performing Search and Compare
operations. They are also used to identify the value to be added operations. They are also used to identify the value to be added or
or deleted when modifying entries, and are used when comparing a deleted when modifying entries, and are used when comparing a
purported distinguished name with the name of an entry. purported distinguished name with the name of an entry.
Most of the attributes given in this document will have an equality Most of the attributes given in this document will have an equality
matching rule defined. matching rule defined.
Matching rule descriptions are written according to the following Matching rule descriptions are written according to the following
BNF. Implementors should note that future versions of this document BNF. Implementors should note that future versions of this document
may have expanded this BNF to include additional terms. may have expanded this BNF to include additional terms. Terms whose
identifier begins with "X-" are reserved for private experiments, and
MUST be followed by a <qdstrings> encoding.
MatchingRuleDescription = "(" whsp MatchingRuleDescription = "(" whsp
numericoid whsp ; MatchingRule identifier numericoid whsp ; MatchingRule identifier
[ "NAME" qdescrs ] [ "NAME" qdescrs ]
[ "DESC" qdstring ] [ "DESC" qdstring ]
[ "OBSOLETE" whsp ] [ "OBSOLETE" whsp ]
"SYNTAX" numericoid "SYNTAX" numericoid
whsp ")" whsp ")"
Values of the matchingRuleUse list the attributes which are suitable Values of the matchingRuleUse list the attributes which are suitable
skipping to change at page 9, line 36 skipping to change at page 11, line 30
[ "DESC" qdstring ] [ "DESC" qdstring ]
[ "OBSOLETE" ] [ "OBSOLETE" ]
"APPLIES" oids ; AttributeType identifiers "APPLIES" oids ; AttributeType identifiers
whsp ")" whsp ")"
Servers which support matching rules and the extensibleMatch SHOULD Servers which support matching rules and the extensibleMatch SHOULD
implement all the matching rules in section 8. implement all the matching rules in section 8.
Servers MAY implement additional matching rules not listed in this Servers MAY implement additional matching rules not listed in this
document, and if they do so, MUST publish the definitions of the document, and if they do so, MUST publish the definitions of the
matching rules in the matchingRules attribute of their matching rules in the matchingRules attribute of their subschema
subschema entries. If the server supports the extensibleMatch, then entries. If the server supports the extensibleMatch, then the server
the server MUST publish the relationship between the matching rules MUST publish the relationship between the matching rules and
and attributes in the matchingRuleUse attribute. attributes in the matchingRuleUse attribute.
For example, a server which implements a privately-defined matching For example, a server which implements a privately-defined matching
rule for performing sound-alike matches on Directory String-valued rule for performing sound-alike matches on Directory String-valued
attributes would include the following in the subschema entry attributes would include the following in the subschema entry
(1.2.3.4.5 is an example, the OID of an actual matching rule would be (1.2.3.4.5 is an example, the OID of an actual matching rule would be
different): different):
matchingRule: ( 1.2.3.4.5 NAME 'soundAlikeMatch' matchingRule: ( 1.2.3.4.5 NAME 'soundAlikeMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
If this matching rule could be used with the attributes 2.5.4.41 and If this matching rule could be used with the attributes 2.5.4.41 and
2.5.4.15, the following would also be present: 2.5.4.15, the following would also be present:
matchingRuleUse: ( 1.2.3.4.5 APPLIES (2.5.4.41 $ 2.5.4.15) ) matchingRuleUse: ( 1.2.3.4.5 APPLIES (2.5.4.41 $ 2.5.4.15) )
A client could then make use of this matching rule by sending a A client could then make use of this matching rule by sending a
search operation in which the filter is of the extensibleMatch choice, search operation in which the filter is of the extensibleMatch
the matchingRule field is "soundAlikeMatch", and the type field is choice, the matchingRule field is "soundAlikeMatch", and the type
"2.5.4.41" or "2.5.4.15". field is "2.5.4.41" or "2.5.4.15".
5. Attribute Types 5. Attribute Types
All LDAP server implementations MUST recognize the attribute types All LDAP server implementations MUST recognize the attribute types
defined in this section. defined in this section.
Servers SHOULD also recognize all the attributes from section 5 of Servers SHOULD also recognize all the attributes from section 5 of
[12]. [12].
5.1. Standard Operational Attributes 5.1. Standard Operational Attributes
Servers MUST maintain values of these attributes in accordance with Servers MUST maintain values of these attributes in accordance with
the definitions in X.501(93). the definitions in X.501(93).
5.1.1. createTimestamp 5.1.1. createTimestamp
This attribute SHOULD appear in entries which were created using This attribute SHOULD appear in entries which were created using the
the Add operation. Add operation.
( 2.5.18.1 NAME 'createTimestamp' EQUALITY generalizedTimeMatch ( 2.5.18.1 NAME 'createTimestamp' EQUALITY generalizedTimeMatch
ORDERING generalizedTimeOrderingMatch ORDERING generalizedTimeOrderingMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.24' SYNTAX 1.3.6.1.4.1.1466.115.121.1.24
SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation ) SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
5.1.2. modifyTimestamp 5.1.2. modifyTimestamp
This attribute SHOULD appear in entries which have been modified This attribute SHOULD appear in entries which have been modified
using the Modify operation. using the Modify operation.
( 2.5.18.2 NAME 'modifyTimestamp' EQUALITY generalizedTimeMatch ( 2.5.18.2 NAME 'modifyTimestamp' EQUALITY generalizedTimeMatch
ORDERING generalizedTimeOrderingMatch ORDERING generalizedTimeOrderingMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.24' SYNTAX 1.3.6.1.4.1.1466.115.121.1.24
SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation ) SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
5.1.3. creatorsName 5.1.3. creatorsName
This attribute SHOULD appear in entries which were created using This attribute SHOULD appear in entries which were created using the
the Add operation. Add operation.
( 2.5.18.3 NAME 'creatorsName' EQUALITY distinguishedNameMatch ( 2.5.18.3 NAME 'creatorsName' EQUALITY distinguishedNameMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation ) SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
5.1.4. modifiersName 5.1.4. modifiersName
This attribute SHOULD appear in entries which have been modified This attribute SHOULD appear in entries which have been modified
using the Modify operation. using the Modify operation.
( 2.5.18.4 NAME 'modifiersName' EQUALITY distinguishedNameMatch ( 2.5.18.4 NAME 'modifiersName' EQUALITY distinguishedNameMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation ) SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
5.1.5. subschemaSubentry 5.1.5. subschemaSubentry
The value of this attribute is the name of a subschema entry (or The value of this attribute is the name of a subschema entry (or
subentry if the server is based on X.500(93)) in which the server subentry if the server is based on X.500(93)) in which the server
makes available attributes specifying the schema. makes available attributes specifying the schema.
( 2.5.18.10 NAME 'subschemaSubentry' ( 2.5.18.10 NAME 'subschemaSubentry'
EQUALITY distinguishedNameMatch EQUALITY distinguishedNameMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' NO-USER-MODIFICATION SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 NO-USER-MODIFICATION
SINGLE-VALUE USAGE directoryOperation ) SINGLE-VALUE USAGE directoryOperation )
5.1.6. attributeTypes 5.1.6. attributeTypes
This attribute is typically located in the subschema entry. This attribute is typically located in the subschema entry.
( 2.5.21.5 NAME 'attributeTypes' ( 2.5.21.5 NAME 'attributeTypes'
EQUALITY objectIdentifierFirstComponentMatch EQUALITY objectIdentifierFirstComponentMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.3' USAGE directoryOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.3 USAGE directoryOperation )
5.1.7. objectClasses 5.1.7. objectClasses
This attribute is typically located in the subschema entry. This attribute is typically located in the subschema entry.
( 2.5.21.6 NAME 'objectClasses' ( 2.5.21.6 NAME 'objectClasses'
EQUALITY objectIdentifierFirstComponentMatch EQUALITY objectIdentifierFirstComponentMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.37' USAGE directoryOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.37 USAGE directoryOperation )
5.1.8. matchingRules 5.1.8. matchingRules
This attribute is typically located in the subschema entry. This attribute is typically located in the subschema entry.
( 2.5.21.4 NAME 'matchingRules' ( 2.5.21.4 NAME 'matchingRules'
EQUALITY objectIdentifierFirstComponentMatch EQUALITY objectIdentifierFirstComponentMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.30' USAGE directoryOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.30 USAGE directoryOperation )
5.1.9. matchingRuleUse 5.1.9. matchingRuleUse
This attribute is typically located in the subschema entry. This attribute is typically located in the subschema entry.
( 2.5.21.8 NAME 'matchingRuleUse' ( 2.5.21.8 NAME 'matchingRuleUse'
EQUALITY objectIdentifierFirstComponentMatch EQUALITY objectIdentifierFirstComponentMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.31' USAGE directoryOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.31 USAGE directoryOperation )
5.2. LDAP Operational Attributes 5.2. LDAP Operational Attributes
These attributes are only present in the root DSE (see [1] and [3]). These attributes are only present in the root DSE (see [1] and [3]).
Servers MUST recognize these attribute names, but it is not required Servers MUST recognize these attribute names, but it is not required
that a server provide values for these attributes, when the that a server provide values for these attributes, when the attribute
attribute corresponds to a feature which the server does not corresponds to a feature which the server does not implement.
implement.
5.2.1. namingContexts 5.2.1. namingContexts
The values of this attribute correspond to naming contexts which this The values of this attribute correspond to naming contexts which this
server masters or shadows. If the server does not master any server masters or shadows. If the server does not master any
information (e.g. it is an LDAP gateway to a public X.500 directory) information (e.g. it is an LDAP gateway to a public X.500 directory)
this attribute will be absent. If the server believes it contains this attribute will be absent. If the server believes it contains
the entire directory, the attribute will have a single value, and the entire directory, the attribute will have a single value, and
that value will be the empty string (indicating the null DN of the that value will be the empty string (indicating the null DN of the
root). This attribute will allow a client to choose suitable base root). This attribute will allow a client to choose suitable base
objects for searching when it has contacted a server. objects for searching when it has contacted a server.
( 1.3.6.1.4.1.1466.101.120.5 NAME 'namingContexts' ( 1.3.6.1.4.1.1466.101.120.5 NAME 'namingContexts'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' USAGE dSAOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 USAGE dSAOperation )
5.2.2. altServer 5.2.2. altServer
The values of this attribute are URLs of other servers which may be The values of this attribute are URLs of other servers which may be
contacted when this server becomes unavailable. If the server does contacted when this server becomes unavailable. If the server does
not know of any other servers which could be used this attribute not know of any other servers which could be used this attribute will
will be absent. Clients may cache this information in case their be absent. Clients may cache this information in case their preferred
preferred LDAP server later becomes unavailable. LDAP server later becomes unavailable.
( 1.3.6.1.4.1.1466.101.120.6 NAME 'altServer' ( 1.3.6.1.4.1.1466.101.120.6 NAME 'altServer'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.26' USAGE dSAOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 USAGE dSAOperation )
5.2.3. supportedExtension 5.2.3. supportedExtension
The values of this attribute are OBJECT IDENTIFIERs identifying the The values of this attribute are OBJECT IDENTIFIERs identifying the
supported extended operations which the server supports. supported extended operations which the server supports.
If the server does not support any extensions this attribute will be If the server does not support any extensions this attribute will be
absent. absent.
( 1.3.6.1.4.1.1466.101.120.7 NAME 'supportedExtension' ( 1.3.6.1.4.1.1466.101.120.7 NAME 'supportedExtension'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.38' USAGE dSAOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 USAGE dSAOperation )
5.2.4. supportedControl 5.2.4. supportedControl
The values of this attribute are the OBJECT IDENTIFIERs identifying The values of this attribute are the OBJECT IDENTIFIERs identifying
controls which the server supports. If the server does not controls which the server supports. If the server does not support
support any controls, this attribute will be absent. any controls, this attribute will be absent.
( 1.3.6.1.4.1.1466.101.120.13 NAME 'supportedControl' ( 1.3.6.1.4.1.1466.101.120.13 NAME 'supportedControl'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.38' USAGE dSAOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 USAGE dSAOperation )
5.2.5. supportedSASLMechanisms 5.2.5. supportedSASLMechanisms
The values of this attribute are the names of supported SASL The values of this attribute are the names of supported SASL
mechanisms which the server supports. If the server does not mechanisms which the server supports. If the server does not support
support any mechanisms this attribute will be absent. any mechanisms this attribute will be absent.
( 1.3.6.1.4.1.1466.101.120.14 NAME 'supportedSASLMechanisms' ( 1.3.6.1.4.1.1466.101.120.14 NAME 'supportedSASLMechanisms'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' USAGE dSAOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 USAGE dSAOperation )
5.2.6. supportedLDAPVersion 5.2.6. supportedLDAPVersion
The values of this attribute are the versions of the LDAP protocol The values of this attribute are the versions of the LDAP protocol
which the server implements. which the server implements.
( 1.3.6.1.4.1.1466.101.120.15 NAME 'supportedLDAPVersion' ( 1.3.6.1.4.1.1466.101.120.15 NAME 'supportedLDAPVersion'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' USAGE dSAOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 USAGE dSAOperation )
5.3. LDAP Subschema Attribute 5.3. LDAP Subschema Attribute
This attribute is typically located in the subschema entry. This attribute is typically located in the subschema entry.
5.3.1. ldapSyntaxes 5.3.1. ldapSyntaxes
Servers MAY use this attribute to list the syntaxes which are Servers MAY use this attribute to list the syntaxes which are
implemented. Each value corresponds to one syntax. implemented. Each value corresponds to one syntax.
( 1.3.6.1.4.1.1466.101.120.16 NAME 'ldapSyntaxes' ( 1.3.6.1.4.1.1466.101.120.16 NAME 'ldapSyntaxes'
EQUALITY objectIdentifierFirstComponentMatch EQUALITY objectIdentifierFirstComponentMatch
SYNTAX '1.3.6.1.4.1.1466.115.121.1.54' USAGE directoryOperation ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.54 USAGE directoryOperation )
5.4. X.500 Subschema attributes
These attributes are located in the subschema entry. All servers
SHOULD recognize their name, although typically only X.500 servers
will implement their functionality.
5.4.1. dITStructureRules
( 2.5.21.1 NAME 'dITStructureRules' EQUALITY integerFirstComponentMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.17 USAGE directoryOperation )
5.4.2. nameForms
( 2.5.21.7 NAME 'nameForms'
EQUALITY objectIdentifierFirstComponentMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.35 USAGE directoryOperation )
5.4.3. ditContentRules
( 2.5.21.2 NAME 'dITContentRules'
EQUALITY objectIdentifierFirstComponentMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.16 USAGE directoryOperation )
6. Syntaxes 6. Syntaxes
Servers SHOULD recognize all the syntaxes described in this section. Servers SHOULD recognize all the syntaxes described in this section.
6.1. Attribute Type Description 6.1. Attribute Type Description
( 1.3.6.1.4.1.1466.115.121.1.3 DESC 'Attribute Type Description' ) ( 1.3.6.1.4.1.1466.115.121.1.3 DESC 'Attribute Type Description' )
Values in this syntax are encoded according to the BNF given at the Values in this syntax are encoded according to the BNF given at the
start of section 4.2. For example, start of section 4.2. For example,
( 2.5.4.0 NAME 'objectClass' ( 2.5.4.0 NAME 'objectClass'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.38' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
6.2. Binary 6.2. Binary
( 1.3.6.1.4.1.1466.115.121.1.5 DESC 'Binary' ) ( 1.3.6.1.4.1.1466.115.121.1.5 DESC 'Binary' )
Values in this syntax are encoded as described in section 4.3.1. Values in this syntax are encoded as described in section 4.3.1.
6.3. Bit String 6.3. Bit String
( 1.3.6.1.4.1.1466.115.121.1.6 DESC 'Bit String' ) ( 1.3.6.1.4.1.1466.115.121.1.6 DESC 'Bit String' )
skipping to change at page 14, line 26 skipping to change at page 17, line 26
Boolean values have an encoding of "TRUE" if they are logically true, Boolean values have an encoding of "TRUE" if they are logically true,
and have an encoding of "FALSE" otherwise. and have an encoding of "FALSE" otherwise.
6.5. Certificate 6.5. Certificate
( 1.3.6.1.4.1.1466.115.121.1.8 DESC 'Certificate' ) ( 1.3.6.1.4.1.1466.115.121.1.8 DESC 'Certificate' )
Because of the changes from X.509(1988) and X.509(1993) and Because of the changes from X.509(1988) and X.509(1993) and
additional changes to the ASN.1 definition to support certificate additional changes to the ASN.1 definition to support certificate
extensions, no string representation is defined, and values in extensions, no string representation is defined, and values in this
this syntax MUST only be transferred using the binary encoding, by syntax MUST only be transferred using the binary encoding, by
requesting or returning the attributes with descriptions requesting or returning the attributes with descriptions
"userCertificate;binary" or "caCertificate;binary". The BNF notation "userCertificate;binary" or "caCertificate;binary". The BNF notation
in RFC 1778 for "User Certificate" is not recommended to be used. in RFC 1778 for "User Certificate" is not recommended to be used.
6.6. Certificate List 6.6. Certificate List
( 1.3.6.1.4.1.1466.115.121.1.9 DESC 'Certificate List' ) ( 1.3.6.1.4.1.1466.115.121.1.9 DESC 'Certificate List' )
Because of the incompatibility of the X.509(1988) and X.509(1993) Because of the incompatibility of the X.509(1988) and X.509(1993)
definitions of revocation lists, values in this syntax MUST only be definitions of revocation lists, values in this syntax MUST only be
transferred using a binary encoding, by requesting or returning the transferred using a binary encoding, by requesting or returning the
attributes with descriptions "certificateRevocationList;binary" or attributes with descriptions "certificateRevocationList;binary" or
"authorityRevocationList;binary". The BNF notation in RFC 1778 for "authorityRevocationList;binary". The BNF notation in RFC 1778 for
"Authority Revocation List" is not recommended to be used. "Authority Revocation List" is not recommended to be used.
6.7. Certificate Pair 6.7. Certificate Pair
( 1.3.6.1.4.1.1466.115.121.1.10 DESC 'Certificate Pair' ) ( 1.3.6.1.4.1.1466.115.121.1.10 DESC 'Certificate Pair' )
Because the Certificate is being carried in binary, values in this Because the Certificate is being carried in binary, values in this
syntax MUST only be transferred using a binary encoding, by requesting syntax MUST only be transferred using a binary encoding, by
or returning the attribute description "crossCertificatePair;binary". requesting or returning the attribute description
The BNF notation in RFC 1778 for "Certificate Pair" is not "crossCertificatePair;binary". The BNF notation in RFC 1778 for
recommended to be used. "Certificate Pair" is not recommended to be used.
6.8. Country String 6.8. Country String
( 1.3.6.1.4.1.1466.115.121.1.11 DESC 'Country String' ) ( 1.3.6.1.4.1.1466.115.121.1.11 DESC 'Country String' )
A value in this syntax is encoded the same as a value of A value in this syntax is encoded the same as a value of Directory
Directory String syntax. Note that this syntax is limited to values String syntax. Note that this syntax is limited to values of exactly
of exactly two printable string characters, as listed in ISO 3166 [14]. two printable string characters, as listed in ISO 3166 [14].
CountryString = p p CountryString = p p
Example: Example:
US US
6.9. DN 6.9. DN
( 1.3.6.1.4.1.1466.115.121.1.12 DESC 'DN' ) ( 1.3.6.1.4.1.1466.115.121.1.12 DESC 'DN' )
skipping to change at page 15, line 32 skipping to change at page 18, line 40
OU=Sales+CN=J. Smith,O=Widget Inc.,C=US OU=Sales+CN=J. Smith,O=Widget Inc.,C=US
CN=L. Eagle,O=Sue\, Grabbit and Runn,C=GB CN=L. Eagle,O=Sue\, Grabbit and Runn,C=GB
CN=Before\0DAfter,O=Test,C=GB CN=Before\0DAfter,O=Test,C=GB
1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB 1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB
SN=Lu\C4\8Di\C4\87 SN=Lu\C4\8Di\C4\87
6.10. Directory String 6.10. Directory String
( 1.3.6.1.4.1.1466.115.121.1.15 DESC 'Directory String' ) ( 1.3.6.1.4.1.1466.115.121.1.15 DESC 'Directory String' )
A string in this syntax is encoded in the UTF-8 form of ISO 10646 A string in this syntax is encoded in the UTF-8 form of ISO 10646 (a
(a superset of Unicode). Servers and clients MUST be prepared to superset of Unicode). Servers and clients MUST be prepared to
receive encodings of arbitrary Unicode characters, including receive encodings of arbitrary Unicode characters, including
characters not presently assigned to any character set. characters not presently assigned to any character set.
For characters in the PrintableString form, the value is encoded as For characters in the PrintableString form, the value is encoded as
the string value itself. the string value itself.
If it is of the TeletexString form, then the characters are If it is of the TeletexString form, then the characters are
transliterated to their equivalents in UniversalString, and encoded transliterated to their equivalents in UniversalString, and encoded
in UTF-8 [9]. in UTF-8 [9].
If it is of the UniversalString or BMPString forms [10], UTF-8 is If it is of the UniversalString or BMPString forms [10], UTF-8 is
used to encode them. used to encode them.
Note: the form of DirectoryString is not indicated in protocol Note: the form of DirectoryString is not indicated in protocol unless
unless the attribute value is carried in binary. Servers which the attribute value is carried in binary. Servers which convert to
convert to DAP MUST choose an appropriate form. Servers MUST NOT DAP MUST choose an appropriate form. Servers MUST NOT reject values
reject values merely because they contain legal Unicode characters merely because they contain legal Unicode characters outside of the
outside of the range of printable ASCII. range of printable ASCII.
Example: Example:
This is a string of DirectoryString containing #!%#@ This is a string of DirectoryString containing #!%#@
6.11. DIT Content Rule Description 6.11. DIT Content Rule Description
( 1.3.6.1.4.1.1466.115.121.1.16 DESC 'DIT Content Rule Description' ) ( 1.3.6.1.4.1.1466.115.121.1.16 DESC 'DIT Content Rule Description' )
Values in this syntax are encoded according to the following BNF. Values in this syntax are encoded according to the following BNF.
Implementors should note that future versions of this document Implementors should note that future versions of this document may
may have expanded this BNF to include additional terms. have expanded this BNF to include additional terms.
DITContentRuleDescription = "(" DITContentRuleDescription = "("
numericoid ; Structural ObjectClass identifier numericoid ; Structural ObjectClass identifier
[ "NAME" qdescrs ] [ "NAME" qdescrs ]
[ "DESC" qdstring ] [ "DESC" qdstring ]
[ "OBSOLETE" ] [ "OBSOLETE" ]
[ "AUX" oids ] ; Auxiliary ObjectClasses [ "AUX" oids ] ; Auxiliary ObjectClasses
[ "MUST" oids ] ; AttributeType identifiers [ "MUST" oids ] ; AttributeType identifiers
[ "MAY" oids ] ; AttributeType identifiers [ "MAY" oids ] ; AttributeType identifiers
[ "NOT" oids ] ; AttributeType identifiers [ "NOT" oids ] ; AttributeType identifiers
skipping to change at page 17, line 15 skipping to change at page 20, line 35
6.15. IA5 String 6.15. IA5 String
( 1.3.6.1.4.1.1466.115.121.1.26 DESC 'IA5 String' ) ( 1.3.6.1.4.1.1466.115.121.1.26 DESC 'IA5 String' )
The encoding of a value in this syntax is the string value itself. The encoding of a value in this syntax is the string value itself.
6.16. INTEGER 6.16. INTEGER
( 1.3.6.1.4.1.1466.115.121.1.27 DESC 'INTEGER' ) ( 1.3.6.1.4.1.1466.115.121.1.27 DESC 'INTEGER' )
Values in this syntax are encoded as the decimal representation Values in this syntax are encoded as the decimal representation of
of their values, with each decimal digit represented by the its their values, with each decimal digit represented by the its
character equivalent. So the number 1321 is represented by the character equivalent. So the number 1321 is represented by the
character string "1321". character string "1321".
6.17. JPEG 6.17. JPEG
( 1.3.6.1.4.1.1466.115.121.1.28 DESC 'JPEG' ) ( 1.3.6.1.4.1.1466.115.121.1.28 DESC 'JPEG' )
Values in this syntax are encoded as strings containing JPEG images in Values in this syntax are encoded as strings containing JPEG images
the JPEG File Interchange Format (JFIF), as described in [8]. in the JPEG File Interchange Format (JFIF), as described in [8].
6.18. Matching Rule Description 6.18. Matching Rule Description
( 1.3.6.1.4.1.1466.115.121.1.30 DESC 'Matching Rule Description' ) ( 1.3.6.1.4.1.1466.115.121.1.30 DESC 'Matching Rule Description' )
Values of type matchingRules are encoded as strings according to Values of type matchingRules are encoded as strings according to the
the BNF given in section 4.5. BNF given in section 4.5.
6.19. Matching Rule Use Description 6.19. Matching Rule Use Description
( 1.3.6.1.4.1.1466.115.121.1.31 DESC 'Matching Rule Use Description' ) ( 1.3.6.1.4.1.1466.115.121.1.31 DESC 'Matching Rule Use Description'
)
Values of type matchingRuleUse are encoded as strings according to Values of type matchingRuleUse are encoded as strings according to
the BNF given in section 4.5. the BNF given in section 4.5.
6.20. MHS OR Address 6.20. MHS OR Address
( 1.3.6.1.4.1.1466.115.121.1.33 DESC 'MHS OR Address' ) ( 1.3.6.1.4.1.1466.115.121.1.33 DESC 'MHS OR Address' )
Values in this syntax are encoded as strings, according to the format Values in this syntax are encoded as strings, according to the format
defined in [11]. defined in [11].
skipping to change at page 18, line 14 skipping to change at page 21, line 41
Example: Example:
1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB#'0101'B 1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB#'0101'B
6.22. Name Form Description 6.22. Name Form Description
( 1.3.6.1.4.1.1466.115.121.1.35 DESC 'Name Form Description' ) ( 1.3.6.1.4.1.1466.115.121.1.35 DESC 'Name Form Description' )
Values in this syntax are encoded according to the following BNF. Values in this syntax are encoded according to the following BNF.
Implementors should note that future versions of this document Implementors should note that future versions of this document may
may have expanded this BNF to include additional terms. have expanded this BNF to include additional terms.
NameFormDescription = "(" whsp NameFormDescription = "(" whsp
numericoid whsp ; NameForm identifier numericoid whsp ; NameForm identifier
[ "NAME" qdescrs ] [ "NAME" qdescrs ]
[ "DESC" qdstring ] [ "DESC" qdstring ]
[ "OBSOLETE" whsp ] [ "OBSOLETE" whsp ]
"OC" woid ; Structural ObjectClass "OC" woid ; Structural ObjectClass
"MUST" oids ; AttributeTypes "MUST" oids ; AttributeTypes
[ "MAY" oids ] ; AttributeTypes [ "MAY" oids ] ; AttributeTypes
whsp ")" whsp ")"
skipping to change at page 18, line 40 skipping to change at page 22, line 18
The encoding of a string in this syntax is the string value itself. The encoding of a string in this syntax is the string value itself.
Example: Example:
1997 1997
6.24. Object Class Description 6.24. Object Class Description
( 1.3.6.1.4.1.1466.115.121.1.37 DESC 'Object Class Description' ) ( 1.3.6.1.4.1.1466.115.121.1.37 DESC 'Object Class Description' )
Values in this syntax are encoded according to the BNF in section 4.4. Values in this syntax are encoded according to the BNF in section
4.4.
6.25. OID 6.25. OID
( 1.3.6.1.4.1.1466.115.121.1.38 DESC 'OID' ) ( 1.3.6.1.4.1.1466.115.121.1.38 DESC 'OID' )
Values in the Object Identifier syntax are encoded according to Values in the Object Identifier syntax are encoded according to
the BNF in section 4.1 for "oid". the BNF in section 4.1 for "oid".
Example: Example:
1.2.3.4 1.2.3.4
cn cn
6.26. Other Mailbox 6.26. Other Mailbox
( 1.3.6.1.4.1.1466.115.121.1.39 DESC 'Other Mailbox' ) ( 1.3.6.1.4.1.1466.115.121.1.39 DESC 'Other Mailbox' )
Values in this syntax are encoded according to the following BNF: Values in this syntax are encoded according to the following BNF:
otherMailbox = mailbox-type "$" mailbox otherMailbox = mailbox-type "$" mailbox
mailbox-type = printablestring mailbox-type = printablestring
mailbox = <an encoded IA5 String> mailbox = <an encoded IA5 String>
In the above, mailbox-type represents the type of mail system in In the above, mailbox-type represents the type of mail system in
which the mailbox resides, for example "MCIMail"; and mailbox is which the mailbox resides, for example "MCIMail"; and mailbox is the
the actual mailbox in the mail system defined by mailbox-type. actual mailbox in the mail system defined by mailbox-type.
6.27. Postal Address 6.27. Postal Address
( 1.3.6.1.4.1.1466.115.121.1.41 DESC 'Postal Address' ) ( 1.3.6.1.4.1.1466.115.121.1.41 DESC 'Postal Address' )
Values in this syntax are encoded according to the following BNF: Values in this syntax are encoded according to the following BNF:
postal-address = dstring *( "$" dstring ) postal-address = dstring *( "$" dstring )
In the above, each dstring component of a postal address value is In the above, each dstring component of a postal address value is
encoded as a value of type Directory String syntax. Backslashes and encoded as a value of type Directory String syntax. Backslashes and
dollar characters, if they occur in the component, are quoted as dollar characters, if they occur in the component, are quoted as
described in section 4.3. Many servers limit the postal address to described in section 4.3. Many servers limit the postal address to
six lines of up to thirty characters. six lines of up to thirty characters.
skipping to change at page 20, line 21 skipping to change at page 24, line 9
international form, as described in E.123 [15]. international form, as described in E.123 [15].
Example: Example:
+1 512 305 0280 +1 512 305 0280
6.31. UTC Time 6.31. UTC Time
( 1.3.6.1.4.1.1466.115.121.1.53 DESC 'UTC Time' ) ( 1.3.6.1.4.1.1466.115.121.1.53 DESC 'UTC Time' )
Values in this syntax are encoded as if they were printable Values in this syntax are encoded as if they were printable strings
strings with the strings containing a UTCTime value. This is with the strings containing a UTCTime value. This is historical; new
historical; new attribute definitions SHOULD use GeneralizedTime attribute definitions SHOULD use GeneralizedTime instead.
instead.
6.32. LDAP Syntax Description 6.32. LDAP Syntax Description
( 1.3.6.1.4.1.1466.115.121.1.54 DESC 'LDAP Syntax Description' ) ( 1.3.6.1.4.1.1466.115.121.1.54 DESC 'LDAP Syntax Description' )
Values in this syntax are encoded according to the BNF in section Values in this syntax are encoded according to the BNF in section
4.3.3. 4.3.3.
6.33. DIT Structure Rule Description
( 1.3.6.1.4.1.1466.115.121.1.17 DESC 'DIT Structure Rule Description'
)
Values with this syntax are encoded according to the following BNF:
DITStructureRuleDescription = "(" whsp
ruleidentifier whsp ; DITStructureRule identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
"FORM" woid whsp ; NameForm
[ "SUP" ruleidentifiers whsp ] ; superior DITStructureRules
")"
ruleidentifier = integer
ruleidentifiers = ruleidentifier |
"(" whsp ruleidentifierlist whsp ")"
ruleidentifierlist = [ ruleidentifier *( ruleidentifier ) ]
7. Object Classes 7. Object Classes
Servers SHOULD recognize all the names of standard classes from Servers SHOULD recognize all the names of standard classes from
section 7 of [12]. section 7 of [12].
7.1. Extensible Object Class 7.1. Extensible Object Class
The extensibleObject object class, if present in an entry, permits The extensibleObject object class, if present in an entry, permits
that entry to optionally hold any attribute. The MAY attribute list that entry to optionally hold any attribute. The MAY attribute list
of this class is implicitly the set of all attributes. of this class is implicitly the set of all attributes.
skipping to change at page 21, line 5 skipping to change at page 25, line 15
( 1.3.6.1.4.1.1466.101.120.111 NAME 'extensibleObject' ( 1.3.6.1.4.1.1466.101.120.111 NAME 'extensibleObject'
SUP top AUXILIARY ) SUP top AUXILIARY )
The mandatory attributes of the other object classes of this entry The mandatory attributes of the other object classes of this entry
are still required to be present. are still required to be present.
Note that not all servers will implement this object class, and those Note that not all servers will implement this object class, and those
which do not will reject requests to add entries which contain this which do not will reject requests to add entries which contain this
object class, or modify an entry to add this object class. object class, or modify an entry to add this object class.
7.2. subschema
This object class is used in the subschema entry.
( 2.5.20.1 NAME 'subschema' AUXILIARY
MAY ( dITStructureRules $ nameForms $ ditContentRules $
objectClasses $ attributeTypes $ matchingRules $
matchingRuleUse ) )
The ldapSyntaxes operational attribute may also be present in
subschema entries.
8. Matching Rules 8. Matching Rules
Servers which implement the extensibleMatch filter SHOULD allow Servers which implement the extensibleMatch filter SHOULD allow all
all the matching rules listed in this section to be used in the the matching rules listed in this section to be used in the
extensibleMatch. In general these servers SHOULD allow matching extensibleMatch. In general these servers SHOULD allow matching
rules to be used with all attribute types known to the server, when rules to be used with all attribute types known to the server, when
the assertion syntax of the matching rule is the same as the value the assertion syntax of the matching rule is the same as the value
syntax of the attribute. syntax of the attribute.
Servers MAY implement additional matching rules. Servers MAY implement additional matching rules.
8.1. Matching Rules used in Equality Filters 8.1. Matching Rules used in Equality Filters
Servers SHOULD be capable of performing the following matching rules. Servers SHOULD be capable of performing the following matching rules.
For all these rules, the assertion syntax is the same as the value For all these rules, the assertion syntax is the same as the value
syntax. syntax.
( 2.5.13.0 NAME 'objectIdentifierMatch' ( 2.5.13.0 NAME 'objectIdentifierMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.38' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
If the client supplies a filter using an objectIdentifierMatch whose If the client supplies a filter using an objectIdentifierMatch whose
matchValue oid is in the "descr" form, and the oid is not recognized matchValue oid is in the "descr" form, and the oid is not recognized
by the server, then the filter is Undefined. by the server, then the filter is Undefined.
( 2.5.13.1 NAME 'distinguishedNameMatch' ( 2.5.13.1 NAME 'distinguishedNameMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.12' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
( 2.5.13.2 NAME 'caseIgnoreMatch' ( 2.5.13.2 NAME 'caseIgnoreMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
( 2.5.13.8 NAME 'numericStringMatch' ( 2.5.13.8 NAME 'numericStringMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.36' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.36 )
( 2.5.13.11 NAME 'caseIgnoreListMatch' ( 2.5.13.11 NAME 'caseIgnoreListMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.41' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
( 2.5.13.14 NAME 'integerMatch' ( 2.5.13.14 NAME 'integerMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )
( 2.5.13.16 NAME 'bitStringMatch' ( 2.5.13.16 NAME 'bitStringMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.6' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.6 )
( 2.5.13.20 NAME 'telephoneNumberMatch' ( 2.5.13.20 NAME 'telephoneNumberMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.50' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
( 2.5.13.22 NAME 'presentationAddressMatch' ( 2.5.13.22 NAME 'presentationAddressMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.43' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.43 )
( 2.5.13.23 NAME 'uniqueMemberMatch' ( 2.5.13.23 NAME 'uniqueMemberMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.34' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 )
( 2.5.13.24 NAME 'protocolInformationMatch' ( 2.5.13.24 NAME 'protocolInformationMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.42' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.42 )
( 2.5.13.27 NAME 'generalizedTimeMatch' ( 2.5.13.27 NAME 'generalizedTimeMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.24' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 )
( 1.3.6.1.4.1.1466.109.114.1 NAME 'caseExactIA5Match' ( 1.3.6.1.4.1.1466.109.114.1 NAME 'caseExactIA5Match'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.26' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
( 1.3.6.1.4.1.1466.109.114.2 NAME 'caseIgnoreIA5Match' ( 1.3.6.1.4.1.1466.109.114.2 NAME 'caseIgnoreIA5Match'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.26' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
When performing the caseIgnoreMatch, caseIgnoreListMatch, When performing the caseIgnoreMatch, caseIgnoreListMatch,
telephoneNumberMatch, caseExactIA5Match and caseIgnoreIA5Match, telephoneNumberMatch, caseExactIA5Match and caseIgnoreIA5Match,
multiple adjoining whitespace characters are treated the same as an multiple adjoining whitespace characters are treated the same as an
individual space, and leading and trailing whitespace is ignored. individual space, and leading and trailing whitespace is ignored.
Clients MUST NOT assume that servers are capable of transliteration Clients MUST NOT assume that servers are capable of transliteration
of Unicode values. of Unicode values.
8.2. Matching Rules used in Inequality Filters 8.2. Matching Rules used in Inequality Filters
Servers SHOULD be capable of performing the following matching rules, Servers SHOULD be capable of performing the following matching rules,
which are used in greaterOrEqual and lessOrEqual filters. which are used in greaterOrEqual and lessOrEqual filters.
( 2.5.13.28 NAME 'generalizedTimeOrderingMatch' ( 2.5.13.28 NAME 'generalizedTimeOrderingMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.24' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 )
( 2.5.13.3 NAME 'caseIgnoreOrderingMatch' ( 2.5.13.3 NAME 'caseIgnoreOrderingMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
The sort ordering for a caseIgnoreOrderingMatch is The sort ordering for a caseIgnoreOrderingMatch is implementation-
implementation-dependent. dependent.
8.3. Matching Rules for Subschema Attributes 8.3. Syntax and Matching Rules used in Substring Filters
The Substring Assertion syntax is used only as the syntax of
assertion values in the extensible match. It is not used as the
syntax of attributes, or in the substring filter.
( 1.3.6.1.4.1.1466.115.121.1.58 DESC 'Substring Assertion' )
The Substring Assertion is encoded according to the following BNF:
substring = [initial] any [final]
initial = value
any = "*" *(value "*")
final = value
The <value> production is UTF-8 encoded string. Should the backslash
or asterix characters be present in a production of <value>, they are
quoted as described in section 4.3.
Servers SHOULD be capable of performing the following matching rules,
which are used in substring filters.
( 2.5.13.4 NAME 'caseIgnoreSubstringsMatch'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 )
( 2.5.13.21 NAME 'telephoneNumberSubstringsMatch'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 )
( 2.5.13.10 NAME 'numericStringSubstringsMatch'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 )
8.4. Matching Rules for Subschema Attributes
Servers which allow subschema entries to be modified by clients MUST Servers which allow subschema entries to be modified by clients MUST
support the following matching rule, as it is the equality matching support the following matching rules, as they are the equality
rule for several of the subschema attributes. matching rules for several of the subschema attributes.
( 2.5.13.29 NAME 'integerFirstComponentMatch'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )
( 2.5.13.30 NAME 'objectIdentifierFirstComponentMatch' ( 2.5.13.30 NAME 'objectIdentifierFirstComponentMatch'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.38' ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
Implementors should note that the assertion syntax of this matching Implementors should note that the assertion syntax of these matching
rule, an OID, is different from the value syntax of attributes for rules, an INTEGER or OID, is different from the value syntax of
which this is the equality matching rule. attributes for which this is the equality matching rule.
If the client supplies a filter using an If the client supplies an extensible filter using an
objectIdentifierFirstComponentMatch whose matchValue oid is in the objectIdentifierFirstComponentMatch whose matchValue is in the
"descr" form, and the oid is not recognized by the server, then the "descr" form, and the OID is not recognized by the server, then the
filter is Undefined. filter is Undefined.
9. Security Considerations 9. Security Considerations
9.1. Disclosure 9.1. Disclosure
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 information about the real-world objects they represent, which can be
be people, organizations or devices. Most countries have privacy people, organizations or devices. Most countries have privacy laws
laws regarding the publication of information about people. regarding the publication of information about people.
9.2. Use of Attribute Values in Security Applications 9.2. Use of Attribute Values 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 or DER form. An example of a situation which requires the same BER or DER form. An example of a situation which requires the
DER form of a distinguished name is the verification of an X.509 DER form of a distinguished name is the verification of an X.509
certificate. 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 23, line 39 skipping to change at page 29, line 11
Applications which require the reconstruction of the DER form of the Applications which require the reconstruction of the DER form of the
value SHOULD NOT use the string representation of attribute syntaxes value SHOULD NOT use the string representation of attribute syntaxes
when converting a value to LDAP format. Instead it SHOULD use the when converting a value to LDAP format. Instead it SHOULD use the
Binary syntax. Binary syntax.
10. Acknowledgements 10. Acknowledgements
This document is based substantially on RFC 1778, written by Tim This document is based substantially on RFC 1778, written by Tim
Howes, Steve Kille, Wengyik Yeong and Colin Robbins. Howes, Steve Kille, Wengyik Yeong and Colin Robbins.
Many of the attribute syntax encodings defined in this and Many of the attribute syntax encodings defined in this and related
related documents are adapted from those used in the QUIPU and the documents are adapted from those used in the QUIPU and the IC R3
IC R3 X.500 implementations. The contributions of the authors of both X.500 implementations. The contributions of the authors of both these
these implementations in the specification of syntaxes are gratefully implementations in the specification of syntaxes are gratefully
acknowledged. acknowledged.
11. Authors Addresses 11. Authors' Addresses
Mark Wahl Mark Wahl
Critical Angle Inc. Critical Angle Inc.
4815 West Braker Lane #502-385 4815 West Braker Lane #502-385
Austin, TX 78759 Austin, TX 78759
USA USA
Phone: +1 512 372-3160 Phone: +1 512 372-3160
EMail: M.Wahl@critical-angle.com EMail: M.Wahl@critical-angle.com
Andy Coulbeck
Isode Inc.
3925 West Braker Lane #333
Austin, TX 78759
USA
Phone: +1 512 305-0280 Andy Coulbeck
EMail: A.Coulbeck@isode.com Isode Inc.
9390 Research Blvd Suite 305
Austin, TX 78759
USA
Tim Howes Phone: +1 512 231-8993
Netscape Communications Corp. EMail: A.Coulbeck@isode.com
501 E. Middlefield Rd
Mountain View, CA 94043
USA
Phone: +1 415 254-1900 Tim Howes
EMail: howes@netscape.com Netscape Communications Corp.
501 E. Middlefield Rd, MS MV068
Mountain View, CA 94043
USA
Steve Kille Phone: +1 650 937-3419
Isode Limited EMail: howes@netscape.com
The Dome, The Square
Richmond
TW9 1DT
UK
Phone: +44-181-332-9091 Steve Kille
EMail: S.Kille@isode.com Isode Limited
The Dome, The Square
Richmond
TW9 1DT
UK
Phone: +44-181-332-9091
EMail: S.Kille@isode.com
12. Bibliography 12. Bibliography
[1] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access [1] Wahl, M., Howes, T., and S. Kille, "Lightweight Directory Access
Protocol (Version 3)", INTERNET-DRAFT Protocol (v3)", RFC 2251, December 1997.
<draft-ietf-asid-ldapv3-protocol-07.txt>, Aug. 1997.
[2] The Directory: Selected Attribute Types. ITU-T Recommendation [2] The Directory: Selected Attribute Types. ITU-T Recommendation
X.520, 1993. X.520, 1993.
[3] The Directory: Models. ITU-T Recommendation X.501, 1993. [3] The Directory: Models. ITU-T Recommendation X.501, 1993.
[4] S. Bradner, "Key words for use in RFCs to Indicate Requirement [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119. Levels", RFC 2119, March 1997.
[5] M. Wahl, S. Kille, "A UTF-8 String Representation of [5] Wahl, M., Kille, S., and T. Howes, "Lightweight Directory Access
Distinguished Names", INTERNET-DRAFT Protocol (v3): UTF-8 String Representation of
<draft-ietf-asid-ldapv3-dn-03.txt>, April 1997. Distinguished Names", RFC 2253, December 1997.
[6] S. Kille, "A String Representation for Presentation Addresses", [6] Kille, S., "A String Representation for Presentation Addresses",
RFC 1278, University College London, November 1991. RFC 1278, November 1991.
[7] Terminal Equipment and Protocols for Telematic Services - [7] Terminal Equipment and Protocols for Telematic Services -
Standardization of Group 3 facsimile apparatus for document Standardization of Group 3 facsimile apparatus for document
transmission. CCITT, Recommendation T.4. transmission. CCITT, Recommendation T.4.
[8] JPEG File Interchange Format (Version 1.02). Eric Hamilton, [8] JPEG File Interchange Format (Version 1.02). Eric Hamilton,
C-Cube Microsystems, Milpitas, CA, September 1, 1992. C-Cube Microsystems, Milpitas, CA, September 1, 1992.
[9] F. Yergeau, "UTF-8, a transformation format of Unicode and ISO [9] Yergeau, F., "UTF-8, a transformation format of Unicode and ISO
10646", RFC 2044, October 1996. 10646", RFC 2044, October 1996.
[10] Universal Multiple-Octet Coded Character Set (UCS) - [10] Universal Multiple-Octet Coded Character Set (UCS) -
Architecture and Basic Multilingual Plane, ISO/IEC 10646-1 : Architecture and Basic Multilingual Plane, ISO/IEC 10646-1 :
1993 (With amendments). 1993 (With amendments).
[11] S. Hardcastle-Kille, "Mapping between X.400(1988) / ISO 10021 [11] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021
and RFC 822", RFC 1327, May 1992. and RFC 822", RFC 1327, May 1992.
[12] M. Wahl, "X.500(96) User Schema for use with LDAP", [12] Wahl, M., "A Summary of the X.500(96) User Schema for use
INTERNET-DRAFT <draft-ietf-asid-ldapv3schema-x500-02.txt>, with LDAPv3", RFC 2256, December 1997.
Aug. 1997.
[13] D. Crocker, "Standard of the Format of ARPA-Internet Text [13] Crocker, D., "Standard of the Format of ARPA-Internet Text
Messages", STD 11, RFC 822, August 1982. Messages", STD 11, RFC 822, August 1982.
[14] ISO 3166, "Codes for the representation of names of countries". [14] ISO 3166, "Codes for the representation of names of countries".
[15] ITU-T Rec. E.123, Notation for national and international [15] ITU-T Rec. E.123, Notation for national and international
telephone numbers, 1988. telephone numbers, 1988.
<draft-ietf-asid-ldapv3-attributes-07.txt> Expires: February 1998 13. Full Copyright Statement
Copyright (C) The Internet Society (1997). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 135 change blocks. 
269 lines changed or deleted 394 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/