Network Working Group K. Zeilenga, Ed.
Request for Comments: 3698 OpenLDAP Foundation
Updates: 2798 February 2004
Category: Standards Track
Network Working Group K. Zeilenga, Ed.
Request for Comments: 3698 OpenLDAP Foundation
Updates: 2798 February 2004
Category: Standards Track
Lightweight Directory Access Protocol (LDAP): Additional Matching Rules
轻量级目录访问协议（LDAP）：其他匹配规则
Status of this Memo
本备忘录的状况
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 (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
Abstract
摘要
This document provides a collection of matching rules for use with the Lightweight Directory Access Protocol (LDAP). As these matching rules are simple adaptations of matching rules specified for use with the X.500 Directory, most are already in wide use.
本文档提供了一组匹配规则，用于轻量级目录访问协议（LDAP）。由于这些匹配规则是指定用于X.500目录的匹配规则的简单改编，因此大多数已被广泛使用。
Table of Contents
目录
1. Background and Intended Use. . . . . . . . . . . . . . . . . . 2
2. Matching Rules . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. booleanMatch . . . . . . . . . . . . . . . . . . . . . . 2
2.2. caseExactMatch . . . . . . . . . . . . . . . . . . . . . 2
2.3. caseExactOrderingMatch . . . . . . . . . . . . . . . . . 3
2.4. caseExactSubstringsMatch . . . . . . . . . . . . . . . . 3
2.5. caseIgnoreListSubstringsMatch. . . . . . . . . . . . . . 3
2.6. directoryStringFirstComponentMatch . . . . . . . . . . . 4
2.7. integerOrderingMatch . . . . . . . . . . . . . . . . . . 4
2.8. keywordMatch . . . . . . . . . . . . . . . . . . . . . . 4
2.9. numericStringOrderingMatch . . . . . . . . . . . . . . . 5
2.10. octetStringOrderingMatch . . . . . . . . . . . . . . . . 5
2.11. storedPrefixMatch. . . . . . . . . . . . . . . . . . . . 5
2.12. wordMatch. . . . . . . . . . . . . . . . . . . . . . . . 6
3. Security Considerations. . . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 6
5. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Background and Intended Use. . . . . . . . . . . . . . . . . . 2
2. Matching Rules . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. booleanMatch . . . . . . . . . . . . . . . . . . . . . . 2
2.2. caseExactMatch . . . . . . . . . . . . . . . . . . . . . 2
2.3. caseExactOrderingMatch . . . . . . . . . . . . . . . . . 3
2.4. caseExactSubstringsMatch . . . . . . . . . . . . . . . . 3
2.5. caseIgnoreListSubstringsMatch. . . . . . . . . . . . . . 3
2.6. directoryStringFirstComponentMatch . . . . . . . . . . . 4
2.7. integerOrderingMatch . . . . . . . . . . . . . . . . . . 4
2.8. keywordMatch . . . . . . . . . . . . . . . . . . . . . . 4
2.9. numericStringOrderingMatch . . . . . . . . . . . . . . . 5
2.10. octetStringOrderingMatch . . . . . . . . . . . . . . . . 5
2.11. storedPrefixMatch. . . . . . . . . . . . . . . . . . . . 5
2.12. wordMatch. . . . . . . . . . . . . . . . . . . . . . . . 6
3. Security Considerations. . . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 6
5. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Normative References . . . . . . . . . . . . . . . . . . 7
6.2. Informative References . . . . . . . . . . . . . . . . . 7
7. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8
8. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 9
6.1. Normative References . . . . . . . . . . . . . . . . . . 7
6.2. Informative References . . . . . . . . . . . . . . . . . 7
7. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8
8. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 9
This document adapts additional X.500 Directory [X.500] matching rules [X.520] for use with the Lightweight Directory Access Protocol (LDAP) [RFC3377]. Most of these rules are widely used today on the Internet, such as in support of the inetOrgPerson [RFC2798] and Policy Core Information Model [RFC3703] LDAP schemas. The rules are applicable to many other applications.
本文档对附加的X.500目录[X.500]匹配规则[X.520]进行了调整，以与轻型目录访问协议（LDAP）[RFC3377]一起使用。这些规则中的大多数现在在Internet上广泛使用，例如支持inetOrgPerson[RFC2798]和策略核心信息模型[RFC3703]LDAP模式。这些规则适用于许多其他应用。
This document supersedes the informational matching rules descriptions provided in RFC 2798 that are now provided in this document. Specifically, section 2 of this document replaces section 9.3.3 of RFC 2798.
本文档取代RFC 2798中提供的信息性匹配规则描述，这些描述现在在本文档中提供。具体而言，本文件第2节取代RFC 2798第9.3.3节。
Schema definitions are provided using LDAP description formats [RFC2252]. Definitions provided here are formatted (line wrapped) for readability.
模式定义使用LDAP描述格式[RFC2252]提供。为了便于阅读，这里提供的定义是格式化的（换行）。
The booleanMatch rule compares for equality a asserted Boolean value with an attribute value of BOOLEAN syntax. The rule returns TRUE if and only if the values are the same, i.e., both are TRUE or both are FALSE. (Source: X.520)
booleanMatch规则将断言的布尔值与布尔语法的属性值进行相等性比较。当且仅当两个值相同（即均为真或均为假）时，该规则才返回TRUE。（来源：X.520）
( 2.5.13.13 NAME 'booleanMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 )
（2.5.13.13名称“布尔匹配”语法1.3.6.1.4.1.1466.115.121.1.7）
The BOOLEAN (1.3.6.1.4.1.1466.115.121.1.7) syntax is described in [RFC2252].
[RFC2252]中描述了布尔（1.3.6.1.4.1.1466.115.121.1.7）语法。
The caseExactMatch rule compares for equality the asserted value with an attribute value of DirectoryString syntax. The rule is identical to the caseIgnoreMatch [RFC2252] rule except that case is not ignored. (Source: X.520)
caseExactMatch规则将断言值与DirectoryString语法的属性值进行相等性比较。该规则与caseIgnoreMatch[RFC2252]规则相同，只是不忽略该案例。（来源：X.520）
( 2.5.13.5 NAME 'caseExactMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（2.5.13.5名称“caseExactMatch”语法1.3.6.1.4.1.1466.115.121.1.15）
The DirectoryString (1.3.6.1.4.1.1466.115.121.1.15) syntax is described in [RFC2252].
[RFC2252]中描述了DirectoryString（1.3.6.1.4.1.1466.115.121.1.15）语法。
The caseExactOrderingMatch rule compares the collation order of the asserted string with an attribute value of DirectoryString syntax. The rule is identical to the caseIgnoreOrderingMatch [RFC2252] rule except that letters are not folded. (Source: X.520)
caseExactOrderingMatch规则将断言字符串的排序规则与DirectoryString语法的属性值进行比较。该规则与caseIgnoreOrderingMatch[RFC2252]规则相同，只是字母没有折叠。（来源：X.520）
( 2.5.13.6 NAME 'caseExactOrderingMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（2.5.13.6名称“caseExactOrderingMatch”语法1.3.6.1.4.1.1466.115.121.1.15）
The DirectoryString (1.3.6.1.4.1.1466.115.121.1.15) syntax is described in [RFC2252].
[RFC2252]中描述了DirectoryString（1.3.6.1.4.1.1466.115.121.1.15）语法。
The caseExactSubstringsMatch rule determines whether the asserted value(s) are substrings of an attribute value of DirectoryString syntax. The rule is identical to the caseIgnoreSubstringsMatch [RFC2252] rule except that case is not ignored. (Source: X.520)
caseExactSubstringsMatch规则确定断言值是否为DirectoryString语法属性值的子字符串。该规则与caseIgnoreSubstringsMatch[RFC2252]规则相同，只是不忽略该案例。（来源：X.520）
( 2.5.13.7 NAME 'caseExactSubstringsMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 )
（2.5.13.7名称“caseExactSubstringsMatch”语法1.3.6.1.4.1.1466.115.121.1.58）
The SubstringsAssertion (1.3.6.1.4.1.1466.115.121.1.58) syntax is described in [RFC2252].
[RFC2252]中描述了substringsSertion（1.3.6.1.4.1.1466.115.121.1.58）语法。
The caseIgnoreListSubstringMatch rule compares the asserted substring with an attribute value which is a sequence of DirectoryStrings, but where the case (upper or lower) is not significant for comparison purposes. The asserted value matches a stored value if and only if the asserted value matches the string formed by concatenating the strings of the stored value. This matching is done according to the caseIgnoreSubstringsMatch [RFC2252] rule; however, none of the initial, any, or final values of the asserted value are considered to match a substring of the concatenated string which spans more than one of the strings of the stored value. (Source: X.520)
caseIgnoreListSubstringMatch规则将断言的子字符串与一个属性值进行比较，该属性值是一系列DirectoryStrings，但大小写（大写或小写）对于比较而言并不重要。当且仅当断言值与通过连接存储值的字符串而形成的字符串匹配时，断言值才与存储值匹配。根据caseIgnoreSubstringsMatch[RFC2252]规则进行匹配；但是，断言值的初始值、任意值或最终值均不被视为与跨存储值的多个字符串的串联字符串的子字符串匹配。（来源：X.520）
( 2.5.13.12 NAME 'caseIgnoreListSubstringsMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 )
（2.5.13.12名称“caseIgnoreListSubstringsMatch”语法1.3.6.1.4.1.1466.115.121.1.58）
The SubstringsAssertion (1.3.6.1.4.1.1466.115.121.1.58) syntax is described in [RFC2252].
[RFC2252]中描述了substringsSertion（1.3.6.1.4.1.1466.115.121.1.58）语法。
The directoryStringFirstComponentMatch rule compares for equality the asserted DirectoryString value with an attribute value of type SEQUENCE whose first component is mandatory and of type DirectoryString. The rule returns TRUE if and only if the attribute value has a first component whose value matches the asserted DirectoryString using the rules of caseIgnoreMatch [RFC2252]. A value of the assertion syntax is derived from a value of the attribute syntax by using the value of the first component of the SEQUENCE. (Source: X.520)
directoryStringFirstComponentMatch规则将断言的DirectoryString值与SEQUENCE类型的属性值进行相等性比较，SEQUENCE类型的第一个组件是必需的，并且是DirectoryString类型的属性值。当且仅当属性值的第一个组件的值与使用caseIgnoreMatch[RFC2252]规则断言的DirectoryString匹配时，该规则才返回TRUE。断言语法的值是通过使用序列的第一个组件的值从属性语法的值派生出来的。（来源：X.520）
( 2.5.13.31 NAME 'directoryStringFirstComponentMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（2.5.13.31名称“directoryStringFirstComponentMatch”语法1.3.6.1.4.1.1466.115.121.1.15）
The DirectoryString (1.3.6.1.4.1.1466.115.121.1.15) syntax is described in [RFC2252].
[RFC2252]中描述了DirectoryString（1.3.6.1.4.1.1466.115.121.1.15）语法。
The integerOrderingMatch rule compares the ordering of the asserted integer with an attribute value of INTEGER syntax. The rule returns True if the attribute value is less than the asserted value. (Source: X.520)
integerOrderingMatch规则将断言整数的顺序与integer语法的属性值进行比较。如果属性值小于断言的值，则规则返回True。（来源：X.520）
( 2.5.13.15 NAME 'integerOrderingMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )
（2.5.13.15名称“integerOrderingMatch”语法1.3.6.1.4.1.1466.115.121.1.27）
The INTEGER (1.3.6.1.4.1.1466.115.121.1.27) syntax is described in [RFC2252].
[RFC2252]中描述了整数（1.3.6.1.4.1.1466.115.121.1.27）语法。
The keywordMatch rule compares the asserted string with keywords in an attribute value of DirectoryString syntax. The rule returns TRUE if and only if the asserted value matches any keyword in the attribute value. The identification of keywords in an attribute value and of the exactness of match are both implementation specific. (Source: X.520)
关键字匹配规则将断言的字符串与DirectoryString语法属性值中的关键字进行比较。当且仅当断言的值与属性值中的任何关键字匹配时，该规则才返回TRUE。属性值中关键字的识别和匹配的精确性都是特定于实现的。（来源：X.520）
( 2.5.13.33 NAME 'keywordMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（2.5.13.33名称“关键字匹配”语法1.3.6.1.4.1.1466.115.121.1.15）
The DirectoryString (1.3.6.1.4.1.1466.115.121.1.15) syntax is described in [RFC2252].
[RFC2252]中描述了DirectoryString（1.3.6.1.4.1.1466.115.121.1.15）语法。
The numericStringOrderingMatch rule compares the collation order of the asserted string with an attribute value of NumericString syntax. The rule is identical to the caseIgnoreOrderingMatch [RFC2252] rule except that all space characters are skipped during comparison (case is irrelevant as characters are numeric). (Source: X.520)
numericStringOrderingMatch规则将断言字符串的排序规则与NumericString语法的属性值进行比较。该规则与caseIgnoreOrderingMatch[RFC2252]规则相同，只是在比较过程中跳过了所有空格字符（由于字符为数字，因此大小写无关）。（来源：X.520）
( 2.5.13.9 NAME 'numericStringOrderingMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.36 )
（2.5.13.9名称“numericStringOrderingMatch”语法1.3.6.1.4.1.1466.115.121.1.36）
The NumericString (1.3.6.1.4.1.1466.115.121.1.36) syntax is described in [RFC2252].
[RFC2252]中描述了NumericString（1.3.6.1.4.1.1466.115.121.1.36）语法。
The octetStringOrderingMatch rule compares the collation order of the asserted octet string with an attribute value of OCTET STRING syntax. The rule compares octet strings from first octet to last octet, and from the most significant bit to the least significant bit within the octet. The first occurrence of a different bit determines the ordering of the strings. A zero bit precedes a one bit. If the strings are identical but contain different numbers of octets, the shorter string precedes the longer string. (Source: X.520)
octetStringOrderingMatch规则将断言的八位字节字符串的排序规则与八位字节字符串语法的属性值进行比较。该规则将八位字节字符串从第一个八位字节到最后一个八位字节，以及从八位字节中的最高有效位到最低有效位进行比较。不同位的第一次出现决定了字符串的顺序。零位先于一位。如果字符串相同但包含不同的八位字节数，则较短的字符串位于较长的字符串之前。（来源：X.520）
( 2.5.13.18 NAME 'octetStringOrderingMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 )
（2.5.13.18名称“octetStringOrderingMatch”语法1.3.6.1.4.1.1466.115.121.1.40）
The OCTET STRING (1.3.6.1.4.1.1466.115.121.1.40) syntax is described in [RFC2252].
[RFC2252]中描述了八位字节字符串（1.3.6.1.4.1.1466.115.121.1.40）语法。
The storedPrefixMatch rule determines whether an attribute value, whose syntax is DirectoryString is a prefix (i.e., initial substring) of the asserted value, without regard to the case (upper or lower) of the strings. The rule returns TRUE if and only if the attribute value is an initial substring of the asserted value with corresponding characters identical except possibly with regard to case. (Source: X.520)
storedPrefixMatch规则确定语法为DirectoryString的属性值是否为断言值的前缀（即初始子字符串），而不考虑字符串的大小写（大写或小写）。当且仅当属性值是断言值的初始子字符串，且除了可能与大小写有关的字符外，其他字符相同时，该规则才返回TRUE。（来源：X.520）
( 2.5.13.41 NAME 'storedPrefixMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（2.5.13.41名称“storedPrefixMatch”语法1.3.6.1.4.1.1466.115.121.1.15）
Note: This rule can be used, for example, to compare values in the Directory which are telephone area codes with a purported value which is a telephone number.
注意：例如，此规则可用于将目录中的电话区号值与声称的电话号码值进行比较。
The DirectoryString (1.3.6.1.4.1.1466.115.121.1.15) syntax is described in [RFC2252].
[RFC2252]中描述了DirectoryString（1.3.6.1.4.1.1466.115.121.1.15）语法。
The wordMatch rule compares the asserted string with words in an attribute value of DirectoryString syntax. The rule returns TRUE if and only if the asserted word matches any word in the attribute value. Individual word matching is as for the caseIgnoreMatch [RFC2252] matching rule. The precise definition of a "word" is implementation specific. (Source: X.520)
wordMatch规则将断言的字符串与DirectoryString语法属性值中的单词进行比较。当且仅当断言的单词与属性值中的任何单词匹配时，该规则才返回TRUE。单个单词匹配与caseIgnoreMatch[RFC2252]匹配规则相同。“单词”的精确定义是特定于实现的。（来源：X.520）
( 2.5.13.32 NAME 'wordMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（2.5.13.32名称“wordMatch”语法1.3.6.1.4.1.1466.115.121.1.15）
The DirectoryString (1.3.6.1.4.1.1466.115.121.1.15) syntax is described in [RFC2252].
[RFC2252]中描述了DirectoryString（1.3.6.1.4.1.1466.115.121.1.15）语法。
General LDAP security considerations [RFC3377] is applicable to the use of this schema. Additional considerations are noted above where appropriate.
一般LDAP安全注意事项[RFC3377]适用于此模式的使用。在适当的情况下，上文还提到了其他注意事项。
The Internet Assigned Numbers Authority (IANA) has updated the LDAP descriptors registry [RFC3383] as indicated in the following template:
互联网分配号码管理局（IANA）已更新LDAP描述符注册表[RFC3383]，如以下模板所示：
Subject: Request for LDAP Descriptor Registration Update Descriptor (short name): see comment Object Identifier: see comments Person & email address to contact for further information: Kurt Zeilenga <kurt@OpenLDAP.org> Usage: see comments Specification: RFC 3698 Author/Change Controller: IESG Comments:
主题：请求LDAP描述符注册更新描述符（简称）：请参阅注释对象标识符：请参阅注释联系人和电子邮件地址以获取更多信息：Kurt Zeilenga<kurt@OpenLDAP.org>用法：参见注释规范：RFC 3698作者/变更控制者：IESG注释：
The following descriptors have been added:
已添加以下描述符：
NAME Type OID
------------------------ ---- ---------
booleanMatch M 2.5.13.13
caseExactMatch M 2.5.13.5
caseExactOrderingMatch M 2.5.13.6
caseExactSubstringsMatch M 2.5.13.7
caseIgnoreListSubstringsMatch M 2.5.13.12
directoryStringFirstComponentMatch M 2.5.13.31
integerOrderingMatch M 2.5.13.15
keywordMatch M 2.5.13.33
numericStringOrderingMatch M 2.5.13.9
octetStringOrderingMatch M 2.5.13.18
storedPrefixMatch M 2.5.13.41
wordMatch M 2.5.13.32
NAME Type OID
------------------------ ---- ---------
booleanMatch M 2.5.13.13
caseExactMatch M 2.5.13.5
caseExactOrderingMatch M 2.5.13.6
caseExactSubstringsMatch M 2.5.13.7
caseIgnoreListSubstringsMatch M 2.5.13.12
directoryStringFirstComponentMatch M 2.5.13.31
integerOrderingMatch M 2.5.13.15
keywordMatch M 2.5.13.33
numericStringOrderingMatch M 2.5.13.9
octetStringOrderingMatch M 2.5.13.18
storedPrefixMatch M 2.5.13.41
wordMatch M 2.5.13.32
where Type M is Matching Rule.
其中，类型M是匹配规则。
This document makes no new OID assignments. It only associates LDAP matching rule descriptions with existing X.500 matching rules.
此文档不进行新的OID分配。它仅将LDAP匹配规则描述与现有的X.500匹配规则相关联。
This document borrows from [X.520], an ITU-T Recommendation.
本文件借鉴了ITU-T建议[X.520]。
[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月。
[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月。
[RFC2798] Smith, M., "The LDAP inetOrgPerson Object Class", RFC 2798, April 2000.
[RFC2798]Smith，M.，“LDAP inetOrgPerson对象类”，RFC 2798，2000年4月。
[RFC3383] Zeilenga, K., "IANA Considerations for LDAP", BCP 64 RFC 3383, September 2002.
[RFC3383]Zeilenga，K.，“LDAP的IANA考虑”，BCP 64 RFC 3383，2002年9月。
[RFC3703] Strassner, J., Moore, B., Moats, R. and E. Ellesson, "Policy Core LDAP Schema", RFC 3703, February 2004.
[RFC3703]Strassner，J.，Moore，B.，Moats，R.和E.Ellesson，“策略核心LDAP模式”，RFC 3703，2004年2月。
[X.500] International Telecommunication Union - Telecommunication Standardization Sector, "The Directory -- Overview of concepts, models and services," X.500(1993) (also ISO/IEC 9594-1:1994).
[X.500]国际电信联盟-电信标准化部门，“目录——概念、模型和服务概述”，X.500（1993）（也指ISO/IEC 9594-1:1994）。
[X.520] International Telecommunication Union - Telecommunication Standardization Sector, "The Directory: Selected Attribute Types", X.520(1997).
[X.520]国际电信联盟-电信标准化部门，“目录：选定的属性类型”，X.520（1997年）。
Kurt D. Zeilenga OpenLDAP Foundation
库尔特D.Zeeliga OpenLDAP基金会
EMail: Kurt@OpenLDAP.org
EMail: Kurt@OpenLDAP.org
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78 and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。