Internet Engineering Task Force (IETF) T. Hansen
Request for Comments: 6839 AT&T Laboratories
Updates: 3023 A. Melnikov
Category: Informational Isode Ltd
ISSN: 2070-1721 January 2013
Internet Engineering Task Force (IETF) T. Hansen
Request for Comments: 6839 AT&T Laboratories
Updates: 3023 A. Melnikov
Category: Informational Isode Ltd
ISSN: 2070-1721 January 2013
Additional Media Type Structured Syntax Suffixes
其他媒体类型结构化语法后缀
Abstract
摘要
A content media type name sometimes includes partitioned meta-information distinguished by a structured syntax to permit noting an attribute of the media as a suffix to the name. This document defines several structured syntax suffixes for use with media type registrations. In particular, it defines and registers the "+json", "+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" structured syntax suffixes, and provides a media type structured syntax suffix registration form for the "+xml" structured syntax suffix.
内容媒体类型名称有时包括通过结构化语法区分的分区元信息，以允许将媒体属性作为名称的后缀。本文档定义了用于媒体类型注册的几个结构化语法后缀。特别是，它定义并注册了“+json”、“+ber”、“+der”、“+FastInfo集”、“+wbxml”和“+zip”结构化语法后缀，并为“+xml”结构化语法后缀提供了媒体类型结构化语法后缀注册表。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6839.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6839.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. When to Use These Structured Syntax Suffixes . . . . . . . . . 3
3. Initial Structured Syntax Suffix Definitions . . . . . . . . . 4
3.1. The +json Structured Syntax Suffix . . . . . . . . . . . . 4
3.2. The +ber Structured Syntax Suffix . . . . . . . . . . . . 5
3.3. The +der Structured Syntax Suffix . . . . . . . . . . . . 6
3.4. The +fastinfoset Structured Syntax Suffix . . . . . . . . 7
3.5. The +wbxml Structured Syntax Suffix . . . . . . . . . . . 9
3.6. The +zip Structured Syntax Suffix . . . . . . . . . . . . 10
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
4.1. The +xml Structured Syntax Suffix . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Normative References . . . . . . . . . . . . . . . . . . . 13
6.2. Informative References . . . . . . . . . . . . . . . . . . 13
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. When to Use These Structured Syntax Suffixes . . . . . . . . . 3
3. Initial Structured Syntax Suffix Definitions . . . . . . . . . 4
3.1. The +json Structured Syntax Suffix . . . . . . . . . . . . 4
3.2. The +ber Structured Syntax Suffix . . . . . . . . . . . . 5
3.3. The +der Structured Syntax Suffix . . . . . . . . . . . . 6
3.4. The +fastinfoset Structured Syntax Suffix . . . . . . . . 7
3.5. The +wbxml Structured Syntax Suffix . . . . . . . . . . . 9
3.6. The +zip Structured Syntax Suffix . . . . . . . . . . . . 10
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
4.1. The +xml Structured Syntax Suffix . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Normative References . . . . . . . . . . . . . . . . . . . 13
6.2. Informative References . . . . . . . . . . . . . . . . . . 13
[RFC3023] created the +xml suffix convention that can be used when defining names for media types whose representation uses XML underneath. That is, they could have been successfully parsed as if the media type had been application/xml in addition to their being parsed as their media type that is using the +xml suffix. [RFC6838] defines the media type "Structured Syntax Suffix Registry" to be used for such structured syntax suffixes.
[RFC3023]创建了+xml后缀约定，该约定可用于定义表示下面使用xml的媒体类型的名称。也就是说，除了将它们解析为使用+xml后缀的媒体类型外，还可以将它们成功解析为媒体类型application/xml。[RFC6838]定义用于此类结构化语法后缀的媒体类型“结构化语法后缀注册表”。
A variety of structured syntax suffixes have already been used in some media type registrations, in particular "+json", "+der", "+fastinfoset", and "+wbxml". This document defines and registers these structured syntax suffixes in the Structured Syntax Suffix Registry, along with "+ber" and "+zip". In addition, this document updates [RFC3023] to formally register the "+xml" structured syntax suffix according to the procedure defined in [RFC6838].
在一些媒体类型注册中已经使用了各种结构化语法后缀，特别是“+json”、“+der”、“+FastInfo集”和“+wbxml”。本文档在结构化语法后缀注册表中定义并注册这些结构化语法后缀，以及“+ber”和“+zip”。此外，本文档更新了[RFC3023]，以根据[RFC6838]中定义的过程正式注册“+xml”结构化语法后缀。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
Each of the structured syntax suffixes defined in this document is appropriate for use when the media type identifies the semantics of the protocol payload. That is, knowing the semantics of the specific media type provides for more specific processing of the content than that afforded by generic processing of the underlying representation.
本文档中定义的每个结构化语法后缀都适合在媒体类型标识协议有效负载的语义时使用。也就是说，了解特定媒体类型的语义可以提供比底层表示的一般处理更具体的内容处理。
At the same time, using the suffix allows receivers of the media types to do generic processing of the underlying representation in cases where
同时，使用后缀允许媒体类型的接收者在以下情况下对底层表示进行一般处理：
they do not need to perform special handling of the particular semantics of the exact media type, and
它们不需要对确切媒体类型的特定语义执行特殊处理，并且
there is no special knowledge needed by such a generic processor in order to parse that underlying representation other than what would be needed to parse any example of that underlying representation.
除了解析该底层表示的任何示例所需的知识外，这种通用处理器不需要特殊知识来解析该底层表示。
[RFC4627] defines the "application/json" media type. The suffix "+json" MAY be used with any media type whose representation follows that established for "application/json". The media type structured syntax suffix registration form follows. See [RFC6838] for definitions of each of the registration form headings.
[RFC4627]定义“应用程序/json”媒体类型。后缀“+json”可用于任何媒体类型，其表示形式遵循为“应用程序/json”建立的表示形式。下面是媒体类型结构化语法后缀注册表。请参见[RFC6838]了解每个注册表标题的定义。
Name: JavaScript Object Notation (JSON)
名称：JavaScript对象表示法（JSON）
+suffix: +json
+suffix: +json
References: [RFC4627]
参考文献：[RFC4627]
Encoding considerations:
编码注意事项：
Per [RFC4627], JSON is allowed to be represented using UTF-8, UTF-16, or UTF-32. When JSON is written in UTF-8, JSON is 8bit compatible ([RFC2045]). When JSON is written in UTF-16 or UTF-32, JSON is binary ([RFC2045]).
根据[RFC4627]，允许使用UTF-8、UTF-16或UTF-32表示JSON。用UTF-8编写JSON时，JSON是8bit兼容的（[RFC2045]）。当用UTF-16或UTF-32编写JSON时，JSON是二进制的（[RFC2045]）。
Fragment identifier considerations:
片段标识符注意事项：
The syntax and semantics of fragment identifiers specified for +json SHOULD be as specified for "application/json". (At publication of this document, there is no fragment identification syntax defined for "application/json".)
为+json指定的片段标识符的语法和语义应该与为“application/json”指定的相同。（在本文档发布时，没有为“application/json”定义片段标识语法。）
The syntax and semantics for fragment identifiers for a specific "xxx/yyy+json" SHOULD be processed as follows:
特定“xxx/yyy+json”的片段标识符的语法和语义应按如下方式处理：
For cases defined in +json, where the fragment identifier resolves per the +json rules, then process as specified in +json.
对于在+json中定义的情况，片段标识符根据+json规则解析，然后按照+json中的指定进行处理。
For cases defined in +json, where the fragment identifier does not resolve per the +json rules, then process as specified in "xxx/yyy+json".
对于+json中定义的情况，如果片段标识符没有按照+json规则解析，则按照“xxx/yyy+json”中的指定进行处理。
For cases not defined in +json, then process as specified in "xxx/yyy+json".
对于+json中未定义的情况，则按照“xxx/yyy+json”中的规定进行处理。
Interoperability considerations: n/a
互操作性注意事项：不适用
Security considerations: See [RFC4627]
安全注意事项：参见[RFC4627]
Contact: Apps Area Working Group (apps-discuss@ietf.org)
联系人：应用程序区域工作组（Apps）-discuss@ietf.org)
Author/Change controller:
作者/变更控制员：
The Apps Area Working Group. IESG has change control over this registration.
应用程序领域工作组。IESG对此注册具有变更控制权。
The ITU defined the Basic Encoding Rules (BER) transfer syntax in [ITU.X690.2008]. The suffix "+ber" MAY be used with any media type whose representation follows the BER transfer syntax. (The Expert Reviewer for media type structured syntax suffix registrations ought to be aware of the relationship between BER and DER to aid in selecting the proper suffix.) The media type structured syntax suffix registration form for +ber follows:
ITU在[ITU.X690.2008]中定义了基本编码规则（BER）传输语法。后缀“+ber”可用于表示形式遵循ber传输语法的任何媒体类型。（媒体类型结构化语法后缀注册的专家评审员应了解BER和DER之间的关系，以帮助选择适当的后缀。）媒体类型结构化语法后缀注册表格+BER如下：
Name: Basic Encoding Rules (BER) transfer syntax
名称：基本编码规则（BER）传输语法
+suffix: +ber
+suffix: +ber
References: [ITU.X690.2008]
参考文献：[ITU.X690.2008]
Encoding considerations: BER is a binary encoding.
编码注意事项：BER是二进制编码。
Fragment identifier considerations:
片段标识符注意事项：
At publication of this document, there is no fragment identification syntax defined for +ber.
在本文档发布时，没有为+ber定义片段标识语法。
The syntax and semantics for fragment identifiers for a specific "xxx/yyy+ber" SHOULD be processed as follows:
特定“xxx/yyy+ber”的片段标识符的语法和语义应按如下方式处理：
For cases defined in +ber, where the fragment identifier resolves per the +ber rules, then process as specified in +ber.
对于在+ber中定义的情况，其中片段标识符根据+ber规则进行解析，然后按照+ber中的指定进行处理。
For cases defined in +ber, where the fragment identifier does not resolve per the +ber rules, then process as specified in "xxx/yyy+ber".
对于+ber中定义的情况，如果片段标识符没有按照+ber规则解析，则按照“xxx/yyy+ber”中的指定进行处理。
For cases not defined in +ber, then process as specified in "xxx/yyy+ber".
对于+ber中未定义的情况，则按照“xxx/yyy+ber”中的规定进行处理。
Interoperability considerations: n/a
互操作性注意事项：不适用
Security considerations:
安全考虑：
Each individual media type registered with a +ber suffix can have additional security considerations.
使用+ber后缀注册的每种媒体类型都有额外的安全注意事项。
BER has a type-length-value structure, and it is easy to construct malicious content with invalid length fields that can cause buffer overrun conditions.
BER具有类型-长度-值结构，很容易使用无效长度字段构造恶意内容，从而导致缓冲区溢出情况。
BER allows for arbitrary levels of nesting, which may make it possible to construct malicious content that will cause a stack overflow.
BER允许任意级别的嵌套，这可能使构建恶意内容成为可能，从而导致堆栈溢出。
Interpreters of the BER structures should be aware of these issues and should take appropriate measures to guard against buffer overflows and stack overruns in particular and malicious content in general.
BER结构的解释器应了解这些问题，并应采取适当措施防止缓冲区溢出和堆栈溢出，尤其是恶意内容。
Contact: Apps Area Working Group (apps-discuss@ietf.org)
联系人：应用程序区域工作组（Apps）-discuss@ietf.org)
Author/Change controller:
作者/变更控制员：
The Apps Area Working Group. IESG has change control over this registration.
应用程序领域工作组。IESG对此注册具有变更控制权。
The ITU defined the Distinguished Encoding Rules (DER) transfer syntax in [ITU.X690.2008]. The suffix "+der" MAY be used with any media type whose representation follows the DER transfer syntax. (The Expert Reviewer for media type structured syntax suffix registrations ought to be aware of the relationship between BER and DER to aid in selecting the proper suffix.) The media type structured syntax suffix registration form for +der follows:
ITU在[ITU.X690.2008]中定义了可分辨编码规则（DER）传输语法。后缀“+der”可用于表示形式遵循der传输语法的任何媒体类型。（媒体类型结构化语法后缀注册的专家评审员应了解BER和DER之间的关系，以帮助选择适当的后缀。）媒体类型结构化语法后缀注册表格+DER如下：
Name: Distinguished Encoding Rules (DER) transfer syntax
名称：可分辨编码规则（DER）传输语法
+suffix: +der
+suffix: +der
References: [ITU.X690.2008]
参考文献：[ITU.X690.2008]
Encoding considerations: DER is a binary encoding.
编码注意事项：DER是二进制编码。
Fragment identifier considerations:
片段标识符注意事项：
At publication of this document, there is no fragment identification syntax defined for +der.
在本文档发布时，没有为+der定义片段标识语法。
The syntax and semantics for fragment identifiers for a specific "xxx/yyy+der" SHOULD be processed as follows:
特定“xxx/yyy+der”的片段标识符的语法和语义应按如下方式处理：
For cases defined in +der, where the fragment identifier resolves per the +der rules, then process as specified in +der.
对于在+der中定义的情况，其中片段标识符按照+der规则解析，然后按照+der中的指定进行处理。
For cases defined in +der, where the fragment identifier does not resolve per the +der rules, then process as specified in "xxx/yyy+der".
对于在+der中定义的情况，如果片段标识符没有按照+der规则解析，则按照“xxx/yyy+der”中的指定进行处理。
For cases not defined in +der, then process as specified in "xxx/yyy+der".
对于+der中未定义的情况，则按照“xxx/yyy+der”中的规定进行处理。
Interoperability considerations: n/a
互操作性注意事项：不适用
Security considerations:
安全考虑：
Each individual media type registered with a +der suffix can have additional security considerations.
使用+der后缀注册的每种媒体类型都有额外的安全注意事项。
DER has a type-length-value structure, and it is easy to construct malicious content with invalid length fields that can cause buffer overrun conditions.
DER具有类型-长度-值结构，很容易使用无效长度字段构造恶意内容，从而导致缓冲区溢出情况。
DER allows for arbitrary levels of nesting, which may make it possible to construct malicious content that will cause a stack overflow.
DER允许任意级别的嵌套，这可能使构建恶意内容成为可能，从而导致堆栈溢出。
Interpreters of the DER structures should be aware of these issues and should take appropriate measures to guard against buffer overflows and stack overruns in particular and malicious content in general.
DER结构的解释器应了解这些问题，并应采取适当措施防止缓冲区溢出和堆栈溢出，尤其是恶意内容。
Contact: Apps Area Working Group (apps-discuss@ietf.org)
联系人：应用程序区域工作组（Apps）-discuss@ietf.org)
Author/Change controller:
作者/变更控制员：
The Apps Area Working Group. IESG has change control over this registration.
应用程序领域工作组。IESG对此注册具有变更控制权。
The ITU defined the Fast Infoset document format as a binary representation of the XML Information Set in [ITU.X891.2005]. These documents further define the "application/fastinfoset" media type. The suffix "+fastinfoset" MAY be used with any media type whose representation follows that established for "application/ fastinfoset". The media type structured syntax suffix registration form follows:
国际电联在[ITU.X891.2005]中将快速信息集文档格式定义为XML信息集的二进制表示形式。这些文档进一步定义了“应用程序/快速信息集”媒体类型。后缀“+fastinfoset”可用于任何媒体类型，其表示形式遵循为“应用程序/fastinfoset”建立的表示形式。媒体类型结构化语法后缀注册表如下所示：
Name: Fast Infoset document format
名称：Fast信息集文档格式
+suffix: +fastinfoset
+suffix: +fastinfoset
References: [ITU.X891.2005]
参考文献：[ITU.X891.2005]
Encoding considerations:
编码注意事项：
Fast Infoset is a binary encoding. The binary, quoted-printable, and base64 content-transfer-encodings are suitable for use with Fast Infoset.
Fast信息集是一种二进制编码。二进制、带引号的可打印和base64内容传输编码适用于Fast Infoset。
Fragment identifier considerations:
片段标识符注意事项：
The syntax and semantics of fragment identifiers specified for +fastinfoset SHOULD be as specified for "application/fastinfoset". (At publication of this document, there is no fragment identification syntax defined for "application/fastinfoset".)
为+fastinfoset指定的片段标识符的语法和语义应与为“application/fastinfoset”指定的相同。（在本文档发布时，没有为“应用程序/FastInfo集”定义片段标识语法。）
The syntax and semantics for fragment identifiers for a specific "xxx/ yyy+fastinfoset" SHOULD be processed as follows:
特定“xxx/yyy+fastinfoset”的片段标识符的语法和语义应按如下方式处理：
For cases defined in +fastinfoset, where the fragment identifier resolves per the +fastinfoset rules, then process as specified in +fastinfoset.
对于在+fastinfoset中定义的情况，其中片段标识符根据+fastinfoset规则解析，然后按照+fastinfoset中的指定进行处理。
For cases defined in +fastinfoset, where the fragment identifier does not resolve per the +fastinfoset rules, then process as specified in "xxx/yyy+fastinfoset".
对于+fastinfoset中定义的情况，如果片段标识符没有按照+fastinfoset规则解析，则按照“xxx/yyy+fastinfoset”中的规定进行处理。
For cases not defined in +fastinfoset, then process as specified in "xxx/ yyy+fastinfoset".
对于+fastinfoset中未定义的情况，则按照“xxx/yyy+fastinfoset”中的规定进行处理。
Interoperability considerations: n/a
互操作性注意事项：不适用
Security considerations:
安全考虑：
There are no security considerations inherent in Fast Infoset. Each individual media type registered with a +fastinfoset suffix can have additional security considerations.
Fast Infoset没有固有的安全考虑。每个使用+FastInfo后缀注册的媒体类型都可能有额外的安全注意事项。
Contact: Apps Area Working Group (apps-discuss@ietf.org)
联系人：应用程序区域工作组（Apps）-discuss@ietf.org)
Author/Change controller:
作者/变更控制员：
The Apps Area Working Group. IESG has change control over this registration.
应用程序领域工作组。IESG对此注册具有变更控制权。
The Wireless Application Protocol (WAP) Forum has defined the WAP Binary XML (WBXML) document format as a binary representation of XML in [WBXML]. This document further defines the "application/ vnd.wap.wbxml" media type. The suffix "+wbxml" MAY be used with any media type whose representation follows that established for "application/vnd.wap.wbxml". The media type structured syntax suffix registration form follows:
无线应用协议（WAP）论坛将WAP二进制XML（WBXML）文档格式定义为[WBXML]中XML的二进制表示形式。本文档进一步定义了“application/vnd.wap.wbxml”媒体类型。后缀“+wbxml”可用于表示形式遵循为“application/vnd.wap.wbxml”建立的表示形式的任何媒体类型。媒体类型结构化语法后缀注册表如下所示：
Name: WAP Binary XML (WBXML) document format
名称：WAP二进制XML（WBXML）文档格式
+suffix: +wbxml
+suffix: +wbxml
References: [WBXML]
参考文献：[WBXML]
Encoding considerations: WBXML is a binary encoding.
编码注意事项：WBXML是二进制编码。
Fragment identifier considerations:
片段标识符注意事项：
The syntax and semantics of fragment identifiers specified for +wbxml SHOULD be as specified for "application/vnd.wap.wbxml". (At publication of this document, there is no fragment identification syntax defined for "application/vnd.wap.wbxml".)
为+wbxml指定的片段标识符的语法和语义应与为“application/vnd.wap.wbxml”指定的相同。（在本文档发布时，没有为“application/vnd.wap.wbxml”定义片段标识语法。）
The syntax and semantics for fragment identifiers for a specific "xxx/yyy+wbxml" SHOULD be processed as follows:
特定“xxx/yyy+wbxml”的片段标识符的语法和语义应按如下方式处理：
For cases defined in +wbxml, where the fragment identifier resolves per the +wbxml rules, then process as specified in +wbxml.
对于在+wbxml中定义的情况，其中片段标识符根据+wbxml规则进行解析，然后按照+wbxml中的指定进行处理。
For cases defined in +wbxml, where the fragment identifier does not resolve per the +wbxml rules, then process as specified in "xxx/yyy+wbxml".
对于在+wbxml中定义的情况，如果片段标识符没有按照+wbxml规则解析，则按照“xxx/yyy+wbxml”中的指定进行处理。
For cases not defined in +wbxml, then process as specified in "xxx/yyy+wbxml".
对于+wbxml中未定义的情况，则按照“xxx/yyy+wbxml”中的规定进行处理。
Interoperability considerations: n/a
互操作性注意事项：不适用
Security considerations:
安全考虑：
There are no security considerations inherent in WBXML. Each individual media type registered with a +wbxml suffix can have additional security considerations.
WBXML中没有固有的安全注意事项。使用+wbxml后缀注册的每个单独的媒体类型都可能有额外的安全注意事项。
Contact: Apps Area Working Group (apps-discuss@ietf.org)
联系人：应用程序区域工作组（Apps）-discuss@ietf.org)
Author/Change controller:
作者/变更控制员：
The Apps Area Working Group. IESG has change control over this registration.
应用程序领域工作组。IESG对此注册具有变更控制权。
The ZIP format is a public domain, cross-platform, interoperable file storage and transfer format, originally defined by PKWARE, Inc.; it supports compression and encryption and is used as the underlying representation by a variety of file formats. The media type "application/zip" has been registered for such files. The suffix "+zip" MAY be used with any media type whose representation follows that established for "application/zip". The media type structured syntax suffix registration form follows:
ZIP格式是一种公共域、跨平台、可互操作的文件存储和传输格式，最初由PKWARE，Inc.定义。；它支持压缩和加密，并被各种文件格式用作底层表示。已为此类文件注册了媒体类型“application/zip”。后缀“+zip”可用于任何媒体类型，其表示形式遵循为“应用程序/zip”建立的表示形式。媒体类型结构化语法后缀注册表如下所示：
Name: ZIP file storage and transfer format
名称：ZIP文件存储和传输格式
+suffix: +zip
+suffix: +zip
References: [ZIP]
参考文献：[ZIP]
Encoding considerations: ZIP is a binary encoding.
编码注意事项：ZIP是二进制编码。
Fragment identifier considerations:
片段标识符注意事项：
The syntax and semantics of fragment identifiers specified for +zip SHOULD be as specified for "application/zip". (At publication of this document, there is no fragment identification syntax defined for "application/zip".)
为+zip指定的片段标识符的语法和语义应该与为“application/zip”指定的相同。（在本文档发布时，没有为“application/zip”定义片段标识语法。）
The syntax and semantics for fragment identifiers for a specific "xxx/yyy+zip" SHOULD be processed as follows:
特定“xxx/yyy+zip”的片段标识符的语法和语义应按如下方式处理：
For cases defined in +zip, where the fragment identifier resolves per the +zip rules, then process as specified in +zip.
对于在+zip中定义的情况，其中片段标识符按照+zip规则解析，然后按照+zip中的指定进行处理。
For cases defined in +zip, where the fragment identifier does not resolve per the +zip rules, then process as specified in "xxx/yyy+zip".
对于+zip中定义的情况，如果片段标识符没有按照+zip规则解析，则按照“xxx/yyy+zip”中的指定进行处理。
For cases not defined in +zip, then process as specified in "xxx/yyy+zip".
对于+zip中未定义的情况，则按照“xxx/yyy+zip”中的规定进行处理。
Interoperability considerations: n/a
互操作性注意事项：不适用
Security considerations:
安全考虑：
IP files support two forms of encryption: Strong Encryption and AES 128-bit, 192-bit, and 256-bit encryption; see the specification for further details. Each individual media type registered with a +zip suffix can have additional security considerations.
IP文件支持两种加密形式：强加密和AES 128位、192位和256位加密；有关更多详细信息，请参阅规范。使用+zip后缀注册的每种媒体类型都可能有额外的安全注意事项。
Contact: Apps Area Working Group (apps-discuss@ietf.org)
联系人：应用程序区域工作组（Apps）-discuss@ietf.org)
Author/Change controller: The Apps Area Working Group. IESG has change control over this registration.
作者/更改控制器：应用程序区域工作组。IESG对此注册具有变更控制权。
See the media type structured syntax suffix registration forms in Sections 3.1 - 3.6.
请参阅第3.1-3.6节中的媒体类型结构化语法后缀注册表。
The following structured syntax suffix registration for "+xml" shall be used to reflect the information found in [RFC3023], with the addition of fragment identifier considerations. (Note that [RFC3023] is in the process of being updated by [XML-MEDIATYPES].)
以下“+xml”的结构化语法后缀注册应用于反映[RFC3023]中的信息，并添加片段标识符注意事项。（注意，[RFC3023]正在被[XML-MEDIATYPES]更新。）
Name: Extensible Markup Language (XML)
名称：可扩展标记语言（XML）
+suffix: +xml
+suffix: +xml
References: [RFC3023]
参考文献：[RFC3023]
Encoding considerations:
编码注意事项：
Per [RFC3023], XML is allowed to be represented using both 7-bit and 8-bit encodings. When XML is written in UTF-8, XML is 8bit compatible ([RFC2045]). When XML is written in UTF-16 or UTF-32, XML is binary ([RFC2045]).
根据[RFC3023]，允许使用7位和8位编码来表示XML。用UTF-8编写XML时，XML是8位兼容的（[RFC2045]）。当用UTF-16或UTF-32编写XML时，XML是二进制的（[RFC2045]）。
Fragment identifier considerations:
片段标识符注意事项：
The syntax and semantics of fragment identifiers specified for +xml SHOULD be as specified for "application/xml". (At publication of this document, the fragment identification syntax considerations for "application/xml" are defined in [RFC3023], Sections 5 and 7.)
为+xml指定的片段标识符的语法和语义应与为“application/xml”指定的相同。（在本文件发布时，“应用程序/xml”的片段标识语法注意事项在[RFC3023]第5节和第7节中定义。）
The syntax and semantics for fragment identifiers for a specific "xxx/yyy+xml" SHOULD be processed as follows:
特定“xxx/yyy+xml”的片段标识符的语法和语义应按如下方式处理：
For cases defined in +xml, where the fragment identifier resolves per the +xml rules, then process as specified in +xml.
对于在+xml中定义的情况，其中片段标识符根据+xml规则进行解析，然后按照+xml中的指定进行处理。
For cases defined in +xml, where the fragment identifier does not resolve per the +xml rules, then process as specified in "xxx/yyy+xml".
对于在+xml中定义的情况，如果片段标识符没有按照+xml规则解析，则按照“xxx/yyy+xml”中的指定进行处理。
For cases not defined in +xml, then process as specified in "xxx/yyy+xml".
对于+xml中未定义的情况，则按照“xxx/yyy+xml”中的规定进行处理。
Interoperability considerations: See [RFC3023].
互操作性注意事项：请参见[RFC3023]。
Security considerations: See [RFC3023]
安全注意事项：参见[RFC3023]
Contact: Apps Area Working Group (apps-discuss@ietf.org)
联系人：应用程序区域工作组（Apps）-discuss@ietf.org)
Author/Change controller:
作者/变更控制员：
The Apps Area Working Group. IESG has change control over this registration.
应用程序领域工作组。IESG对此注册具有变更控制权。
See the Security Considerations sections found in the media type structured syntax suffix registration forms from Sections 3 and 4.
请参阅第3节和第4节的媒体类型结构化语法后缀注册表中的安全注意事项部分。
When updating a +<suffix> registration, care should be taken to review all previously-registered xxx/yyy+<suffix> media types as to whether they might be affected by the updated +<suffix> registration. Because the generic fragment identifier processing rules take precedence over media-type-specific rules, introducing new or changing existing definitions may break the existing registrations of specific media types, as well as particular implementations of applications that process affected media types. Such changes can introduce interoperability and security issues.
更新+<suffix>注册时，应注意查看所有以前注册的xxx/yyy+<suffix>媒体类型，以确定它们是否会受到更新的+<suffix>注册的影响。由于通用片段标识符处理规则优先于媒体类型特定规则，因此引入新的或更改现有定义可能会破坏特定媒体类型的现有注册，以及处理受影响媒体类型的应用程序的特定实现。这些变化可能会带来互操作性和安全问题。
When updating the fragment identifier processing rules for a specific xxx/yyy+<suffix> media type, care should be taken to review the generic fragment identifier processing rules for the +<suffix> registration and not introduce any conflicts. Because the generic fragment identifier processing rules take precedence over media-type-specific rules, such conflicting processing requirements should be ignored by an implementation, but such conflicts can introduce interoperability and security issues.
更新特定xxx/yyy+<suffix>媒体类型的片段标识符处理规则时，应注意查看+<suffix>注册的通用片段标识符处理规则，不要引入任何冲突。由于通用片段标识符处理规则优先于媒体类型特定的规则，因此实现应忽略此类冲突的处理要求，但此类冲突可能会引入互操作性和安全问题。
Note that [FRAGID-BP] provides additional advice to designers of fragment identifier rules for media type suffixes and specific media types.
请注意，[FRAGID-BP]为媒体类型后缀和特定媒体类型的片段标识符规则的设计者提供了额外的建议。
[RFC4627] Crockford, D., "The application/json Media Type for JavaScript Object Notation (JSON)", RFC 4627, July 2006.
[RFC4627]Crockford，D.，“JavaScript对象表示法（json）的应用程序/json媒体类型”，RFC4627，2006年7月。
[ITU.X690.2008] International Telecommunications Union, "Recommendation ITU-T X.690 | ISO/IEC 8825-1 (2008), ASN.1 encoding rules: Specification of basic encoding Rules (BER), Canonical encoding rules (CER) and Distinguished encoding rules (DER)", ITU-T Recommendation X.690, November 2008.
[ITU.X690.2008]国际电信联盟，“建议ITU-T X.690 | ISO/IEC 8825-1（2008），ASN.1编码规则：基本编码规则规范（BER）、规范编码规则（CER）和区分编码规则（DER）”，ITU-T建议X.690，2008年11月。
[ITU.X891.2005] International Telecommunications Union, "Recommendation ITU-T X.891 | ISO/IEC 24824-1 (2007), Generic applications of ASN.1: Fast infoset", ITU-T Recommendation X.891, May 2005.
[ITU.X891.2005]国际电信联盟，“建议ITU-T X.891 | ISO/IEC 24824-1（2007），ASN.1的一般应用：快速信息集”，ITU-T建议X.891，2005年5月。
[WBXML] Open Mobile Alliance, "Binary XML Content Format Specification", OMA Wireless Access Protocol WAP-192- WBXML-20010725-a, July 2001.
[WBXML]开放移动联盟，“二进制XML内容格式规范”，OMA无线接入协议WAP-192-WBXML-20010725-a，2001年7月。
[ZIP] PKWARE, Inc., "APPNOTE.TXT - .ZIP File Format Specification", PKWARE .ZIP File Format Specification - Version 6.3.2, September 2007.
[ZIP]PKWARE，Inc.，“APPNOTE.TXT-.ZIP文件格式规范”，PKWARE.ZIP文件格式规范-版本6.3.2，2007年9月。
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[RFC2045]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第一部分：Internet邮件正文格式”，RFC 20451996年11月。
[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月。
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.
[RFC3023]Murata，M.，St.Laurent，S.，和D.Kohn，“XML媒体类型”，RFC 3023，2001年1月。
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, January 2013.
[RFC6838]Freed，N.，Klensin，J.和T.Hansen，“媒体类型规范和注册程序”，BCP 13，RFC 6838，2013年1月。
[FRAGID-BP] Tennison, J., "Best Practices for Fragment Identifiers and Media Type Definitions", July 2012, <http://www.w3.org/TR/fragid-best-practices/>.
[FRAGID-BP]Tennison，J.，“片段标识符和媒体类型定义的最佳实践”，2012年7月<http://www.w3.org/TR/fragid-best-practices/>.
[XML-MEDIATYPES] Lilley, C., Makoto, M., Melnikov, A., and H. Thompson, "XML Media Types", Work in Progress, November 2012.
[XML-MEDIATYPES]Lilley，C.，Makoto，M.，Melnikov，A.，和H.Thompson，“XML媒体类型”，正在进行的工作，2012年11月。
Authors' Addresses
作者地址
Tony Hansen AT&T Laboratories 200 Laurel Ave. South Middletown, NJ 07748 USA
美国新泽西州南米德尔顿劳雷尔大道200号托尼·汉森AT&T实验室，邮编：07748
EMail: tony+sss@maillennium.att.com
EMail: tony+sss@maillennium.att.com
Alexey Melnikov Isode Ltd 5 Castle Business Village 36 Station Road Hampton, Middlesex TW12 2BX UK
英国米德尔塞克斯郡汉普顿车站路36号城堡商业村5号Alexey Melnikov Isode有限公司TW12 2BX
EMail: Alexey.Melnikov@isode.com
EMail: Alexey.Melnikov@isode.com