Internet Engineering Task Force (IETF) M. Tuexen
Request for Comments: 6096 Muenster Univ. of Applied Sciences
Updates: 4960 R. Stewart
Category: Standards Track Huawei
ISSN: 2070-1721 January 2011
Internet Engineering Task Force (IETF) M. Tuexen
Request for Comments: 6096 Muenster Univ. of Applied Sciences
Updates: 4960 R. Stewart
Category: Standards Track Huawei
ISSN: 2070-1721 January 2011
Stream Control Transmission Protocol (SCTP) Chunk Flags Registration
流控制传输协议（SCTP）块标志注册
Abstract
摘要
This document defines the procedure for registering chunk flags with the Internet Assigned Numbers Authority (IANA) for the Stream Control Transmission Protocol (SCTP). It updates RFC 4960 and also defines the IANA registry for contents for currently defined chunk types. It does not change SCTP in any other way.
本文档定义了向互联网分配号码管理局（IANA）注册流控制传输协议（SCTP）的区块标志的过程。它更新RFC 4960，并为当前定义的块类型的内容定义IANA注册表。它不会以任何其他方式改变SCTP。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
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). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（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/rfc6096.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6096.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 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. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Updated IETF-Defined Chunk Extension . . . . . . . . . . . 3
3.2. New IETF Chunk Flags Registration . . . . . . . . . . . . . 4
3.3. Initial Registrations . . . . . . . . . . . . . . . . . . . 4
3.3.1. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . 4
3.3.2. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.3. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.4. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.5. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.6. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . 5
3.3.7. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.8. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.9. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . 6
3.3.10. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . 6
3.3.11. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . 6
3.3.12. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . 6
3.3.13. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . 6
3.3.14. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . 6
3.3.15. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . 6
3.3.16. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . 7
3.3.17. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . 7
3.3.18. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . 7
3.3.19. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . 7
3.3.20. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Normative References . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Updated IETF-Defined Chunk Extension . . . . . . . . . . . 3
3.2. New IETF Chunk Flags Registration . . . . . . . . . . . . . 4
3.3. Initial Registrations . . . . . . . . . . . . . . . . . . . 4
3.3.1. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . 4
3.3.2. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.3. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.4. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.5. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.6. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . 5
3.3.7. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . 5
3.3.8. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . 5
3.3.9. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . 6
3.3.10. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . 6
3.3.11. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . 6
3.3.12. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . 6
3.3.13. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . 6
3.3.14. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . 6
3.3.15. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . 6
3.3.16. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . 7
3.3.17. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . 7
3.3.18. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . 7
3.3.19. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . 7
3.3.20. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Normative References . . . . . . . . . . . . . . . . . . . . . 8
[RFC4960], which currently defines the Stream Control Transmission Protocol (SCTP), provides a procedure to define new chunk types. However, several protocol extensions currently being discussed need to define new chunk flags for existing chunks.
[RFC4960]目前定义了流控制传输协议（SCTP），提供了定义新块类型的过程。然而，目前正在讨论的几个协议扩展需要为现有块定义新的块标志。
This document updates RFC 4960 to overcome this limitation. It defines the procedure to register chunk flags and specifies the registry entries for existing chunk types. The protocol is not changed in any other way. Therefore, only Section 14.1 of [RFC4960] is affected.
本文档更新RFC 4960以克服此限制。它定义了注册区块标志的过程，并为现有区块类型指定注册表项。协议没有以任何其他方式更改。因此，只有[RFC4960]的第14.1节受到影响。
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]中所述进行解释。
Section 3.1 provides the updated procedure for SCTP Chunk Type registration; it replaces Section 14.1 of [RFC4960].
第3.1节提供了SCTP区块类型注册的更新程序；它取代了[RFC4960]的第14.1节。
Section 3.2 provides a new procedure for SCTP Chunk Flag registration. A registry entry must be created for each SCTP Chunk Type.
第3.2节提供了SCTP区块标志注册的新程序。必须为每个SCTP区块类型创建注册表项。
Section 3.3 provides the SCTP Chunk Flag registry values for the SCTP Chunk Types specified in [RFC3758], [RFC4820], [RFC4960], [RFC4895], and [RFC5061].
第3.3节提供了[RFC3758]、[RFC4820]、[RFC4960]、[RFC4895]和[RFC5061]中指定的SCTP区块类型的SCTP区块标志注册表值。
The assignment of new chunk type codes is done through an IETF Review action, as defined in [RFC5226]. Documentation of a new chunk MUST contain the following information:
按照[RFC5226]中的定义，通过IETF审查行动完成新区块类型代码的分配。新区块的文档必须包含以下信息：
a) A long and short name for the new chunk type;
a) 新块类型的长名称和短名称；
b) A detailed description of the structure of the chunk, which MUST conform to the basic structure defined in Section 3.2 of [RFC4960];
b) 区块结构的详细说明，必须符合[RFC4960]第3.2节中定义的基本结构；
c) A detailed definition and description of intended use of each field within the chunk, including the chunk flags if any. Defined chunk flags will be used as initial entries in the chunk flags table for the new chunk type;
c) 区块内每个字段预期用途的详细定义和说明，包括区块标志（如果有）。定义的块标志将用作新块类型的块标志表中的初始条目；
d) A detailed procedural description of the use of the new chunk type within the operation of the protocol.
d) 协议操作中使用新块类型的详细过程描述。
The last chunk type (255) is reserved for future extension if necessary.
最后一个块类型（255）保留供将来扩展（如有必要）。
For each new chunk type, IANA creates a registration table for the chunk flags of that type. The procedure for registering particular chunk flags is described in the following Section 3.2.
对于每个新的块类型，IANA都会为该类型的块标志创建一个注册表。以下第3.2节描述了注册特定区块标志的过程。
The assignment of new chunk flags is done through an RFC required action, as defined in [RFC5226]. Documentation of the chunk flags MUST contain the following information:
新区块标志的分配通过[RFC5226]中定义的RFC必需操作完成。区块标志的文档必须包含以下信息：
a) A name for the new chunk flag;
a) 新区块标志的名称；
b) A detailed procedural description of the use of the new chunk flag within the operation of the protocol. It MUST be considered that implementations not supporting the flag will send '0' on transmit and just ignore it on receipt.
b) 协议操作中使用新区块标志的详细过程描述。必须考虑到，不支持该标志的实现将在传输时发送“0”，在接收时忽略它。
IANA selects a chunk flags value. This must be one of 0x01, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within the chunk flag values for the specific chunk type.
IANA选择块标志值。这必须是0x01、0x02、0x04、0x08、0x10、0x20、0x40或0x80中的一个，在特定块类型的块标志值内必须是唯一的。
This section describes the initial values of the chunk flag tables, one table for each chunk. Most tables are currently empty. IANA used these values to create the new registry.
本节介绍区块标志表的初始值，每个区块对应一个表。大多数表当前为空。IANA使用这些值创建新注册表。
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | E bit | [RFC4960] |
| 0x02 | B bit | [RFC4960] |
| 0x04 | U bit | [RFC4960] |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | E bit | [RFC4960] |
| 0x02 | B bit | [RFC4960] |
| 0x04 | U bit | [RFC4960] |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | T bit | [RFC4960] |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | T bit | [RFC4960] |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | T bit | [RFC4960] |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
| 0x01 | T bit | [RFC4960] |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
+------------------+-----------------+-----------+
| Chunk Flag Value | Chunk Flag Name | Reference |
+------------------+-----------------+-----------+
This document does not add any additional security considerations in addition to the ones given in [RFC4960].
除[RFC4960]中给出的安全注意事项外，本文档未添加任何其他安全注意事项。
The authors wish to thank Anna Brunstroem, Gorry Fairhurst, Russ Housley, Suresh Krishnan, and Dan Romascanu for their invaluable comments.
作者希望感谢安娜·布伦斯特伦、戈里·费尔赫斯特、罗斯·霍斯利、苏雷什·克里希南和丹·罗马斯坎努的宝贵评论。
[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月。
[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. Conrad, "Stream Control Transmission Protocol (SCTP) Partial Reliability Extension", RFC 3758, May 2004.
[RFC3758]Stewart，R.，Ramalho，M.，Xie，Q.，Tuexen，M.，和P.Conrad，“流控制传输协议（SCTP）部分可靠性扩展”，RFC 3758，2004年5月。
[RFC4820] Tuexen, M., Stewart, R., and P. Lei, "Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP)", RFC 4820, March 2007.
[RFC4820]Tuexen，M.，Stewart，R.，和P.Lei，“流控制传输协议（SCTP）的填充块和参数”，RFC 4820，2007年3月。
[RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, "Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)", RFC 4895, August 2007.
[RFC4895]Tuexen，M.，Stewart，R.，Lei，P.，和E.Rescorla，“流控制传输协议（SCTP）的认证块”，RFC 48952007年8月。
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC 4960, September 2007.
[RFC4960]Stewart，R.，“流控制传输协议”，RFC 49602007年9月。
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. Kozuka, "Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration", RFC 5061, September 2007.
[RFC5061]Stewart，R.，Xie，Q.，Tuexen，M.，Maruyama，S.，和M.Kozuka，“流控制传输协议（SCTP）动态地址重新配置”，RFC 50612007年9月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
Authors' Addresses
作者地址
Michael Tuexen Muenster University of Applied Sciences Stegerwaldstr. 39 48565 Steinfurt DE
米迦勒TuxEN明斯特应用科学大学StigalddSTR。斯坦福德德39 48565
EMail: tuexen@fh-muenster.de
EMail: tuexen@fh-muenster.de
Randall R. Stewart Huawei Chapin, SC 29036 US
Randall R.Stewart Huawei Chapin，SC 29036美国
EMail: randall@lakerest.net
EMail: randall@lakerest.net