Network Working Group M. Wahl
Request for Comments: 2256 Critical Angle Inc.
Category: Standards Track December 1997
Network Working Group M. Wahl
Request for Comments: 2256 Critical Angle Inc.
Category: Standards Track December 1997
A Summary of the X.500(96) User Schema for use with LDAPv3
用于LDAPv3的X.500（96）用户模式摘要
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发布。
This document provides an overview of the attribute types and object classes defined by the ISO and ITU-T committees in the X.500 documents, in particular those intended for use by directory clients. This is the most widely used schema for LDAP/X.500 directories, and many other schema definitions for white pages objects use it as a basis. This document does not cover attributes used for the administration of X.500 directory servers, nor does it include attributes defined by other ISO/ITU-T documents.
本文档概述了ISO和ITU-T委员会在X.500文档中定义的属性类型和对象类，特别是目录客户端使用的属性类型和对象类。这是LDAP/X.500目录中使用最广泛的模式，许多其他白页对象的模式定义都以此为基础。本文件不包括用于管理X.500目录服务器的属性，也不包括其他ISO/ITU-T文件定义的属性。
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 [6].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[6]中所述进行解释。
This document references syntaxes given in section 6 of this document and section 6 of [1]. Matching rules are listed in section 8 of this document and section 8 of [1].
本文件引用了本文件第6节和[1]第6节中给出的语法。本文件第8节和[1]第8节列出了匹配规则。
The attribute type and object class definitions are written using the BNF form of AttributeTypeDescription and ObjectClassDescription given in [1]. Lines have been folded for readability.
属性类型和对象类定义是使用[1]中给出的AttributeTypeDescription和ObjectClassDescription的BNF形式编写的。为便于阅读，行已折叠。
The schema definitions in this document are based on those found in X.500 [2],[3],[4],[5], and updates to these documents, specifically:
本文档中的架构定义基于X.500[2]、[3]、[4]、[5]中的定义，以及对这些文档的更新，具体如下：
Sections Source
============ ============
5.1 - 5.2 X.501(93)
5.3 - 5.36 X.520(88)
5.37 - 5.41 X.509(93)
5.42 - 5.52 X.520(93)
5.53 - 5.54 X.509(96)
5.55 X.520(96)
6.1 RFC 1274
6.2 (new syntax)
6.3 - 6.6 RFC 1274
7.1 - 7.2 X.501(93)
7.3 - 7.18 X.521(93)
Sections Source
============ ============
5.1 - 5.2 X.501(93)
5.3 - 5.36 X.520(88)
5.37 - 5.41 X.509(93)
5.42 - 5.52 X.520(93)
5.53 - 5.54 X.509(96)
5.55 X.520(96)
6.1 RFC 1274
6.2 (new syntax)
6.3 - 6.6 RFC 1274
7.1 - 7.2 X.501(93)
7.3 - 7.18 X.521(93)
7.19 - 7.21 X.509(96) 7.22 X.521(96)
7.19 -7.21X.509（96）7.22X.521（96）
Some attribute names are different from those found in X.520(93).
有些属性名与X.520（93）中的属性名不同。
Three new attributes supportedAlgorithms, deltaRevocationList and dmdName, and the objectClass dmd, are defined in the X.500(96) documents.
X.500（96）文档中定义了算法支持的三个新属性：deltaRevocationList和dmdName，以及objectClass dmd。
An LDAP server implementation SHOULD recognize the attribute types described in this section.
LDAP服务器实现应该识别本节中描述的属性类型。
The values of the objectClass attribute describe the kind of object which an entry represents. The objectClass attribute is present in every entry, with at least two values. One of the values is either "top" or "alias".
objectClass属性的值描述条目表示的对象类型。objectClass属性存在于每个条目中，至少有两个值。其中一个值是“top”或“alias”。
( 2.5.4.0 NAME 'objectClass' EQUALITY objectIdentifierMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
（2.5.4.0名称'objectClass'相等objectIdentifierMatch语法1.3.6.1.4.1.1466.115.121.1.38）
The aliasedObjectName attribute is used by the directory service if the entry containing this attribute is an alias.
如果包含此属性的条目是别名，则目录服务将使用aliasedObjectName属性。
( 2.5.4.1 NAME 'aliasedObjectName' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE )
（2.5.4.1名称“别名对象名称”相等区分名称匹配语法1.3.6.1.4.1.1466.115.121.1.12单值）
This attribute is no longer used.
此属性不再使用。
( 2.5.4.2 NAME 'knowledgeInformation' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} )
（2.5.4.2名称“knowledgeInformation”相等caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15{32768}）
This is the X.500 commonName attribute, which contains a name of an object. If the object corresponds to a person, it is typically the person's full name.
这是X.500 commonName属性，它包含对象的名称。如果对象对应于一个人，则通常是该人的全名。
( 2.5.4.3 NAME 'cn' SUP name )
（2.5.4.3名称“cn”SUP名称）
This is the X.500 surname attribute, which contains the family name of a person.
这是X.500姓氏属性，它包含一个人的姓氏。
( 2.5.4.4 NAME 'sn' SUP name )
（2.5.4.4名称“序列号”辅助名称）
This attribute contains the serial number of a device.
此属性包含设备的序列号。
( 2.5.4.5 NAME 'serialNumber' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{64} )
（2.5.4.5名称'serialNumber'相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.44{64}）
This attribute contains a two-letter ISO 3166 country code (countryName).
此属性包含两个字母的ISO 3166国家代码（countryName）。
( 2.5.4.6 NAME 'c' SUP name SINGLE-VALUE )
（2.5.4.6名称“c”辅助名称单值）
This attribute contains the name of a locality, such as a city, county or other geographic region (localityName).
此属性包含地区的名称，例如城市、县或其他地理区域（LocationName）。
( 2.5.4.7 NAME 'l' SUP name )
（2.5.4.7名称“l”辅助名称）
This attribute contains the full name of a state or province (stateOrProvinceName).
此属性包含州或省的全名（州或省名）。
( 2.5.4.8 NAME 'st' SUP name )
（2.5.4.8名称“st”SUP名称）
This attribute contains the physical address of the object to which the entry corresponds, such as an address for package delivery (streetAddress).
此属性包含条目对应的对象的物理地址，例如包传递地址（streetAddress）。
( 2.5.4.9 NAME 'street' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} )
（2.5.4.9名称'street'相等caseIgnoreMatch SUBSTR caseignoresubstrings匹配语法1.3.6.1.4.1.1466.115.121.1.15{128}）
This attribute contains the name of an organization (organizationName).
此属性包含组织的名称（organizationName）。
( 2.5.4.10 NAME 'o' SUP name )
（2.5.4.10名称“o”SUP名称）
This attribute contains the name of an organizational unit (organizationalUnitName).
此属性包含组织单位的名称（organizationalUnitName）。
( 2.5.4.11 NAME 'ou' SUP name )
（2.5.4.11名称“ou”SUP名称）
This attribute contains the title, such as "Vice President", of a person in their organizational context. The "personalTitle" attribute would be used for a person's title independent of their job function.
此属性包含组织环境中人员的头衔，如“副总裁”。“personalTitle”属性将用于独立于其职务职能的人员的职务。
( 2.5.4.12 NAME 'title' SUP name )
（2.5.4.12名称“标题”辅助名称）
This attribute contains a human-readable description of the object.
此属性包含对象的可读描述。
( 2.5.4.13 NAME 'description' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} )
（2.5.4.13名称'description'相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15{1024}）
This attribute is for use by X.500 clients in constructing search filters. It is obsoleted by enhancedSearchGuide, described below in 5.48.
此属性供X.500客户端在构造搜索筛选器时使用。它已被enhancedSearchGuide淘汰，如下文5.48所述。
( 2.5.4.14 NAME 'searchGuide' SYNTAX 1.3.6.1.4.1.1466.115.121.1.25 )
（2.5.4.14名称“searchGuide”语法1.3.6.1.4.1.1466.115.121.1.25）
This attribute describes the kind of business performed by an organization.
此属性描述组织执行的业务类型。
( 2.5.4.15 NAME 'businessCategory' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} )
（2.5.4.15名称'businessCategory'相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15{128}）
( 2.5.4.16 NAME 'postalAddress' EQUALITY caseIgnoreListMatch SUBSTR caseIgnoreListSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
（2.5.4.16名称“PostLaddress”相等caseIgnoreListMatch子字符串caseIgnoreListSubstringsMatch语法1.3.6.1.4.1.1466.115.121.1.41）
( 2.5.4.17 NAME 'postalCode' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} )
（2.5.4.17名称'postalCode'相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15{40}）
( 2.5.4.18 NAME 'postOfficeBox' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} )
（2.5.4.18名称'postOfficeBox'相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15{40}）
( 2.5.4.19 NAME 'physicalDeliveryOfficeName' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} )
（2.5.4.19名称'physicalDeliveryOfficeName'相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15{128}）
( 2.5.4.20 NAME 'telephoneNumber' EQUALITY telephoneNumberMatch SUBSTR telephoneNumberSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.50{32} )
（2.5.4.20名称'telephoneNumber'相等telephoneNumberMatch SUBSTR电话号码SubStringsMatch语法1.3.6.1.4.1.1466.115.121.1.50{32}）
( 2.5.4.21 NAME 'telexNumber' SYNTAX 1.3.6.1.4.1.1466.115.121.1.52 )
（2.5.4.21名称“电传号码”语法1.3.6.1.4.1.1466.115.121.1.52）
( 2.5.4.22 NAME 'teletexTerminalIdentifier' SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 )
（2.5.4.22名称“Teletexterminalidentier”语法1.3.6.1.4.1.1466.115.121.1.51）
( 2.5.4.23 NAME 'facsimileTelephoneNumber' SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 )
（2.5.4.23名称“facsimileTelephoneNumber”语法1.3.6.1.4.1.1466.115.121.1.22）
( 2.5.4.24 NAME 'x121Address' EQUALITY numericStringMatch SUBSTR numericStringSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15} )
（2.5.4.24名称'X121地址'EQUALITY numericStringMatch SubTR numericStringSubstringsMatch语法1.3.6.1.4.1.1466.115.121.1.36{15}）
( 2.5.4.25 NAME 'internationaliSDNNumber' EQUALITY numericStringMatch SUBSTR numericStringSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{16} )
（2.5.4.25名称'internationaliSDNNumber'相等数值字符串匹配SUBSTR numericStringSubstringsMatch语法1.3.6.1.4.1.1466.115.121.1.36{16}）
This attribute holds a postal address suitable for reception of telegrams or expedited documents, where it is necessary to have the recipient accept delivery.
此属性保存适合接收电报或加急文件的邮政地址，在这种情况下，必须让收件人接收邮件。
( 2.5.4.26 NAME 'registeredAddress' SUP postalAddress SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
（2.5.4.26名称“registeredAddress”辅助邮资语法1.3.6.1.4.1.1466.115.121.1.41）
This attribute is used for the telegram service.
此属性用于电报服务。
( 2.5.4.27 NAME 'destinationIndicator' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{128} )
（2.5.4.27名称'destinationIndicator'相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.44{128}）
( 2.5.4.28 NAME 'preferredDeliveryMethod' SYNTAX 1.3.6.1.4.1.1466.115.121.1.14 SINGLE-VALUE )
（2.5.4.28名称“preferredDeliveryMethod”语法1.3.6.1.4.1.1466.115.121.1.14单值）
This attribute contains an OSI presentation address.
此属性包含OSI表示地址。
( 2.5.4.29 NAME 'presentationAddress' EQUALITY presentationAddressMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.43 SINGLE-VALUE )
（2.5.4.29名称'presentationAddress'相等presentationAddressMatch语法1.3.6.1.4.1.1466.115.121.1.43单值）
This attribute contains the identifiers of OSI application contexts.
此属性包含OSI应用程序上下文的标识符。
( 2.5.4.30 NAME 'supportedApplicationContext' EQUALITY objectIdentifierMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
（2.5.4.30名称“supportedApplicationContext”相等objectIdentifierMatch语法1.3.6.1.4.1.1466.115.121.1.38）
( 2.5.4.31 NAME 'member' SUP distinguishedName )
（2.5.4.31名称“成员”辅助识别名称）
( 2.5.4.32 NAME 'owner' SUP distinguishedName )
（2.5.4.32名称“业主”辅助识别名称）
( 2.5.4.33 NAME 'roleOccupant' SUP distinguishedName )
（2.5.4.33名称“角色扮演者”辅助识别名称）
( 2.5.4.34 NAME 'seeAlso' SUP distinguishedName )
（2.5.4.34名称“另见”辅助区分名称）
( 2.5.4.35 NAME 'userPassword' EQUALITY octetStringMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.40{128} )
（2.5.4.35名称'userPassword'相等八位字符串匹配语法1.3.6.1.4.1.1466.115.121.1.40{128}）
Passwords are stored using an Octet String syntax and are not encrypted. Transfer of cleartext passwords are strongly discouraged where the underlying transport service cannot guarantee confidentiality and may result in disclosure of the password to unauthorized parties.
密码使用八位字节字符串语法存储，不加密。如果基础传输服务不能保证机密性，并且可能导致密码泄露给未经授权的方，则强烈反对传输明文密码。
This attribute is to be stored and requested in the binary form, as 'userCertificate;binary'.
该属性将以二进制形式存储和请求，如“userCertificate”；二进制'。
( 2.5.4.36 NAME 'userCertificate' SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 )
（2.5.4.36名称“用户证书”语法1.3.6.1.4.1.1466.115.121.1.8）
This attribute is to be stored and requested in the binary form, as 'cACertificate;binary'.
该属性以二进制形式存储和请求，如“cACertificate”；二进制'。
( 2.5.4.37 NAME 'cACertificate' SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 )
（2.5.4.37名称“cACertificate”语法1.3.6.1.4.1.1466.115.121.1.8）
This attribute is to be stored and requested in the binary form, as 'authorityRevocationList;binary'.
此属性将以二进制形式存储和请求，如“authorityRevocationList”；二进制'。
( 2.5.4.38 NAME 'authorityRevocationList' SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 )
（2.5.4.38名称“authorityRevocationList”语法1.3.6.1.4.1.1466.115.121.1.9）
This attribute is to be stored and requested in the binary form, as 'certificateRevocationList;binary'.
该属性将以二进制形式存储和请求，如“CertificateReceiveList”；二进制'。
( 2.5.4.39 NAME 'certificateRevocationList' SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 )
（2.5.4.39名称“证书职业列表”语法1.3.6.1.4.1.1466.115.121.1.9）
This attribute is to be stored and requested in the binary form, as 'crossCertificatePair;binary'.
该属性以二进制形式存储和请求，如“crossCertificatePair；二进制'。
( 2.5.4.40 NAME 'crossCertificatePair' SYNTAX 1.3.6.1.4.1.1466.115.121.1.10 )
（2.5.4.40名称“crossCertificatePair”语法1.3.6.1.4.1.1466.115.121.1.10）
The name attribute type is the attribute supertype from which string attribute types typically used for naming may be formed. It is unlikely that values of this type itself will occur in an entry. LDAP server implementations which do not support attribute subtyping need not recognize this attribute in requests. Client implementations MUST NOT assume that LDAP servers are capable of performing attribute subtyping.
名称属性类型是属性超类型，通常用于命名的字符串属性类型可以从中形成。这种类型的值本身不太可能出现在条目中。不支持属性子类型的LDAP服务器实现不需要在请求中识别此属性。客户端实现不能假定LDAP服务器能够执行属性子类型。
( 2.5.4.41 NAME 'name' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} )
（2.5.4.41名称'NAME'相等caseIgnoreMatch SUBSTR caseignoresubstrings匹配语法1.3.6.1.4.1.1466.115.121.1.15{32768}）
The givenName attribute is used to hold the part of a person's name which is not their surname nor middle name.
givenName属性用于保留一个人的名字中既不是他们的姓氏也不是中间名的部分。
( 2.5.4.42 NAME 'givenName' SUP name )
（2.5.4.42名称“givenName”辅助名称）
The initials attribute contains the initials of some or all of an individuals names, but not the surname(s).
“姓名首字母”属性包含部分或全部个人姓名的首字母，但不包含姓氏。
( 2.5.4.43 NAME 'initials' SUP name )
（2.5.4.43名称“缩写”SUP名称）
The generationQualifier attribute contains the part of the name which typically is the suffix, as in "IIIrd".
generationQualifier属性包含名称的一部分，该部分通常是后缀，如“IIIrd”中所示。
( 2.5.4.44 NAME 'generationQualifier' SUP name )
（2.5.4.44名称“generationQualifier”辅助名称）
The x500UniqueIdentifier attribute is used to distinguish between objects when a distinguished name has been reused. This is a different attribute type from both the "uid" and "uniqueIdentifier" types.
x500UniqueIdentifier属性用于在重用可分辨名称时区分对象。这是与“uid”和“uniqueIdentifier”类型不同的属性类型。
( 2.5.4.45 NAME 'x500UniqueIdentifier' EQUALITY bitStringMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.6 )
（2.5.4.45名称'x500UniqueIdentifier'相等位字符串匹配语法1.3.6.1.4.1.1466.115.121.1.6）
The dnQualifier attribute type specifies disambiguating information to add to the relative distinguished name of an entry. It is intended for use when merging data from multiple sources in order to prevent conflicts between entries which would otherwise have the same name. It is recommended that the value of the dnQualifier attribute be the same for all entries from a particular source.
dnQualifier属性类型指定要添加到条目的相对可分辨名称中的消歧信息。它用于合并来自多个源的数据时，以防止具有相同名称的条目之间发生冲突。对于来自特定源的所有条目，建议dnQualifier属性的值相同。
( 2.5.4.46 NAME 'dnQualifier' EQUALITY caseIgnoreMatch ORDERING caseIgnoreOrderingMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 )
（2.5.4.46名称“dnQualifier”相等caseIgnoreMatch排序caseIgnoreOrderingMatch子字符串caseIgnoreSubstringsMatch语法1.3.6.1.4.1.1466.115.121.1.44）
This attribute is for use by X.500 clients in constructing search filters.
此属性供X.500客户端在构造搜索筛选器时使用。
( 2.5.4.47 NAME 'enhancedSearchGuide' SYNTAX 1.3.6.1.4.1.1466.115.121.1.21 )
（2.5.4.47名称“enhancedSearchGuide”语法1.3.6.1.4.1.1466.115.121.1.21）
This attribute is used in conjunction with the presentationAddress attribute, to provide additional information to the OSI network service.
此属性与presentationAddress属性一起使用，以向OSI网络服务提供附加信息。
( 2.5.4.48 NAME 'protocolInformation' EQUALITY protocolInformationMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.42 )
（2.5.4.48名称“协议信息”相等协议信息匹配语法1.3.6.1.4.1.1466.115.121.1.42）
This attribute type is not used as the name of the object itself, but it is instead a base type from which attributes with DN syntax inherit.
此属性类型不用作对象本身的名称，而是具有DN语法的属性从中继承的基本类型。
It is unlikely that values of this type itself will occur in an entry. LDAP server implementations which do not support attribute subtyping need not recognize this attribute in requests. Client implementations MUST NOT assume that LDAP servers are capable of performing attribute subtyping.
这种类型的值本身不太可能出现在条目中。不支持属性子类型的LDAP服务器实现不需要在请求中识别此属性。客户端实现不能假定LDAP服务器能够执行属性子类型。
( 2.5.4.49 NAME 'distinguishedName' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
（2.5.4.49名称“DifferentiedName”相等DifferentiedNameMatch语法1.3.6.1.4.1.1466.115.121.1.12）
( 2.5.4.50 NAME 'uniqueMember' EQUALITY uniqueMemberMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 )
（2.5.4.50名称“uniqueMember”相等uniqueMemberMatch语法1.3.6.1.4.1.1466.115.121.1.34）
This attribute is used to identify a building within a location.
此属性用于标识位置内的建筑。
( 2.5.4.51 NAME 'houseIdentifier' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} )
（2.5.4.51名称'houseIdentifier'相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15{32768}）
This attribute is to be stored and requested in the binary form, as 'supportedAlgorithms;binary'.
该属性以二进制形式存储和请求，如“supportedAlgorithms”；二进制'。
( 2.5.4.52 NAME 'supportedAlgorithms' SYNTAX 1.3.6.1.4.1.1466.115.121.1.49 )
（2.5.4.52名称“supportedAlgorithms”语法1.3.6.1.4.1.1466.115.121.1.49）
This attribute is to be stored and requested in the binary form, as 'deltaRevocationList;binary'.
该属性以二进制形式存储和请求，如“deltaRevocationList”；二进制'。
( 2.5.4.53 NAME 'deltaRevocationList' SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 )
（2.5.4.53名称“deltaRevocationList”语法1.3.6.1.4.1.1466.115.121.1.9）
The value of this attribute specifies a directory management domain (DMD), the administrative authority which operates the directory server.
此属性的值指定目录管理域（DMD），即操作目录服务器的管理机构。
( 2.5.4.54 NAME 'dmdName' SUP name )
（2.5.4.54名称“dmdName”辅助名称）
Servers SHOULD recognize the syntaxes defined in this section. Each syntax begins with a sample value of the ldapSyntaxes attribute which defines the OBJECT IDENTIFIER of the syntax. The descriptions of syntax names are not carried in protocol, and are not guaranteed to be unique.
服务器应该识别本节中定义的语法。每个语法都以ldapSyntaxes属性的示例值开始，该属性定义语法的对象标识符。协议中不包含语法名称的描述，也不保证其唯一性。
( 1.3.6.1.4.1.1466.115.121.1.14 DESC 'Delivery Method' )
（1.3.6.1.4.1.1466.115.121.1.14描述“交付方法”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
delivery-value = pdm / ( pdm whsp "$" whsp delivery-value )
交付价值=pdm/（pdm whsp“$”whsp交付价值）
pdm = "any" / "mhs" / "physical" / "telex" / "teletex" /
"g3fax" / "g4fax" / "ia5" / "videotex" / "telephone"
pdm = "any" / "mhs" / "physical" / "telex" / "teletex" /
"g3fax" / "g4fax" / "ia5" / "videotex" / "telephone"
Example:
例子：
telephone
电话
( 1.3.6.1.4.1.1466.115.121.1.21 DESC 'Enhanced Guide' )
（1.3.6.1.4.1.1466.115.121.1.21说明“增强指南”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
EnhancedGuide = woid whsp "#" whsp criteria whsp "#" whsp subset
EnhancedGuide = woid whsp "#" whsp criteria whsp "#" whsp subset
subset = "baseobject" / "oneLevel" / "wholeSubtree"
subset = "baseobject" / "oneLevel" / "wholeSubtree"
The criteria production is defined in the Guide syntax below. This syntax has been added subsequent to RFC 1778.
标准产品在下面的指南语法中定义。此语法是在RFC 1778之后添加的。
Example:
例子：
person#(sn)#oneLevel
个人#（sn）#一级
( 1.3.6.1.4.1.1466.115.121.1.25 DESC 'Guide' )
（1.3.6.1.4.1.1466.115.121.1.25说明“指南”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
guide-value = [ object-class "#" ] criteria
guide-value = [ object-class "#" ] criteria
object-class = woid
object-class = woid
criteria = criteria-item / criteria-set / ( "!" criteria )
criteria = criteria-item / criteria-set / ( "!" criteria )
criteria-set = ( [ "(" ] criteria "&" criteria-set [ ")" ] ) /
( [ "(" ] criteria "|" criteria-set [ ")" ] )
criteria-set = ( [ "(" ] criteria "&" criteria-set [ ")" ] ) /
( [ "(" ] criteria "|" criteria-set [ ")" ] )
criteria-item = [ "(" ] attributetype "$" match-type [ ")" ]
criteria-item = [ "(" ] attributetype "$" match-type [ ")" ]
match-type = "EQ" / "SUBSTR" / "GE" / "LE" / "APPROX"
match-type = "EQ" / "SUBSTR" / "GE" / "LE" / "APPROX"
This syntax should not be used for defining new attributes.
此语法不应用于定义新属性。
( 1.3.6.1.4.1.1466.115.121.1.40 DESC 'Octet String' )
（1.3.6.1.4.1.1466.115.121.1.40描述“八进制字符串”）
Values in this syntax are encoded as octet strings.
此语法中的值编码为八位字节字符串。
Example:
例子：
secret
秘密
( 1.3.6.1.4.1.1466.115.121.1.51 DESC 'Teletex Terminal Identifier' )
（1.3.6.1.4.1.1466.115.121.1.51描述“电传终端标识符”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
teletex-id = ttx-term 0*("$" ttx-param)
电传id=ttx术语0*（“$”ttx参数）
ttx-term = printablestring
ttx-term = printablestring
ttx-param = ttx-key ":" ttx-value
ttx参数=ttx键“：“ttx值
ttx-key = "graphic" / "control" / "misc" / "page" / "private"
ttx-key = "graphic" / "control" / "misc" / "page" / "private"
ttx-value = octetstring
ttx-value = octetstring
In the above, the first printablestring is the encoding of the first portion of the teletex terminal identifier to be encoded, and the subsequent 0 or more octetstrings are subsequent portions of the teletex terminal identifier.
在上面，第一个可打印字符串是要编码的电传终端标识符的第一部分的编码，随后的0个或更多个八位字符串是电传终端标识符的后续部分。
( 1.3.6.1.4.1.1466.115.121.1.52 DESC 'Telex Number' )
（1.3.6.1.4.1.1466.115.121.1.52描述“电传号码”）
Values in this syntax are encoded according to the following BNF:
此语法中的值根据以下BNF进行编码：
telex-number = actual-number "$" country "$" answerback
电传号码=实际号码“$”国家“$”应答
actual-number = printablestring
actual-number = printablestring
country = printablestring
country = printablestring
answerback = printablestring
answerback = printablestring
In the above, actual-number is the syntactic representation of the number portion of the TELEX number being encoded, country is the TELEX country code, and answerback is the answerback code of a TELEX terminal.
在上面，实际数字是正在编码的电传号码的数字部分的语法表示，国家是电传国家代码，应答是电传终端的应答代码。
( 1.3.6.1.4.1.1466.115.121.1.49 DESC 'Supported Algorithm' )
（1.3.6.1.4.1.1466.115.121.1.49描述“支持的算法”）
No printable representation of values of the supportedAlgorithms attribute is defined in this document. Clients which wish to store and retrieve this attribute MUST use "supportedAlgorithms;binary", in which the value is transferred as a binary encoding.
本文档中未定义supportedAlgorithms属性值的可打印表示形式。希望存储和检索此属性的客户端必须使用“supportedAlgorithms；binary”，其中值作为二进制编码传输。
LDAP servers MUST recognize the object classes "top" and "subschema". LDAP servers SHOULD recognize all the other object classes listed here as values of the objectClass attribute.
LDAP服务器必须识别对象类“top”和“subschema”。LDAP服务器应将此处列出的所有其他对象类识别为objectClass属性的值。
( 2.5.6.0 NAME 'top' ABSTRACT MUST objectClass )
（2.5.6.0名称“top”抽象必须为objectClass）
( 2.5.6.1 NAME 'alias' SUP top STRUCTURAL MUST aliasedObjectName )
（2.5.6.1名称“alias”SUP top STRUCTURAL必须别名为Object NAME）
( 2.5.6.2 NAME 'country' SUP top STRUCTURAL MUST c MAY ( searchGuide $ description ) )
（2.5.6.2名称“国家”SUP top STRUCTURAL c MAY（searchGuide$说明））
( 2.5.6.3 NAME 'locality' SUP top STRUCTURAL MAY ( street $ seeAlso $ searchGuide $ st $ l $ description ) )
（2.5.6.3名称“地点”辅助顶部结构可能（街道$另见$搜索指南$st$l$说明））
( 2.5.6.4 NAME 'organization' SUP top STRUCTURAL MUST o MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ st $ l $ description ) )
（2.5.6.4名称“组织”支持顶部结构必须（用户密码$searchGuide$另请参见$businessCategory$X121地址$registeredAddress$destinationIndicator$preferredDeliveryMethod$telexNumber$teletexTerminalIdentifier$telephoneNumber$internationaliSDNNumber$facsimileTelephoneNumber$street$postOfficeBox$postalCode$postalAddress$physicalDeliveryOfficeName$st$l$d描述）
( 2.5.6.5 NAME 'organizationalUnit' SUP top STRUCTURAL MUST ou MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ st $ l $ description ) )
（2.5.6.5必须将“组织单元”的名称命名为顶部结构单元（用户密码$searchGuide$另请参见$businessCategory$X121地址$registeredAddress$destinationIndicator$preferredDeliveryMethod$telexNumber$teletexTerminalIdentifier$telephoneNumber$internationaliSDNNumber$facsimileTelephoneNumber$street$postOfficeBox$postalCode$postalAddress$physicalDeliveryOfficeName$st$l$d描述）
( 2.5.6.6 NAME 'person' SUP top STRUCTURAL MUST ( sn $ cn ) MAY ( userPassword $ telephoneNumber $ seeAlso $ description ) )
（2.5.6.6名称“人员”支持顶部结构必须（sn$cn）可以（用户密码$telephoneNumber$另见$description））
( 2.5.6.7 NAME 'organizationalPerson' SUP person STRUCTURAL MAY ( title $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $
（2.5.6.7名称“组织人员”辅助人员结构可能（标题$X121地址$registeredAddress$destinationIndicator$PreferredDelivery方法$telexNumber$teletexTerminalIdentifier$电话号码$internationaliSDNNumber）$
facsimileTelephoneNumber $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ ou $ st $ l ) )
传真电话号码$street$邮局信箱$postalCode$邮局地址$physicalDeliveryOfficeName$ou$st$l））
( 2.5.6.8 NAME 'organizationalRole' SUP top STRUCTURAL MUST cn MAY ( x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ seeAlso $ roleOccupant $ preferredDeliveryMethod $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ ou $ st $ l $ description ) )
（2.5.6.8名称“组织角色”支持顶部结构（X121地址$registeredAddress$destinationIndicator$preferredDeliveryMethod$telexNumber$teletexTerminalIdentifier$telephoneNumber$facsimileTelephoneNumber$另请参见$roleOccupant$preferredDeliveryMethod$street$postOfficeBox$postalCode$Postladdress$physicalDeliveryOfficeName$ou$st$l$des（抄录）
( 2.5.6.9 NAME 'groupOfNames' SUP top STRUCTURAL MUST ( member $ cn ) MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) )
（2.5.6.9名称“groupOfNames”SUP top STRUCTURAL MUST（会员$cn）MAY（业务类别$SEE另见$owner$ou$o$description））
( 2.5.6.10 NAME 'residentialPerson' SUP person STRUCTURAL MUST l MAY ( businessCategory $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ preferredDeliveryMethod $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ st $ l ) )
（2.5.6.10“住户人员”的姓名（业务类别$X121地址$registeredAddress$destinationIndicator$preferredDeliveryMethod$telexNumber$Teletexterminalidentier$telephoneNumber$InternationalIsDN号码$FacSimiletPhoneNumber$preferredDeliveryMethod$street$postOfficeBox$postalCode$postalAddress$physicalDeliveryOfficeName$st$l））
( 2.5.6.11 NAME 'applicationProcess' SUP top STRUCTURAL MUST cn MAY ( seeAlso $ ou $ l $ description ) )
（2.5.6.11名称“申请流程”SUP-top结构必须cn-MAY（另请参见$ou$l$说明））
( 2.5.6.12 NAME 'applicationEntity' SUP top STRUCTURAL MUST ( presentationAddress $ cn ) MAY ( supportedApplicationContext $ seeAlso $ ou $ o $ l $ description ) )
（2.5.6.12名称“applicationEntity”Supp top STRUCTURAL MUST（表示地址$cn）MAY（支持的应用程序上下文$参见$ou$o$l$说明））
( 2.5.6.13 NAME 'dSA' SUP applicationEntity STRUCTURAL MAY knowledgeInformation )
（2.5.6.13名称“dSA”辅助应用程序属性知识信息）
( 2.5.6.14 NAME 'device' SUP top STRUCTURAL MUST cn MAY ( serialNumber $ seeAlso $ owner $ ou $ o $ l $ description ) )
（2.5.6.14名称“设备”支持顶部结构必须为cn-MAY（序列号$另见$所有者$ou$o$l$说明））
( 2.5.6.15 NAME 'strongAuthenticationUser' SUP top AUXILIARY MUST userCertificate )
（2.5.6.15名称'strongAuthenticationUser'辅助用户证书）
( 2.5.6.16 NAME 'certificationAuthority' SUP top AUXILIARY MUST ( authorityRevocationList $ certificateRevocationList $ cACertificate ) MAY crossCertificatePair )
（2.5.6.16名称“certificationAuthority”SUP-top辅助必须（authorityRevocationList$CertificatereJournalist$cACertificate）可以交叉认证Pair）
( 2.5.6.17 NAME 'groupOfUniqueNames' SUP top STRUCTURAL MUST ( uniqueMember $ cn ) MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) )
（2.5.6.17命名“groupOfUniqueNames”SUP top STRUCTURAL MUST（uniqueMember$cn）MAY（businessCategory$另见$owner$ou$o$说明））
( 2.5.6.18 NAME 'userSecurityInformation' SUP top AUXILIARY MAY ( supportedAlgorithms ) )
（2.5.6.18名称“userSecurityInformation”SUP-top辅助可能（支持的算法））
( 2.5.6.16.2 NAME 'certificationAuthority-V2' SUP certificationAuthority AUXILIARY MAY ( deltaRevocationList ) )
（2.5.6.16.2名称'certificationAuthority-V2'SUP certificationAuthority Assistant MAY（Deltar唤起列表））
( 2.5.6.19 NAME 'cRLDistributionPoint' SUP top STRUCTURAL MUST ( cn ) MAY ( certificateRevocationList $ authorityRevocationList $ deltaRevocationList ) )
（2.5.6.19命名“cRLDistributionPoint”SUP top STRUCTURAL MUST（cn）MAY（CertificatereJournalist$authorityRevocationList$DeltarRevocationList））
( 2.5.6.20 NAME 'dmd' SUP top STRUCTURAL MUST ( dmdName ) MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $
（2.5.6.20名称“dmd”SUP top STRUCTURAL MUST（dmdName）MAY（用户密码$searchGuide$另请参见$businessCategory$X121地址$registeredAddress$destinationIndicator$preferredDeliveryMethod$telexNumber$Teletexterminalidentier$电话号码$InternationalISDN号码$FacSimiletPhonenumber$
street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ st $ l $ description ) )
街道$postOfficeBox$postalCode$postalAddress$physicalDeliveryOfficeName$st$l$description））
Servers MAY implement additional matching rules.
服务器可以实现额外的匹配规则。
Servers which implement the extensibleMatch filter SHOULD allow the matching rule 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中使用本节中列出的匹配规则。通常，当匹配规则的断言语法与属性的值语法相同时，这些服务器应允许将匹配规则用于服务器已知的所有属性类型。
( 2.5.13.17 NAME 'octetStringMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 )
（2.5.13.17名称“octetStringMatch”语法1.3.6.1.4.1.1466.115.121.1.40）
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.
目录项的属性用于提供有关它们所表示的真实对象的描述性信息，这些对象可以是人、组织或设备。大多数国家都有关于发布个人信息的隐私法。
Transfer of cleartext passwords are strongly discouraged where the underlying transport service cannot guarantee confidentiality and may result in disclosure of the password to unauthorized parties.
如果基础传输服务不能保证机密性，并且可能导致密码泄露给未经授权的方，则强烈反对传输明文密码。
The definitions on which this document have been developed by committees for telecommunications and international standards. No new attribute definitions have been added. The syntax definitions are based on the ISODE "QUIPU" implementation of X.500.
电信委员会和国际标准委员会制定本文件所依据的定义。未添加新的属性定义。语法定义基于X.500的ISODE“QUIPU”实现。
[1] Wahl, M., Coulbeck, A., Howes, T., and S. Kille, "Lightweight X.500 Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 2252, December 1997.
[1] Wahl，M.，Coulbeck，A.，Howes，T.，和S.Kille，“轻量级X.500目录访问协议（v3）：属性语法定义”，RFC2252，1997年12月。
[2] The Directory: Models. ITU-T Recommendation X.501, 1996.
[2] 目录：Models。ITU-T建议X.501，1996年。
[3] The Directory: Authentication Framework. ITU-T Recommendation X.509, 1996.
[3] 目录：身份验证框架。ITU-T建议X.509，1996年。
[4] The Directory: Selected Attribute Types. ITU-T Recommendation X.520, 1996.
[4] 目录：选定的属性类型。ITU-T建议X.520，1996年。
[5] The Directory: Selected Object Classes. ITU-T Recommendation X.521, 1996.
[5] 目录：选定的对象类。ITU-T建议X.5211996。
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997.
[6] Bradner，S.，“RFC中用于表示需求水平的关键词”，RFC 211997年3月。
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
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。