Network Working Group K. Zeilenga
Request for Comments: 3383 OpenLDAP Foundation
BCP: 64 September 2002
Category: Best Current Practice
Network Working Group K. Zeilenga
Request for Comments: 3383 OpenLDAP Foundation
BCP: 64 September 2002
Category: Best Current Practice
Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)
轻量级目录访问协议（LDAP）的Internet分配号码管理局（IANA）注意事项
Status of this Memo
本备忘录的状况
This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This document provides procedures for registering extensible elements of the Lightweight Directory Access Protocol (LDAP). This document also provides guidelines to the Internet Assigned Numbers Authority (IANA) describing conditions under which new values can be assigned.
本文档提供了注册轻量级目录访问协议（LDAP）的可扩展元素的过程。本文件还向互联网分配号码管理局（IANA）提供了指南，说明可以分配新值的条件。
The Lightweight Directory Access Protocol (LDAP) [RFC3377] is an extensible protocol. LDAP supports:
轻量级目录访问协议（LDAP）[RFC3377]是一种可扩展协议。LDAP支持：
- addition of new operations, - extension of existing operations, and - extensible schema.
- 添加新操作、-扩展现有操作和-可扩展模式。
This document details procedures for registering values of used to unambiguously identify extensible elements of the protocol including:
本文件详细说明了注册用于明确标识协议可扩展元素的值的程序，包括：
- LDAP message types; - LDAP extended operations and controls; - LDAP result codes; - LDAP authentication methods; - LDAP attribute description options; and - Object Identifier descriptors.
- LDAP消息类型；-LDAP扩展操作和控制；-LDAP结果代码；-LDAP身份验证方法；-LDAP属性描述选项；和-对象标识符描述符。
These registries are maintained by the Internet Assigned Numbers Authority (IANA).
这些登记册由互联网分配号码管理局（IANA）维护。
In addition, this document provides guidelines to IANA describing the conditions under which new values can be assigned.
此外，本文件为IANA提供了指南，说明了可分配新值的条件。
This section details terms and conventions used in this document.
本节详细介绍了本文件中使用的术语和约定。
The terms "IESG Approval", "Standards Action", "IETF Consensus", "Specification Required", "First Come First Served", "Expert Review", and "Private Use" are used as defined in BCP 26 [RFC2434].
术语“IESG批准”、“标准行动”、“IETF共识”、“所需规范”、“先到先得”、“专家评审”和“私人使用”的使用如BCP 26[RFC2434]所定义。
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 BCP 14 [RFC2119]. In this case, "the specification" as used by BCP 14 refers to the processing of protocols being submitted to the IETF standards process.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14[RFC2119]中所述进行解释。在这种情况下，BCP 14使用的“规范”指的是提交给IETF标准过程的协议处理。
A number of syntaxes in this document are described using ABNF [RFC2234]. These syntaxes rely on the following common productions:
本文档中的许多语法使用ABNF[RFC2234]进行描述。这些语法依赖于以下常见结果：
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
LDIGIT = %x31-39 ; 1-9
LDIGIT = %x31-39 ; 1-9
DIGIT = %x30 / LDIGIT ; 0-9
DIGIT = %x30 / LDIGIT ; 0-9
HYPHEN = %x2D ; "-"
HYPHEN = %x2D ; "-"
DOT = %x2E ; "."
DOT = %x2E ; "."
number = DIGIT / ( LDIGIT 1*DIGIT )
number = DIGIT / ( LDIGIT 1*DIGIT )
keychar = ALPHA / DIGIT / HYPHEN
keychar = ALPHA / DIGIT / HYPHEN
leadkeychar = ALPHA
leadkeychar = ALPHA
keystring = leadkeychar *keychar
keystring=leadkeychar*keychar
A keyword is a case-insensitive string of UTF-8 [RFC2279] encoded characters from the Universal Character Set (UCS) [ISO10646] restricted to the <keystring> production.
关键字是来自通用字符集（UCS）[ISO10646]的UTF-8[RFC2279]编码字符的不区分大小写字符串，仅限于<keystring>产品。
This section details each kind of protocol value which can be registered and provides IANA guidelines on how to assign new values.
本节详细介绍了可以注册的每种协议值，并提供了IANA关于如何分配新值的指南。
IANA may reject obviously bogus registration requests.
IANA可能会拒绝明显虚假的注册请求。
Numerous LDAP schema and protocol elements are identified by Object Identifiers. Specifications which assign OIDs to elements SHOULD state who delegated the OIDs for its use.
许多LDAP模式和协议元素由对象标识符标识。将OID分配给元素的规范应说明是谁委托OID使用。
For IETF developed elements, specifications SHOULD use OIDs under "Internet Directory Numbers" (1.3.6.1.1.x). Numbers under this OID arc will be assigned upon Expert Review with Specification Required. Only one OID per specification will be assigned. The specification MAY then assign any number of OIDs within this arc without further coordination with IANA.
对于IETF开发的元件，规范应使用“互联网目录号”（1.3.6.1.1.x）下的OID。本OID arc下的编号将在专家审查后指定，并提供所需的规范。每个规范仅分配一个OID。然后，规范可在此arc内分配任意数量的OID，而无需与IANA进一步协调。
For elements developed by others, any properly delegated OID can be used, including those under "Internet Private Enterprise Numbers" (1.3.6.1.4.1.x) assigned by IANA <http://www.iana.org/cgi-bin/enterprise.pl>.
对于其他人开发的元素，可以使用任何适当授权的OID，包括IANA指定的“互联网私有企业编号”（1.3.6.1.4.1.x）下的OID<http://www.iana.org/cgi-bin/enterprise.pl>.
To avoid interoperability problems between early implementations of "works in progress" and implementations of the published specification (e.g., the RFC), experimental OIDs SHOULD be used in "works in progress" and early implementations. OIDs under the Internet Experimental OID arc (1.3.6.1.3.x) may be used for this purpose.
为了避免“正在进行的工作”的早期实现和已发布规范（如RFC）的实现之间的互操作性问题，应在“正在进行的工作”和早期实现中使用实验OID。互联网实验OID arc（1.3.6.1.3.x）下的OID可用于此目的。
Experimental OIDs are not to used in published specifications (e.g., RFCs).
试验OID不得用于已发布的规范（如RFC）。
Practices for IANA assignment of Internet Enterprise and Experimental OIDs are detailed in STD 16 [RFC1155].
STD 16[RFC1155]详细介绍了互联网企业和实验OID的IANA分配实践。
LDAP provides a number of Root DSE attributes for discovery of protocol mechanisms identified by OIDs, including:
LDAP提供了许多根DSE属性，用于发现由OID标识的协议机制，包括：
- supportedControl [RFC2252] and - supportedExtension [RFC2252].
- supportedControl[RFC2252]和-supportedExtension[RFC2252]。
A registry of OIDs used for discover of protocol mechanisms is provided to allow implementors and others to locate the technical specification for these protocol mechanisms. Future specifications of additional Root DSE attributes holding values identifying protocol mechanisms MAY extend this registry for their values.
提供了用于发现协议机制的OID注册表，以允许实现者和其他人找到这些协议机制的技术规范。持有用于识别协议机制的值的附加根DSE属性的未来规范可能会扩展此注册表以获取其值。
OIDs associated with discoverable protocol mechanisms SHOULD be registered. These are be considered on a First Come First Served with Specification Required basis.
应注册与可发现协议机制关联的OID。应按照先到先得的原则考虑这些问题，并提供所需的规范。
OIDs associated with Standard Track mechanisms MUST be registered and require Standards Action.
必须注册与标准跟踪机制关联的OID，并要求执行标准操作。
LDAP allows short descriptive names (or descriptors) to be used instead of a numeric Object Identifier to identify protocol extensions [RFC2251], schema elements [RFC2252], LDAP URL [RFC2255] extensions, and other objects. Descriptors are restricted to strings of UTF-8 encoded UCS characters restricted by the following ABNF:
LDAP允许使用简短的描述性名称（或描述符）而不是数字对象标识符来标识协议扩展[RFC2251]、模式元素[RFC2252]、LDAP URL[RFC2255]扩展和其他对象。描述符仅限于UTF-8编码UCS字符的字符串，这些字符受以下ABNF限制：
name = keystring
name = keystring
Descriptors are case-insensitive.
描述符不区分大小写。
Multiple names may be assigned to a given OID. For purposes of registration, an OID is to be represented in numeric OID form conforming to the ABNF:
可以为给定OID分配多个名称。出于注册目的，OID应以符合ABNF的数字OID形式表示：
numericoid = number *( DOT number ) ; e.g., 1.1.0.23.40
numericoid = number *( DOT number ) ; e.g., 1.1.0.23.40
While the protocol places no maximum length restriction upon descriptors, they should be short. Descriptors longer than 48 characters may be viewed as too long to register.
虽然协议没有对描述符设置最大长度限制，但是描述符应该很短。超过48个字符的描述符可能被视为太长而无法注册。
A values ending with a hyphen ("-") reserve all descriptors which start with the value. For example, the registration of the option "descrFamily-" reserves all options which start with "descrFamily-" for some related purpose.
以连字符（“-”）结尾的值保留所有以该值开头的描述符。例如，注册选项“descrFamily-”将保留所有以“descrFamily-”开头的选项，以用于某些相关目的。
Descriptors beginning with "x-" are for Private Use and cannot be registered.
以“x-”开头的描述符仅供私人使用，不能注册。
Descriptors beginning with "e-" are reserved for experiments and will be registered on a First Come First Served basis.
以“e-”开头的描述符保留用于实验，并将按照先到先得的原则进行注册。
All other descriptors require Expert Review to be registered.
所有其他描述符都需要注册专家评审。
The registrant need not "own" the OID being named.
注册人不需要“拥有”被命名的OID。
The OID namespace is managed by The ISO/IEC Joint Technical Committee 1 - Subcommittee 6.
OID名称空间由ISO/IEC联合技术委员会1-小组委员会6管理。
An AttributeDescription [RFC2251, Section 4.1.5] can contain zero or more options specifying additional semantics. An option SHALL be restricted to a string UTF-8 encoded UCS characters limited by the following ABNF:
属性描述[RFC2251，第4.1.5节]可以包含零个或多个指定附加语义的选项。选项应限制为以下ABNF限制的字符串UTF-8编码UCS字符：
option = keystring
option = keystring
Options are case-insensitive.
选项不区分大小写。
While the protocol places no maximum length restriction upon option strings, they should be short. Options longer than 24 characters may be viewed as too long to register.
虽然协议对选项字符串没有最大长度限制，但它们应该很短。超过24个字符的选项可能被视为太长而无法注册。
Values ending with a hyphen ("-") reserve all option names which start with the name. For example, the registration of the option "optionFamily-" reserves all options which start with "optionFamily-" for some related purpose.
以连字符（“-”）结尾的值保留以该名称开头的所有选项名称。例如，选项“optionFamily-”的注册保留了所有以“optionFamily-”开头的选项，用于某些相关目的。
Options beginning with "x-" are for Private Use and cannot be registered.
以“x-”开头的选项仅供私人使用，不能注册。
Options beginning with "e-" are reserved for experiments and will be registered on a First Come First Served basis.
以“e-”开头的选项保留用于实验，并将以先到先得的方式注册。
All other options require Standards Action or Expert Review with Specification Required to be registered.
所有其他选项需要标准行动或专家审查，规范需要注册。
Each protocol message is encapsulated in an LDAPMessage envelope [RFC2251, Section 4.1.1]. The protocolOp CHOICE indicates the type of message encapsulated. Each message type consists of a keyword and a non-negative choice number is combined with the class (APPLICATION) and data type (CONSTRUCTED or PRIMITIVE) to construct the BER tag in the message's encoding. The choice numbers for existing protocol messages are implicit in the protocol's ASN.1 defined in [RFC2251].
每个协议消息封装在LDAPMessage信封中[RFC2251，第4.1.1节]。protocolOp选项指示封装的消息类型。每种消息类型由一个关键字和一个非负选择号组成，并与类（应用程序）和数据类型（构造的或原语）相结合，以构造消息编码中的BER标记。现有协议消息的选择号隐含在[RFC2251]中定义的协议ASN.1中。
New values will be registered upon Standards Action.
新值将在标准行动时登记。
Note: LDAP provides extensible messages which reduces, but does not eliminate, the need to add new message types.
注意：LDAP提供了可扩展消息，这减少了但并没有消除添加新消息类型的需要。
LDAP result messages carry an resultCode enumerated value to indicate the outcome of the operation [RFC2251, Section 4.1.10]. Each result code consists of a keyword and a non-negative integer.
LDAP结果消息带有resultCode枚举值，以指示操作的结果[RFC2251，第4.1.10节]。每个结果代码由一个关键字和一个非负整数组成。
New resultCodes integers in the range 0-1023 require Standards Action to be registered. New resultCode integers in the range 1024-4095 require Expert Review with Specification Required. New resultCode integers in the range 4096-16383 will be registered on a First Come First Served basis. Keywords associated with integers in the range 0-4095 SHALL NOT start with "e-" or "x-". Keywords associated with integers in the range 4096-16383 SHALL start with "e-". Values greater than or equal to 16384 and keywords starting with "x-" are for Private Use and cannot be registered.
范围为0-1023的新resultCodes整数需要注册标准操作。1024-4095范围内的新resultCode整数需要专家审查，并需要规范。范围为4096-16383的新resultCode整数将以先到先得的方式注册。与0-4095范围内整数相关的关键字不得以“e-”或“x-”开头。与4096-16383范围内的整数关联的关键字应以“e-”开头。大于或等于16384的值和以“x-”开头的关键字仅供私人使用，无法注册。
The LDAP Bind operation supports multiple authentication methods [RFC2251, Section 4.2]. Each authentication choice consists of a keyword and a non-negative integer.
LDAP绑定操作支持多种身份验证方法[RFC2251，第4.2节]。每个身份验证选项由一个关键字和一个非负整数组成。
The registrant SHALL classify the authentication method usage using one of the following terms:
注册人应使用以下术语之一对认证方法的使用进行分类：
COMMON - method is appropriate for common use on the Internet, LIMITED USE - method is appropriate for limited use, OBSOLETE - method has been deprecated or otherwise found to be inappropriate for any use.
通用-方法适用于Internet上的通用，有限使用-方法适用于有限使用，过时-方法已被弃用或发现不适合任何用途。
Methods without publicly available specifications SHALL NOT be classified as COMMON. New registrations of class OBSOLETE cannot be registered.
没有公开可用规范的方法不得归类为普通方法。无法注册过时类的新注册。
New authentication method integers in the range 0-1023 require Standards Action to be registered. New authentication method integers in the range 1024-4095 require Expert Review with Specification Required. New authentication method integers in the range 4096-16383 will be registered on a First Come First Served basis. Keywords associated with integers in the range 0-4095 SHALL NOT start with "e-" or "x-". Keywords associated with integers in the range 4096-16383 SHALL start with "e-". Values greater than or equal to 16384 and keywords starting with "x-" are for Private Use and cannot be registered.
范围为0-1023的新身份验证方法整数需要注册标准操作。1024-4095范围内的新身份验证方法整数需要专家审查，并需要规范。范围4096-16383的新身份验证方法整数将以先到先得的方式注册。与0-4095范围内整数相关的关键字不得以“e-”或“x-”开头。与4096-16383范围内的整数关联的关键字应以“e-”开头。大于或等于16384的值和以“x-”开头的关键字仅供私人使用，无法注册。
Note: LDAP supports SASL [RFC2222] as an Authentication CHOICE. SASL is an extensible LDAP authentication method.
注意：LDAP支持SASL[RFC2222]作为身份验证选项。SASL是一种可扩展的LDAP身份验证方法。
The IANA-maintained "Directory Systems Names" registry [IANADSN] of valid keywords for well known attributes used in the LDAPv2 string representation of a distinguished name [RFC1779]. RFC 1779 was obsoleted by RFC 2253.
IANA维护了可分辨名称[RFC1779]的LDAPv2字符串表示中使用的已知属性的有效关键字的“目录系统名称”注册表[IANADSN]。RFC 1779被RFC 2253淘汰。
Directory systems names are not known to be used in any other context. LDAPv3 uses Object Identifier Descriptors [Section 3.2] (which have a different syntax than directory system names).
在任何其他上下文中都无法使用目录系统名称。LDAPv3使用对象标识符描述符[第3.2节]（与目录系统名称的语法不同）。
New Directory System Names will no longer be accepted. For historical purposes, the current list of registered names should remain publicly available.
将不再接受新的目录系统名称。出于历史目的，当前的注册名称列表应保持公开。
The procedure given here MUST be used by anyone who wishes to use a new value of a type described in Section 3 of this document.
希望使用本文件第3节所述类型的新值的任何人必须使用此处给出的程序。
The first step is for the requester to fill out the appropriate form. Templates are provided in Appendix A.
第一步是请求者填写适当的表格。附录A中提供了模板。
If the policy is Standards Action, the completed form SHOULD be provided to the IESG with the request for Standards Action. Upon approval of the Standards Action, the IESG SHALL forward the request (possibly revised) to IANA. The IESG SHALL be viewed as the owner of all values requiring Standards Action.
如果政策是标准行动，则应向IESG提供填写完整的表格以及标准行动请求。在批准标准行动后，IESG应将请求（可能修改）转发给IANA。IESG应被视为所有需要标准行动的价值观的所有者。
If the policy is Expert Review, the requester SHALL post the completed form to the <directory@apps.ietf.org> mailing list for public review. The review period is two (2) weeks. If a revised form is later submitted, the review period is restarted. Anyone may subscribe to this list by sending a request to <directory-request@apps.ietf.org>. During the review, objections may be raised by anyone (including the Expert) on the list. After completion of the review, the Expert, based upon public comments, SHALL either approve the request and forward it to the IESG OR deny the request. In either case, the Expert SHALL promptly notify the requester of the action. Actions of the Expert may be appealed [RFC2026]. The Expert is appointed by Applications Area Director(s). The requester is viewed as the owner of values registered under Expert Review.
如果政策是专家评审，申请人应将填写好的表格张贴到<directory@apps.ietf.org>供公众查阅的邮件列表。审查期为两（2）周。如果以后提交了修订后的表格，则重新开始审查期。任何人都可以通过向<目录发送请求来订阅此列表-request@apps.ietf.org>. 审查期间，名单上的任何人（包括专家）都可能提出反对意见。审查完成后，专家应根据公众意见批准该请求并将其转发给IESG，或拒绝该请求。在任何一种情况下，专家都应立即将行动通知请求者。可对专家的行为提出上诉[RFC2026]。专家由应用领域主管任命。请求者被视为在专家审查下登记的价值的所有者。
If the policy is First Come First Served, the requester SHALL submit the completed form directly to the IANA: <iana@iana.org>. The requester is viewed as the owner of values registered under First Come First Served.
如果政策先到先得，申请人应直接向IANA提交填妥的表格：<iana@iana.org>. 请求者被视为根据“先到先得”注册的值的所有者。
Neither the Expert nor IANA will take position on the claims of copyright or trademarks issues regarding completed forms.
专家和IANA均不会就已完成表格的版权或商标问题采取立场。
Prior to submission of the Internet Draft (I-D) to the RFC Editor but after IESG review and tentative approval, the document editor SHOULD revise the I-D to use registered values.
在向RFC编辑提交互联网草案（I-D）之前，但在IESG审查和初步批准之后，文件编辑应修改I-D以使用注册值。
This section discusses maintenance of registrations.
本节讨论注册的维护。
IANA makes lists of registered values readily available to the Internet community on their web site: <http://www.iana.org/>.
IANA在其网站上为互联网社区提供注册价值清单：<http://www.iana.org/>.
The registration owner MAY update the registration subject to the same constraints and review as with new registrations. In cases where the owner is not unable or unwilling to make necessary updates, the IESG MAY assert ownership in order to update the registration.
登记所有人可根据与新登记相同的约束条件和审查条件更新登记。如果所有者不能或不愿意进行必要的更新，IESG可以主张所有权以更新注册。
For cases where others (anyone other than the owner) have significant objections to the claims in a registration and the owner does not agree to change the registration, comments MAY be attached to a registration upon Expert Review. For registrations owned by the IESG, the objections SHOULD be addressed by initiating a request for Expert Review.
如果其他人（除所有者以外的任何人）对登记中的索赔有重大异议，且所有者不同意更改登记，则可在专家审查后将意见附在登记上。对于IESG拥有的注册，应通过提出专家审查请求来解决异议。
The form of these requests is ad hoc, but MUST include the specific objections to be reviewed and SHOULD contain (directly or by reference) materials supporting the objections.
这些请求的形式是临时的，但必须包括要审查的具体反对意见，并应包含（直接或通过引用）支持反对意见的材料。
The security considerations detailed in [RFC2434] are generally applicable to this document. Additional security considerations specific to each namespace are discussed in Section 3 where appropriate.
[RFC2434]中详述的安全注意事项通常适用于本文件。第3节讨论了特定于每个名称空间的其他安全注意事项（如适用）。
Security considerations for LDAP are discussed in documents comprising the technical specification [RFC3377].
包含技术规范[RFC3377]的文档中讨论了LDAP的安全注意事项。
This document is a product of the IETF LDAP Revision (LDAPbis) Working Group. Some text was borrowed from "Guidelines for Writing an IANA Considerations Section in RFCs" [RFC2434] by Thomas Narten and Harald Alvestrand.
本文件是IETF LDAP修订（LDAPbis）工作组的产品。一些文本是从Thomas Narten和Harald Alvestrand的“在RFCs中编写IANA注意事项部分的指南”[RFC2434]中借用的。
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1155]Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[RFC2234]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。
[RFC2251] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory Access Protocol (v3)", RFC 2251, December 1997.
[RFC2251]Wahl，M.，Howes，T.和S.Kille，“轻量级目录访问协议（v3）”，RFC 2251，1997年12月。
[RFC2252] Wahl, M., Coulbeck, A., Howes, T. and S. Kille, "Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 2252, December 1997.
[RFC2252]Wahl，M.，Coulbeck，A.，Howes，T.和S.Kille，“轻量级目录访问协议（v3）：属性语法定义”，RFC2252，1997年12月。
[RFC2255] Howes, T. and M. Smith, "The LDAP URL Format", RFC 2255, December, 1997.
[RFC2255]Howes，T.和M.Smith，“LDAP URL格式”，RFC2255，1997年12月。
[RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use with LDAPv3", RFC 2256, December 1997.
[RFC2256]Wahl，M.，“用于LDAPv3的X.500（96）用户模式摘要”，RFC 2256，1997年12月。
[RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998.
[RFC2279]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，RFC 2279，1998年1月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access Protocol (v3): Technical Specification", RFC 3377, September 2002.
[RFC3377]Hodges，J.和R.Morgan，“轻量级目录访问协议（v3）：技术规范”，RFC 3377，2002年9月。
[IANADSN] IANA, "Directory Systems Names",
http://www.iana.org/assignments/directory-system-names
[IANADSN] IANA, "Directory Systems Names",
http://www.iana.org/assignments/directory-system-names
[ISO10646] Universal Multiple-Octet Coded Character Set (UCS) - Architecture and Basic Multilingual Plane, ISO/IEC 10646-1: 1993.
[ISO10646]通用多八位编码字符集（UCS）-体系结构和基本多语言平面，ISO/IEC 10646-1:1993。
[RFC1779] Kille, S., "A String Representation of Distinguished Names", RFC 1779, March 1995.
[RFC1779]Kille，S.，“可分辨名称的字符串表示”，RFC17791995年3月。
[RFC2222] Myers, J., "Simple Authentication and Security Layer (SASL)", RFC 2222, October 1997.
[RFC2222]迈尔斯，J.，“简单认证和安全层（SASL）”，RFC22221997年10月。
This appendix provides registration templates for registering new LDAP values.
本附录提供了注册新LDAP值的注册模板。
Subject: Request for LDAP OID Registration
主题：请求LDAP OID注册
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Specification: (I-D)
规格：（I-D）
Author/Change Controller:
作者/变更控制员：
Comments:
评论：
(Any comments that the requester deems relevant to the request)
（请求人认为与请求相关的任何评论）
Subject: Request for LDAP Protocol Mechanism Registration
主题：请求LDAP协议机制注册
Object Identifier:
对象标识符：
Description:
说明：
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Usage: (One of Control or Extension)
用法：（控制或扩展之一）
Specification: (I-D)
规格：（I-D）
Author/Change Controller:
作者/变更控制员：
Comments:
评论：
(Any comments that the requester deems relevant to the request)
（请求人认为与请求相关的任何评论）
Subject: Request for LDAP Descriptor Registration
主题：请求LDAP描述符注册
Descriptor (short name):
描述符（简称）：
Object Identifier:
对象标识符：
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Usage: (One of attribute type, URL extension, object class, or other)
用法：（属性类型、URL扩展、对象类或其他类型之一）
Specification: (RFC, I-D, URI)
规范：（RFC、I-D、URI）
Author/Change Controller:
作者/变更控制员：
Comments:
评论：
(Any comments that the requester deems relevant to the request)
（请求人认为与请求相关的任何评论）
Subject: Request for LDAP Attribute Description Option Registration
主题：请求LDAP属性描述选项注册
Option Name:
选项名称：
Family of Options: (YES or NO)
选项系列：（是或否）
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Specification: (RFC, I-D, URI)
规范：（RFC、I-D、URI）
Author/Change Controller:
作者/变更控制员：
Comments:
评论：
(Any comments that the requester deems relevant to the request)
（请求人认为与请求相关的任何评论）
Subject: Request for LDAP Message Type Registration
主题：请求LDAP消息类型注册
LDAP Message Name:
LDAP消息名称：
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Specification: (Approved I-D)
规格：（经批准的I-D）
Comments:
评论：
(Any comments that the requester deems relevant to the request)
（请求人认为与请求相关的任何评论）
Subject: Request for LDAP Result Code Registration
主题：请求LDAP结果代码注册
Result Code Name:
结果代码名称：
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Specification: (RFC, I-D, URI)
规范：（RFC、I-D、URI）
Author/Change Controller:
作者/变更控制员：
Comments:
评论：
(Any comments that the requester deems relevant to the request)
（请求人认为与请求相关的任何评论）
Subject: Request for LDAP Authentication Method Registration
主题：请求LDAP身份验证方法注册
Authentication Method Name:
身份验证方法名称：
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
Specification: (RFC, I-D, URI)
规范：（RFC、I-D、URI）
Intended Usage: (One of COMMON, LIMITED-USE, OBSOLETE)
预期用途：（常用、限用、过时）
Author/Change Controller:
作者/变更控制员：
Comments:
评论：
(Any comments that the requester deems relevant to the request)
（请求人认为与请求相关的任何评论）
The following values are currently assigned.
当前已指定以下值。
Currently registered "Internet Private Enterprise Numbers" can be found at <http://www.iana.org/assignments/enterprise-numbers>.
目前注册的“互联网私营企业编号”可在<http://www.iana.org/assignments/enterprise-numbers>.
Currently registered "Internet Directory Numbers" can be found at <http://www.iana.org/assignments/smi-numbers>.
目前注册的“互联网目录号”可在<http://www.iana.org/assignments/smi-numbers>.
Object Identifier Type Description Reference
-------------------------- ---- -------------- ---------
1.2.840.113556.1.4.473 C Sort Request [RFC2891]
1.2.840.113556.1.4.474 C Sort Response [RFC2891]
1.3.6.1.4.1.1466.101.119.1 E Dynamic Refresh [RFC2589]
1.3.6.1.4.1.1466.20037 E Start TLS [RFC2830]
1.3.6.1.4.1.4203.1.11.1 E Modify Password [RFC3062]
2.16.840.1.113730.3.4.2 C ManageDsaIT [RFC3296]
Object Identifier Type Description Reference
-------------------------- ---- -------------- ---------
1.2.840.113556.1.4.473 C Sort Request [RFC2891]
1.2.840.113556.1.4.474 C Sort Response [RFC2891]
1.3.6.1.4.1.1466.101.119.1 E Dynamic Refresh [RFC2589]
1.3.6.1.4.1.1466.20037 E Start TLS [RFC2830]
1.3.6.1.4.1.4203.1.11.1 E Modify Password [RFC3062]
2.16.840.1.113730.3.4.2 C ManageDsaIT [RFC3296]
Legend
------------------------
C => supportedControl
E => supportedExtension
Legend
------------------------
C => supportedControl
E => supportedExtension
NAME Type OID [REF]
------------------------ ---- -----------------
account O 0.9.2342.19200300.100.4.5 [RFC1274]
alias O 2.5.6.1 [RFC2256]
aliasedEntryName A 2.5.4.1 [X.501]
aliasedObjectName A 2.5.4.1 [RFC2256]
altServer A 1.3.6.1.4.1.1466.101.120.6 [RFC2252]
applicationEntity O 2.5.6.12 [RFC2256]
applicationProcess O 2.5.6.11 [RFC2256]
aRecord A 0.9.2342.19200300.100.1.26 [RFC1274]
associatedDomain A 0.9.2342.19200300.100.1.37 [RFC1274]
associatedInternetGateway A 1.3.6.1.4.1.453.7.2.8 [RFC2164]
associatedName A 0.9.2342.19200300.100.1.38 [RFC1274]
associatedORAddress A 1.3.6.1.4.1.453.7.2.6 [RFC2164]
associatedX400Gateway A 1.3.6.1.4.1.453.7.2.3 [RFC2164]
attributeTypes A 2.5.21.5 [RFC2252]
audio A 0.9.2342.19200300.100.1.55 [RFC1274]
authorityRevocationList A 2.5.4.38 [RFC2256]
NAME Type OID [REF]
------------------------ ---- -----------------
account O 0.9.2342.19200300.100.4.5 [RFC1274]
alias O 2.5.6.1 [RFC2256]
aliasedEntryName A 2.5.4.1 [X.501]
aliasedObjectName A 2.5.4.1 [RFC2256]
altServer A 1.3.6.1.4.1.1466.101.120.6 [RFC2252]
applicationEntity O 2.5.6.12 [RFC2256]
applicationProcess O 2.5.6.11 [RFC2256]
aRecord A 0.9.2342.19200300.100.1.26 [RFC1274]
associatedDomain A 0.9.2342.19200300.100.1.37 [RFC1274]
associatedInternetGateway A 1.3.6.1.4.1.453.7.2.8 [RFC2164]
associatedName A 0.9.2342.19200300.100.1.38 [RFC1274]
associatedORAddress A 1.3.6.1.4.1.453.7.2.6 [RFC2164]
associatedX400Gateway A 1.3.6.1.4.1.453.7.2.3 [RFC2164]
attributeTypes A 2.5.21.5 [RFC2252]
audio A 0.9.2342.19200300.100.1.55 [RFC1274]
authorityRevocationList A 2.5.4.38 [RFC2256]
bitStringMatch M 2.5.13.16 [RFC2252]
buildingName A 0.9.2342.19200300.100.1.48 [RFC1274]
businessCategory A 2.5.4.15 [RFC2256]
C A 2.5.4.6 [RFC2256]
cACertificate A 2.5.4.37 [RFC2256]
calCalAdrURI A 1.2.840.113556.1.4.481 [RFC2739]
calCalURI A 1.2.840.113556.1.4.478 [RFC2739]
calCAPURI A 1.2.840.113556.1.4.480 [RFC2739]
calEntry O 1.2.840.113556.1.5.87 [RFC2739]
calFBURL A 1.2.840.113556.1.4.479 [RFC2739]
calOtherCalAdrURIs A 1.2.840.113556.1.4.485 [RFC2739]
calOtherCalURIs A 1.2.840.113556.1.4.482 [RFC2739]
calOtherCAPURIs A 1.2.840.113556.1.4.484 [RFC2739]
calOtherFBURLs A 1.2.840.113556.1.4.483 [RFC2739]
caseExactIA5Match M 1.3.6.1.4.1.1466.109.114.1 [RFC2252]
caseIgnoreIA5Match M 1.3.6.1.4.1.1466.109.114.2 [RFC2252]
caseIgnoreListMatch M 2.5.13.11 [RFC2252]
caseIgnoreMatch M 2.5.13.2 [RFC2252]
caseIgnoreOrderingMatch M 2.5.13.3 [RFC2252]
caseIgnoreSubstringsMatch M 2.5.13.4 [RFC2252]
certificateRevocationList A 2.5.4.39 [RFC2256]
certificationAuthority O 2.5.6.16 [RFC2256]
certificationAuthority-V2 O 2.5.6.16.2 [RFC2256]
CN A 2.5.4.3 [RFC2256]
cNAMERecord A 0.9.2342.19200300.100.1.31 [RFC1274]
co A 0.9.2342.19200300.100.1.43 [RFC1274]
commonName A 2.5.4.3 [RFC2256]
country O 2.5.6.2 [RFC2256]
countryName A 2.5.4.6 [RFC2256]
createTimestamp A 2.5.18.1 [RFC2252]
creatorsName A 2.5.18.3 [RFC2252]
cRLDistributionPoint O 2.5.6.19 [RFC2256]
crossCertificatePair A 2.5.4.40 [RFC2256]
DC A 0.9.2342.19200300.100.1.25 [RFC2247]
dcObject O 1.3.6.1.4.1.1466.344 [RFC2247]
deltaCRL O 2.5.6.23 [RFC2587]
deltaRevocationList A 2.5.4.53 [RFC2256]
description A 2.5.4.13 [RFC2256]
destinationIndicator A 2.5.4.27 [RFC2256]
device O 2.5.6.14 [RFC2256]
distinguishedName A 2.5.4.49 [RFC2256]
distinguishedNameMatch M 2.5.13.1 [RFC2252]
distinguishedNameTableEntry O 1.3.6.1.4.1.453.7.1.5 [RFC2293]
distinguishedNameTableKey A 1.3.6.1.4.1.453.7.2.3 [RFC2293]
dITContentRules A 2.5.21.2 [RFC2252]
dITRedirect A 0.9.2342.19200300.100.1.54 [RFC1274]
dITStructureRules A 2.5.21.1 [RFC2252]
dmd O 2.5.6.20 [RFC2256]
bitStringMatch M 2.5.13.16 [RFC2252]
buildingName A 0.9.2342.19200300.100.1.48 [RFC1274]
businessCategory A 2.5.4.15 [RFC2256]
C A 2.5.4.6 [RFC2256]
cACertificate A 2.5.4.37 [RFC2256]
calCalAdrURI A 1.2.840.113556.1.4.481 [RFC2739]
calCalURI A 1.2.840.113556.1.4.478 [RFC2739]
calCAPURI A 1.2.840.113556.1.4.480 [RFC2739]
calEntry O 1.2.840.113556.1.5.87 [RFC2739]
calFBURL A 1.2.840.113556.1.4.479 [RFC2739]
calOtherCalAdrURIs A 1.2.840.113556.1.4.485 [RFC2739]
calOtherCalURIs A 1.2.840.113556.1.4.482 [RFC2739]
calOtherCAPURIs A 1.2.840.113556.1.4.484 [RFC2739]
calOtherFBURLs A 1.2.840.113556.1.4.483 [RFC2739]
caseExactIA5Match M 1.3.6.1.4.1.1466.109.114.1 [RFC2252]
caseIgnoreIA5Match M 1.3.6.1.4.1.1466.109.114.2 [RFC2252]
caseIgnoreListMatch M 2.5.13.11 [RFC2252]
caseIgnoreMatch M 2.5.13.2 [RFC2252]
caseIgnoreOrderingMatch M 2.5.13.3 [RFC2252]
caseIgnoreSubstringsMatch M 2.5.13.4 [RFC2252]
certificateRevocationList A 2.5.4.39 [RFC2256]
certificationAuthority O 2.5.6.16 [RFC2256]
certificationAuthority-V2 O 2.5.6.16.2 [RFC2256]
CN A 2.5.4.3 [RFC2256]
cNAMERecord A 0.9.2342.19200300.100.1.31 [RFC1274]
co A 0.9.2342.19200300.100.1.43 [RFC1274]
commonName A 2.5.4.3 [RFC2256]
country O 2.5.6.2 [RFC2256]
countryName A 2.5.4.6 [RFC2256]
createTimestamp A 2.5.18.1 [RFC2252]
creatorsName A 2.5.18.3 [RFC2252]
cRLDistributionPoint O 2.5.6.19 [RFC2256]
crossCertificatePair A 2.5.4.40 [RFC2256]
DC A 0.9.2342.19200300.100.1.25 [RFC2247]
dcObject O 1.3.6.1.4.1.1466.344 [RFC2247]
deltaCRL O 2.5.6.23 [RFC2587]
deltaRevocationList A 2.5.4.53 [RFC2256]
description A 2.5.4.13 [RFC2256]
destinationIndicator A 2.5.4.27 [RFC2256]
device O 2.5.6.14 [RFC2256]
distinguishedName A 2.5.4.49 [RFC2256]
distinguishedNameMatch M 2.5.13.1 [RFC2252]
distinguishedNameTableEntry O 1.3.6.1.4.1.453.7.1.5 [RFC2293]
distinguishedNameTableKey A 1.3.6.1.4.1.453.7.2.3 [RFC2293]
dITContentRules A 2.5.21.2 [RFC2252]
dITRedirect A 0.9.2342.19200300.100.1.54 [RFC1274]
dITStructureRules A 2.5.21.1 [RFC2252]
dmd O 2.5.6.20 [RFC2256]
dmdName A 2.5.4.54 [RFC2256]
dnQualifier A 2.5.4.46 [RFC2256]
dNSDomain O 0.9.2342.19200300.100.4.15 [RFC1274]
document O 0.9.2342.19200300.100.4.6 [RFC1274]
documentAuthor A 0.9.2342.19200300.100.1.14 [RFC1274]
documentIdentifier A 0.9.2342.19200300.100.1.11 [RFC1274]
documentLocation A 0.9.2342.19200300.100.1.15 [RFC1274]
documentPublisher A 0.9.2342.19200300.100.1.56 [RFC1274]
documentSeries O 0.9.2342.19200300.100.4.8 [RFC1274]
documentTitle A 0.9.2342.19200300.100.1.12 [RFC1274]
documentVersion A 0.9.2342.19200300.100.1.13 [RFC1274]
domain O 0.9.2342.19200300.100.4.13 [RFC2247]
domainComponent A 0.9.2342.19200300.100.1.25 [RFC2247]
domainNameForm N 1.3.6.1.4.1.1466.345 [RFC2247]
domainRelatedObject O 0.9.2342.19200300.100.4.17 [RFC1274]
drink A 0.9.2342.19200300.100.1.5 [RFC1274]
dSA O 2.5.6.13 [RFC2256]
dSAQuality A 0.9.2342.19200300.100.1.49 [RFC1274]
dynamicObject O 1.3.6.1.4.1.1466.101.119.2 [RFC2589]
dynamicSubtrees A 1.3.6.1.4.1.1466.101.119.4 [RFC2589]
enhancedSearchGuide A 2.5.4.47 [RFC2256]
entryTtl A 1.3.6.1.4.1.1466.101.119.3 [RFC2589]
extensibleObject O 1.3.6.1.4.1.1466.101.120.111 [RFC2252]
facsimileTelephoneNumber A 2.5.4.23 [RFC2256]
favouriteDrink A 0.9.2342.19200300.100.1.5 [RFC1274]
friendlyCountry O 0.9.2342.19200300.100.4.18 [RFC1274]
friendlyCountryName A 0.9.2342.19200300.100.1.43 [RFC1274]
generalizedTimeMatch M 2.5.13.27 [RFC2252]
generalizedTimeOrderingMatch M 2.5.13.28 [RFC2252]
generationQualifier A 2.5.4.44 [RFC2256]
givenName A 2.5.4.42 [RFC2256]
GN A 2.5.4.42 [RFC2256]
groupOfNames O 2.5.6.9 [RFC2256]
groupOfUniqueNames O 2.5.6.17 [RFC2256]
homePhone A 0.9.2342.19200300.100.1.20 [RFC1274]
homePostalAddress A 0.9.2342.19200300.100.1.39 [RFC1274]
homeTelephone A 0.9.2342.19200300.100.1.20 [RFC1274]
host A 0.9.2342.19200300.100.1.9 [RFC1274]
houseIdentifier A 2.5.4.51 [RFC2256]
info A 0.9.2342.19200300.100.1.4 [RFC1274]
initials A 2.5.4.43 [RFC2256]
integerFirstComponentMatch M 2.5.13.29 [RFC2252]
integerMatch M 2.5.13.14 [RFC2252]
internationaliSDNNumber A 2.5.4.25 [RFC2256]
janetMailbox A 0.9.2342.19200300.100.1.46 [RFC1274]
jpegPhoto A 0.9.2342.19200300.100.1.60 [RFC1488]
knowledgeInformation A 2.5.4.2 [RFC2256]
L A 2.5.4.7 [RFC2256]
dmdName A 2.5.4.54 [RFC2256]
dnQualifier A 2.5.4.46 [RFC2256]
dNSDomain O 0.9.2342.19200300.100.4.15 [RFC1274]
document O 0.9.2342.19200300.100.4.6 [RFC1274]
documentAuthor A 0.9.2342.19200300.100.1.14 [RFC1274]
documentIdentifier A 0.9.2342.19200300.100.1.11 [RFC1274]
documentLocation A 0.9.2342.19200300.100.1.15 [RFC1274]
documentPublisher A 0.9.2342.19200300.100.1.56 [RFC1274]
documentSeries O 0.9.2342.19200300.100.4.8 [RFC1274]
documentTitle A 0.9.2342.19200300.100.1.12 [RFC1274]
documentVersion A 0.9.2342.19200300.100.1.13 [RFC1274]
domain O 0.9.2342.19200300.100.4.13 [RFC2247]
domainComponent A 0.9.2342.19200300.100.1.25 [RFC2247]
domainNameForm N 1.3.6.1.4.1.1466.345 [RFC2247]
domainRelatedObject O 0.9.2342.19200300.100.4.17 [RFC1274]
drink A 0.9.2342.19200300.100.1.5 [RFC1274]
dSA O 2.5.6.13 [RFC2256]
dSAQuality A 0.9.2342.19200300.100.1.49 [RFC1274]
dynamicObject O 1.3.6.1.4.1.1466.101.119.2 [RFC2589]
dynamicSubtrees A 1.3.6.1.4.1.1466.101.119.4 [RFC2589]
enhancedSearchGuide A 2.5.4.47 [RFC2256]
entryTtl A 1.3.6.1.4.1.1466.101.119.3 [RFC2589]
extensibleObject O 1.3.6.1.4.1.1466.101.120.111 [RFC2252]
facsimileTelephoneNumber A 2.5.4.23 [RFC2256]
favouriteDrink A 0.9.2342.19200300.100.1.5 [RFC1274]
friendlyCountry O 0.9.2342.19200300.100.4.18 [RFC1274]
friendlyCountryName A 0.9.2342.19200300.100.1.43 [RFC1274]
generalizedTimeMatch M 2.5.13.27 [RFC2252]
generalizedTimeOrderingMatch M 2.5.13.28 [RFC2252]
generationQualifier A 2.5.4.44 [RFC2256]
givenName A 2.5.4.42 [RFC2256]
GN A 2.5.4.42 [RFC2256]
groupOfNames O 2.5.6.9 [RFC2256]
groupOfUniqueNames O 2.5.6.17 [RFC2256]
homePhone A 0.9.2342.19200300.100.1.20 [RFC1274]
homePostalAddress A 0.9.2342.19200300.100.1.39 [RFC1274]
homeTelephone A 0.9.2342.19200300.100.1.20 [RFC1274]
host A 0.9.2342.19200300.100.1.9 [RFC1274]
houseIdentifier A 2.5.4.51 [RFC2256]
info A 0.9.2342.19200300.100.1.4 [RFC1274]
initials A 2.5.4.43 [RFC2256]
integerFirstComponentMatch M 2.5.13.29 [RFC2252]
integerMatch M 2.5.13.14 [RFC2252]
internationaliSDNNumber A 2.5.4.25 [RFC2256]
janetMailbox A 0.9.2342.19200300.100.1.46 [RFC1274]
jpegPhoto A 0.9.2342.19200300.100.1.60 [RFC1488]
knowledgeInformation A 2.5.4.2 [RFC2256]
L A 2.5.4.7 [RFC2256]
labeledURI A 1.3.6.1.4.1.250.1.57 [RFC2079]
labeledURIObject A 1.3.6.1.4.1.250.3.15 [RFC2079]
lastModifiedBy A 0.9.2342.19200300.100.1.24 [RFC1274]
lastModifiedTime A 0.9.2342.19200300.100.1.23 [RFC1274]
ldapSyntaxes A 1.3.6.1.4.1.1466.101.120.16 [RFC2252]
locality O 2.5.6.3 [RFC2256]
localityName A 2.5.4.7 [RFC2256]
mail A 0.9.2342.19200300.100.1.3 [RFC2798]
mailPreferenceOption A 0.9.2342.19200300.100.1.47 [RFC1274]
manager A 0.9.2342.19200300.100.1.10 [RFC1274]
matchingRules A 2.5.21.4 [RFC2252]
matchingRuleUse A 2.5.21.8 [RFC2252]
mcgamTables A 1.3.6.1.4.1.453.7.2.9 [RFC2164]
mDRecord A 0.9.2342.19200300.100.1.27 [RFC1274]
member A 2.5.4.31 [RFC2256]
mixerGateway O 1.3.6.1.4.1.453.7.1.4 [RFC2164]
mobile A 0.9.2342.19200300.100.1.41 [RFC1274]
mobileTelephoneNumber A 0.9.2342.19200300.100.1.41 [RFC1274]
modifiersName A 2.5.18.4 [RFC2252]
modifyTimestamp A 2.5.18.2 [RFC2252]
mXRecord A 0.9.2342.19200300.100.1.28 [RFC1274]
name A 2.5.4.41 [RFC2256]
nameForms A 2.5.21.7 [RFC2252]
namingContexts A 1.3.6.1.4.1.1466.101.120.5 [RFC2252]
nSRecord A 0.9.2342.19200300.100.1.29 [RFC1274]
numericStringMatch M 2.5.13.8 [RFC2252]
numericStringSubstringsMatch M 2.5.13.10 [RFC2252]
O A 2.5.4.10 [RFC2256]
objectClass A 2.5.4.0 [RFC2256]
objectClasses A 2.5.21.6 [RFC2252]
objectIdentifierFirstComponentMatch M 2.5.13.30 [RFC2252]
objectIdentifiersMatch M 2.5.13.0 [RFC2252]
octetStringMatch M 2.5.13.17 [RFC2252]
omittedORAddressComponent O 1.3.6.1.4.1.453.7.1.3 [RFC2164]
oRAddressComponentType A 1.3.6.1.4.1.453.7.2.7 [RFC2164]
organization O 2.5.6.4 [RFC2256]
organizationalPerson O 2.5.6.7 [RFC2256]
organizationalRole O 2.5.6.8 [RFC2256]
organizationalStatus A 0.9.2342.19200300.100.1.45 [RFC1274]
organizationalUnit O 2.5.6.5 [RFC2256]
organizationalUnitName A 2.5.4.11 [RFC2256]
organizationName A 2.5.4.10 [RFC2256]
otherMailbox A 0.9.2342.19200300.100.1.22 [RFC1274]
OU A 2.5.4.11 [RFC2256]
owner A 2.5.4.32 [RFC2256]
pager A 0.9.2342.19200300.100.1.42 [RFC1274]
pagerTelephoneNumber A 0.9.2342.19200300.100.1.42 [RFC1274]
person O 2.5.6.6 [RFC2256]
labeledURI A 1.3.6.1.4.1.250.1.57 [RFC2079]
labeledURIObject A 1.3.6.1.4.1.250.3.15 [RFC2079]
lastModifiedBy A 0.9.2342.19200300.100.1.24 [RFC1274]
lastModifiedTime A 0.9.2342.19200300.100.1.23 [RFC1274]
ldapSyntaxes A 1.3.6.1.4.1.1466.101.120.16 [RFC2252]
locality O 2.5.6.3 [RFC2256]
localityName A 2.5.4.7 [RFC2256]
mail A 0.9.2342.19200300.100.1.3 [RFC2798]
mailPreferenceOption A 0.9.2342.19200300.100.1.47 [RFC1274]
manager A 0.9.2342.19200300.100.1.10 [RFC1274]
matchingRules A 2.5.21.4 [RFC2252]
matchingRuleUse A 2.5.21.8 [RFC2252]
mcgamTables A 1.3.6.1.4.1.453.7.2.9 [RFC2164]
mDRecord A 0.9.2342.19200300.100.1.27 [RFC1274]
member A 2.5.4.31 [RFC2256]
mixerGateway O 1.3.6.1.4.1.453.7.1.4 [RFC2164]
mobile A 0.9.2342.19200300.100.1.41 [RFC1274]
mobileTelephoneNumber A 0.9.2342.19200300.100.1.41 [RFC1274]
modifiersName A 2.5.18.4 [RFC2252]
modifyTimestamp A 2.5.18.2 [RFC2252]
mXRecord A 0.9.2342.19200300.100.1.28 [RFC1274]
name A 2.5.4.41 [RFC2256]
nameForms A 2.5.21.7 [RFC2252]
namingContexts A 1.3.6.1.4.1.1466.101.120.5 [RFC2252]
nSRecord A 0.9.2342.19200300.100.1.29 [RFC1274]
numericStringMatch M 2.5.13.8 [RFC2252]
numericStringSubstringsMatch M 2.5.13.10 [RFC2252]
O A 2.5.4.10 [RFC2256]
objectClass A 2.5.4.0 [RFC2256]
objectClasses A 2.5.21.6 [RFC2252]
objectIdentifierFirstComponentMatch M 2.5.13.30 [RFC2252]
objectIdentifiersMatch M 2.5.13.0 [RFC2252]
octetStringMatch M 2.5.13.17 [RFC2252]
omittedORAddressComponent O 1.3.6.1.4.1.453.7.1.3 [RFC2164]
oRAddressComponentType A 1.3.6.1.4.1.453.7.2.7 [RFC2164]
organization O 2.5.6.4 [RFC2256]
organizationalPerson O 2.5.6.7 [RFC2256]
organizationalRole O 2.5.6.8 [RFC2256]
organizationalStatus A 0.9.2342.19200300.100.1.45 [RFC1274]
organizationalUnit O 2.5.6.5 [RFC2256]
organizationalUnitName A 2.5.4.11 [RFC2256]
organizationName A 2.5.4.10 [RFC2256]
otherMailbox A 0.9.2342.19200300.100.1.22 [RFC1274]
OU A 2.5.4.11 [RFC2256]
owner A 2.5.4.32 [RFC2256]
pager A 0.9.2342.19200300.100.1.42 [RFC1274]
pagerTelephoneNumber A 0.9.2342.19200300.100.1.42 [RFC1274]
person O 2.5.6.6 [RFC2256]
personalSignature A 0.9.2342.19200300.100.1.53 [RFC1274]
personalTitle A 0.9.2342.19200300.100.1.40 [RFC1274]
photo A 0.9.2342.19200300.100.1.7 [RFC1274]
physicalDeliveryOfficeName A 2.5.4.19 [RFC2256]
pilotDSA O 0.9.2342.19200300.100.4.21 [RFC1274]
pilotObject O 0.9.2342.19200300.100.4.3 [RFC1274]
pilotOrganization O 0.9.2342.19200300.100.4.20 [RFC1274]
pilotPerson O 0.9.2342.19200300.100.4.4 [RFC1274]
pkiCA O 2.5.6.22 [RFC2587]
pkiUser O 2.5.6.21 [RFC2587]
postalAddress A 2.5.4.16 [RFC2256]
postalCode A 2.5.4.17 [RFC2256]
postOfficeBox A 2.5.4.18 [RFC2256]
preferredDeliveryMethod A 2.5.4.28 [RFC2256]
presentationAddress A 2.5.4.29 [RFC2256]
presentationAddressMatch M 2.5.13.22 [RFC2252]
protocolInformation A 2.5.4.48 [RFC2256]
protocolInformationMatch M 2.5.13.24 [RFC2252]
qualityLabelledData O 0.9.2342.19200300.100.4.22 [RFC1274]
ref A 2.16.840.1.113730.3.1.34 [RFC3296]
referral 0 2.16.840.1.113730.3.2.6 [RFC3296]
registeredAddress A 2.5.4.26 [RFC2256]
residentialPerson O 2.5.6.10 [RFC2256]
RFC822LocalPart O 0.9.2342.19200300.100.4.14 [RFC1274]
RFC822Mailbox A 0.9.2342.19200300.100.1.3 [RFC1274]
rFC822ToX400Mapping O 1.3.6.1.4.1.453.7.1.1 [RFC2164]
roleOccupant A 2.5.4.33 [RFC2256]
room O 0.9.2342.19200300.100.4.7 [RFC1274]
roomNumber A 0.9.2342.19200300.100.1.6 [RFC1274]
searchGuide A 2.5.4.14 [RFC2256]
secretary A 0.9.2342.19200300.100.1.21 [RFC1274]
seeAlso A 2.5.4.34 [RFC2256]
serialNumber A 2.5.4.5 [RFC2256]
simpleSecurityObject O 0.9.2342.19200300.100.4.19 [RFC1274]
singleLevelQuality A 0.9.2342.19200300.100.1.50 [RFC1274]
SN A 2.5.4.4 [RFC2256]
sOARecord A 0.9.2342.19200300.100.1.30 [RFC1274]
ST A 2.5.4.8 [RFC2256]
stateOrProvinceName A 2.5.4.8 [RFC2256]
street A 2.5.4.9 [RFC2256]
streetAddress A 2.5.4.9 [RFC2256]
strongAuthenticationUser O 2.5.6.15 [RFC2256]
subschema O 2.5.20.1 [RFC2252]
subschemaSubentry A 2.5.18.10 [RFC2252]
subtree O 1.3.6.1.4.1.453.7.1.1 [RFC2293]
subtreeMaximumQuality A 0.9.2342.19200300.100.1.52 [RFC1274]
subtreeMinimumQuality A 0.9.2342.19200300.100.1.51 [RFC1274]
supportedAlgorithms A 2.5.4.52 [RFC2256]
personalSignature A 0.9.2342.19200300.100.1.53 [RFC1274]
personalTitle A 0.9.2342.19200300.100.1.40 [RFC1274]
photo A 0.9.2342.19200300.100.1.7 [RFC1274]
physicalDeliveryOfficeName A 2.5.4.19 [RFC2256]
pilotDSA O 0.9.2342.19200300.100.4.21 [RFC1274]
pilotObject O 0.9.2342.19200300.100.4.3 [RFC1274]
pilotOrganization O 0.9.2342.19200300.100.4.20 [RFC1274]
pilotPerson O 0.9.2342.19200300.100.4.4 [RFC1274]
pkiCA O 2.5.6.22 [RFC2587]
pkiUser O 2.5.6.21 [RFC2587]
postalAddress A 2.5.4.16 [RFC2256]
postalCode A 2.5.4.17 [RFC2256]
postOfficeBox A 2.5.4.18 [RFC2256]
preferredDeliveryMethod A 2.5.4.28 [RFC2256]
presentationAddress A 2.5.4.29 [RFC2256]
presentationAddressMatch M 2.5.13.22 [RFC2252]
protocolInformation A 2.5.4.48 [RFC2256]
protocolInformationMatch M 2.5.13.24 [RFC2252]
qualityLabelledData O 0.9.2342.19200300.100.4.22 [RFC1274]
ref A 2.16.840.1.113730.3.1.34 [RFC3296]
referral 0 2.16.840.1.113730.3.2.6 [RFC3296]
registeredAddress A 2.5.4.26 [RFC2256]
residentialPerson O 2.5.6.10 [RFC2256]
RFC822LocalPart O 0.9.2342.19200300.100.4.14 [RFC1274]
RFC822Mailbox A 0.9.2342.19200300.100.1.3 [RFC1274]
rFC822ToX400Mapping O 1.3.6.1.4.1.453.7.1.1 [RFC2164]
roleOccupant A 2.5.4.33 [RFC2256]
room O 0.9.2342.19200300.100.4.7 [RFC1274]
roomNumber A 0.9.2342.19200300.100.1.6 [RFC1274]
searchGuide A 2.5.4.14 [RFC2256]
secretary A 0.9.2342.19200300.100.1.21 [RFC1274]
seeAlso A 2.5.4.34 [RFC2256]
serialNumber A 2.5.4.5 [RFC2256]
simpleSecurityObject O 0.9.2342.19200300.100.4.19 [RFC1274]
singleLevelQuality A 0.9.2342.19200300.100.1.50 [RFC1274]
SN A 2.5.4.4 [RFC2256]
sOARecord A 0.9.2342.19200300.100.1.30 [RFC1274]
ST A 2.5.4.8 [RFC2256]
stateOrProvinceName A 2.5.4.8 [RFC2256]
street A 2.5.4.9 [RFC2256]
streetAddress A 2.5.4.9 [RFC2256]
strongAuthenticationUser O 2.5.6.15 [RFC2256]
subschema O 2.5.20.1 [RFC2252]
subschemaSubentry A 2.5.18.10 [RFC2252]
subtree O 1.3.6.1.4.1.453.7.1.1 [RFC2293]
subtreeMaximumQuality A 0.9.2342.19200300.100.1.52 [RFC1274]
subtreeMinimumQuality A 0.9.2342.19200300.100.1.51 [RFC1274]
supportedAlgorithms A 2.5.4.52 [RFC2256]
supportedApplicationContext A 2.5.4.30 [RFC2256]
supportedControl A 1.3.6.1.4.1.1466.101.120.13 [RFC2252]
supportedExtension A 1.3.6.1.4.1.1466.101.120.7 [RFC2252]
supportedLDAPVersion A 1.3.6.1.4.1.1466.101.120.15 [RFC2252]
supportedSASLMechanisms A 1.3.6.1.4.1.1466.101.120.14 [RFC2252]
surname A 2.5.4.4 [RFC2256]
table O 1.3.6.1.4.1.453.7.1.2 [RFC2293]
tableEntry O 1.3.6.1.4.1.453.7.1.3 [RFC2293]
telephoneNumber A 2.5.4.20 [RFC2256]
telephoneNumberMatch M 2.5.13.20 [RFC2252]
telephoneNumberSubstringsMatch M 2.5.13.21 [RFC2252]
teletexTerminalIdentifier A 2.5.4.22 [RFC2256]
telexNumber A 2.5.4.21 [RFC2256]
textEncodedORAddress A 0.9.2342.19200300.100.1.2 [RFC1274]
textTableEntry O 1.3.6.1.4.1.453.7.1.4 [RFC2293]
textTableKey A 1.3.6.1.4.1.453.7.2.1 [RFC2293]
textTableValue A 1.3.6.1.4.1.453.7.2.2 [RFC2293]
title A 2.5.4.12 [RFC2256]
top O 2.5.6.0 [RFC2256]
uid A 0.9.2342.19200300.100.1.1 [RFC2253]
uniqueIdentifier A 0.9.2342.19200300.100.1.44 [RFC1274]
uniqueMember A 2.5.4.50 [RFC2256]
uniqueMemberMatch M 2.5.13.23 [RFC2252]
userCertificate A 2.5.4.36 [RFC2256]
userClass A 0.9.2342.19200300.100.1.8 [RFC1274]
userId A 0.9.2342.19200300.100.1.1 [RFC1274]
userPassword A 2.5.4.35 [RFC2256]
userSecurityInformation O 2.5.6.18 [RFC2256]
x121Address A 2.5.4.24 [RFC2256]
x400ToRFC822Mapping O 1.3.6.1.4.1.453.7.1.2 [RFC2164]
x500UniqueIdentifier A 2.5.4.45 [RFC2256]
supportedApplicationContext A 2.5.4.30 [RFC2256]
supportedControl A 1.3.6.1.4.1.1466.101.120.13 [RFC2252]
supportedExtension A 1.3.6.1.4.1.1466.101.120.7 [RFC2252]
supportedLDAPVersion A 1.3.6.1.4.1.1466.101.120.15 [RFC2252]
supportedSASLMechanisms A 1.3.6.1.4.1.1466.101.120.14 [RFC2252]
surname A 2.5.4.4 [RFC2256]
table O 1.3.6.1.4.1.453.7.1.2 [RFC2293]
tableEntry O 1.3.6.1.4.1.453.7.1.3 [RFC2293]
telephoneNumber A 2.5.4.20 [RFC2256]
telephoneNumberMatch M 2.5.13.20 [RFC2252]
telephoneNumberSubstringsMatch M 2.5.13.21 [RFC2252]
teletexTerminalIdentifier A 2.5.4.22 [RFC2256]
telexNumber A 2.5.4.21 [RFC2256]
textEncodedORAddress A 0.9.2342.19200300.100.1.2 [RFC1274]
textTableEntry O 1.3.6.1.4.1.453.7.1.4 [RFC2293]
textTableKey A 1.3.6.1.4.1.453.7.2.1 [RFC2293]
textTableValue A 1.3.6.1.4.1.453.7.2.2 [RFC2293]
title A 2.5.4.12 [RFC2256]
top O 2.5.6.0 [RFC2256]
uid A 0.9.2342.19200300.100.1.1 [RFC2253]
uniqueIdentifier A 0.9.2342.19200300.100.1.44 [RFC1274]
uniqueMember A 2.5.4.50 [RFC2256]
uniqueMemberMatch M 2.5.13.23 [RFC2252]
userCertificate A 2.5.4.36 [RFC2256]
userClass A 0.9.2342.19200300.100.1.8 [RFC1274]
userId A 0.9.2342.19200300.100.1.1 [RFC1274]
userPassword A 2.5.4.35 [RFC2256]
userSecurityInformation O 2.5.6.18 [RFC2256]
x121Address A 2.5.4.24 [RFC2256]
x400ToRFC822Mapping O 1.3.6.1.4.1.453.7.1.2 [RFC2164]
x500UniqueIdentifier A 2.5.4.45 [RFC2256]
Legend
------------------------
A => Attribute Type
C => DIT Content Rule
E => LDAP URL Extension
M => Matching Rule
N => Name Form
O => Object Class
Legend
------------------------
A => Attribute Type
C => DIT Content Rule
E => LDAP URL Extension
M => Matching Rule
N => Name Form
O => Object Class
Option Owner Reference
---------------- ----- ---------
binary IESG [RFC2251]
lang-* IESG [RFC2596]
Option Owner Reference
---------------- ----- ---------
binary IESG [RFC2251]
lang-* IESG [RFC2596]
* family of options
* 期权家族
Name Code Owner Reference
--------------------------- ---- ----- ---------
bindRequest 0 IESG [RFC2251]
bindResponse 1 IESG [RFC2251]
unbindRequest 2 IESG [RFC2251]
searchRequest 3 IESG [RFC2251]
searchResEntry 4 IESG [RFC2251]
searchResDone 5 IESG [RFC2251]
modifyRequest 6 IESG [RFC2251]
modifyResponse 7 IESG [RFC2251]
addRequest 8 IESG [RFC2251]
addResponse 9 IESG [RFC2251]
delRequest 10 IESG [RFC2251]
delResponse 11 IESG [RFC2251]
modDNRequest 12 IESG [RFC2251]
modDNResponse 13 IESG [RFC2251]
compareRequest 14 IESG [RFC2251]
compareResponse 15 IESG [RFC2251]
abandonRequest 16 IESG [RFC2251]
reserved 17-18 IESG
searchResRef 19 IESG [RFC2251]
reserved 20-22 IESG
extendedReq 23 IESG [RFC2251]
extendedResp 24 IESG [RFC2251]
Name Code Owner Reference
--------------------------- ---- ----- ---------
bindRequest 0 IESG [RFC2251]
bindResponse 1 IESG [RFC2251]
unbindRequest 2 IESG [RFC2251]
searchRequest 3 IESG [RFC2251]
searchResEntry 4 IESG [RFC2251]
searchResDone 5 IESG [RFC2251]
modifyRequest 6 IESG [RFC2251]
modifyResponse 7 IESG [RFC2251]
addRequest 8 IESG [RFC2251]
addResponse 9 IESG [RFC2251]
delRequest 10 IESG [RFC2251]
delResponse 11 IESG [RFC2251]
modDNRequest 12 IESG [RFC2251]
modDNResponse 13 IESG [RFC2251]
compareRequest 14 IESG [RFC2251]
compareResponse 15 IESG [RFC2251]
abandonRequest 16 IESG [RFC2251]
reserved 17-18 IESG
searchResRef 19 IESG [RFC2251]
reserved 20-22 IESG
extendedReq 23 IESG [RFC2251]
extendedResp 24 IESG [RFC2251]
Name Code Owner Reference
--------------------------- ---- ----- ---------
success 0 IESG [RFC2251]
operationsError 1 IESG [RFC2251]
protocolError 2 IESG [RFC2251]
timeLimitExceeded 3 IESG [RFC2251]
sizeLimitExceeded 4 IESG [RFC2251]
compareFalse 5 IESG [RFC2251]
compareTrue 6 IESG [RFC2251]
authMethodNotSupported 7 IESG [RFC2251]
Name Code Owner Reference
--------------------------- ---- ----- ---------
success 0 IESG [RFC2251]
operationsError 1 IESG [RFC2251]
protocolError 2 IESG [RFC2251]
timeLimitExceeded 3 IESG [RFC2251]
sizeLimitExceeded 4 IESG [RFC2251]
compareFalse 5 IESG [RFC2251]
compareTrue 6 IESG [RFC2251]
authMethodNotSupported 7 IESG [RFC2251]
strongAuthRequired 8 IESG [RFC2251]
reserved (partialResults) 9 IESG [RFC2251]
referral 10 IESG [RFC2251]
adminLimitExceeded 11 IESG [RFC2251]
unavailableCriticalExtension 12 IESG [RFC2251]
confidentialityRequired 13 IESG [RFC2251]
saslBindInProgress 14 IESG [RFC2251]
noSuchAttribute 16 IESG [RFC2251]
undefinedAttributeType 17 IESG [RFC2251]
inappropriateMatching 18 IESG [RFC2251]
constraintViolation 19 IESG [RFC2251]
attributeOrValueExists 20 IESG [RFC2251]
invalidAttributeSyntax 21 IESG [RFC2251]
noSuchObject 32 IESG [RFC2251]
aliasProblem 33 IESG [RFC2251]
invalidDNSyntax 34 IESG [RFC2251]
reserved (isLeaf) 35 IESG [RFC2251]
aliasDereferencingProblem 36 IESG [RFC2251]
reserved 37-47 IESG
inappropriateAuthentication 48 IESG [RFC2251]
invalidCredentials 49 IESG [RFC2251]
insufficientAccessRights 50 IESG [RFC2251]
busy 51 IESG [RFC2251]
unavailable 52 IESG [RFC2251]
unwillingToPerform 53 IESG [RFC2251]
loopDetect 54 IESG [RFC2251]
reserved 55-63 IESG
namingViolation 64 IESG [RFC2251]
objectClassViolation 65 IESG [RFC2251]
notAllowedOnNonLeaf 66 IESG [RFC2251]
notAllowedOnRDN 67 IESG [RFC2251]
entryAlreadyExists 68 IESG [RFC2251]
objectClassModsProhibited 69 IESG [RFC2251]
reserved (resultsTooLarge) 70 IESG [RFC2251]
reserved 71-79 IESG
other 80 IESG [RFC2251]
reserved (APIs) 81-90 IESG [RFC2251]
strongAuthRequired 8 IESG [RFC2251]
reserved (partialResults) 9 IESG [RFC2251]
referral 10 IESG [RFC2251]
adminLimitExceeded 11 IESG [RFC2251]
unavailableCriticalExtension 12 IESG [RFC2251]
confidentialityRequired 13 IESG [RFC2251]
saslBindInProgress 14 IESG [RFC2251]
noSuchAttribute 16 IESG [RFC2251]
undefinedAttributeType 17 IESG [RFC2251]
inappropriateMatching 18 IESG [RFC2251]
constraintViolation 19 IESG [RFC2251]
attributeOrValueExists 20 IESG [RFC2251]
invalidAttributeSyntax 21 IESG [RFC2251]
noSuchObject 32 IESG [RFC2251]
aliasProblem 33 IESG [RFC2251]
invalidDNSyntax 34 IESG [RFC2251]
reserved (isLeaf) 35 IESG [RFC2251]
aliasDereferencingProblem 36 IESG [RFC2251]
reserved 37-47 IESG
inappropriateAuthentication 48 IESG [RFC2251]
invalidCredentials 49 IESG [RFC2251]
insufficientAccessRights 50 IESG [RFC2251]
busy 51 IESG [RFC2251]
unavailable 52 IESG [RFC2251]
unwillingToPerform 53 IESG [RFC2251]
loopDetect 54 IESG [RFC2251]
reserved 55-63 IESG
namingViolation 64 IESG [RFC2251]
objectClassViolation 65 IESG [RFC2251]
notAllowedOnNonLeaf 66 IESG [RFC2251]
notAllowedOnRDN 67 IESG [RFC2251]
entryAlreadyExists 68 IESG [RFC2251]
objectClassModsProhibited 69 IESG [RFC2251]
reserved (resultsTooLarge) 70 IESG [RFC2251]
reserved 71-79 IESG
other 80 IESG [RFC2251]
reserved (APIs) 81-90 IESG [RFC2251]
Method Value Owner Usage Reference
------ ----- ----- ----------- -----------------
simple 0 IESG LIMITED USE [RFC2251,RFC2829]
krbv42LDAP 1 IESG OBSOLETE* [RFC1777]
krbv42DSA 2 IESG OBSOLETE* [RFC1777]
sasl 3 IESG COMMON [RFC2251,RFC2829]
Method Value Owner Usage Reference
------ ----- ----- ----------- -----------------
simple 0 IESG LIMITED USE [RFC2251,RFC2829]
krbv42LDAP 1 IESG OBSOLETE* [RFC1777]
krbv42DSA 2 IESG OBSOLETE* [RFC1777]
sasl 3 IESG COMMON [RFC2251,RFC2829]
* These LDAPv2-only mechanisms were deprecated in favor of the LDAPv3 SASL authentication method, specifically the GSSAPI mechanism.
* 这些仅限LDAPv2的机制被弃用，取而代之的是LDAPv3 SASL身份验证方法，特别是GSSAPI机制。
Author's Address
作者地址
Kurt D. Zeilenga OpenLDAP Foundation
库尔特D.Zeeliga OpenLDAP基金会
EMail: Kurt@OpenLDAP.org
EMail: Kurt@OpenLDAP.org
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。