Network Working Group N. Freed
Request for Comments: 2278 Innosoft
BCP: 19 J. Postel
Category: Best Current Practice ISI
January 1998
Network Working Group N. Freed
Request for Comments: 2278 Innosoft
BCP: 19 J. Postel
Category: Best Current Practice ISI
January 1998
IANA Charset Registration Procedures
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 (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. In particular, the general applicability and appropriateness of a given registered charset is a protocol issue, not a registration issue, and is not dealt with by this registration procedure.
MIME[RFC-2045、RFC-2046、RFC-2047、RFC-2184]和各种其他现代互联网协议能够使用许多不同的字符集。这反过来意味着标记不同字符集的能力至关重要。此注册过程仅用于将一个或多个特定名称与给定的字符集相关联，并指示是否可以在MIME文本对象中使用给定的字符集。特别是，给定注册字符集的一般适用性和适当性是一个协议问题，而不是注册问题，并且不在本注册程序中处理。
The following sections define various terms used in this document.
以下各节定义了本文件中使用的各种术语。
This document occasionally uses terms that appear in capital letters. When the terms "MUST", "SHOULD", "MUST NOT", "SHOULD NOT", and "MAY" appear capitalized, they are being used to indicate particular requirements of this specification. A discussion of the meanings of these terms appears in [RFC-2119].
本文档偶尔使用大写字母表示的术语。当术语“必须”、“应该”、“不得”、“不应该”和“可能”出现大写时，它们被用来表示本规范的特殊要求。[RFC-2119]中对这些术语的含义进行了讨论。
A member of a set of elements used for the organisation, control, or representation of data.
用于组织、控制或表示数据的一组元素的成员。
The term "charset" (see historical note below) is used here to refer to a method of converting a sequence of octets into a sequence of characters. This conversion may also optionally produce additional control information such as directionality indicators.
这里使用术语“字符集”（参见下面的历史注释）指的是将八位字节序列转换为字符序列的方法。该转换还可以选择性地产生附加控制信息，例如方向性指示符。
Note that unconditional and unambiguous conversion in the other direction is not required, in that not all characters may be representable by a given charset and a charset may provide more than one sequence of octets to represent a particular sequence of characters.
注意，不需要在另一个方向上进行无条件和明确的转换，因为并非所有字符都可以由给定的字符集表示，并且一个字符集可以提供多个八位字节序列来表示特定的字符序列。
This definition is intended to allow charsets to be defined in a variety of different ways, from simple single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO 2022's techniques, to be used as charsets. However, the definition associated with a charset name must fully specify the mapping to be performed. In particular, use of external profiling information to determine the exact mapping is not permitted.
此定义旨在允许以多种不同的方式定义字符集，从简单的单表映射（如US-ASCII）到复杂的表交换方法（如使用ISO 2022技术的转换方法），将其用作字符集。但是，与字符集名称关联的定义必须完全指定要执行的映射。特别是，不允许使用外部分析信息来确定精确的映射。
HISTORICAL NOTE: The term "character set" was originally used in MIME to describe such straightforward schemes as US-ASCII and ISO-8859-1 which consist of a small set of characters and a simple one-to-one mapping from single octets to single characters. Multi-octet character encoding schemes and switching techniques make the situation much more complex. As such, the definition of this term was revised to emphasize both the conversion aspect of the process, and the term itself has been changed to "charset" to emphasize that it is not, after all, just a set of characters. A discussion of these issues as well as specification of standard terminology for use in the IETF appears in RFC 2130.
历史注释：“字符集”一词最初在MIME中用于描述US-ASCII和ISO-8859-1等简单方案，这些方案由一小部分字符和从单个八位字节到单个字符的简单一对一映射组成。多八进制字符编码方案和切换技术使情况更加复杂。因此，对该术语的定义进行了修订，以强调该过程的转换方面，并且将该术语本身更改为“字符集”，以强调它毕竟不仅仅是一组字符。关于这些问题的讨论以及IETF中使用的标准术语规范见RFC 2130。
A Coded Character Set (CCS) is a mapping from a set of abstract characters to a set of integers. Examples of coded character sets are ISO 10646 [ISO-10646], US-ASCII [US-ASCII], and the ISO-8859 series [ISO-8859].
编码字符集（CCS）是从一组抽象字符到一组整数的映射。编码字符集的示例有ISO 10646[ISO-10646]、US-ASCII[US-ASCII]和ISO-8859系列[ISO-8859]。
A Character Encoding Scheme (CES) is a mapping from a Coded Character Set or several coded character sets to a set of octets. A given CES is typically associated with a single CCS; for example, UTF-8 applies only to ISO 10646.
字符编码方案（CES）是从一个或多个编码字符集到一组八位字节的映射。给定的CES通常与单个CCS相关联；例如，UTF-8仅适用于ISO 10646。
Registered charsets are expected to conform to a number of requirements as described below.
注册的字符集应符合如下所述的许多要求。
Registered charsets MUST conform to the definition of a "charset" given above. In addition, charsets intended for use in MIME content types under the "text" top-level type must conform to the restrictions on that type described in RFC 2045. All registered charsets MUST note whether or not they are suitable for use in MIME.
注册的字符集必须符合上述“字符集”的定义。此外，“text”顶级类型下MIME内容类型中使用的字符集必须符合RFC 2045中描述的对该类型的限制。所有注册的字符集必须注意它们是否适合在MIME中使用。
All charsets which are constructed as a composition of a CCS and a CES MUST either include the CCS and CES they are based on in their registration or else cite a definition of their CCS and CES that appears elsewhere.
构成CCS和CES组成部分的所有字符集必须包括其注册中基于的CCS和CES，或者引用其他地方出现的CCS和CES定义。
All registered charsets MUST be specified in a stable, openly available specification. Registration of charsets whose specifications aren't stable and openly available is forbidden.
所有注册的字符集必须在稳定、公开的规范中指定。禁止注册规格不稳定且不公开的字符集。
This registration mechanism is not intended to be a vehicle for the definition of entirely new charsets. This is due to the fact that the registration process does NOT contain adequate review mechanisims for such undertakings.
该注册机制并非用于定义全新字符集的工具。这是因为登记过程中没有为此类企业提供充分的审查机制。
As such, only charsets defined by other processes and standards bodies, or specific profiles of such charsets, are eligible for registration.
因此，只有其他流程和标准机构定义的字符集或此类字符集的特定配置文件才有资格注册。
One or more names MUST be assigned to all registered charsets. Multiple names for the same charset are permitted, but if multiple names are assigned a single primary name for the charset MUST be identified. All other names are considered to be aliases for the primary name and use of the primary name is preferred over use of any of the aliases.
必须为所有已注册的字符集分配一个或多个名称。允许为同一字符集指定多个名称，但如果为多个名称分配了一个主名称，则必须为该字符集标识一个主名称。所有其他名称都被视为主要名称的别名，使用主要名称优先于使用任何别名。
Each assigned name MUST uniquely identify a single charset. All charset names MUST be suitable for use as the value of a MIME content type charset parameter and hence MUST conform to MIME parameter value syntax. This applies even if the specific charset being registered is not suitable for use with the "text" media type.
每个分配的名称必须唯一标识一个字符集。所有字符集名称必须适合用作MIME内容类型字符集参数的值，因此必须符合MIME参数值语法。即使正在注册的特定字符集不适合与“文本”媒体类型一起使用，这也适用。
Finally, charsets being registered for use with the "text" media type MUST have a primary name that conforms to the more restrictive syntax of the charset field in MIME encoded-words [RFC-2047, RFC-2184] and MIME extended parameter values [RFC-2184]. A combined ABNF definition for such names is as follows:
最后，注册用于“文本”媒体类型的字符集的主名称必须符合MIME编码字[RFC-2047，RFC-2184]和MIME扩展参数值[RFC-2184]中字符集字段更严格的语法。此类名称的组合ABNF定义如下：
mime-charset = 1*<Any CHAR except SPACE, CTLs, and cspecials>
mime-charset = 1*<Any CHAR except SPACE, CTLs, and cspecials>
cspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "
<"> / "/" / "[" / "]" / "?" / "." / "=" / "*"
cspecials = "(" / ")" / "<" / ">" / "@" / "," / ";" / ":" / "
<"> / "/" / "[" / "]" / "?" / "." / "=" / "*"
CHAR = <any ASCII character> ; ( 0-177, 0.-127.)
SPACE = <ASCII SP, space> ; ( 40, 32.)
CTL = <any ASCII control ; ( 0- 37, 0.- 31.)
character and DEL> ; ( 177, 127.)
CHAR = <any ASCII character> ; ( 0-177, 0.-127.)
SPACE = <ASCII SP, space> ; ( 40, 32.)
CTL = <any ASCII control ; ( 0- 37, 0.- 31.)
character and DEL> ; ( 177, 127.)
Charsets must function as actual charsets: Registration of things that are better thought of as a transfer encoding, as a media type, or as a collection of separate entities of another type, is not allowed. For example, although HTML could theoretically be thought of as a charset, it is really better thought of as a media type and as such it cannot be registered as a charset.
字符集必须像实际的字符集一样工作：不允许注册更好地被认为是传输编码、媒体类型或其他类型的单独实体的集合的东西。例如，虽然理论上HTML可以被认为是一个字符集，但它实际上更好地被认为是一种媒体类型，因此它不能注册为字符集。
Use of a large number of charsets in a given protocol may hamper interoperability. However, the use of a large number of undocumented and/or unlabelled charsets hampers interoperability even more.
在给定协议中使用大量字符集可能会妨碍互操作性。然而，大量未记录和/或未标记字符集的使用更妨碍了互操作性。
A charset should therefore be registered ONLY if it adds significant functionality that is valuable to a large community, OR if it documents existing practice in a large community. Note that charsets registered for the second reason should be explicitly marked as being of limited or specialized use and should only be used in Internet messages with prior bilateral agreement.
因此，只有当字符集添加了对大型社区有价值的重要功能，或者记录了大型社区中的现有实践时，才应该注册该字符集。请注意，出于第二个原因注册的字符集应明确标记为有限或专用，并且仅应在事先获得双边协议的互联网消息中使用。
Charset registrations can be published in RFCs, however, RFC publication is not required to register a new charset.
可以在RFC中发布字符集注册，但是注册新字符集不需要RFC发布。
The registration of a charset does not imply endorsement, approval, or recommendation by the IANA, IESG, or IETF, or even certification that the specification is adequate. It is expected that applicability statements for particular applications will be published from time to time that recommend implementation of, and support for, charsets that have proven particularly useful in those contexts.
字符集的注册并不意味着IANA、IESG或IETF的认可、批准或建议，甚至也不意味着证明该规范是充分的。预计将不时发布特定应用程序的适用性声明，建议在这些环境中特别有用的字符集的实现和支持。
Each registered charset MUST also be assigned a unique enumerated integer value. These "MIBenum" values are defined by and used in the Printer MIB [RFC-1759].
每个注册的字符集还必须分配一个唯一的枚举整数值。这些“MIBenum”值由打印机MIB[RFC-1759]定义并在其中使用。
A MIBenum value for each charset will be assigned by IANA at the time of registration.
IANA将在注册时为每个字符集分配一个MIBenum值。
The following procedure has been implemented by the IANA for review and approval of new charsets. This is not a formal standards process, but rather an administrative procedure intended to allow community comment and sanity checking without excessive time delay.
IANA已实施以下程序，以审查和批准新字符集。这不是一个正式的标准过程，而是一个行政程序，旨在允许社区评论和健全性检查，而不需要过多的时间延迟。
Send the proposed charset registration to the "ietf-charsets@iana.org" mailing list. This mailing list has been established for the sole purpose of reviewing proposed charset registrations. Proposed charsets are not formally registered and must not be used; the "x-" prefix specified in RFC 2045 can be used until registration is complete.
将建议的字符集注册发送到“ietf”-charsets@iana.org“邮件列表。本邮件列表仅用于审查拟议的字符集注册。提议的字符集未正式注册，不得使用；RFC 2045中指定的“x-”前缀可以使用，直到注册完成。
The intent of the public posting is to solicit comments and feedback on the definition of the charset and the name chosen for it over a two week period.
公开发布的目的是在两周内就字符集的定义和为其选择的名称征求意见和反馈。
When the two week period has passed and the registration proposer is convinced that consensus has been achieved, the registration application should be submitted to IANA and the charset reviewer. The charset reviewer, who is appointed by the IETF Applications Area Director(s), either approves the request for registration or rejects it. Rejection may occur because of significant objections raised on the list or objections raised externally. If the charset reviewer considers the registration sufficiently important and controversial, a last call for comments may be issued to the full IETF. The charset
两周时间过后，注册申请人确信已达成共识后，应将注册申请提交给IANA和字符集审查员。IETF应用领域主管指定的字符集审查员批准或拒绝注册请求。由于清单上提出的重大异议或外部提出的异议，可能会导致拒绝。如果字符集评审员认为注册足够重要且有争议，则可向完整的IETF发出最后一次征求意见的通知。字符集
reviewer may also recommend standards track processing (before or after registration) when that appears appropriate and the level of specification of the charset is adequate.
当合适且字符集的规格级别足够时，评审员还可以建议标准跟踪处理（注册前或注册后）。
Decisions made by the reviewer must be posted to the ietf-charsets mailing list within 14 days. Decisions made by the reviewer may be appealed to the IESG.
评审员做出的决定必须在14天内发布到ietf字符集邮件列表中。评审员做出的决定可向IESG提出上诉。
Provided that the charset registration has either passed review or has been successfully appealed to the IESG, the IANA will register the charset, assign a MIBenum value, and make its registration available to the community.
如果字符集注册已通过审查或已成功上诉至IESG，IANA将注册该字符集，分配MIBenum值，并向社区提供其注册。
Charset registrations will be posted in the anonymous FTP file "ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets" and all registered charsets will be listed in the periodically issued "Assigned Numbers" RFC [currently RFC-1700]. The description of the charset may also be published as an Informational RFC by sending it to "rfc-editor@isi.edu" (please follow the instructions to RFC authors [RFC-2223]).
字符集注册将发布在匿名FTP文件中“ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets所有注册的字符集都将列在定期发布的“分配号码”RFC[目前为RFC-1700]中。字符集的描述也可以通过发送到“RFC”作为信息RFC发布-editor@isi.edu“（请遵循RFC作者须知[RFC-2223]）。
To: ietf-charsets@iana.org Subject: Registration of new charset
致：ietf-charsets@iana.org主题：新字符集的注册
Charset name(s):
字符集名称：
(All names must be suitable for use as the value of a MIME content-type parameter.)
（所有名称必须适合用作MIME内容类型参数的值。）
Published specification(s):
已发布的规范：
(A specification for the charset must be openly available that accurately describes what is being registered. If a charset is defined as a composition of a CCS and a CES then these defintions must either be included or referenced.)
（必须公开提供准确描述注册内容的字符集规范。如果字符集定义为CCS和CES的组合，则必须包含或引用这些定义。）
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
This registration procedure is not known to raise any sort of security considerations that are appreciably different from those already existing in the protocols that employ registered charsets.
我们不知道这个注册过程会引起任何类型的安全考虑，这些安全考虑与使用注册字符集的协议中已经存在的安全考虑有明显的不同。
[ISO-2022] International Standard -- Information Processing -- Character Code Structure and Extension Techniques, ISO/IEC 2022:1994, 4th ed.
[ISO-2022]国际标准——信息处理——字符代码结构和扩展技术，ISO/IEC 2022:1994，第4版。
[ISO-8859] International Standard -- Information Processing -- 8-bit Single-Byte Coded Graphic Character Sets - Part 1: Latin Alphabet No. 1, ISO 8859-1:1987, 1st ed. - Part 2: Latin Alphabet No. 2, ISO 8859-2:1987, 1st ed. - Part 3: Latin Alphabet No. 3, ISO 8859-3:1988, 1st ed. - Part 4: Latin Alphabet No. 4, ISO 8859-4:1988, 1st ed. - Part 5: Latin/Cyrillic Alphabet, ISO 8859-5:1988, 1st ed. - Part 6: Latin/Arabic Alphabet, ISO 8859-6:1987, 1st ed. - Part 7: Latin/Greek Alphabet, ISO 8859-7:1987, 1st ed. - Part 8: Latin/Hebrew Alphabet, ISO 8859-8:1988, 1st ed. - Part 9: Latin Alphabet No. 5, ISO/IEC 8859-9:1989, 1st ed. International Standard -- Information Technology -- 8-bit Single-Byte Coded Graphic Character Sets - Part 10: Latin Alphabet No. 6, ISO/IEC 8859-10:1992, 1st ed.
[ISO-8859]国际标准——信息处理——8位单字节编码图形字符集——第1部分：拉丁字母表1，ISO 8859-1:1987，第1版——第2部分：拉丁字母表2，ISO 8859-2:1987，第1版——第3部分：拉丁字母表3，ISO 8859-3:1988，第1版——第4部分：拉丁字母表4，ISO 8859-4:1988，第1版-第5部分：拉丁/西里尔字母表，ISO 8859-5:1988，第1版-第6部分：拉丁/阿拉伯字母表，ISO 8859-6:1987，第1版-第7部分：拉丁/希腊字母表，ISO 8859-7:1987，第1版-第8部分：拉丁/希伯来字母表，ISO 8859-8:1988，第1版-第9部分：拉丁字母表5，ISO/IEC 8859-9:1989，第1版国际标准信息技术8位单字节编码图形字符集第10部分：第6号拉丁字母ISO/IEC 8859-10:1992第1版。
[ISO-10646] ISO/IEC 10646-1:1993(E), "Information technology -- Universal Multiple-Octet Coded Character Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane", JTC1/SC2, 1993.
[ISO-10646]ISO/IEC 10646-1:1993（E），“信息技术——通用多八位编码字符集（UCS）——第1部分：体系结构和基本多语言平面”，JTC1/SC2，1993年。
[RFC-2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", RFC 2048, November 1996.
[RFC-2048]Freed，N.，Klensin，J.，和J.Postel，“多用途互联网邮件扩展（MIME）第四部分：注册程序”，RFC 2048，1996年11月。
[RFC-1700] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC 1700, October 1994.
[RFC-1700]雷诺兹，J.和J.波斯特尔，“分配的数字”，标准2，RFC 1700，1994年10月。
[RFC-1759] Smith, R., Wright, F., Hastings, T., Zilles, S., and J. Gyllenskog, "Printer MIB", RFC 1759, March 1995.
[RFC-1759]Smith，R.，Wright，F.，Hastings，T.，Zilles，S.，和J.Gylenskog，“打印机MIB”，RFC 1759，1995年3月。
[RFC-2045] Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[RFC-2045]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第一部分：Internet邮件正文格式”，RFC 20451996年11月。
[RFC-2046] Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996.
[RFC-2046]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第二部分：媒体类型”，RFC 2046，1996年11月。
[RFC-2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) Part Three: Representation of Non-Ascii Text in Internet Message Headers", RFC 2047, November 1996.
[RFC-2047]Moore，K.，“多用途Internet邮件扩展（MIME）第三部分：Internet消息头中非Ascii文本的表示”，RFC 2047，1996年11月。
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC-2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC-2130] Weider, C., Preston, C., Simonsen, K., Alvestrand, H., Atkinson, R., Crispin, M., and P. Svanberg, "Report from the IAB Character Set Workshop", RFC 2130, April 1997.
[RFC-2130]Weider，C.，Preston，C.，Simonsen，K.，Alvestrand，H.，Atkinson，R.，Crispin，M.，和P.Svanberg，“来自IAB字符集研讨会的报告”，RFC 2130，1997年4月。
[RFC-2184] Freed, N., and K. Moore, "MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations", RFC 2184, August 1997.
[RFC-2184]Freed，N.和K.Moore，“MIME参数值和编码字扩展：字符集、语言和连续体”，RFC 21842997年8月。
[US-ASCII] Coded Character Set -- 7-Bit American Standard Code for Information Interchange, ANSI X3.4-1986.
[US-ASCII]编码字符集——信息交换用7位美国标准代码，ANSI X3.4-1986。
Ned Freed Innosoft International, Inc. 1050 Lakes Drive West Covina, CA 91790 USA
Ned Freed Innosoft International，Inc.美国加利福尼亚州西科维纳湖大道1050号，邮编：91790
Phone: +1 626 919 3600
Fax: +1 626 919 3614
EMail: ned.freed@innosoft.com
Phone: +1 626 919 3600
Fax: +1 626 919 3614
EMail: ned.freed@innosoft.com
Jon Postel USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 USA
Jon Postel USC/信息科学研究所4676金钟路Marina del Rey，加利福尼亚州90292
Phone: +1 310 822 1511
Fax: +1 310 823 6714
EMail: Postel@ISI.EDU
Phone: +1 310 822 1511
Fax: +1 310 823 6714
EMail: Postel@ISI.EDU
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。