Network Working Group M. Wahl
Request for Comments: 2252 Critical Angle Inc.
Category: Standards Track A. Coulbeck
Isode Inc.
T. Howes
Netscape Communications Corp.
S. Kille
Isode Limited
December 1997
Network Working Group M. Wahl
Request for Comments: 2252 Critical Angle Inc.
Category: Standards Track A. Coulbeck
Isode Inc.
T. Howes
Netscape Communications Corp.
S. Kille
Isode Limited
December 1997
Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions
轻量级目录访问协议（v3）：属性语法定义
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1997). All Rights Reserved.
版权所有（C）互联网协会（1997年）。版权所有。
IESG Note
IESG注释
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:
根据RFC 2026第4.4.1节，IESG批准本规范作为拟定标准，尽管存在此限制，原因如下：
a. to encourage implementation and interoperability testing of these protocols (with or without update access) before they are deployed, and
a. 鼓励在部署这些协议之前实施和互操作性测试（有或没有更新访问），以及
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
b. 鼓励在只读应用程序中部署和使用这些协议。（例如，使用LDAPv3作为目录查询语言的应用程序，这些目录由LDAP以外的安全机制更新），以及
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.
c. 为避免延迟其他Internet标准的推进和部署，跟踪协议需要能够查询但不更新LDAPv3目录服务器。
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.
在此不鼓励实施者部署实现更新功能的LDAPv3客户端或服务器，直到LDAPv3中的强制性身份验证建议标准获得批准并作为RFC发布。
The Lightweight Directory Access Protocol (LDAP) [1] requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines a set of syntaxes for LDAPv3, and the rules by which attribute values of these syntaxes are represented as octet strings for transmission in the LDAP protocol. The syntaxes defined in this document are referenced by this and other documents that define attribute types. This document also defines the set of attribute types which LDAP servers should support.
轻量级目录访问协议（LDAP）[1]要求协议元素中AttributeValue字段的内容为八位字符串。本文档定义了LDAPv3的一组语法，以及将这些语法的属性值表示为八位字节字符串以在LDAP协议中传输的规则。本文档和其他定义属性类型的文档引用了本文档中定义的语法。本文档还定义了LDAP服务器应支持的属性类型集。
This document defines the framework for developing schemas for directories accessible via the Lightweight Directory Access Protocol.
本文档定义了为可通过轻量级目录访问协议访问的目录开发模式的框架。
Schema is the collection of attribute type definitions, object class definitions and other information which a server uses to determine how to match a filter or attribute value assertion (in a compare operation) against the attributes of an entry, and whether to permit add and modify operations.
模式是属性类型定义、对象类定义和其他信息的集合，服务器使用这些信息来确定如何将筛选器或属性值断言（在比较操作中）与条目的属性相匹配，以及是否允许添加和修改操作。
Section 4 states the general requirements and notations for attribute types, object classes, syntax and matching rule definitions.
第4节说明了属性类型、对象类、语法和匹配规则定义的一般要求和符号。
Section 5 lists attributes, section 6 syntaxes and section 7 object classes.
第5节列出了属性、第6节语法和第7节对象类。
Additional documents define schemas for representing real-world objects as directory entries.
其他文档定义了将真实对象表示为目录项的模式。
This document describes encodings used in an Internet protocol.
本文档描述在Internet协议中使用的编码。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [4].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[4]中所述进行解释。
Attribute Type and Object Class definitions are written in a string representation of the AttributeTypeDescription and ObjectClassDescription data types defined in X.501(93) [3]. Implementors are strongly advised to first read the description of how schema is represented in X.500 before reading the rest of this document.
属性类型和对象类定义以X.501（93）[3]中定义的AttributeTypeDescription和ObjectClassDescription数据类型的字符串表示形式编写。强烈建议实施者在阅读本文档其余部分之前，先阅读X.500中对模式表示方式的描述。
For the purposes of defining the encoding rules for attribute syntaxes, the following BNF definitions will be used. They are based on the BNF styles of RFC 822 [13].
为了定义属性语法的编码规则，将使用以下BNF定义。它们基于RFC 822[13]的BNF样式。
a = "a" / "b" / "c" / "d" / "e" / "f" / "g" / "h" / "i" /
"j" / "k" / "l" / "m" / "n" / "o" / "p" / "q" / "r" /
"s" / "t" / "u" / "v" / "w" / "x" / "y" / "z" / "A" /
"B" / "C" / "D" / "E" / "F" / "G" / "H" / "I" / "J" /
"K" / "L" / "M" / "N" / "O" / "P" / "Q" / "R" / "S" /
"T" / "U" / "V" / "W" / "X" / "Y" / "Z"
a = "a" / "b" / "c" / "d" / "e" / "f" / "g" / "h" / "i" /
"j" / "k" / "l" / "m" / "n" / "o" / "p" / "q" / "r" /
"s" / "t" / "u" / "v" / "w" / "x" / "y" / "z" / "A" /
"B" / "C" / "D" / "E" / "F" / "G" / "H" / "I" / "J" /
"K" / "L" / "M" / "N" / "O" / "P" / "Q" / "R" / "S" /
"T" / "U" / "V" / "W" / "X" / "Y" / "Z"
d = "0" / "1" / "2" / "3" / "4" /
"5" / "6" / "7" / "8" / "9"
d = "0" / "1" / "2" / "3" / "4" /
"5" / "6" / "7" / "8" / "9"
hex-digit = d / "a" / "b" / "c" / "d" / "e" / "f" /
"A" / "B" / "C" / "D" / "E" / "F"
hex-digit = d / "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 ]
键串=一个[a字符串]
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]
transformation of a character from ISO10646 [10]>
utf8 = <any sequence of octets formed from the UTF-8 [9]
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 IDENTIFIERs, descr is the syntactic representation of an object descriptor, which consists of letters and digits, starting with a 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 not be generated).
在以下对象标识符的字符串表示的BNF中，descr是对象描述符的语法表示，它由字母和数字组成，以字母开头。numericoid格式的对象标识符不应具有前导零（例如，允许使用“0.9.3”，但不应生成“0.09.3”）。
When encoding 'oid' elements in a value, the descr encoding option SHOULD be used in preference to the numericoid. An object descriptor is a more readable alias for a number OBJECT IDENTIFIER, and these (where assigned and known by the implementation) SHOULD be used in preference to numeric oids to the greatest extent possible. Examples of object descriptors in LDAP are attribute type, object class and matching rule names.
对值中的“oid”元素进行编码时，应优先使用descr编码选项而不是numericoid。对象描述符是数字对象标识符的一个更可读的别名，并且这些（由实现分配和已知的）应尽可能优先于数字OID使用。LDAP中的对象描述符示例有属性类型、对象类和匹配规则名称。
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
oids = woid / ( "(" oidlist ")" )
; set of oids of either form
oids = woid / ( "(" oidlist ")" )
oidlist = woid *( "$" woid )
oidlist=woid*（“$”woid）
; object descriptors used as schema element names
qdescrs = qdescr / ( whsp "(" qdescrlist ")" whsp )
; object descriptors used as schema element names
qdescrs = qdescr / ( whsp "(" qdescrlist ")" whsp )
qdescrlist = [ qdescr *( qdescr ) ]
qdescrlist = [ qdescr *( qdescr ) ]
qdescr = whsp "'" descr "'" whsp
qdescr=whsp“描述”whsp
The attribute types are described by sample values for the subschema "attributeTypes" attribute, which is written in the AttributeTypeDescription syntax. While lines have been folded for readability, the values transferred in protocol would not contain newlines.
属性类型由子模式“attributeTypes”属性的示例值描述，该子模式使用AttributeTypeDescription语法编写。虽然为了可读性已折叠行，但协议中传输的值将不包含换行符。
The AttributeTypeDescription is encoded according to the following BNF, and the productions for oid, qdescrs and qdstring are given in section 4.1. Implementors should note that future versions of this document may have expanded this BNF to include additional terms. Terms which begin with the characters "X-" are reserved for private experiments, and MUST be followed by a <qdstrings>.
AttributeTypeDescription根据以下BNF编码，oid、qdescrs和qdstring的结果在第4.1节中给出。实施者应注意，本文档的未来版本可能已经扩展了此BNF，以包括其他术语。以字符“X-”开头的术语仅供私人实验使用，后面必须跟一个<qdstrings>。
AttributeTypeDescription = "(" whsp
numericoid whsp ; AttributeType identifier
[ "NAME" qdescrs ] ; name used in AttributeType
[ "DESC" qdstring ] ; description
[ "OBSOLETE" whsp ]
[ "SUP" woid ] ; derived from this other
; AttributeType
[ "EQUALITY" woid ; Matching Rule name
[ "ORDERING" woid ; Matching Rule name
[ "SUBSTR" woid ] ; Matching Rule name
[ "SYNTAX" whsp noidlen whsp ] ; see section 4.3
[ "SINGLE-VALUE" whsp ] ; default multi-valued
[ "COLLECTIVE" whsp ] ; default not collective
[ "NO-USER-MODIFICATION" whsp ]; default user modifiable
[ "USAGE" whsp AttributeUsage ]; default userApplications
whsp ")"
AttributeTypeDescription = "(" whsp
numericoid whsp ; AttributeType identifier
[ "NAME" qdescrs ] ; name used in AttributeType
[ "DESC" qdstring ] ; description
[ "OBSOLETE" whsp ]
[ "SUP" woid ] ; derived from this other
; AttributeType
[ "EQUALITY" woid ; Matching Rule name
[ "ORDERING" woid ; Matching Rule name
[ "SUBSTR" woid ] ; Matching Rule name
[ "SYNTAX" whsp noidlen whsp ] ; see section 4.3
[ "SINGLE-VALUE" whsp ] ; default multi-valued
[ "COLLECTIVE" whsp ] ; default not collective
[ "NO-USER-MODIFICATION" whsp ]; default user modifiable
[ "USAGE" whsp AttributeUsage ]; default userApplications
whsp ")"
AttributeUsage = "userApplications" / "directoryOperation" / "distributedOperation" / ; DSA-shared "dSAOperation" ; DSA-specific, value depends on server
AttributeUsage=“userApplications”/“directoryOperation”/“distributedOperation”/；DSA共享“DSAO操作”；DSA特定，值取决于服务器
Servers are not required to provide the same or any text in the description part of the subschema values they maintain. Servers SHOULD provide at least one of the "SUP" and "SYNTAX" fields for each AttributeTypeDescription.
服务器不需要在其维护的子模式值的描述部分提供相同或任何文本。服务器应为每个AttributeTypeDescription提供至少一个“SUP”和“SYNTAX”字段。
Servers MUST implement all the attribute types referenced in sections 5.1, 5.2 and 5.3.
服务器必须实现第5.1、5.2和5.3节中引用的所有属性类型。
Servers MAY recognize additional names and attributes not listed in this document, and if they do so, MUST publish the definitions of the types in the attributeTypes attribute of their subschema entries.
服务器可能会识别本文档中未列出的其他名称和属性，如果这样做，则必须在其子模式条目的AttributeType属性中发布类型定义。
Schema developers MUST NOT create attribute definitions whose names conflict with attributes defined for use with LDAP in existing standards-track RFCs.
模式开发人员不得创建名称与现有标准跟踪RFC中为LDAP使用而定义的属性冲突的属性定义。
An AttributeDescription can be used as the value in a NAME part of an AttributeTypeDescription. Note that these are case insensitive.
AttributeDescription可以用作AttributeTypeDescription的名称部分中的值。注意，它们不区分大小写。
Note that the AttributeTypeDescription does not list the matching rules which can can be used with that attribute type in an extensibleMatch search filter. This is done using the matchingRuleUse attribute described in section 4.5.
请注意，AttributeTypeDescription未列出可在ExtensionMatch搜索筛选器中与该属性类型一起使用的匹配规则。这是使用第4.5节中描述的matchingRuleUse属性完成的。
This document refines the schema description of X.501 by requiring that the syntax field in an AttributeTypeDescription be a string representation of an OBJECT IDENTIFIER for the LDAP string syntax definition, and an optional indication of the maximum length of a value of this attribute (defined in section 4.3.2).
本文档通过要求AttributeTypeDescription中的语法字段是LDAP字符串语法定义的对象标识符的字符串表示形式，以及该属性值的最大长度（在第4.3.2节中定义）的可选指示来细化X.501的模式描述。
This section defines general requirements for LDAP attribute value syntax encodings. All documents defining attribute syntax encodings for use with LDAP are expected to conform to these requirements.
本节定义了LDAP属性值语法编码的一般要求。所有定义用于LDAP的属性语法编码的文档都应符合这些要求。
The encoding rules defined for a given attribute syntax must produce octet strings. To the greatest extent possible, encoded octet strings should be usable in their native encoded form for display purposes. In particular, encoding rules for attribute syntaxes defining non-binary values should produce strings that can be displayed with little or no translation by clients implementing LDAP. There are a few cases (e.g. audio) however, when it is not sensible to produce a printable representation, and clients MUST NOT assume that an unrecognized syntax is a string representation.
为给定属性语法定义的编码规则必须生成八位字节字符串。在最大程度上，编码的八位字节字符串应以其本机编码形式用于显示目的。特别是，定义非二进制值的属性语法的编码规则应该生成字符串，实现LDAP的客户端只需很少或根本不需要翻译即可显示这些字符串。但是，在某些情况下（例如音频），生成可打印的表示是不明智的，并且客户端不得假定无法识别的语法是字符串表示。
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 Distinguished Name, a backslash quoting mechanism is used to escape the following separator symbol character (such as "'", "$" or "#") if it should occur in that string. The backslash is followed by a pair of hexadecimal digits representing the next character. A backslash 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.
在将任意字符串（而不是可分辨名称）用作较大产品的一部分，而不是作为可分辨名称的一部分的编码中，如果下列分隔符符号字符（如“'”、“$”或“#”）出现在该字符串中，则使用反斜杠引用机制对其进行转义。反斜杠后面是一对十六进制数字，表示下一个字符。构成较大语法一部分的字符串中的反斜杠本身始终作为“\5C”或“\5C”传输。第6.27节给出了一个示例。
Syntaxes are also defined for matching rules whose assertion value syntax is different from the attribute value syntax.
还为断言值语法不同于属性值语法的匹配规则定义了语法。
This encoding format is used if the binary encoding is requested by the client for an attribute, or if the attribute syntax name is "1.3.6.1.4.1.1466.115.121.1.5". The contents of the LDAP AttributeValue or AssertionValue field is a BER-encoded instance of the attribute value or a matching rule assertion value ASN.1 data 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.)
如果客户端请求对属性进行二进制编码，或者如果属性语法名称为“1.3.6.1.4.1.1466.115.121.1.5”，则使用此编码格式。LDAP AttributeValue或AssertionValue字段的内容是属性值的BER编码实例或匹配规则断言值ASN.1数据类型，定义用于X.500。（八位字节字符串包装器中的第一个字节是标记八位字节。但是，八位字节字符串仍然以原始形式编码。）
All servers MUST implement this form for both generating attribute values in search responses, and parsing attribute values in add, compare and modify requests, if the attribute type is recognized and the attribute syntax name is that of Binary. Clients which request that all attributes be returned from entries MUST be prepared to receive values in binary (e.g. userCertificate;binary), and SHOULD NOT simply display binary or unrecognized values to users.
如果识别属性类型且属性语法名称为二进制，则所有服务器都必须实现此表单，以便在搜索响应中生成属性值，并在添加、比较和修改请求中解析属性值。请求从条目返回所有属性的客户机必须准备好接收二进制值（例如userCertificate；binary），而不应简单地向用户显示二进制或无法识别的值。
Syntaxes for use with LDAP are named by OBJECT IDENTIFIERs, which are dotted-decimal strings. These are not intended to be displayed to users.
与LDAP一起使用的语法由对象标识符命名，这些标识符是点十进制字符串。这些内容不打算向用户显示。
noidlen = numericoid [ "{" len "}" ]
noidlen = numericoid [ "{" len "}" ]
len = numericstring
len = numericstring
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 syntax would likely be a human readable string. Clients and servers need not implement all the syntaxes listed here, and MAY implement other syntaxes.
下表列出了迄今为止为LDAP定义的一些语法。H-R列表示该语法中的值是否可能是人类可读的字符串。客户端和服务器不需要实现此处列出的所有语法，可以实现其他语法。
Other documents may define additional syntaxes. However, the definition of additional arbitrary syntaxes is strongly deprecated since it will hinder interoperability: today's client and server implementations generally do not have the ability to dynamically recognize new syntaxes. In most cases attributes will be defined with the syntax for directory strings.
其他文档可能会定义其他语法。但是，强烈反对使用附加任意语法的定义，因为它会妨碍互操作性：今天的客户机和服务器实现通常不具备动态识别新语法的能力。在大多数情况下，属性将使用目录字符串的语法定义。
Value being represented H-R OBJECT IDENTIFIER
=================================================================
ACI Item N 1.3.6.1.4.1.1466.115.121.1.1
Access Point Y 1.3.6.1.4.1.1466.115.121.1.2
Attribute Type Description Y 1.3.6.1.4.1.1466.115.121.1.3
Audio N 1.3.6.1.4.1.1466.115.121.1.4
Binary N 1.3.6.1.4.1.1466.115.121.1.5
Bit String Y 1.3.6.1.4.1.1466.115.121.1.6
Boolean Y 1.3.6.1.4.1.1466.115.121.1.7
Certificate N 1.3.6.1.4.1.1466.115.121.1.8
Certificate List N 1.3.6.1.4.1.1466.115.121.1.9
Certificate Pair N 1.3.6.1.4.1.1466.115.121.1.10
Country String Y 1.3.6.1.4.1.1466.115.121.1.11
DN Y 1.3.6.1.4.1.1466.115.121.1.12
Data Quality Syntax Y 1.3.6.1.4.1.1466.115.121.1.13
Delivery Method Y 1.3.6.1.4.1.1466.115.121.1.14
Directory String Y 1.3.6.1.4.1.1466.115.121.1.15
DIT Content Rule Description Y 1.3.6.1.4.1.1466.115.121.1.16
DIT Structure Rule Description Y 1.3.6.1.4.1.1466.115.121.1.17
DL Submit Permission Y 1.3.6.1.4.1.1466.115.121.1.18
DSA Quality Syntax Y 1.3.6.1.4.1.1466.115.121.1.19
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
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
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
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
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 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
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
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
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 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
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
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
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
Value being represented H-R OBJECT IDENTIFIER
=================================================================
ACI Item N 1.3.6.1.4.1.1466.115.121.1.1
Access Point Y 1.3.6.1.4.1.1466.115.121.1.2
Attribute Type Description Y 1.3.6.1.4.1.1466.115.121.1.3
Audio N 1.3.6.1.4.1.1466.115.121.1.4
Binary N 1.3.6.1.4.1.1466.115.121.1.5
Bit String Y 1.3.6.1.4.1.1466.115.121.1.6
Boolean Y 1.3.6.1.4.1.1466.115.121.1.7
Certificate N 1.3.6.1.4.1.1466.115.121.1.8
Certificate List N 1.3.6.1.4.1.1466.115.121.1.9
Certificate Pair N 1.3.6.1.4.1.1466.115.121.1.10
Country String Y 1.3.6.1.4.1.1466.115.121.1.11
DN Y 1.3.6.1.4.1.1466.115.121.1.12
Data Quality Syntax Y 1.3.6.1.4.1.1466.115.121.1.13
Delivery Method Y 1.3.6.1.4.1.1466.115.121.1.14
Directory String Y 1.3.6.1.4.1.1466.115.121.1.15
DIT Content Rule Description Y 1.3.6.1.4.1.1466.115.121.1.16
DIT Structure Rule Description Y 1.3.6.1.4.1.1466.115.121.1.17
DL Submit Permission Y 1.3.6.1.4.1.1466.115.121.1.18
DSA Quality Syntax Y 1.3.6.1.4.1.1466.115.121.1.19
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
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
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
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
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 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
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
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
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 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
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
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
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
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 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 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 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 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 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
演示文稿地址Y 1.3.6.1.4.1.1466.115.121.1.43可打印字符串Y 1.3.6.1.1466.115.121.1.44子字符串断言Y 1.3.6.1.4.1.1466.115.121.1.58子树规范Y 1.3.6.1.4.1.1466.115.121.1.45供应商信息Y 1.3.6.1.1.1.4.1.1.1.1.1.1466.115.121.1.1.1供应商或消费者Y 1.6.1.1.4.1.1.1.1.1.1.1.1.141.3.6.1.4.1.1466.115.121.1.48支持的算法N1.3.6.1.4.1.1466.115.121.1.49电话号码Y1.3.6.1.1466.115.121.1.50电传终端标识符Y1.3.6.1.4.1.1466.115.121.1.51电传号码Y1.3.6.1.4.1.1466.115.121.1.52 UTC时间Y1.3.6.1.4.1.1.1.1.1466.121.53
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 other syntaxes, may be indicated by appending this bound count inside of curly braces following the syntax name's OBJECT IDENTIFIER in an Attribute Type Description. This bound is not part of the syntax name itself. For instance, "1.3.6.4.1.1466.0{64}" suggests that server implementations should allow a string to be 64 characters long, although they may allow longer strings. Note that a single character of the Directory String syntax may be encoded in more than one byte since UTF-8 is a variable-length encoding.
使用基于字符串的语法的值中的字符数或所有其他语法的值中的字节数的建议最小上限可以通过在属性类型描述中语法名称的对象标识符后的大括号内追加此绑定计数来指示。此绑定不是语法名称本身的一部分。例如，“1.3.6.4.1.1466.0{64}”建议服务器实现应允许字符串长度为64个字符，尽管它们可能允许更长的字符串。请注意，目录字符串语法的单个字符可以用多个字节编码，因为UTF-8是可变长度编码。
The following BNF may be used to associate a short description with a syntax OBJECT IDENTIFIER. Implementors should note that future versions of this document may expand this definition to include additional terms. Terms whose identifier begins with "X-" are reserved for private experiments, and MUST be followed by a <qdstrings>.
以下BNF可用于将简短描述与语法对象标识符相关联。实施者应注意，本文档的未来版本可能会扩展此定义，以包括其他术语。标识符以“X-”开头的术语保留用于私人实验，后面必须跟一个<qdstrings>。
SyntaxDescription = "(" whsp numericoid whsp [ "DESC" qdstring ] whsp ")"
SyntaxDescription=“（“whsp numericoid whsp[“DESC”qdstring]whsp”）”
The format for representation of object classes is defined in X.501 [3]. In general every entry will contain an abstract class ("top" or "alias"), at least one structural object class, and zero or more auxiliary object classes. Whether an object class is abstract, structural or auxiliary is defined when the object class identifier is assigned. An object class definition should not be changed without having a new identifier assigned to it.
对象类的表示格式在X.501[3]中定义。通常，每个条目将包含一个抽象类（“top”或“alias”）、至少一个结构对象类以及零个或多个辅助对象类。对象类是抽象的、结构的还是辅助的，都是在指定对象类标识符时定义的。在没有为对象类定义分配新标识符的情况下，不应更改对象类定义。
Object class descriptions are written according to the following BNF. Implementors should note that future versions of this document may expand this definition to include additional terms. Terms whose identifier begins with "X-" are reserved for private experiments, and MUST be followed by a <qdstrings> encoding.
对象类描述是根据以下BNF编写的。实施者应注意，本文档的未来版本可能会扩展此定义，以包括其他术语。标识符以“X-”开头的术语是为私人实验保留的，必须后跟<qdstrings>编码。
ObjectClassDescription = "(" whsp
numericoid whsp ; ObjectClass identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
[ "SUP" oids ] ; Superior ObjectClasses
[ ( "ABSTRACT" / "STRUCTURAL" / "AUXILIARY" ) whsp ]
; default structural
[ "MUST" oids ] ; AttributeTypes
[ "MAY" oids ] ; AttributeTypes
whsp ")"
ObjectClassDescription = "(" whsp
numericoid whsp ; ObjectClass identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
[ "SUP" oids ] ; Superior ObjectClasses
[ ( "ABSTRACT" / "STRUCTURAL" / "AUXILIARY" ) whsp ]
; default structural
[ "MUST" oids ] ; AttributeTypes
[ "MAY" oids ] ; AttributeTypes
whsp ")"
These are described as sample values for the subschema "objectClasses" attribute for a server which implements the LDAP schema. While lines have been folded for readability, the values transferred in protocol would not contain newlines.
这些被描述为实现LDAP模式的服务器的子模式“objectClasses”属性的示例值。虽然为了可读性已折叠行，但协议中传输的值将不包含换行符。
Servers SHOULD implement all the object classes referenced in section 7, except for extensibleObject, which is optional. Servers MAY implement additional object classes not listed in this document, and if they do so, MUST publish the definitions of the classes in the objectClasses attribute of their subschema entries.
服务器应该实现第7节中引用的所有对象类，但extensibleObject除外，extensibleObject是可选的。服务器可能实现本文档中未列出的其他对象类，如果实现了这些类，则必须在其子模式条目的objectClasses属性中发布这些类的定义。
Schema developers MUST NOT create object class definitions whose names conflict with attributes defined for use with LDAP in existing standards-track RFCs.
模式开发人员不得创建名称与现有标准跟踪RFC中为LDAP使用而定义的属性冲突的对象类定义。
Matching rules are used by servers to compare attribute values against assertion values when performing Search and Compare operations. They are also used to identify the value to be added or deleted when modifying entries, and are used when comparing a purported distinguished name with the name of an entry.
在执行搜索和比较操作时，服务器使用匹配规则将属性值与断言值进行比较。它们还用于标识修改条目时要添加或删除的值，并用于将声称的可分辨名称与条目名称进行比较。
Most of the attributes given in this document will have an equality matching rule defined.
本文档中给出的大多数属性都定义了相等匹配规则。
Matching rule descriptions are written according to the following BNF. Implementors should note that future versions of this document may have expanded this BNF to include additional terms. Terms whose identifier begins with "X-" are reserved for private experiments, and
匹配规则描述根据以下BNF编写。实施者应注意，本文档的未来版本可能已经扩展了此BNF，以包括其他术语。标识符以“X-”开头的术语保留用于私人实验，以及
MUST be followed by a <qdstrings> encoding.
必须后跟<qdstrings>编码。
MatchingRuleDescription = "(" whsp
numericoid whsp ; MatchingRule identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
"SYNTAX" numericoid
whsp ")"
MatchingRuleDescription = "(" whsp
numericoid whsp ; MatchingRule identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
"SYNTAX" numericoid
whsp ")"
Values of the matchingRuleUse list the attributes which are suitable for use with an extensible matching rule.
matchingRuleUse的值列出了适用于可扩展匹配规则的属性。
MatchingRuleUseDescription = "(" whsp
numericoid whsp ; MatchingRule identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" ]
"APPLIES" oids ; AttributeType identifiers
whsp ")"
MatchingRuleUseDescription = "(" whsp
numericoid whsp ; MatchingRule identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" ]
"APPLIES" oids ; AttributeType identifiers
whsp ")"
Servers which support matching rules and the extensibleMatch SHOULD implement all the matching rules in section 8.
支持匹配规则和ExtensionMatch的服务器应实现第8节中的所有匹配规则。
Servers MAY implement additional matching rules not listed in this document, and if they do so, MUST publish the definitions of the matching rules in the matchingRules attribute of their subschema entries. If the server supports the extensibleMatch, then the server MUST publish the relationship between the matching rules and attributes in the matchingRuleUse attribute.
服务器可能会实现本文档中未列出的其他匹配规则，如果它们这样做，则必须在其子模式条目的matchingRules属性中发布匹配规则的定义。如果服务器支持ExtensionMatch，则服务器必须在matchingRuleUse属性中发布匹配规则和属性之间的关系。
For example, a server which implements a privately-defined matching rule for performing sound-alike matches on Directory String-valued 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 different):
例如，实现私有定义的匹配规则以对目录字符串值属性执行声音相似匹配的服务器将在子模式条目中包含以下内容（例如，1.2.3.4.5，实际匹配规则的OID将不同）：
matchingRule: ( 1.2.3.4.5 NAME 'soundAlikeMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
匹配规则：（1.2.3.4.5名称“soundAlikeMatch”语法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 2.5.4.15, the following would also be present:
如果此匹配规则可与属性2.5.4.41和2.5.4.15一起使用，则还将出现以下内容：
matchingRuleUse: ( 1.2.3.4.5 APPLIES (2.5.4.41 $ 2.5.4.15) )
匹配规则用法：（1.2.3.4.5适用（2.5.4.41$2.5.4.15））
A client could then make use of this matching rule by sending a search operation in which the filter is of the extensibleMatch choice, the matchingRule field is "soundAlikeMatch", and the type field is "2.5.4.41" or "2.5.4.15".
然后，客户机可以通过发送一个搜索操作来使用该匹配规则，在该操作中，过滤器是extensibleMatch选项，匹配规则字段是“soundAlikeMatch”，类型字段是“2.5.4.41”或“2.5.4.15”。
All LDAP server implementations MUST recognize the attribute types defined in this section.
所有LDAP服务器实现必须识别本节中定义的属性类型。
Servers SHOULD also recognize all the attributes from section 5 of [12].
服务器还应识别[12]第5节中的所有属性。
Servers MUST maintain values of these attributes in accordance with the definitions in X.501(93).
服务器必须根据X.501（93）中的定义维护这些属性的值。
This attribute SHOULD appear in entries which were created using the Add operation.
此属性应出现在使用“添加”操作创建的条目中。
( 2.5.18.1 NAME 'createTimestamp' EQUALITY generalizedTimeMatch ORDERING generalizedTimeOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
（2.5.18.1名称'createTimestamp'相等GeneraledTimeMatch排序GeneraledTimeOrderingMatch语法1.3.6.1.4.1.1466.115.121.1.24单值无用户修改使用目录操作）
This attribute SHOULD appear in entries which have been modified using the Modify operation.
此属性应出现在使用“修改”操作修改的条目中。
( 2.5.18.2 NAME 'modifyTimestamp' EQUALITY generalizedTimeMatch ORDERING generalizedTimeOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
（2.5.18.2名称'modifyTimestamp'相等GeneraledTimeMatch排序GeneraledTimeOrderingMatch语法1.3.6.1.4.1.1466.115.121.1.24单值无用户修改使用目录操作）
This attribute SHOULD appear in entries which were created using the Add operation.
此属性应出现在使用“添加”操作创建的条目中。
( 2.5.18.3 NAME 'creatorsName' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
（2.5.18.3名称“创建者名称”相等区分名称匹配语法1.3.6.1.4.1.1466.115.121.1.12单值无用户修改使用目录操作）
This attribute SHOULD appear in entries which have been modified using the Modify operation.
此属性应出现在使用“修改”操作修改的条目中。
( 2.5.18.4 NAME 'modifiersName' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
（2.5.18.4名称'ModifierName'相等区分名称匹配语法1.3.6.1.4.1.1466.115.121.1.12单值无用户修改使用目录操作）
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 makes available attributes specifying the schema.
此属性的值是子模式条目（如果服务器基于X.500（93））的名称，则为子条目），其中服务器提供指定模式的可用属性。
( 2.5.18.10 NAME 'subschemaSubentry' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 NO-USER-MODIFICATION SINGLE-VALUE USAGE directoryOperation )
（2.5.18.10名称“subschemaSubentry”相等区分名称匹配语法1.3.6.1.4.1.1466.115.121.1.12无用户修改单值使用目录操作）
This attribute is typically located in the subschema entry.
此属性通常位于子模式条目中。
( 2.5.21.5 NAME 'attributeTypes' EQUALITY objectIdentifierFirstComponentMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.3 USAGE directoryOperation )
（2.5.21.5名称'AttributeType'相等objectIdentifierFirstComponentMatch语法1.3.6.1.4.1.1466.115.121.1.3用法目录操作）
This attribute is typically located in the subschema entry.
此属性通常位于子模式条目中。
( 2.5.21.6 NAME 'objectClasses' EQUALITY objectIdentifierFirstComponentMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.37 USAGE directoryOperation )
（2.5.21.6名称'ObjectClass'相等objectIdentifierFirstComponentMatch语法1.3.6.1.4.1.1466.115.121.1.37用法目录操作）
This attribute is typically located in the subschema entry.
此属性通常位于子模式条目中。
( 2.5.21.4 NAME 'matchingRules' EQUALITY objectIdentifierFirstComponentMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.30 USAGE directoryOperation )
（2.5.21.4名称“匹配规则”相等objectIdentifierFirstComponentMatch语法1.3.6.1.4.1.1466.115.121.1.30使用目录操作）
This attribute is typically located in the subschema entry.
此属性通常位于子模式条目中。
( 2.5.21.8 NAME 'matchingRuleUse' EQUALITY objectIdentifierFirstComponentMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.31 USAGE directoryOperation )
（2.5.21.8名称“matchingRuleUse”相等objectIdentifierFirstComponentMatch语法1.3.6.1.4.1.1466.115.121.1.31使用目录操作）
These attributes are only present in the root DSE (see [1] and [3]).
这些属性仅存在于根DSE中（请参见[1]和[3]）。
Servers MUST recognize these attribute names, but it is not required that a server provide values for these attributes, when the attribute corresponds to a feature which the server does not implement.
服务器必须识别这些属性名称，但当属性对应于服务器未实现的功能时，服务器不需要为这些属性提供值。
The values of this attribute correspond to naming contexts which this 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) this attribute will be absent. If the server believes it contains the entire directory, the attribute will have a single value, and that value will be the empty string (indicating the null DN of the root). This attribute will allow a client to choose suitable base objects for searching when it has contacted a server.
此属性的值对应于此服务器控制或隐藏的命名上下文。如果服务器不掌握任何信息（例如，它是公共X.500目录的LDAP网关），则此属性将不存在。如果服务器认为它包含整个目录，则该属性将有一个值，该值将是空字符串（表示根的null DN）。此属性允许客户端在与服务器联系后选择合适的基本对象进行搜索。
( 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 )
（1.3.6.1.4.1.1466.101.120.5名称“namingContexts”语法1.3.6.1.4.1.1466.115.121.1.12用法DSAO操作）
The values of this attribute are URLs of other servers which may be contacted when this server becomes unavailable. If the server does not know of any other servers which could be used this attribute will be absent. Clients may cache this information in case their preferred LDAP server later becomes unavailable.
此属性的值是其他服务器的URL，当此服务器不可用时，可能会联系这些服务器。如果服务器不知道任何其他可以使用的服务器，则此属性将不存在。客户端可能会缓存此信息，以防其首选LDAP服务器稍后变得不可用。
( 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 )
（1.3.6.1.4.1.1466.101.120.6名称“altServer”语法1.3.6.1.4.1.1466.115.121.1.26用法DSAO操作）
The values of this attribute are OBJECT IDENTIFIERs identifying the supported extended operations which the server supports.
此属性的值是标识服务器支持的受支持扩展操作的对象标识符。
If the server does not support any extensions this attribute will be absent.
如果服务器不支持任何扩展，则此属性将不存在。
( 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 )
（1.3.6.1.4.1.1466.101.120.7名称“supportedExtension”语法1.3.6.1.4.1.1466.115.121.1.38用法dSAOperation）
The values of this attribute are the OBJECT IDENTIFIERs identifying controls which the server supports. If the server does not support any controls, this attribute will be absent.
此属性的值是标识服务器支持的控件的对象标识符。如果服务器不支持任何控件，则此属性将不存在。
( 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 )
（1.3.6.1.4.1.1466.101.120.13名称“supportedControl”语法1.3.6.1.4.1.1466.115.121.1.38用法DSAO操作）
The values of this attribute are the names of supported SASL mechanisms which the server supports. If the server does not support any mechanisms this attribute will be absent.
此属性的值是服务器支持的受支持SASL机制的名称。如果服务器不支持任何机制，则此属性将不存在。
( 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 )
（1.3.6.1.4.1.1466.101.120.14名称“supportedSASLMechanisms”语法1.3.6.1.4.1.1466.115.121.1.15用法DSAO操作）
The values of this attribute are the versions of the LDAP protocol which the server implements.
此属性的值是服务器实现的LDAP协议的版本。
( 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 )
（1.3.6.1.4.1.1466.101.120.15名称“supportedLDAPVersion”语法1.3.6.1.4.1.1466.115.121.1.27使用DSAOOperation）
This attribute is typically located in the subschema entry.
此属性通常位于子模式条目中。
Servers MAY use this attribute to list the syntaxes which are implemented. Each value corresponds to one syntax.
服务器可以使用此属性列出实现的语法。每个值对应一种语法。
( 1.3.6.1.4.1.1466.101.120.16 NAME 'ldapSyntaxes' EQUALITY objectIdentifierFirstComponentMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.54 USAGE directoryOperation )
（1.3.6.1.4.1.1466.101.120.16名称'ldapSyntaxes'相等对象标识符FirstComponentMatch语法1.3.6.1.4.1.1466.115.121.1.54使用目录操作）
These attributes are located in the subschema entry. All servers SHOULD recognize their name, although typically only X.500 servers will implement their functionality.
这些属性位于子模式条目中。所有服务器都应该识别它们的名称，尽管通常只有X.500服务器将实现它们的功能。
( 2.5.21.1 NAME 'dITStructureRules' EQUALITY integerFirstComponentMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.17 USAGE directoryOperation )
（2.5.21.1名称“dITStructureRules”相等integerFirstComponentMatch语法1.3.6.1.4.1.1466.115.121.1.17用法目录操作）
( 2.5.21.7 NAME 'nameForms' EQUALITY objectIdentifierFirstComponentMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.35 USAGE directoryOperation )
（2.5.21.7名称'nameForms'相等对象IdentifierFirstComponentMatch语法1.3.6.1.4.1.1466.115.121.1.35使用目录操作）
( 2.5.21.2 NAME 'dITContentRules' EQUALITY objectIdentifierFirstComponentMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.16 USAGE directoryOperation )
（2.5.21.2名称'dITContentRules'相等objectIdentifierFirstComponentMatch语法1.3.6.1.4.1.1466.115.121.1.16用法目录操作）
Servers SHOULD recognize all the syntaxes described in this section.
服务器应该识别本节中描述的所有语法。
( 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描述“属性类型描述”）
Values in this syntax are encoded according to the BNF given at the start of section 4.2. For example,
此语法中的值根据第4.2节开头给出的BNF进行编码。例如
( 2.5.4.0 NAME 'objectClass' SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
（2.5.4.0名称“objectClass”语法1.3.6.1.4.1.1466.115.121.1.38）
( 1.3.6.1.4.1.1466.115.121.1.5 DESC 'Binary' )
（1.3.6.1.4.1.1466.115.121.1.5描述“二进制”）
Values in this syntax are encoded as described in section 4.3.1.
此语法中的值按照第4.3.1节所述进行编码。
( 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描述“位字符串”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
bitstring = "'" *binary-digit "'B"
bitstring=“”*二进制数字“'B”
binary-digit = "0" / "1"
binary-digit = "0" / "1"
Example:
例子：
'0101111101'B
'0101111101'B
( 1.3.6.1.4.1.1466.115.121.1.7 DESC 'Boolean' )
（1.3.6.1.4.1.1466.115.121.1.7描述“布尔值”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
boolean = "TRUE" / "FALSE"
boolean = "TRUE" / "FALSE"
Boolean values have an encoding of "TRUE" if they are logically true, and have an encoding of "FALSE" otherwise.
如果布尔值在逻辑上为真，则其编码为“真”，否则其编码为“假”。
( 1.3.6.1.4.1.1466.115.121.1.8 DESC 'Certificate' )
（1.3.6.1.4.1.1466.115.121.1.8说明“证书”）
Because of the changes from X.509(1988) and X.509(1993) and additional changes to the ASN.1 definition to support certificate extensions, no string representation is defined, and values in this syntax MUST only be transferred using the binary encoding, by requesting or returning the attributes with descriptions "userCertificate;binary" or "caCertificate;binary". The BNF notation in RFC 1778 for "User Certificate" is not recommended to be used.
由于X.509（1988）和X.509（1993）的变化，以及ASN.1定义的额外变化，以支持证书扩展，因此未定义字符串表示，此语法中的值只能使用二进制编码进行传输，方法是请求或返回描述为“userCertificate；binary”或“证书；不建议使用RFC 1778中“用户证书”的BNF符号。
( 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说明“证书清单”）
Because of the incompatibility of the X.509(1988) and X.509(1993) definitions of revocation lists, values in this syntax MUST only be transferred using a binary encoding, by requesting or returning the attributes with descriptions "certificateRevocationList;binary" or "authorityRevocationList;binary". The BNF notation in RFC 1778 for "Authority Revocation List" is not recommended to be used.
由于撤销列表的X.509（1988）和X.509（1993）定义不兼容，此语法中的值只能使用二进制编码进行传输，方法是请求或返回描述为“CertificateResortionList；binary”或“authorityRevocationList；binary”的属性。不建议使用RFC 1778中“授权撤销列表”的BNF符号。
( 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描述“证书对”）
Because the Certificate is being carried in binary, values in this syntax MUST only be transferred using a binary encoding, by requesting or returning the attribute description "crossCertificatePair;binary". The BNF notation in RFC 1778 for "Certificate Pair" is not recommended to be used.
由于证书是以二进制形式传输的，因此此语法中的值只能通过请求或返回属性描述“crossCertificatePair；binary”使用二进制编码进行传输。不建议使用RFC 1778中“证书对”的BNF符号。
( 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描述“国家字符串”）
A value in this syntax is encoded the same as a value of Directory String syntax. Note that this syntax is limited to values of exactly two printable string characters, as listed in ISO 3166 [14].
此语法中的值与目录字符串语法中的值编码相同。请注意，此语法仅限于两个可打印字符串的值，如ISO 3166[14]中所列。
CountryString = p p
CountryString = p p
Example: US
例子：美国
( 1.3.6.1.4.1.1466.115.121.1.12 DESC 'DN' )
（1.3.6.1.4.1.1466.115.121.1.12描述“DN”）
Values in the Distinguished Name syntax are encoded to have the representation defined in [5]. Note that this representation is not reversible to an ASN.1 encoding used in X.500 for Distinguished Names, as the CHOICE of any DirectoryString element in an RDN is no longer known.
可分辨名称语法中的值被编码为具有[5]中定义的表示形式。请注意，此表示与X.500中用于可分辨名称的ASN.1编码是不可逆的，因为RDN中任何DirectoryString元素的选择不再是已知的。
Examples (from [5]):
CN=Steve Kille,O=Isode Limited,C=GB
OU=Sales+CN=J. Smith,O=Widget Inc.,C=US
CN=L. Eagle,O=Sue\, Grabbit and Runn,C=GB
CN=Before\0DAfter,O=Test,C=GB
1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB
SN=Lu\C4\8Di\C4\87
Examples (from [5]):
CN=Steve Kille,O=Isode Limited,C=GB
OU=Sales+CN=J. Smith,O=Widget Inc.,C=US
CN=L. Eagle,O=Sue\, Grabbit and Runn,C=GB
CN=Before\0DAfter,O=Test,C=GB
1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB
SN=Lu\C4\8Di\C4\87
( 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描述“目录字符串”）
A string in this syntax is encoded in the UTF-8 form of ISO 10646 (a superset of Unicode). Servers and clients MUST be prepared to receive encodings of arbitrary Unicode characters, including characters not presently assigned to any character set.
此语法中的字符串以ISO10646（Unicode的超集）的UTF-8格式编码。服务器和客户端必须准备好接收任意Unicode字符的编码，包括当前未分配给任何字符集的字符。
For characters in the PrintableString form, the value is encoded as the string value itself.
对于可打印字符串形式的字符，该值被编码为字符串值本身。
If it is of the TeletexString form, then the characters are transliterated to their equivalents in UniversalString, and encoded in UTF-8 [9].
如果是电传字符串形式，则字符将被音译为UniversalString中的等效字符，并用UTF-8编码[9]。
If it is of the UniversalString or BMPString forms [10], UTF-8 is used to encode them.
如果是UniversalString或BMPString形式[10]，则使用UTF-8对其进行编码。
Note: the form of DirectoryString is not indicated in protocol unless the attribute value is carried in binary. Servers which convert to DAP MUST choose an appropriate form. Servers MUST NOT reject values merely because they contain legal Unicode characters outside of the range of printable ASCII.
注意：除非属性值以二进制形式携带，否则协议中未指明DirectoryString的形式。转换为DAP的服务器必须选择适当的形式。服务器不能仅仅因为包含超出可打印ASCII范围的合法Unicode字符而拒绝值。
Example:
例子：
This is a string of DirectoryString containing #!%#@
This is a string of DirectoryString containing #!%#@
( 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说明“DIT内容规则说明”）
Values in this syntax are encoded according to the following BNF. Implementors should note that future versions of this document may have expanded this BNF to include additional terms.
此语法中的值根据以下BNF进行编码。实施者应注意，本文档的未来版本可能已经扩展了此BNF，以包括其他术语。
DITContentRuleDescription = "("
numericoid ; Structural ObjectClass identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" ]
[ "AUX" oids ] ; Auxiliary ObjectClasses
[ "MUST" oids ] ; AttributeType identifiers
[ "MAY" oids ] ; AttributeType identifiers
[ "NOT" oids ] ; AttributeType identifiers
")"
DITContentRuleDescription = "("
numericoid ; Structural ObjectClass identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" ]
[ "AUX" oids ] ; Auxiliary ObjectClasses
[ "MUST" oids ] ; AttributeType identifiers
[ "MAY" oids ] ; AttributeType identifiers
[ "NOT" oids ] ; AttributeType identifiers
")"
( 1.3.6.1.4.1.1466.115.121.1.22 DESC 'Facsimile Telephone Number' )
（1.3.6.1.4.1.1466.115.121.1.22描述“传真电话号码”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
fax-number = printablestring [ "$" faxparameters ]
传真号码=可打印字符串[“$”传真参数]
faxparameters = faxparm / ( faxparm "$" faxparameters )
faxparameters=faxparm/（faxparm“$”faxparameters）
faxparm = "twoDimensional" / "fineResolution" /
"unlimitedLength" /
"b4Length" / "a3Width" / "b4Width" / "uncompressed"
faxparm = "twoDimensional" / "fineResolution" /
"unlimitedLength" /
"b4Length" / "a3Width" / "b4Width" / "uncompressed"
In the above, the first printablestring is the telephone number, based on E.123 [15], and the faxparm tokens represent fax parameters.
在上面，第一个可打印字符串是基于E.123[15]的电话号码，faxparm令牌表示传真参数。
( 1.3.6.1.4.1.1466.115.121.1.23 DESC 'Fax' )
（1.3.6.1.4.1.1466.115.121.1.23说明“传真”）
Values in this syntax are encoded as if they were octet strings containing Group 3 Fax images as defined in [7].
此语法中的值被编码为包含[7]中定义的第3组传真图像的八进制字符串。
( 1.3.6.1.4.1.1466.115.121.1.24 DESC 'Generalized Time' )
（1.3.6.1.4.1.1466.115.121.1.24描述“广义时间”）
Values in this syntax are encoded as printable strings, represented as specified in X.208. Note that the time zone must be specified. It is strongly recommended that GMT time be used. For example,
此语法中的值编码为可打印字符串，如X.208中所述。请注意，必须指定时区。强烈建议使用GMT时间。例如
199412161032Z
199412161032Z
( 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描述“IA5串”）
The encoding of a value in this syntax is the string value itself.
此语法中的值编码是字符串值本身。
( 1.3.6.1.4.1.1466.115.121.1.27 DESC 'INTEGER' )
（1.3.6.1.4.1.1466.115.121.1.27描述“整数”）
Values in this syntax are encoded as the decimal representation of their values, with each decimal digit represented by the its character equivalent. So the number 1321 is represented by the character string "1321".
此语法中的值被编码为其值的十进制表示形式，每个十进制数字由其等效字符表示。因此，数字1321由字符串“1321”表示。
( 1.3.6.1.4.1.1466.115.121.1.28 DESC 'JPEG' )
（1.3.6.1.4.1.1466.115.121.1.28描述“JPEG”）
Values in this syntax are encoded as strings containing JPEG images in the JPEG File Interchange Format (JFIF), as described in [8].
此语法中的值被编码为包含JPEG文件交换格式（JFIF）的JPEG图像的字符串，如[8]所述。
( 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描述“匹配规则说明”）
Values of type matchingRules are encoded as strings according to the BNF given in section 4.5.
类型匹配规则的值根据第4.5节中给出的BNF编码为字符串。
( 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描述“匹配规则使用说明”）
Values of type matchingRuleUse are encoded as strings according to the BNF given in section 4.5.
matchingRuleUse类型的值根据第4.5节中给出的BNF编码为字符串。
( 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描述“MHS或地址”）
Values in this syntax are encoded as strings, according to the format defined in [11].
此语法中的值按照[11]中定义的格式编码为字符串。
( 1.3.6.1.4.1.1466.115.121.1.34 DESC 'Name And Optional UID' )
（1.3.6.1.4.1.1466.115.121.1.34描述“名称和可选UID”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
NameAndOptionalUID = DistinguishedName [ "#" bitstring ]
NameAndOptionalUID=区分名称[“#”位字符串]
Although the '#' character may occur in a string representation of a distinguished name, no additional special quoting is done. This syntax has been added subsequent to RFC 1778.
尽管“#”字符可能出现在可分辨名称的字符串表示形式中，但不会进行额外的特殊引用。此语法是在RFC 1778之后添加的。
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
( 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描述“姓名表说明”）
Values in this syntax are encoded according to the following BNF. Implementors should note that future versions of this document may have expanded this BNF to include additional terms.
此语法中的值根据以下BNF进行编码。实施者应注意，本文档的未来版本可能已经扩展了此BNF，以包括其他术语。
NameFormDescription = "(" whsp
numericoid whsp ; NameForm identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
"OC" woid ; Structural ObjectClass
"MUST" oids ; AttributeTypes
[ "MAY" oids ] ; AttributeTypes
whsp ")"
NameFormDescription = "(" whsp
numericoid whsp ; NameForm identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
"OC" woid ; Structural ObjectClass
"MUST" oids ; AttributeTypes
[ "MAY" oids ] ; AttributeTypes
whsp ")"
( 1.3.6.1.4.1.1466.115.121.1.36 DESC 'Numeric String' )
（1.3.6.1.4.1.1466.115.121.1.36描述“数字字符串”）
The encoding of a string in this syntax is the string value itself. Example:
此语法中字符串的编码是字符串值本身。例子：
1997
1997
( 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描述“对象类别说明”）
Values in this syntax are encoded according to the BNF in section 4.4.
此语法中的值根据第4.4节中的BNF进行编码。
( 1.3.6.1.4.1.1466.115.121.1.38 DESC 'OID' )
（1.3.6.1.4.1.1466.115.121.1.38说明“OID”）
Values in the Object Identifier syntax are encoded according to the BNF in section 4.1 for "oid".
对象标识符语法中的值根据第4.1节中“oid”的BNF进行编码。
Example:
例子：
1.2.3.4 cn
1.2.3.4 cn
( 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描述“其他邮箱”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
otherMailbox = mailbox-type "$" mailbox
otherMailbox=邮箱类型“$”邮箱
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 which the mailbox resides, for example "MCIMail"; and mailbox is the actual mailbox in the mail system defined by mailbox-type.
在上面的示例中，邮箱类型表示邮箱所在的邮件系统的类型，例如“MCIMail”；邮箱是邮件系统中由邮箱类型定义的实际邮箱。
( 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描述“邮政地址”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
postal-address = dstring *( "$" dstring )
邮政地址=dstring*（“$”dstring）
In the above, each dstring component of a postal address value is encoded as a value of type Directory String syntax. Backslashes and dollar characters, if they occur in the component, are quoted as described in section 4.3. Many servers limit the postal address to six lines of up to thirty characters.
在上面，邮政地址值的每个dstring组件都被编码为目录字符串语法类型的值。如果反斜杠和美元字符出现在部件中，则按照第4.3节所述引用。许多服务器将邮政地址限制为6行，最多30个字符。
Example:
例子：
1234 Main St.$Anytown, CA 12345$USA \241,000,000 Sweepstakes$PO Box 1000000$Anytown, CA 12345$USA
1234 Main St.$Anytown，加利福尼亚州12345$USA\241000000抽奖$PO Box 1000000$Anytown，加利福尼亚州12345$USA
( 1.3.6.1.4.1.1466.115.121.1.43 DESC 'Presentation Address' )
（1.3.6.1.4.1.1466.115.121.1.43描述“展示地址”）
Values in this syntax are encoded with the representation described in RFC 1278 [6].
此语法中的值使用RFC 1278[6]中描述的表示进行编码。
( 1.3.6.1.4.1.1466.115.121.1.44 DESC 'Printable String' )
（1.3.6.1.4.1.1466.115.121.1.44描述“可打印字符串”）
The encoding of a value in this syntax is the string value itself. PrintableString is limited to the characters in production p of section 4.1.
此语法中的值编码是字符串值本身。可打印字符串仅限于第4.1节产品p中的字符。
Example:
例子：
This is a PrintableString
这是一个可打印的字符串
( 1.3.6.1.4.1.1466.115.121.1.50 DESC 'Telephone Number' )
（1.3.6.1.4.1.1466.115.121.1.50描述“电话号码”）
Values in this syntax are encoded as if they were Printable String types. Telephone numbers are recommended in X.520 to be in international form, as described in E.123 [15].
此语法中的值被编码为可打印的字符串类型。如E.123[15]所述，X.520中建议电话号码采用国际形式。
Example:
例子：
+1 512 305 0280
+1 512 305 0280
( 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描述“UTC时间”）
Values in this syntax are encoded as if they were printable strings with the strings containing a UTCTime value. This is historical; new attribute definitions SHOULD use GeneralizedTime instead.
此语法中的值被编码为可打印字符串，字符串包含UTCTime值。这是历史的,；新属性定义应改为使用GeneratedTime。
( 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描述“LDAP语法描述”）
Values in this syntax are encoded according to the BNF in section 4.3.3.
此语法中的值根据第4.3.3节中的BNF进行编码。
( 1.3.6.1.4.1.1466.115.121.1.17 DESC 'DIT Structure Rule Description' )
（1.3.6.1.4.1.1466.115.121.1.17说明“DIT结构规则说明”）
Values with this syntax are encoded according to the following BNF:
具有此语法的值根据以下BNF进行编码：
DITStructureRuleDescription = "(" whsp
ruleidentifier whsp ; DITStructureRule identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
"FORM" woid whsp ; NameForm
[ "SUP" ruleidentifiers whsp ] ; superior DITStructureRules
")"
DITStructureRuleDescription = "(" whsp
ruleidentifier whsp ; DITStructureRule identifier
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
"FORM" woid whsp ; NameForm
[ "SUP" ruleidentifiers whsp ] ; superior DITStructureRules
")"
ruleidentifier = integer
ruleidentifier = integer
ruleidentifiers = ruleidentifier | "(" whsp ruleidentifierlist whsp ")"
规则标识符=规则标识符|“（“whsp规则标识符列表whsp”）”
ruleidentifierlist = [ ruleidentifier *( ruleidentifier ) ]
ruleidentifierlist = [ ruleidentifier *( ruleidentifier ) ]
Servers SHOULD recognize all the names of standard classes from section 7 of [12].
服务器应识别[12]第7节中标准类的所有名称。
The extensibleObject object class, if present in an entry, permits that entry to optionally hold any attribute. The MAY attribute list of this class is implicitly the set of all attributes.
extensibleObject对象类（如果存在于条目中）允许该条目选择性地保存任何属性。此类的MAY属性列表隐式地是所有属性的集合。
( 1.3.6.1.4.1.1466.101.120.111 NAME 'extensibleObject' SUP top AUXILIARY )
（1.3.6.1.4.1.1466.101.120.111名称“可扩展对象”辅助顶部辅助）
The mandatory attributes of the other object classes of this entry are still required to be present.
此条目的其他对象类的强制属性仍然需要存在。
Note that not all servers will implement this object class, and those which do not will reject requests to add entries which contain this object class, or modify an entry to add this object class.
请注意，并非所有服务器都将实现此对象类，否则将拒绝添加包含此对象类的条目或修改条目以添加此对象类的请求。
This object class is used in the subschema entry.
此对象类用于子模式条目中。
( 2.5.20.1 NAME 'subschema' AUXILIARY MAY ( dITStructureRules $ nameForms $ ditContentRules $ objectClasses $ attributeTypes $ matchingRules $ matchingRuleUse ) )
（2.5.20.1名称“子模式”辅助可能（dITStructureRules$nameForms$ditContentRules$objectClasses$AttributeType$matchingRules$matchingRuleUse））
The ldapSyntaxes operational attribute may also be present in subschema entries.
ldapSyntaxes操作属性也可能出现在子模式条目中。
Servers which implement the extensibleMatch filter SHOULD allow all the matching rules listed in this section to be used in the extensibleMatch. In general these servers SHOULD allow matching 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 syntax of the attribute.
实现extensibleMatch筛选器的服务器应允许在extensibleMatch中使用本节中列出的所有匹配规则。通常，当匹配规则的断言语法与属性的值语法相同时，这些服务器应允许将匹配规则用于服务器已知的所有属性类型。
Servers MAY implement additional 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 syntax.
对于所有这些规则，断言语法与值语法相同。
( 2.5.13.0 NAME 'objectIdentifierMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
（2.5.13.0名称“objectIdentifierMatch”语法1.3.6.1.4.1.1466.115.121.1.38）
If the client supplies a filter using an objectIdentifierMatch whose matchValue oid is in the "descr" form, and the oid is not recognized by the server, then the filter is Undefined.
如果客户端使用objectIdentifierMatch提供筛选器，其matchValue oid为“descr”格式，并且服务器无法识别该oid，则该筛选器未定义。
( 2.5.13.1 NAME 'distinguishedNameMatch'
（2.5.13.1名称“区分名称匹配”
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
语法1.3.6.1.4.1.1466.115.121.1.12）
( 2.5.13.2 NAME 'caseIgnoreMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（2.5.13.2名称“caseIgnoreMatch”语法1.3.6.1.4.1.1466.115.121.1.15）
( 2.5.13.8 NAME 'numericStringMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.36 )
（2.5.13.8名称“numericStringMatch”语法1.3.6.1.4.1.1466.115.121.1.36）
( 2.5.13.11 NAME 'caseIgnoreListMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
（2.5.13.11名称“caseIgnoreListMatch”语法1.3.6.1.4.1.1466.115.121.1.41）
( 2.5.13.14 NAME 'integerMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )
（2.5.13.14名称“integerMatch”语法1.3.6.1.4.1.1466.115.121.1.27）
( 2.5.13.16 NAME 'bitStringMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.6 )
（2.5.13.16名称“bitStringMatch”语法1.3.6.1.4.1.1466.115.121.1.6）
( 2.5.13.20 NAME 'telephoneNumberMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 )
（2.5.13.20名称“电话号码格式”语法1.3.6.1.4.1.1466.115.121.1.50）
( 2.5.13.22 NAME 'presentationAddressMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.43 )
（2.5.13.22名称“presentationAddressMatch”语法1.3.6.1.4.1.1466.115.121.1.43）
( 2.5.13.23 NAME 'uniqueMemberMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 )
（2.5.13.23名称“uniqueMemberMatch”语法1.3.6.1.4.1.1466.115.121.1.34）
( 2.5.13.24 NAME 'protocolInformationMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.42 )
（2.5.13.24名称“协议信息匹配”语法1.3.6.1.4.1.1466.115.121.1.42）
( 2.5.13.27 NAME 'generalizedTimeMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 )
（2.5.13.27名称“GeneratedTimeMatch”语法1.3.6.1.4.1.1466.115.121.1.24）
( 1.3.6.1.4.1.1466.109.114.1 NAME 'caseExactIA5Match' SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
（1.3.6.1.4.1.1466.109.114.1名称“caseExactIA5Match”语法1.3.6.1.4.1.1466.115.121.1.26）
( 1.3.6.1.4.1.1466.109.114.2 NAME 'caseIgnoreIA5Match' SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
（1.3.6.1.4.1.1466.109.114.2名称“caseIgnoreIA5Match”语法1.3.6.1.4.1.1466.115.121.1.26）
When performing the caseIgnoreMatch, caseIgnoreListMatch, telephoneNumberMatch, caseExactIA5Match and caseIgnoreIA5Match, multiple adjoining whitespace characters are treated the same as an individual space, and leading and trailing whitespace is ignored.
在执行caseIgnoreMatch、caseIgnoreListMatch、telephoneNumberMatch、caseExactIA5Match和caseIgnoreIA5Match时，多个相邻的空格字符被视为一个单独的空格，前导和尾随空格被忽略。
Clients MUST NOT assume that servers are capable of transliteration of Unicode values.
客户端不能假设服务器能够音译Unicode值。
Servers SHOULD be capable of performing the following matching rules, which are used in greaterOrEqual and lessOrEqual filters.
服务器应该能够执行以下匹配规则，这些规则在GreaterEqual和lessOrEqual筛选器中使用。
( 2.5.13.28 NAME 'generalizedTimeOrderingMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 )
（2.5.13.28名称“generalizedTimeOrderingMatch”语法1.3.6.1.4.1.1466.115.121.1.24）
( 2.5.13.3 NAME 'caseIgnoreOrderingMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（2.5.13.3名称“caseIgnoreOrderingMatch”语法1.3.6.1.4.1.1466.115.121.1.15）
The sort ordering for a caseIgnoreOrderingMatch is implementation-dependent.
caseIgnoreOrderingMatch的排序顺序取决于实现。
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' )
（1.3.6.1.4.1.1466.115.121.1.58描述“子字符串断言”）
The Substring Assertion is encoded according to the following BNF:
子字符串断言根据以下BNF编码：
substring = [initial] any [final]
initial = value
any = "*" *(value "*")
final = value
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.
<value>产品是UTF-8编码的字符串。如果反斜杠或星号字符出现在<value>的产品中，则按照第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.4名称“caseIgnoreSubstringsMatch”语法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.21名称“电话号码substringsmatch”语法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 )
（2.5.13.10名称“numericStringSubstringsMatch”语法1.3.6.1.4.1.1466.115.121.1.58）
Servers which allow subschema entries to be modified by clients MUST support the following matching rules, as they are the equality 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.29名称“integerFirstComponentMatch”语法1.3.6.1.4.1.1466.115.121.1.27）
( 2.5.13.30 NAME 'objectIdentifierFirstComponentMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
（2.5.13.30名称'objectIdentifierFirstComponentMatch'语法1.3.6.1.4.1.1466.115.121.1.38）
Implementors should note that the assertion syntax of these matching rules, an INTEGER or OID, is different from the value syntax of attributes for which this is the equality matching rule.
实现者应该注意，这些匹配规则（整数或OID）的断言语法不同于属性的值语法，这是相等匹配规则。
If the client supplies an extensible filter using an objectIdentifierFirstComponentMatch whose matchValue is in the "descr" form, and the OID is not recognized by the server, then the filter is Undefined.
如果客户端使用objectIdentifierFirstComponentMatch（其匹配值为“descr”格式）提供可扩展筛选器，并且服务器无法识别OID，则该筛选器未定义。
Attributes of directory entries are used to provide descriptive information about the real-world objects they represent, which can be people, organizations or devices. Most countries have privacy laws regarding the publication of information about people.
目录项的属性用于提供有关它们所表示的真实对象的描述性信息，这些对象可以是人、组织或设备。大多数国家都有关于发布个人信息的隐私法。
The transformations of an AttributeValue value from its X.501 form to an LDAP string representation are not always reversible back to 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 certificate.
AttributeValue值从其X.501形式到LDAP字符串表示形式的转换并不总是可逆地返回到相同的BER或DER形式。验证X.509证书是需要可分辨名称的DER格式的一个示例。
For example, a distinguished name consisting of one RDN with one AVA, in which the type is commonName and the value is of the TeletexString choice with the letters 'Sam' would be represented in LDAP as the string CN=Sam. Another distinguished name in which the value is still 'Sam' but of the PrintableString choice would have the same representation CN=Sam.
例如，由一个RDN和一个AVA组成的可分辨名称，其中类型为commonName，值为TeletextString选项，字母为“Sam”，在LDAP中表示为字符串CN=Sam。另一个可分辨名称，其中值仍然为“Sam”，但为可打印字符串选项，其表示形式为CN=Sam。
Applications which require the reconstruction of the DER form of the value SHOULD NOT use the string representation of attribute syntaxes when converting a value to LDAP format. Instead it SHOULD use the
在将值转换为LDAP格式时，需要重构值的顺序形式的应用程序不应使用属性语法的字符串表示。相反，它应该使用
Binary syntax.
二进制语法。
This document is based substantially on RFC 1778, written by Tim Howes, Steve Kille, Wengyik Yeong and Colin Robbins.
本文件主要基于蒂姆·豪斯、史蒂夫·基尔、杨文杰和科林·罗宾斯撰写的RFC 1778。
Many of the attribute syntax encodings defined in this and related documents are adapted from those used in the QUIPU and the IC R3 X.500 implementations. The contributions of the authors of both these implementations in the specification of syntaxes are gratefully acknowledged.
本文档和相关文档中定义的许多属性语法编码都是从QUIPU和IC R3 X.500实现中使用的编码改编而来的。感谢这两个实现的作者在语法规范中的贡献。
Mark Wahl Critical Angle Inc. 4815 West Braker Lane #502-385 Austin, TX 78759 USA
马克·沃尔临界角公司，美国德克萨斯州奥斯汀市西布雷克巷4815号，502-385号，邮编78759
Phone: +1 512 372-3160
EMail: M.Wahl@critical-angle.com
Phone: +1 512 372-3160
EMail: M.Wahl@critical-angle.com
Andy Coulbeck Isode Inc. 9390 Research Blvd Suite 305 Austin, TX 78759 USA
Andy Coulbeck Isode Inc.美国德克萨斯州奥斯汀研究大道9390号305室，邮编78759
Phone: +1 512 231-8993
EMail: A.Coulbeck@isode.com
Phone: +1 512 231-8993
EMail: A.Coulbeck@isode.com
Tim Howes Netscape Communications Corp. 501 E. Middlefield Rd, MS MV068 Mountain View, CA 94043 USA
Tim Howes Netscape Communications Corp.美国加利福尼亚州山景城MV068米德菲尔德东路501号，邮编94043
Phone: +1 650 937-3419
EMail: howes@netscape.com
Phone: +1 650 937-3419
EMail: howes@netscape.com
Steve Kille Isode Limited The Dome, The Square Richmond TW9 1DT UK
Steve Kille Isode有限公司位于英国里士满TW9 1DT广场的穹顶
Phone: +44-181-332-9091
EMail: S.Kille@isode.com
Phone: +44-181-332-9091
EMail: S.Kille@isode.com
[1] Wahl, M., Howes, T., and S. Kille, "Lightweight Directory Access Protocol (v3)", RFC 2251, December 1997.
[1] Wahl，M.，Howes，T.，和S.Kille，“轻量级目录访问协议（v3）”，RFC 2251，1997年12月。
[2] The Directory: Selected Attribute Types. ITU-T Recommendation X.520, 1993.
[2] 目录：选定的属性类型。ITU-T建议X.520，1993年。
[3] The Directory: Models. ITU-T Recommendation X.501, 1993.
[3] 目录：Models。ITU-T建议X.501，1993年。
[4] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997.
[4] Bradner，S.，“RFC中用于表示需求水平的关键词”，RFC 211997年3月。
[5] Wahl, M., Kille, S., and T. Howes, "Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names", RFC 2253, December 1997.
[5] Wahl，M.，Kille，S.，和T.Howes，“轻量级目录访问协议（v3）：可分辨名称的UTF-8字符串表示”，RFC 2253，1997年12月。
[6] Kille, S., "A String Representation for Presentation Addresses", RFC 1278, November 1991.
[6] Kille，S.，“表示地址的字符串表示法”，RFC 12781991年11月。
[7] Terminal Equipment and Protocols for Telematic Services - Standardization of Group 3 facsimile apparatus for document transmission. CCITT, Recommendation T.4.
[7] 远程信息处理服务用终端设备和协议.文件传输用第3组传真设备的标准化。CCITT，建议T.4。
[8] JPEG File Interchange Format (Version 1.02). Eric Hamilton, C-Cube Microsystems, Milpitas, CA, September 1, 1992.
[8] JPEG文件交换格式（版本1.02）。埃里克·汉密尔顿，C-Cube微系统公司，加利福尼亚州米尔皮塔斯，1992年9月1日。
[9] Yergeau, F., "UTF-8, a transformation format of Unicode and ISO 10646", RFC 2044, October 1996.
[9] “UTF-8，Unicode和ISO10646的转换格式”，RFC 2044，1996年10月。
[10] Universal Multiple-Octet Coded Character Set (UCS) - Architecture and Basic Multilingual Plane, ISO/IEC 10646-1 : 1993 (With amendments).
[10] 通用多八位编码字符集（UCS）.体系结构和基本多语言平面，ISO/IEC 10646-1:1993（含修订件）。
[11] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822", RFC 1327, May 1992.
[11] Hardcastle Kille，S.，“X.400（1988）/ISO 10021和RFC 822之间的映射”，RFC 1327，1992年5月。
[12] Wahl, M., "A Summary of the X.500(96) User Schema for use with LDAPv3", RFC 2256, December 1997.
[12] Wahl，M.，“与LDAPv3一起使用的X.500（96）用户模式摘要”，RFC 2256，1997年12月。
[13] Crocker, D., "Standard of the Format of ARPA-Internet Text Messages", STD 11, RFC 822, August 1982.
[13] Crocker，D.，“ARPA互联网文本信息格式标准”，STD 11，RFC 822，1982年8月。
[14] ISO 3166, "Codes for the representation of names of countries".
[14] ISO 3166，“国家名称表示代码”。
[15] ITU-T Rec. E.123, Notation for national and international telephone numbers, 1988.
[15] ITU-T Rec.E.123，《国家和国际电话号码符号》，1988年。
Copyright (C) The Internet Society (1997). All Rights Reserved.
版权所有（C）互联网协会（1997年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。