Internet Engineering Task Force (IETF) R. Stewart
Request for Comments: 6525 Adara Networks
Category: Standards Track M. Tuexen
ISSN: 2070-1721 Muenster Univ. of Appl. Sciences
P. Lei
Cisco Systems, Inc.
February 2012
Internet Engineering Task Force (IETF) R. Stewart
Request for Comments: 6525 Adara Networks
Category: Standards Track M. Tuexen
ISSN: 2070-1721 Muenster Univ. of Appl. Sciences
P. Lei
Cisco Systems, Inc.
February 2012
Stream Control Transmission Protocol (SCTP) Stream Reconfiguration
流控制传输协议（SCTP）流重新配置
Abstract
摘要
Many applications that use the Stream Control Transmission Protocol (SCTP) want the ability to "reset" a stream. The intention of resetting a stream is to set the numbering sequence of the stream back to 'zero' with a corresponding notification to the application layer that the reset has been performed. Applications requiring this feature want it so that they can "reuse" streams for different purposes but still utilize the stream sequence number so that the application can track the message flows. Thus, without this feature, a new use of an old stream would result in message numbers greater than expected, unless there is a protocol mechanism to "reset the streams back to zero". This document also includes methods for resetting the transmission sequence numbers, adding additional streams, and resetting all stream sequence numbers.
许多使用流控制传输协议（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/rfc6525.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6525.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 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 .....................................................4
3. New Chunk Type ..................................................4
3.1. RE-CONFIG Chunk ............................................5
4. New Parameter Types .............................................6
4.1. Outgoing SSN Reset Request Parameter .......................7
4.2. Incoming SSN Reset Request Parameter .......................8
4.3. SSN/TSN Reset Request Parameter ............................9
4.4. Re-configuration Response Parameter .......................10
4.5. Add Outgoing Streams Request Parameter ....................12
4.6. Add Incoming Streams Request Parameter ....................13
5. Procedures .....................................................14
5.1. Sender-Side Procedures ....................................14
5.1.1. Sender-Side Procedures for the RE-CONFIG Chunk .....14
5.1.2. Sender-Side Procedures for the Outgoing SSN
Reset Request Parameter ............................15
5.1.3. Sender-Side Procedures for the Incoming SSN
Reset Request Parameter ............................16
5.1.4. Sender-Side Procedures for the SSN/TSN
Reset Request Parameter ............................17
5.1.5. Sender-Side Procedures for the Add Outgoing
Streams Request Parameter ..........................17
5.1.6. Sender-Side Procedures for the Add Incoming
Streams Request Parameter ..........................17
5.1.7. Sender-Side Procedures for the
Re-configuration Response Parameter ................18
1. Introduction ....................................................3
2. Conventions .....................................................4
3. New Chunk Type ..................................................4
3.1. RE-CONFIG Chunk ............................................5
4. New Parameter Types .............................................6
4.1. Outgoing SSN Reset Request Parameter .......................7
4.2. Incoming SSN Reset Request Parameter .......................8
4.3. SSN/TSN Reset Request Parameter ............................9
4.4. Re-configuration Response Parameter .......................10
4.5. Add Outgoing Streams Request Parameter ....................12
4.6. Add Incoming Streams Request Parameter ....................13
5. Procedures .....................................................14
5.1. Sender-Side Procedures ....................................14
5.1.1. Sender-Side Procedures for the RE-CONFIG Chunk .....14
5.1.2. Sender-Side Procedures for the Outgoing SSN
Reset Request Parameter ............................15
5.1.3. Sender-Side Procedures for the Incoming SSN
Reset Request Parameter ............................16
5.1.4. Sender-Side Procedures for the SSN/TSN
Reset Request Parameter ............................17
5.1.5. Sender-Side Procedures for the Add Outgoing
Streams Request Parameter ..........................17
5.1.6. Sender-Side Procedures for the Add Incoming
Streams Request Parameter ..........................17
5.1.7. Sender-Side Procedures for the
Re-configuration Response Parameter ................18
5.2. Receiver-Side Procedures ..................................18
5.2.1. Receiver-Side Procedures for the RE-CONFIG Chunk ...18
5.2.2. Receiver-Side Procedures for the Outgoing
SSN Reset Request Parameter ........................19
5.2.3. Receiver-Side Procedures for the Incoming
SSN Reset Request Parameter ........................20
5.2.4. Receiver-Side Procedures for the SSN/TSN
Reset Request Parameter ............................21
5.2.5. Receiver-Side Procedures for the Add
Outgoing Streams Request Parameter .................21
5.2.6. Receiver-Side Procedures for the Add
Incoming Streams Request Parameter .................22
5.2.7. Receiver-Side Procedures for the
Re-configuration Response Parameter ................22
6. Sockets API Considerations .....................................23
6.1. Events ....................................................23
6.1.1. Stream Reset Event .................................24
6.1.2. Association Reset Event ............................25
6.1.3. Stream Change Event ................................26
6.2. Event Subscription ........................................27
6.3. Socket Options ............................................27
6.3.1. Enable/Disable Stream Reset
(SCTP_ENABLE_STREAM_RESET) .........................28
6.3.2. Reset Incoming and/or Outgoing Streams
(SCTP_RESET_STREAMS) ...............................29
6.3.3. Reset SSN/TSN (SCTP_RESET_ASSOC) ...................29
6.3.4. Add Incoming and/or Outgoing Streams
(SCTP_ADD_STREAMS) .................................30
7. Security Considerations ........................................30
8. IANA Considerations ............................................31
8.1. A New Chunk Type ..........................................31
8.2. Six New Chunk Parameter Types .............................31
9. Acknowledgments ................................................31
10. References ....................................................32
10.1. Normative References .....................................32
10.2. Informative References ...................................32
Appendix A. Examples of the Reconfiguration Procedures ............33
5.2. Receiver-Side Procedures ..................................18
5.2.1. Receiver-Side Procedures for the RE-CONFIG Chunk ...18
5.2.2. Receiver-Side Procedures for the Outgoing
SSN Reset Request Parameter ........................19
5.2.3. Receiver-Side Procedures for the Incoming
SSN Reset Request Parameter ........................20
5.2.4. Receiver-Side Procedures for the SSN/TSN
Reset Request Parameter ............................21
5.2.5. Receiver-Side Procedures for the Add
Outgoing Streams Request Parameter .................21
5.2.6. Receiver-Side Procedures for the Add
Incoming Streams Request Parameter .................22
5.2.7. Receiver-Side Procedures for the
Re-configuration Response Parameter ................22
6. Sockets API Considerations .....................................23
6.1. Events ....................................................23
6.1.1. Stream Reset Event .................................24
6.1.2. Association Reset Event ............................25
6.1.3. Stream Change Event ................................26
6.2. Event Subscription ........................................27
6.3. Socket Options ............................................27
6.3.1. Enable/Disable Stream Reset
(SCTP_ENABLE_STREAM_RESET) .........................28
6.3.2. Reset Incoming and/or Outgoing Streams
(SCTP_RESET_STREAMS) ...............................29
6.3.3. Reset SSN/TSN (SCTP_RESET_ASSOC) ...................29
6.3.4. Add Incoming and/or Outgoing Streams
(SCTP_ADD_STREAMS) .................................30
7. Security Considerations ........................................30
8. IANA Considerations ............................................31
8.1. A New Chunk Type ..........................................31
8.2. Six New Chunk Parameter Types .............................31
9. Acknowledgments ................................................31
10. References ....................................................32
10.1. Normative References .....................................32
10.2. Informative References ...................................32
Appendix A. Examples of the Reconfiguration Procedures ............33
Many applications that use SCTP as defined in [RFC4960] want the ability to "reset" a stream. The intention of resetting a stream is to set the Stream Sequence Numbers (SSNs) of the stream back to 'zero' with a corresponding notification to the application layer that the reset has been performed. Applications requiring this feature want to "reuse" streams for different purposes but still utilize the SSN so that the application can track the message flows. Thus, without this feature, a new use of an old stream would result
许多使用[RFC4960]中定义的SCTP的应用程序都希望能够“重置”流。重置流的目的是将流的流序列号（SSN）设置回“零”，并向应用层发出重置已执行的相应通知。需要此功能的应用程序希望为不同目的“重用”流，但仍然使用SSN，以便应用程序可以跟踪消息流。因此，如果没有此功能，将导致对旧流的新使用
in message numbers greater than expected, unless there is a protocol mechanism to "reset the streams back to zero". This document also includes methods for resetting the Transmission Sequence Numbers (TSNs), adding additional streams, and resetting all SSNs.
除非存在“将流重置为零”的协议机制，否则消息数大于预期值。本文件还包括重置传输序列号（TSN）、添加额外流和重置所有SSN的方法。
The sockets API for SCTP defined in [RFC6458] exposes the sequence numbers used by SCTP for user message transfer. Therefore, resetting them can be used by application writers. Please note that the corresponding sequence number for TCP is not exposed via the sockets API for TCP.
[RFC6458]中定义的SCTP套接字API公开了SCTP用于用户消息传输的序列号。因此，应用程序编写器可以使用重置它们。请注意，TCP的相应序列号不会通过TCP的套接字API公开。
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]中所述进行解释。
This section defines the new chunk type that will be used to reconfigure streams. Table 1 illustrates the new chunk type.
本节定义将用于重新配置流的新块类型。表1说明了新的块类型。
+------------+------------------------------------+
| Chunk Type | Chunk Name |
+------------+------------------------------------+
| 130 | Re-configuration Chunk (RE-CONFIG) |
+------------+------------------------------------+
+------------+------------------------------------+
| Chunk Type | Chunk Name |
+------------+------------------------------------+
| 130 | Re-configuration Chunk (RE-CONFIG) |
+------------+------------------------------------+
Table 1
表1
It should be noted that the format of the RE-CONFIG chunk requires that the receiver ignore the chunk if it is not understood and continue processing all chunks that follow. This is accomplished by the use of the upper bits of the chunk type as described in Section 3.2 of [RFC4960].
需要注意的是，重新配置块的格式要求接收方忽略未理解的块，并继续处理随后的所有块。如[RFC4960]第3.2节所述，这是通过使用块类型的高位来实现的。
All transported integer numbers are in "network byte order", a.k.a. Big Endian.
所有传输的整数都是“网络字节顺序”，即Big-Endian。
This document adds one new chunk type to SCTP. The chunk has the following format:
本文档向SCTP添加了一个新的块类型。区块具有以下格式：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 130 | Chunk Flags | Chunk Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Re-configuration Parameter /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Re-configuration Parameter (optional) /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 130 | Chunk Flags | Chunk Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Re-configuration Parameter /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Re-configuration Parameter (optional) /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Chunk Type: 1 byte (unsigned integer) This field holds the IANA-defined chunk type for the RE-CONFIG chunk. The value of this field is 130.
块类型：1字节（无符号整数）此字段保存重新配置块的IANA定义的块类型。此字段的值为130。
Chunk Flags: 1 byte (unsigned integer) This field is set to 0 by the sender and ignored by the receiver.
区块标志：1字节（无符号整数）此字段由发送方设置为0，接收方忽略。
Chunk Length: 2 bytes (unsigned integer) This field holds the length of the chunk in bytes, including the Chunk Type, Chunk Flags, and Chunk Length.
Chunk Length:2字节（无符号整数）此字段以字节为单位保存块的长度，包括块类型、块标志和块长度。
Re-configuration Parameter This field holds a Re-configuration Request Parameter or a Re-configuration Response Parameter.
重新配置参数此字段包含重新配置请求参数或重新配置响应参数。
Note that each RE-CONFIG chunk holds at least one parameter and at most two parameters. Only the following combinations are allowed:
请注意，每个重新配置块至少包含一个参数，最多包含两个参数。仅允许以下组合：
1. Outgoing SSN Reset Request Parameter.
1. 传出SSN重置请求参数。
2. Incoming SSN Reset Request Parameter.
2. 传入的SSN重置请求参数。
3. Outgoing SSN Reset Request Parameter, Incoming SSN Reset Request Parameter.
3. 传出SSN重置请求参数，传入SSN重置请求参数。
4. SSN/TSN Reset Request Parameter.
4. SSN/TSN重置请求参数。
5. Add Outgoing Streams Request Parameter.
5. 添加传出流请求参数。
6. Add Incoming Streams Request Parameter.
6. 添加传入流请求参数。
7. Add Outgoing Streams Request Parameter, Add Incoming Streams Request Parameter.
7. 添加传出流请求参数，添加传入流请求参数。
8. Re-configuration Response Parameter.
8. 重新配置响应参数。
9. Re-configuration Response Parameter, Outgoing SSN Reset Request Parameter.
9. 重新配置响应参数，传出SSN重置请求参数。
10. Re-configuration Response Parameter, Re-configuration Response Parameter.
10. 重新配置响应参数，重新配置响应参数。
If a sender transmits an unsupported combination, the receiver SHOULD send an ERROR chunk with a Protocol Violation cause, as defined in Section 3.3.10.13 of [RFC4960]).
如[RFC4960]第3.3.10.13节所述，如果发送方发送不受支持的组合，接收方应发送带有协议冲突原因的错误块。
This section defines the new parameter types that will be used in the RE-CONFIG chunk. Table 2 illustrates the new parameter types.
本节定义将在重新配置块中使用的新参数类型。表2说明了新的参数类型。
+----------------+----------------------------------------+
| Parameter Type | Parameter Name |
+----------------+----------------------------------------+
| 13 | Outgoing SSN Reset Request Parameter |
| 14 | Incoming SSN Reset Request Parameter |
| 15 | SSN/TSN Reset Request Parameter |
| 16 | Re-configuration Response Parameter |
| 17 | Add Outgoing Streams Request Parameter |
| 18 | Add Incoming Streams Request Parameter |
+----------------+----------------------------------------+
+----------------+----------------------------------------+
| Parameter Type | Parameter Name |
+----------------+----------------------------------------+
| 13 | Outgoing SSN Reset Request Parameter |
| 14 | Incoming SSN Reset Request Parameter |
| 15 | SSN/TSN Reset Request Parameter |
| 16 | Re-configuration Response Parameter |
| 17 | Add Outgoing Streams Request Parameter |
| 18 | Add Incoming Streams Request Parameter |
+----------------+----------------------------------------+
Table 2
表2
It should be noted that the parameter format requires that the receiver stop processing the parameter and not process any further parameters within the chunk if the parameter type is not recognized. This is accomplished by the use of the upper bits of the parameter type as described in Section 3.2.1 of [RFC4960].
需要注意的是，参数格式要求接收方停止处理参数，如果参数类型无法识别，则不处理区块内的任何其他参数。这通过使用[RFC4960]第3.2.1节所述参数类型的高位来实现。
All transported integer numbers are in "network byte order", a.k.a. Big Endian.
所有传输的整数都是“网络字节顺序”，即Big-Endian。
This parameter is used by the sender to request the reset of some or all outgoing streams.
发送方使用此参数请求重置部分或所有传出流。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 13 | Parameter Length = 16 + 2 * N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Response Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender's Last Assigned TSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number 1 (optional) | Stream Number 2 (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ...... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number N-1 (optional) | Stream Number N (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 13 | Parameter Length = 16 + 2 * N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Response Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender's Last Assigned TSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number 1 (optional) | Stream Number 2 (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ...... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number N-1 (optional) | Stream Number N (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) This field holds the IANA-defined parameter type for the Outgoing SSN Reset Request Parameter. The value of this field is 13.
参数类型：2字节（无符号整数）此字段保存传出SSN重置请求参数的IANA定义的参数类型。此字段的值为13。
Parameter Length: 2 bytes (unsigned integer) This field holds the length in bytes of the parameter; the value MUST be 16 + 2 * N, where N is the number of stream numbers listed.
参数长度：2字节（无符号整数）此字段保存参数的长度（以字节为单位）；该值必须为16+2*N，其中N是列出的流编号数。
Re-configuration Request Sequence Number: 4 bytes (unsigned integer) This field is used to identify the request. It is a monotonically increasing number that is initialized to the same value as the initial TSN. It is increased by 1 whenever sending a new Re-configuration Request Parameter.
重新配置请求序列号：4字节（无符号整数）。此字段用于标识请求。它是一个单调递增的数，初始化为与初始TSN相同的值。每当发送新的重新配置请求参数时，它将增加1。
Re-configuration Response Sequence Number: 4 bytes (unsigned integer) When this Outgoing SSN Reset Request Parameter is sent in response to an Incoming SSN Reset Request Parameter, this parameter is also an implicit response to the incoming request. This field then holds the Re-configuration Request Sequence Number of the incoming request. In other cases, it holds the next expected Re-configuration Request Sequence Number minus 1.
重新配置响应序列号：4字节（无符号整数）当发送此传出SSN重置请求参数以响应传入SSN重置请求参数时，此参数也是对传入请求的隐式响应。然后，此字段保存传入请求的重新配置请求序列号。在其他情况下，它保存下一个预期的重新配置请求序列号减1。
Sender's Last Assigned TSN: 4 bytes (unsigned integer) This value holds the next TSN minus 1 -- in other words, the last TSN that this sender assigned.
发送方最后分配的TSN:4字节（无符号整数）此值保存下一个TSN减去1——换句话说，就是此发送方分配的最后一个TSN。
Stream Number 1..N: 2 bytes (unsigned integer) This optional field, if included, is used to indicate specific streams that are to be reset. If no streams are listed, then all streams are to be reset.
流编号1..N:2字节（无符号整数）此可选字段（如果包括）用于指示要重置的特定流。如果未列出任何流，则应重置所有流。
This parameter can appear in a RE-CONFIG chunk. This parameter MUST NOT appear in any other chunk type.
此参数可以出现在重新配置块中。此参数不得出现在任何其他块类型中。
This parameter is used by the sender to request that the peer reset some or all of its outgoing streams.
发送方使用此参数请求对等方重置其部分或全部传出流。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 14 | Parameter Length = 8 + 2 * N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number 1 (optional) | Stream Number 2 (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ...... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number N-1 (optional) | Stream Number N (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 14 | Parameter Length = 8 + 2 * N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number 1 (optional) | Stream Number 2 (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ...... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number N-1 (optional) | Stream Number N (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) This field holds the IANA-defined parameter type for the Incoming SSN Reset Request Parameter. The value of this field is 14.
参数类型：2字节（无符号整数）此字段保存传入SSN重置请求参数的IANA定义的参数类型。此字段的值为14。
Parameter Length: 2 bytes (unsigned integer) This field holds the length in bytes of the parameter; the value MUST be 8 + 2 * N.
参数长度：2字节（无符号整数）此字段保存参数的长度（以字节为单位）；该值必须为8+2*N。
Re-configuration Request Sequence Number: 4 bytes (unsigned integer) This field is used to identify the request. It is a monotonically increasing number that is initialized to the same value as the initial TSN. It is increased by 1 whenever sending a new Re-configuration Request Parameter.
重新配置请求序列号：4字节（无符号整数）。此字段用于标识请求。它是一个单调递增的数，初始化为与初始TSN相同的值。每当发送新的重新配置请求参数时，它将增加1。
Stream Number 1..N: 2 bytes (unsigned integer) This optional field, if included, is used to indicate specific streams that are to be reset. If no streams are listed, then all streams are to be reset.
流编号1..N:2字节（无符号整数）此可选字段（如果包括）用于指示要重置的特定流。如果未列出任何流，则应重置所有流。
This parameter can appear in a RE-CONFIG chunk. This parameter MUST NOT appear in any other chunk type.
此参数可以出现在重新配置块中。此参数不得出现在任何其他块类型中。
This parameter is used by the sender to request a reset of the TSN and SSN numbering of all incoming and outgoing streams.
发送方使用此参数请求重置所有传入和传出流的TSN和SSN编号。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 15 | Parameter Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 15 | Parameter Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) This field holds the IANA-defined parameter type for the SSN/TSN Reset Request Parameter. The value of this field is 15.
参数类型：2字节（无符号整数）此字段保存IANA为SSN/TSN重置请求参数定义的参数类型。此字段的值为15。
Parameter Length: 2 bytes (unsigned integer) This field holds the length in bytes of the parameter; the value MUST be 8.
参数长度：2字节（无符号整数）此字段保存参数的长度（以字节为单位）；该值必须为8。
Re-configuration Request Sequence Number: 4 bytes (unsigned integer) This field is used to identify the request. It is a monotonically increasing number that is initialized to the same value as the initial TSN. It is increased by 1 whenever sending a new Re-configuration Request Parameter.
重新配置请求序列号：4字节（无符号整数）。此字段用于标识请求。它是一个单调递增的数，初始化为与初始TSN相同的值。每当发送新的重新配置请求参数时，它将增加1。
This parameter can appear in a RE-CONFIG chunk. This parameter MUST NOT appear in any other chunk type.
此参数可以出现在重新配置块中。此参数不得出现在任何其他块类型中。
This parameter is used by the receiver of a Re-configuration Request Parameter to respond to the request.
此参数由重新配置请求参数的接收器用于响应请求。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 16 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Response Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender's Next TSN (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver's Next TSN (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 16 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Response Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender's Next TSN (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver's Next TSN (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) This field holds the IANA-defined parameter type for the Re-configuration Response Parameter. The value of this field is 16.
参数类型：2字节（无符号整数）此字段保存重新配置响应参数的IANA定义的参数类型。此字段的值为16。
Parameter Type Length: 2 bytes (unsigned integer) This field holds the length in bytes of the parameter; the value MUST be 12 if the optional fields are not present and 20 otherwise.
参数类型长度：2字节（无符号整数），该字段保存参数的字节长度；如果可选字段不存在，则该值必须为12，否则为20。
Re-configuration Response Sequence Number: 4 bytes (unsigned integer) This value is copied from the request parameter and is used by the receiver of the Re-configuration Response Parameter to tie the response to the request.
重新配置响应序列号：4字节（无符号整数）此值从请求参数复制，并由重新配置响应参数的接收器用于将响应与请求联系起来。
Result: 4 bytes (unsigned integer) This value describes the result of the processing of the request. It is encoded as indicated in Table 3:
结果：4字节（无符号整数）此值描述请求处理的结果。其编码如表3所示：
+--------+-------------------------------------+
| Result | Description |
+--------+-------------------------------------+
| 0 | Success - Nothing to do |
| 1 | Success - Performed |
| 2 | Denied |
| 3 | Error - Wrong SSN |
| 4 | Error - Request already in progress |
| 5 | Error - Bad Sequence Number |
| 6 | In progress |
+--------+-------------------------------------+
+--------+-------------------------------------+
| Result | Description |
+--------+-------------------------------------+
| 0 | Success - Nothing to do |
| 1 | Success - Performed |
| 2 | Denied |
| 3 | Error - Wrong SSN |
| 4 | Error - Request already in progress |
| 5 | Error - Bad Sequence Number |
| 6 | In progress |
+--------+-------------------------------------+
Table 3
表3
Sender's Next TSN: 4 bytes (unsigned integer) This field holds the TSN that the sender of the response will use to send the next DATA chunk. The field is only applicable in responses to SSN/TSN reset requests.
发送方的下一个TSN:4字节（无符号整数）此字段保存响应发送方将用于发送下一个数据块的TSN。该字段仅适用于对SSN/TSN重置请求的响应。
Receiver's Next TSN: 4 bytes (unsigned integer) This field holds the TSN that the receiver of the response must use to send the next DATA chunk. The field is only applicable in responses to SSN/TSN reset requests.
Receiver's Next TSN:4字节（无符号整数）此字段保存响应接收器发送下一个数据块时必须使用的TSN。该字段仅适用于对SSN/TSN重置请求的响应。
Either both optional fields (Sender's Next TSN and Receiver's Next TSN) MUST be present, or no field.
两个可选字段（发送方的下一个TSN和接收方的下一个TSN）都必须存在，或者没有字段。
This parameter can appear in a RE-CONFIG chunk. This parameter MUST NOT appear in any other chunk type.
此参数可以出现在重新配置块中。此参数不得出现在任何其他块类型中。
This parameter is used by the sender to request that an additional number of outgoing streams (i.e., the receiver's incoming streams) be added to the association.
发送方使用此参数请求将额外数量的传出流（即接收方的传入流）添加到关联中。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 17 | Parameter Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of new streams | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 17 | Parameter Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of new streams | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) This field holds the IANA-defined parameter type for the Add Outgoing Streams Request Parameter. The value of this field is 17.
参数类型：2字节（无符号整数）此字段保存IANA为添加传出流请求参数定义的参数类型。此字段的值为17。
Parameter Length: 2 bytes (unsigned integer) This field holds the length in bytes of the parameter; the value MUST be 12.
参数长度：2字节（无符号整数）此字段保存参数的长度（以字节为单位）；该值必须为12。
Re-configuration Request Sequence Number: 4 bytes (unsigned integer) This field is used to identify the request. It is a monotonically increasing number that is initialized to the same value as the initial TSN. It is increased by 1 whenever sending a new Re-configuration Request Parameter.
重新配置请求序列号：4字节（无符号整数）。此字段用于标识请求。它是一个单调递增的数，初始化为与初始TSN相同的值。每当发送新的重新配置请求参数时，它将增加1。
Number of new streams: 2 bytes (unsigned integer) This value holds the number of additional outgoing streams that the sender requests be added to the association. Streams are added in order and are consecutive; e.g., if an association has 4 outgoing streams (0-3) and a request is made to add 3 streams, then the new streams will be 4, 5, and 6.
新流数：2字节（无符号整数）此值保存发送方请求添加到关联中的其他传出流数。流按顺序添加，并且是连续的；e、 例如，如果一个关联有4个传出流（0-3），并且请求添加3个流，那么新流将是4、5和6。
Reserved: 2 bytes (unsigned integer) This field is reserved. It SHOULD be set to 0 by the sender and ignored by the receiver.
保留：2字节（无符号整数）此字段为保留字段。发送方应将其设置为0，接收方应将其忽略。
This parameter MAY appear in a RE-CONFIG chunk. This parameter MUST NOT appear in any other chunk type.
此参数可能出现在重新配置块中。此参数不得出现在任何其他块类型中。
This parameter is used by the sender to request that the peer add an additional number of outgoing streams (i.e., the sender's incoming streams) to the association.
发送方使用此参数请求对等方向关联中添加额外数量的传出流（即发送方的传入流）。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 18 | Parameter Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of new streams | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 18 | Parameter Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Re-configuration Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of new streams | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) This field holds the IANA-defined parameter type for the Add Incoming Streams Request Parameter. The value of this field is 18.
参数类型：2字节（无符号整数）此字段保存IANA为添加传入流请求参数定义的参数类型。此字段的值为18。
Parameter Length: 2 bytes (unsigned integer) This field holds the length in bytes of the parameter; the value MUST be 12.
参数长度：2字节（无符号整数）此字段保存参数的长度（以字节为单位）；该值必须为12。
Re-configuration Request Sequence Number: 4 bytes (unsigned integer) This field is used to identify the request. It is a monotonically increasing number that is initialized to the same value as the initial TSN. It is increased by 1 whenever sending a new Re-configuration Request Parameter.
重新配置请求序列号：4字节（无符号整数）。此字段用于标识请求。它是一个单调递增的数，初始化为与初始TSN相同的值。每当发送新的重新配置请求参数时，它将增加1。
Number of new streams: 2 bytes (unsigned integer) This value holds the number of additional incoming streams that the sender requests be added to the association. Streams are added in order and are consecutive; e.g., if an association has 4 outgoing streams (0-3) and a request is made to add 3 streams, then the new streams will be 4, 5, and 6.
新流数：2字节（无符号整数）此值保存发送方请求添加到关联中的其他传入流数。流按顺序添加，并且是连续的；e、 例如，如果一个关联有4个传出流（0-3），并且请求添加3个流，那么新流将是4、5和6。
Reserved: 2 bytes (unsigned integer) This field is reserved. It SHOULD be set to 0 by the sender and ignored by the receiver.
保留：2字节（无符号整数）此字段为保留字段。发送方应将其设置为0，接收方应将其忽略。
This parameter MAY appear in a RE-CONFIG chunk. This parameter MUST NOT appear in any other chunk type.
此参数可能出现在重新配置块中。此参数不得出现在任何其他块类型中。
This section defines the procedures used by both the sender and receiver of a RE-CONFIG chunk. Various examples of re-configuration scenarios are given in Appendix A.
本节定义重新配置块的发送方和接收方使用的过程。附录A中给出了各种重新配置场景的示例。
One important thing to remember about SCTP streams is that they are uni-directional and there is no correspondence between outgoing and incoming streams. The procedures outlined in this section are designed so that the incoming side will always reset its SSN first (before the outgoing side), which means the re-configuration request must always originate from the outgoing side. These two issues have important ramifications upon how an SCTP endpoint might request that its incoming streams be reset. In effect, it must ask the peer to start an outgoing reset procedure and once that request is acknowledged let the peer actually control the reset operation.
关于SCTP流，需要记住的一件重要事情是，它们是单向的，传出流和传入流之间没有对应关系。本节中概述的程序旨在确保输入端始终首先重置其SSN（在输出端之前），这意味着重新配置请求必须始终源自输出端。这两个问题对SCTP端点如何请求重置其传入流具有重要影响。实际上，它必须要求对等方启动一个传出重置过程，一旦该请求得到确认，让对等方实际控制重置操作。
This section describes the procedures related to the sending of RE-CONFIG chunks. A RE-CONFIG chunk is composed of one or two Type-Length-Value (TLV) parameters.
本节描述与发送重新配置块相关的过程。重新配置块由一个或两个类型长度值（TLV）参数组成。
The SCTP protocol extension described in this document uses the Supported Extensions Parameter defined in [RFC5061] for negotiating the support.
本文档中描述的SCTP协议扩展使用[RFC5061]中定义的Supported Extensions参数协商支持。
An SCTP endpoint supporting this extension MUST include the chunk type of the RE-CONFIG chunk in the Supported Extensions Parameter in either the INIT or INIT-ACK. Before sending a RE-CONFIG chunk, the sender MUST ensure that the peer advertised support for the re-configuration extension. If the chunk type of the RE-CONFIG chunk does not appear in the supported extension's list of chunks, then the sender MUST NOT send any re-configuration request to the peer, and any request by the application for such service SHOULD be responded to with an appropriate error indicating that the peer SCTP stack does not support the re-configuration extension.
支持此扩展的SCTP端点必须在INIT或INIT-ACK中的Supported Extensions参数中包含重新配置块的块类型。在发送重新配置块之前，发送方必须确保对等方已公布对重新配置扩展的支持。如果重新配置区块的区块类型未出现在受支持扩展的区块列表中，则发送方不得向对等方发送任何重新配置请求，并且应用程序对此类服务的任何请求都应响应一个适当的错误，表明对等SCTP堆栈不支持重新配置扩展。
At any given time, there MUST NOT be more than one request in flight. So, if the Re-configuration Timer is running and the RE-CONFIG chunk contains at least one request parameter, the chunk MUST be buffered.
在任何给定时间，飞行中的请求不得超过一个。因此，如果重新配置计时器正在运行，并且重新配置区块至少包含一个请求参数，则必须对区块进行缓冲。
After packaging the RE-CONFIG chunk and sending it to the peer, the sender MUST start the Re-configuration Timer if the RE-CONFIG chunk contains at least one request parameter. If it contains no request parameters, the Re-configuration Timer MUST NOT be started. This
打包重新配置区块并将其发送给对等方后，如果重新配置区块至少包含一个请求参数，则发送方必须启动重新配置计时器。如果不包含请求参数，则不得启动重新配置计时器。这
timer MUST use the same value as SCTP's data transmission timer (i.e., the retransmission timeout (RTO) timer) and MUST use exponential backoff, doubling the value at every expiration. If the timer expires, besides doubling the value, the sender MUST retransmit the RE-CONFIG chunk, increment the appropriate error counts (for both the association and the destination), and perform threshold management, possibly destroying the association if SCTP retransmission thresholds are exceeded.
计时器必须使用与SCTP的数据传输计时器（即，重传超时（RTO）计时器）相同的值，并且必须使用指数退避，在每次过期时将该值加倍。如果计时器过期，除了加倍值外，发送方还必须重新传输重新配置块，增加适当的错误计数（对于关联和目标），并执行阈值管理，如果超过SCTP重新传输阈值，可能会破坏关联。
5.1.2. Sender-Side Procedures for the Outgoing SSN Reset Request Parameter
5.1.2. 传出SSN重置请求参数的发送方程序
When an SCTP sender wants to reset the SSNs of some or all outgoing streams, it can send an Outgoing SSN Reset Request Parameter, provided that the Re-configuration Timer is not running. The following steps must be followed:
当SCTP发送方希望重置部分或所有传出流的SSN时，只要重新配置计时器未运行，它可以发送传出SSN重置请求参数。必须遵循以下步骤：
A1: The sender MUST stop assigning new SSNs to new user data provided by the upper layer for the affected streams and queue it. This is because it is not known whether the receiver of the request will accept or deny it; moreover, a lost request might cause an out-of-sequence error in a stream that the receiver is not yet prepared to handle.
A1：发送方必须停止将新SSN分配给上层为受影响流提供的新用户数据，并将其排队。这是因为不知道请求的接收者是否会接受或拒绝请求；此外，丢失的请求可能会在接收方尚未准备好处理的流中导致顺序错误。
A2: The sender MUST assign the next re-configuration request sequence number and MUST put it into the Re-configuration Request Sequence Number field of the Outgoing SSN Reset Request Parameter. The next re-configuration request sequence number MUST then be incremented by 1.
A2：发送方必须分配下一个重新配置请求序列号，并且必须将其放入传出SSN重置请求参数的重新配置请求序列号字段中。然后，下一个重新配置请求序列号必须增加1。
A3: The Sender's Last Assigned TSN MUST be set to the next TSN the sender assigns minus 1.
A3：发送方最后分配的TSN必须设置为发送方分配的下一个TSN减去1。
A4: If this Outgoing SSN Reset Request Parameter is sent in response to an Incoming SSN Reset Request Parameter, the stream numbers MUST be copied from the Incoming SSN Reset Request Parameter to the Outgoing SSN Reset Request Parameter. The Re-configuration Response Sequence Number of the Outgoing SSN Reset Request Parameter MUST be the Re-configuration Request Sequence Number of the Incoming SSN Reset Request Parameter. If this Outgoing SSN Reset Request Parameter is sent at the request of the upper layer and the sender requests that all outgoing streams be reset, stream numbers SHOULD NOT be put into the Outgoing SSN Reset Request Parameter. If the sender requests that only some outgoing streams be reset, these stream numbers MUST be placed in the Outgoing SSN Reset Request Parameter. The Re-configuration Response Sequence Number is the next expected Re-configuration Request Sequence Number of the peer minus 1.
A4：如果发送此传出SSN重置请求参数以响应传入SSN重置请求参数，则必须将流号从传入SSN重置请求参数复制到传出SSN重置请求参数。传出SSN重置请求参数的重新配置响应序列号必须是传入SSN重置请求参数的重新配置请求序列号。如果在上层请求时发送此传出SSN重置请求参数，并且发送方请求重置所有传出流，则流号不应放入传出SSN重置请求参数中。如果发送方请求仅重置一些传出流，则必须将这些流编号放入传出SSN重置请求参数中。重新配置响应序列号是对等方的下一个预期重新配置请求序列号减去1。
A5: The Outgoing SSN Reset Request Parameter MUST be put into a RE-CONFIG Chunk. The Outgoing SSN Reset Request Parameter MAY be put together with either an Incoming SSN Reset Request Parameter or a Re-configuration Response Parameter, but not with both. It MUST NOT be put together with any other parameter, as described in Section 3.1.
A5：传出的SSN重置请求参数必须放入重新配置块中。传出SSN重置请求参数可以与传入SSN重置请求参数或重新配置响应参数放在一起，但不能同时与两者放在一起。如第3.1节所述，不得将其与任何其他参数放在一起。
A6: The RE-CONFIG chunk MUST be sent following the rules given in Section 5.1.1.
A6：必须按照第5.1.1节中给出的规则发送重新配置块。
5.1.3. Sender-Side Procedures for the Incoming SSN Reset Request Parameter
5.1.3. 传入SSN重置请求参数的发送方程序
When an SCTP sender wants to reset the SSNs of some or all incoming streams, it can send an Incoming SSN Reset Request Parameter, provided that the Re-configuration Timer is not running. The following steps must be followed:
当SCTP发送方希望重置部分或所有传入流的SSN时，只要重新配置计时器未运行，它可以发送传入SSN重置请求参数。必须遵循以下步骤：
B1: The sender MUST assign the next re-configuration request sequence number and MUST put it into the Re-configuration Request Sequence Number field of the Incoming SSN Reset Request Parameter. After assigning it, the next re-configuration request sequence number MUST be incremented by 1.
B1：发送方必须分配下一个重新配置请求序列号，并且必须将其放入传入SSN重置请求参数的重新配置请求序列号字段中。分配后，下一个重新配置请求序列号必须增加1。
B2: If the sender wants all incoming streams to be reset, stream numbers SHOULD NOT be put into the Incoming SSN Reset Request Parameter. If the sender wants only some incoming streams to be reset, these stream numbers MUST be filled in the Incoming SSN Reset Request Parameter.
B2：如果发送方希望重置所有传入流，则不应将流编号放入传入SSN重置请求参数中。如果发送方只希望重置一些传入流，则必须在传入SSN重置请求参数中填写这些流编号。
B3: The Incoming SSN Reset Request Parameter MUST be put into a RE-CONFIG Chunk. It MAY be put together with an Outgoing SSN Reset Request Parameter but MUST NOT be put together with any other parameter.
B3：传入的SSN重置请求参数必须放入重新配置块中。它可以与传出的SSN重置请求参数放在一起，但不能与任何其他参数放在一起。
B4: The RE-CONFIG chunk MUST be sent following the rules given in Section 5.1.1.
B4：必须按照第5.1.1节中给出的规则发送重新配置块。
When sending an Incoming SSN Reset Request, there is a potential that the peer has just reset or is in the process of resetting the same streams via an Outgoing SSN Reset Request. This collision scenario is discussed in Section 5.2.3.
发送传入SSN重置请求时，可能是对等方刚刚重置或正在通过传出SSN重置请求重置相同的流。第5.2.3节讨论了这种碰撞情况。
When an SCTP sender wants to reset the SSNs and TSNs, it can send an SSN/TSN Reset Request Parameter, provided that the Re-configuration Timer is not running. The following steps must be followed:
当SCTP发送方希望重置SSN和TSN时，只要重新配置计时器未运行，它可以发送SSN/TSN重置请求参数。必须遵循以下步骤：
C1: The sender MUST assign the next re-configuration request sequence number and put it into the Re-configuration Request Sequence Number field of the SSN/TSN Reset Request Parameter. After assigning it, the next re-configuration request sequence number MUST be incremented by 1.
C1：发送方必须分配下一个重新配置请求序列号，并将其放入SSN/TSN重置请求参数的重新配置请求序列号字段中。分配后，下一个重新配置请求序列号必须增加1。
C2: The sender has either no outstanding TSNs or considers all outstanding TSNs abandoned. The sender MUST queue any user data, suspending any new transmissions and TSN assignment until the reset procedure is finished by the peer either acknowledging or denying the request.
C2：发送方没有未完成的TSN或认为所有未完成的TSN都已放弃。发送方必须对任何用户数据排队，暂停任何新传输和TSN分配，直到对等方完成重置过程，确认或拒绝请求。
C3: The SSN/TSN Reset Request Parameter MUST be put into a RE-CONFIG chunk. There MUST NOT be any other parameter in this chunk.
C3:必须将SSN/TSN重置请求参数放入重新配置块中。此块中不能有任何其他参数。
C4: The RE-CONFIG chunk MUST be sent following the rules given in Section 5.1.1.
C4：必须按照第5.1.1节中给出的规则发送重新配置块。
Only one SSN/TSN Reset Request SHOULD be sent within 30 seconds, which is considered a maximum segment lifetime (the IP MSL).
在30秒内只应发送一个SSN/TSN重置请求，这被视为最大段生存期（IP MSL）。
5.1.5. Sender-Side Procedures for the Add Outgoing Streams Request Parameter
5.1.5. 添加传出流请求参数的发送方端过程
When an SCTP sender wants to increase the number of outbound streams to which it is able to send, it may add an Add Outgoing Streams Request Parameter to the RE-CONFIG chunk. Upon sending the request, the sender MUST await a positive acknowledgment (Success) before using any additional stream added by this request. Note that new streams are added adjacent to the previous streams with no gaps. This means that if a request is made to add 2 streams to an association that already has 5 (0-4), then the new streams, upon successful completion, are streams 5 and 6. A new stream MUST use SSN 0 for its first ordered message.
当SCTP发送方希望增加其能够发送到的出站流的数量时，它可以向RE-CONFIG区块中添加add OUTPING streams Request参数。发送请求时，发送方必须等待肯定确认（成功），然后才能使用此请求添加的任何附加流。请注意，新的流是在前一个流附近添加的，没有间隙。这意味着，如果请求向已经有5（0-4）个流的关联添加2个流，那么成功完成后的新流是流5和6。新流的第一条有序消息必须使用SSN 0。
5.1.6. Sender-Side Procedures for the Add Incoming Streams Request Parameter
5.1.6. 添加传入流请求参数的发送方端过程
When an SCTP sender wants to increase the number of inbound streams to which the peer is able to send, it may add an Add Incoming Streams Request Parameter to the RE-CONFIG chunk. Note that new streams are added adjacent to the previous streams with no gaps. This means that
当SCTP发送方希望增加对等方能够发送到的入站流的数量时，它可以向重新配置块添加addincomingstreams请求参数。请注意，新的流是在前一个流附近添加的，没有间隙。这意味着
if a request is made to add 2 streams to an association that already has 5 (0-4), then the new streams, upon successful completion, are streams 5 and 6. A new stream MUST use SSN 0 for its first ordered message.
如果请求向已经有5（0-4）个流的关联添加2个流，则成功完成后的新流是流5和6。新流的第一条有序消息必须使用SSN 0。
5.1.7. Sender-Side Procedures for the Re-configuration Response Parameter
5.1.7. 重新配置响应参数的发送方程序
When an implementation receives a reset request parameter, it must respond with a Re-configuration Response Parameter in the following manner:
当实现接收到重置请求参数时，它必须以以下方式使用重新配置响应参数进行响应：
D1: The Re-configuration Request Sequence number of the incoming request MUST be copied to the Re-configuration Response Sequence Number field of the Re-configuration Response Parameter.
D1：传入请求的重新配置请求序列号必须复制到重新配置响应参数的重新配置响应序列号字段。
D2: The result of the processing of the incoming request according to Table 3 MUST be placed in the Result field of the Re-configuration Response Parameter.
D2：根据表3处理传入请求的结果必须放在重新配置响应参数的结果字段中。
D3: If the incoming request is an SSN/TSN reset request, the Sender's Next TSN field MUST be filled with the next TSN the sender of this Re-configuration Response Parameter will assign. For other requests, the Sender's Next TSN field, which is optional, MUST NOT be used.
D3：如果传入请求是SSN/TSN重置请求，则发送方的下一个TSN字段必须填入此重新配置响应参数的发送方将分配的下一个TSN。对于其他请求，不能使用发件人的下一个TSN字段（可选）。
D4: If the incoming request is an SSN/TSN reset request, the Receiver's Next TSN field MUST be filled with a TSN such that the sender of the Re-configuration Response Parameter can be sure it can discard received DATA chunks with smaller TSNs. The value SHOULD be the smallest TSN not acknowledged by the receiver of the request plus 2^31. For other requests, the Receiver's Next TSN field, which is optional, MUST NOT be used.
D4：如果传入请求是SSN/TSN重置请求，则接收器的下一个TSN字段必须填充TSN，以便重新配置响应参数的发送方可以确保它可以丢弃具有较小TSN的接收数据块。该值应为请求接收方未确认的最小TSN加上2^31。对于其他请求，不得使用接收方的下一个TSN字段（可选）。
Upon reception of a RE-CONFIG chunk, each parameter within it SHOULD be processed. If multiple parameters have to be returned, they MUST be put into one RE_CONFIG chunk. If the received RE-CONFIG chunk contains at least one request parameter, a selective acknowledgment (SACK) chunk SHOULD be sent back and MAY be bundled with the RE-CONFIG chunk. If the received RE-CONFIG chunk contains at least one request and based on the analysis of the Re-configuration Request Sequence Numbers this is the last received RE-CONFIG chunk (i.e., a retransmission), the same RE-CONFIG chunk MUST to be sent back in response, as it was earlier.
接收到重新配置块后，应处理其中的每个参数。如果必须返回多个参数，则必须将它们放入一个RE_CONFIG块中。如果收到的重新配置区块至少包含一个请求参数，则应发回选择性确认（SACK）区块，并可与重新配置区块捆绑。如果接收到的重新配置块包含至少一个请求，并且根据对重新配置请求序列号的分析，这是最后一次接收到的重新配置块（即，重新传输），则必须将相同的重新配置块发送回以响应，一如前所述。
The decision to deny a re-configuration request is an administrative decision and may be user configurable even after the association has formed. If for whatever reason the endpoint does not wish to process a received request parameter, it MUST send a corresponding response parameter as described in Section 5.1.7, with an appropriate Result field.
拒绝重新配置请求的决定是一项管理决定，即使在关联已经形成之后，也可以由用户配置。如果出于任何原因，端点不希望处理接收到的请求参数，则必须发送第5.1.7节所述的相应响应参数，并带有适当的结果字段。
Implementation Note: It is recommended that a SACK be bundled with any re-configuration response so that any retransmission processing that needs to occur can be expedited. A SACK chunk is not required for this feature to work, but it will in effect help minimize the delay in completing a re-configuration operation in the face of any data loss.
实施说明：建议将SACK与任何重新配置响应捆绑在一起，以便加快需要进行的任何重传处理。SACK块不是此功能工作所必需的，但它实际上将有助于在面临任何数据丢失时最大限度地减少完成重新配置操作的延迟。
5.2.2. Receiver-Side Procedures for the Outgoing SSN Reset Request Parameter
5.2.2. 传出SSN重置请求参数的接收器端程序
In the case that the endpoint is willing to perform a stream reset, the following steps must be followed:
如果端点愿意执行流重置，则必须遵循以下步骤：
E1: If the Re-configuration Timer is running for the Re-configuration Request Sequence Number indicated in the Re-configuration Response Sequence Number field, the Re-configuration Request Sequence Number MUST be marked as acknowledged. If all Re-configuration Request Sequence Numbers for which the Re-configuration Timer is running are acknowledged, the Re-configuration Timer MUST be stopped.
E1：如果重新配置计时器针对重新配置响应序列号字段中指示的重新配置请求序列号运行，则必须将重新配置请求序列号标记为已确认。如果确认运行重新配置计时器的所有重新配置请求序列号，则必须停止重新配置计时器。
E2: If the Sender's Last Assigned TSN is greater than the cumulative acknowledgment point, then the endpoint MUST enter "deferred reset processing". In this mode, any data arriving with a TSN larger than the Sender's Last Assigned TSN for the affected stream(s) MUST be queued locally and held until the cumulative acknowledgment point reaches the Sender's Last Assigned TSN. When the cumulative acknowledgment point reaches the last assigned TSN, then proceed to the next step. If the endpoint enters "deferred reset processing", it MUST put a Re-configuration Response Parameter into a RE-CONFIG chunk indicating "In progress" and MUST send the RE-CONFIG chunk.
E2：如果发送方最后分配的TSN大于累计确认点，则端点必须输入“延迟重置处理”。在此模式下，任何到达的TSN大于发送方上次为受影响流分配的TSN的数据必须在本地排队并保留，直到累积确认点到达发送方上次分配的TSN。当累积确认点到达最后分配的TSN时，继续下一步。如果端点进入“延迟重置处理”，它必须将重新配置响应参数放入指示“正在进行”的重新配置块中，并且必须发送重新配置块。
E3: If no stream numbers are listed in the parameter, then all incoming streams MUST be reset to 0 as the next expected SSN. If specific stream numbers are listed, then only these specific streams MUST be reset to 0, and all other non-listed SSNs remain unchanged.
E3：如果参数中未列出流编号，则所有传入流必须重置为0，作为下一个预期SSN。如果列出了特定流编号，则只有这些特定流必须重置为0，并且所有其他未列出的SSN保持不变。
E4: Any queued TSNs (queued at step E2) MUST now be released and processed normally.
E4：现在必须释放并正常处理任何排队的TSN（在步骤E2排队）。
E5: A Re-configuration Response Parameter MUST be put into a RE-CONFIG chunk indicating successful processing.
E5:必须将重新配置响应参数放入重新配置块中，以指示处理成功。
E6: The RE-CONFIG chunk MUST be sent after the incoming RE-CONFIG chunk is processed completely.
E6：重新配置区块必须在传入的重新配置区块被完全处理后发送。
5.2.3. Receiver-Side Procedures for the Incoming SSN Reset Request Parameter
5.2.3. 传入SSN重置请求参数的接收器端程序
In the case that the endpoint is willing to perform a stream reset, the following steps must be followed:
如果端点愿意执行流重置，则必须遵循以下步骤：
F1: An Outgoing SSN Reset Request Parameter MUST be put into a RE-CONFIG chunk according to Section 5.1.2.
F1：必须根据第5.1.2节将传出SSN重置请求参数放入重新配置块中。
F2: The RE-CONFIG chunk MUST be sent after the incoming RE-CONFIG chunk is processed completely.
F2：重新配置区块必须在传入的重新配置区块完全处理后发送。
When a peer endpoint requests an Incoming SSN Reset Request, it is possible that the local endpoint has just sent an Outgoing SSN Reset Request on the same association and has not yet received a response. In such a case, the local endpoint MUST do the following:
当对等端点请求传入的SSN重置请求时，本地端点可能刚刚在同一关联上发送了传出的SSN重置请求，并且尚未收到响应。在这种情况下，本地端点必须执行以下操作：
o If the Outgoing SSN Reset Request Parameter that was just sent completely overlaps the received Incoming SSN Reset Request Parameter, respond to the peer with an acknowledgment indicating that there was "Nothing to do".
o 如果刚刚发送的传出SSN重置请求参数与接收到的传入SSN重置请求参数完全重叠，则向对等方发出确认，表明“无事可做”。
o Otherwise, process the Incoming SSN Reset Request Parameter normally, responding to the peer with an acknowledgment. Note that this case includes the situation where some of the streams requested overlap with the Outgoing SSN Reset Request that was just sent. Even in such a situation, the Incoming SSN Reset MUST be processed normally, even though this means that (if the endpoint elects to do the stream reset) streams that are already at SSN 0 will be reset a subsequent time.
o 否则，正常处理传入的SSN重置请求参数，以确认的方式响应对等方。注意，这种情况包括一些请求的流与刚刚发送的传出SSN重置请求重叠的情况。即使在这种情况下，也必须正常处理传入的SSN重置，即使这意味着（如果端点选择执行流重置）已经在SSN 0的流将在随后的时间重置。
It is also possible that the Incoming request will arrive after the Outgoing SSN Reset Request just completed. In such a case, all of the streams being requested will be already set to 0. If so, the local endpoint SHOULD send back a Re-configuration Response with the success code "Nothing to do".
也有可能传入请求将在传出SSN重置请求刚刚完成后到达。在这种情况下，所有被请求的流都将被设置为0。如果是这样，本地端点应该发回一个重新配置响应，成功代码为“Nothing to do”。
Note that in either race condition, the local endpoint could optionally also perform the reset. This would result in streams that are already at sequence 0 being reset again to 0, which would cause no harm to the application but will add an extra message to the network.
请注意，在任一竞争条件下，本地端点也可以选择性地执行重置。这将导致已经处于序列0的流再次被重置为0，这不会对应用程序造成损害，但会向网络添加额外的消息。
In the case that the endpoint is willing to perform an SSN/TSN reset, the following steps must be followed:
如果端点愿意执行SSN/TSN重置，则必须遵循以下步骤：
G1: Compute an appropriate value for the Receiver's Next TSN -- the TSN that the peer should use to send the next DATA chunk. The value SHOULD be the smallest TSN not acknowledged by the receiver of the request plus 2^31.
G1：为接收方的下一个TSN计算一个适当的值——对等方应使用该TSN发送下一个数据块。该值应为请求接收方未确认的最小TSN加上2^31。
G2: Compute an appropriate value for the local endpoint's next TSN, i.e., the next TSN assigned by the receiver of the SSN/TSN reset chunk. The value SHOULD be the highest TSN sent by the receiver of the request plus 1.
G2：为本地端点的下一个TSN计算适当的值，即SSN/TSN重置块的接收器分配的下一个TSN。该值应为请求接收方发送的最高TSN加1。
G3: The same processing as though a SACK chunk with no gap report and a cumulative TSN ACK of the Sender's Next TSN minus 1 were received MUST be performed.
G3：必须执行相同的处理，就像接收到没有间隙报告的SACK块和发送方下一个TSN减去1的累积TSN ACK一样。
G4: The same processing as though a FWD-TSN chunk (as defined in [RFC3758]) with all streams affected and a new cumulative TSN ACK of the Receiver's Next TSN minus 1 were received MUST be performed.
G4：必须执行与所有流受影响的FWD-TSN块（如[RFC3758]中所定义）以及接收器下一个TSN减去1的新累积TSN ACK相同的处理。
G5: The next expected and outgoing SSNs MUST be reset to 0 for all incoming and outgoing streams.
G5：对于所有传入和传出流，下一个预期和传出SSN必须重置为0。
G6: A Re-configuration Response Parameter MUST be put into a RE-CONFIG chunk indicating successful processing.
G6:必须将重新配置响应参数放入表示成功处理的重新配置块中。
G7: The RE-CONFIG chunk MUST be sent after the incoming RE-CONFIG chunk is processed completely.
G7:重新配置区块必须在传入的重新配置区块被完全处理之后发送。
5.2.5. Receiver-Side Procedures for the Add Outgoing Streams Request Parameter
5.2.5. 添加传出流请求参数的接收器端过程
When an SCTP endpoint receives a re-configuration request adding additional streams, it MUST send a response parameter either acknowledging or denying the request. If the response is successful, the receiver MUST add the requested number of inbound streams to the association, initializing the next expected SSN to 0. The SCTP endpoint SHOULD deny the request if the number of streams exceeds a limit that should be configurable by the application.
当SCTP端点接收到添加额外流的重新配置请求时，它必须发送一个响应参数来确认或拒绝该请求。如果响应成功，接收方必须将请求的入站流数量添加到关联中，将下一个预期SSN初始化为0。如果流的数量超过应用程序应配置的限制，则SCTP端点应拒绝该请求。
5.2.6. Receiver-Side Procedures for the Add Incoming Streams Request Parameter
5.2.6. 添加传入流请求参数的接收器端过程
When an SCTP endpoint receives a re-configuration request adding additional incoming streams, it MUST either send a response parameter denying the request or send a corresponding Add Outgoing Streams Request Parameter, following the rules given in Section 5.1.5. The SCTP endpoint SHOULD deny the request if the number of streams exceeds a limit that should be configurable by the application.
当SCTP端点接收到添加额外传入流的重新配置请求时，它必须按照第5.1.5节中给出的规则发送拒绝请求的响应参数或发送相应的添加传出流请求参数。如果流的数量超过应用程序应配置的限制，则SCTP端点应拒绝该请求。
5.2.7. Receiver-Side Procedures for the Re-configuration Response Parameter
5.2.7. 重新配置响应参数的接收器端程序
On receipt of a Re-configuration Response Parameter, the following must be performed:
收到重新配置响应参数后，必须执行以下操作：
H1: If the Re-configuration Timer is running for the Re-configuration Request Sequence Number indicated in the Re-configuration Response Sequence Number field, the Re-configuration Request Sequence Number MUST be marked as acknowledged. If all Re-configuration Request Sequence Numbers for which the Re-configuration Timer is running are acknowledged, the Re-configuration Timer MUST be stopped. If the timer was not running for the Re-configuration Request Sequence Number, the processing of the Re-configuration Response Parameter is complete.
H1：如果重新配置计时器针对重新配置响应序列号字段中指示的重新配置请求序列号运行，则必须将重新配置请求序列号标记为已确认。如果确认运行重新配置计时器的所有重新配置请求序列号，则必须停止重新配置计时器。如果重新配置请求序列号的计时器未运行，则重新配置响应参数的处理完成。
H2: If the Result field indicates "In progress", the timer for the Re-configuration Request Sequence Number is started again. If the timer runs out, the RE-CONFIG chunk MUST be retransmitted but the corresponding error counters MUST NOT be incremented.
H2：如果结果字段指示“正在进行”，则重新配置请求序列号的计时器将再次启动。如果计时器用完，则必须重新传输重新配置块，但不得增加相应的错误计数器。
H3: If the Result field does not indicate successful processing, the processing of this response is complete.
H3：如果结果字段未指示处理成功，则此响应的处理完成。
H4: If the request was an Outgoing SSN Reset Request, the affected streams MUST now be reset and all queued data should now be processed. The assigning of SSNs is allowed again.
H4：如果请求是传出的SSN重置请求，则现在必须重置受影响的流，并处理所有排队的数据。再次允许分配SSN。
H5: If the request was an SSN/TSN Reset Request, new data MUST be sent from the Receiver's Next TSN, beginning with SSN 0 for all outgoing streams. All incoming streams MUST be reset to 0 as the next expected SSN. The peer will send DATA chunks starting with the Sender's Next TSN.
H5：如果请求是SSN/TSN重置请求，则必须从接收器的下一个TSN发送新数据，从所有传出流的SSN 0开始。所有传入流必须重置为0，作为下一个预期SSN。对等方将从发送方的下一个TSN开始发送数据块。
H6: If the request was to add outgoing streams, the endpoint MUST add the additional streams to the association. Note that an implementation may allocate the memory at the time of the request, but it MUST NOT use the streams until the peer has responded with a positive acknowledgment.
H6：如果请求是添加传出流，则端点必须将附加流添加到关联中。请注意，实现可以在请求时分配内存，但在对等方以肯定确认响应之前，它不得使用流。
This section describes how the sockets API defined in [RFC6458] needs to be extended to make the features of SCTP re-configuration available to the application.
本节描述了需要如何扩展[RFC6458]中定义的套接字API，以使应用程序能够使用SCTP重新配置的功能。
Please note that this section is informational only.
请注意，本节仅供参考。
When the SCTP_ASSOC_CHANGE notification is delivered and both peers support the extension described in this document, SCTP_ASSOC_SUPPORTS_RE_CONFIG should be listed in the sac_info field.
当SCTP_ASSOC_变更通知发出且两个对等方都支持本文档中描述的扩展时，SCTP_ASSOC_SUPPORTS_RE_CONFIG应列在sac_info字段中。
The union sctp_notification {} is extended to contain three new fields: sn_strreset_event, sn_assocreset_event, and sn_strchange_event:
联合sctp_通知{}扩展为包含三个新字段：sn_strreset_事件、sn_assocreset_事件和sn_strchange_事件：
union sctp_notification {
struct sctp_tlv {
uint16_t sn_type; /* Notification type. */
uint16_t sn_flags;
uint32_t sn_length;
} sn_header;
...
struct sctp_stream_reset_event sn_strreset_event;
struct sctp_assoc_reset_event sn_assocreset_event;
struct sctp_stream_change_event sn_strchange_event;
...
}
union sctp_notification {
struct sctp_tlv {
uint16_t sn_type; /* Notification type. */
uint16_t sn_flags;
uint32_t sn_length;
} sn_header;
...
struct sctp_stream_reset_event sn_strreset_event;
struct sctp_assoc_reset_event sn_assocreset_event;
struct sctp_stream_change_event sn_strchange_event;
...
}
The corresponding sn_type values are given in Table 4.
表4给出了相应的sn_类型值。
+--------------------------+----------------------------------------+
| sn_type | valid field in union sctp_notification |
+--------------------------+----------------------------------------+
| SCTP_STREAM_RESET_EVENT | sn_strreset_event |
| SCTP_ASSOC_RESET_EVENT | sn_assocreset_event |
| SCTP_STREAM_CHANGE_EVENT | sn_strchange_event |
+--------------------------+----------------------------------------+
+--------------------------+----------------------------------------+
| sn_type | valid field in union sctp_notification |
+--------------------------+----------------------------------------+
| SCTP_STREAM_RESET_EVENT | sn_strreset_event |
| SCTP_ASSOC_RESET_EVENT | sn_assocreset_event |
| SCTP_STREAM_CHANGE_EVENT | sn_strchange_event |
+--------------------------+----------------------------------------+
Table 4
表4
These events are delivered when an incoming request was processed successfully or the processing of an outgoing request has been finished.
当传入请求成功处理或传出请求的处理完成时，将传递这些事件。
The event delivered has the following structure:
交付的事件具有以下结构：
struct sctp_stream_reset_event {
uint16_t strreset_type;
uint16_t strreset_flags;
uint32_t strreset_length;
sctp_assoc_t strreset_assoc_id;
uint16_t strreset_stream_list[];
};
struct sctp_stream_reset_event {
uint16_t strreset_type;
uint16_t strreset_flags;
uint32_t strreset_length;
sctp_assoc_t strreset_assoc_id;
uint16_t strreset_stream_list[];
};
strreset_type: This field should be SCTP_STREAM_RESET_EVENT.
strreset\u类型：此字段应为SCTP\u流\u重置\u事件。
strreset_flags: This field is formed from the bitwise OR of one or more of the following currently defined flags:
strreset_标志：此字段由以下一个或多个当前定义的标志的按位或组成：
SCTP_STREAM_RESET_INCOMING_SSN: The stream identifiers given in strreset_stream_list[] refer to incoming streams of the endpoint.
SCTP_STREAM_RESET_INCOMING_SSN：strreset_STREAM_list[]中给出的流标识符表示端点的传入流。
SCTP_STREAM_RESET_OUTGOING_SSN: The stream identifiers given in strreset_stream_list[] refer to outgoing streams of the endpoint.
SCTP_STREAM_RESET_OUTGOING_SSN：strreset_STREAM_list[]中给出的流标识符表示端点的传出流。
SCTP_STREAM_RESET_DENIED: The corresponding request was denied by the peer.
SCTP_STREAM_RESET_DENIED：对等方拒绝了相应的请求。
SCTP_STREAM_RESET_FAILED: The corresponding request failed.
SCTP_流_重置_失败：相应的请求失败。
At least one of SCTP_STREAM_RESET_INCOMING_SSN and SCTP_STREAM_RESET_OUTGOING_SSN is set. SCTP_STREAM_RESET_DENIED and SCTP_STREAM_RESET_FAILED are mutually exclusive. If the request was successful, none of these are set.
设置了SCTP\ U流\重置\传入\ SSN和SCTP\ U流\重置\传出\ SSN中的至少一个。SCTP_流_重置_拒绝和SCTP_流_重置_失败是互斥的。如果请求成功，则不会设置任何设置。
strreset_length: This field is the total length in bytes of the delivered event, including the header.
strreset_length：此字段是已传递事件（包括标头）的总长度（以字节为单位）。
strreset_assoc_id: This association id field holds the identifier for the association. All notifications for a given association have the same association identifier. For one-to-one style sockets, this field is ignored.
strreset_assoc_id：此关联id字段包含关联的标识符。给定关联的所有通知都具有相同的关联标识符。对于一对一样式的套接字，将忽略此字段。
strreset_stream_list: This is the list of stream identifiers to which this event refers. An empty list identifies all streams as being reset. Depending on strreset_flags, the identifiers refer to incoming or outgoing streams, or both.
strreset_stream_list：这是此事件引用的流标识符列表。空列表将所有流标识为正在重置。根据strreset_标志，标识符指的是传入或传出流，或两者。
The event delivered has the following structure:
交付的事件具有以下结构：
struct sctp_assoc_reset_event {
uint16_t assocreset_type;
uint16_t assocreset_flags;
uint32_t assocreset_length;
sctp_assoc_t assocreset_assoc_id;
uint32_t assocreset_local_tsn;
uint32_t assocreset_remote_tsn;
};
struct sctp_assoc_reset_event {
uint16_t assocreset_type;
uint16_t assocreset_flags;
uint32_t assocreset_length;
sctp_assoc_t assocreset_assoc_id;
uint32_t assocreset_local_tsn;
uint32_t assocreset_remote_tsn;
};
assocreset_type: This field should be SCTP_ASSOC_RESET_EVENT.
assocreset\u类型：此字段应为SCTP\u ASSOC\u RESET\u事件。
assocreset_flags: This field is formed from the bitwise OR of one or more of the following currently defined flags:
assocreset_标志：此字段由以下一个或多个当前定义的标志的按位OR组成：
SCTP_ASSOC_RESET_DENIED: The corresponding outgoing request was denied by the peer.
SCTP_ASSOC_RESET_DENIED：对等方拒绝了相应的传出请求。
SCTP_ASSOC_RESET_FAILED: The corresponding outgoing request failed.
SCTP_ASSOC_RESET_失败：相应的传出请求失败。
SCTP_ASSOC_RESET_DENIED and SCTP_ASSOC_RESET_FAILED are mutually exclusive. If the request was successful, none of these are set.
SCTP\U ASSOC\U RESET\U DENITED和SCTP\U ASSOC\U RESET\U FAILED是互斥的。如果请求成功，则不会设置任何设置。
assocreset_length: This field is the total length in bytes of the delivered event, including the header.
assocreset_length：此字段是已传递事件（包括标头）的总长度（以字节为单位）。
assocreset_assoc_id: This association id field holds the identifier for the association. All notifications for a given association have the same association identifier. For one-to-one style sockets, this field is ignored.
assocreset\u assoc\u id：此关联id字段包含关联的标识符。给定关联的所有通知都具有相同的关联标识符。对于一对一样式的套接字，将忽略此字段。
assocreset_local_tsn: This field is the next TSN used by the endpoint.
assocreset_local_tsn：此字段是端点使用的下一个tsn。
assocreset_remote_tsn: This field is the next TSN used by the peer.
assocreset_remote_tsn：此字段是对等方使用的下一个tsn。
The event delivered has the following structure:
交付的事件具有以下结构：
struct sctp_stream_change_event {
uint16_t strchange_type;
uint16_t strchange_flags;
uint32_t strchange_length;
sctp_assoc_t strchange_assoc_id;
uint16_t strchange_instrms;
uint16_t strchange_outstrms;
};
struct sctp_stream_change_event {
uint16_t strchange_type;
uint16_t strchange_flags;
uint32_t strchange_length;
sctp_assoc_t strchange_assoc_id;
uint16_t strchange_instrms;
uint16_t strchange_outstrms;
};
strchange_type: This field should be SCTP_STREAM_CHANGE_EVENT.
strchange\U类型：此字段应为SCTP\U STREAM\U CHANGE\U事件。
strchange_flags: This field is formed from the bitwise OR of one or more of the following currently defined flags:
strchange_标志：此字段由以下一个或多个当前定义的标志的按位OR组成：
SCTP_STREAM_CHANGE_DENIED: The corresponding request was denied by the peer.
SCTP_流_更改_被拒绝：对等方拒绝了相应的请求。
SCTP_STREAM_CHANGE_FAILED: The corresponding request failed.
SCTP_流_更改_失败：相应的请求失败。
SCTP_STREAM_CHANGE_DENIED and SCTP_STREAM_CHANGE_FAILED are mutually exclusive. If the request was successful, none of these are set.
SCTP_流_更改_拒绝和SCTP_流_更改_失败是互斥的。如果请求成功，则不会设置任何设置。
strchange_length: This field is the total length in bytes of the delivered event, including the header.
strchange_length：此字段是已传递事件（包括标头）的总长度（以字节为单位）。
strchange_assoc_id: This association id field holds the identifier for the association. All notifications for a given association have the same association identifier. For one-to-one style sockets, this field is ignored.
strchange\u assoc\u id：此关联id字段包含关联的标识符。给定关联的所有通知都具有相同的关联标识符。对于一对一样式的套接字，将忽略此字段。
strchange_instrms: The number of streams that the peer is allowed to use outbound.
strchange_instrms：允许对等方使用出站的流数。
strchange_outstrms: The number of streams that the endpoint is allowed to use outbound.
strchange_outstrms：允许端点使用出站的流数。
Subscribing to events as described in [RFC6458] uses a setsockopt() call with the SCTP_EVENT socket option. This option takes the following structure, which specifies the association, the event type (using the same value found in the event type field), and an on/off boolean.
订阅[RFC6458]中所述的事件时，使用带有SCTP_事件套接字选项的setsockopt（）调用。此选项采用以下结构，指定关联、事件类型（使用在“事件类型”字段中找到的相同值）和开/关布尔值。
struct sctp_event {
sctp_assoc_t se_assoc_id;
uint16_t se_type;
uint8_t se_on;
};
struct sctp_event {
sctp_assoc_t se_assoc_id;
uint16_t se_type;
uint8_t se_on;
};
The user fills in the se_type field with the same value found in the strreset_type field, i.e., SCTP_STREAM_RESET_EVENT. The user will also fill in the se_assoc_id field with either the association to set this event on (this field is ignored for one-to-one style sockets) or one of the reserved constant values defined in [RFC6458]. Finally, the se_on field is set with a 1 to enable the event or a 0 to disable the event.
用户使用strreset_type字段中相同的值填写se_type字段，即SCTP_STREAM_RESET_事件。用户还将在se_assoc_id字段中填写要设置此事件的关联（对于一对一样式套接字，此字段被忽略）或[RFC6458]中定义的一个保留常量值。最后，se_on字段设置为1以启用事件，或设置为0以禁用事件。
Table 5 describes the new socket options that make the re-configuration features accessible to the user. They all use IPPROTO_SCTP as their level.
表5描述了使用户可以访问重新配置功能的新套接字选项。他们都使用IPPROTO_SCTP作为他们的级别。
If a call to setsockopt() is used to issue a re-configuration request while the Re-configuration timer is running, setsockopt() will return -1, and error is set to EALREADY.
如果在重新配置计时器运行时使用对setsockopt（）的调用发出重新配置请求，则setsockopt（）将返回-1，错误设置为EALREADY。
+--------------------------+---------------------------+-----+-----+
| option name | data type | get | set |
+--------------------------+---------------------------+-----+-----+
| SCTP_ENABLE_STREAM_RESET | struct sctp_assoc_value | X | X |
| SCTP_RESET_STREAMS | struct sctp_reset_streams | | X |
| SCTP_RESET_ASSOC | sctp_assoc_t | | X |
| SCTP_ADD_STREAMS | struct sctp_add_streams | | X |
+--------------------------+---------------------------+-----+-----+
+--------------------------+---------------------------+-----+-----+
| option name | data type | get | set |
+--------------------------+---------------------------+-----+-----+
| SCTP_ENABLE_STREAM_RESET | struct sctp_assoc_value | X | X |
| SCTP_RESET_STREAMS | struct sctp_reset_streams | | X |
| SCTP_RESET_ASSOC | sctp_assoc_t | | X |
| SCTP_ADD_STREAMS | struct sctp_add_streams | | X |
+--------------------------+---------------------------+-----+-----+
Table 5
表5
This option allows a user to control whether the SCTP implementation processes or denies incoming requests in STREAM_RESET chunks.
此选项允许用户控制SCTP实现是处理还是拒绝STREAM_RESET区块中的传入请求。
The default is to deny all incoming requests.
默认设置是拒绝所有传入请求。
To set or get this option, the user fills in the following structure:
要设置或获取此选项，用户需要填写以下结构：
struct sctp_assoc_value {
sctp_assoc_t assoc_id;
uint32_t assoc_value;
};
struct sctp_assoc_value {
sctp_assoc_t assoc_id;
uint32_t assoc_value;
};
assoc_id: This parameter is ignored for one-to-one style sockets. For one-to-many style sockets, this parameter indicates which association the user is performing an action upon.
assoc_id：对于一对一样式的套接字，此参数被忽略。对于一对多样式套接字，此参数指示用户对哪个关联执行操作。
assoc_value: This field is formed from the bitwise OR of one or more of the following currently defined flags:
assoc_值：此字段由以下一个或多个当前定义的标志的按位或组成：
SCTP_ENABLE_RESET_STREAM_REQ: Process received Incoming/Outgoing SSN Reset Requests if this flag is set; deny them if not.
SCTP_ENABLE_RESET_STREAM_REQ：如果设置了此标志，则处理接收到的传入/传出SSN重置请求；如果没有，就拒绝。
SCTP_ENABLE_RESET_ASSOC_REQ: Process received SSN/TSN Reset Requests if this flag is set; deny them if not.
SCTP_ENABLE_RESET_ASSOC_REQ：如果设置了此标志，则处理收到的SSN/TSN重置请求；如果没有，就拒绝。
SCTP_ENABLE_CHANGE_ASSOC_REQ: Process received Add Outgoing Streams Requests if this flag is set; deny them if not.
SCTP_ENABLE_CHANGE_ASSOC_REQ：如果设置了此标志，则处理接收的添加传出流请求；如果没有，就拒绝。
The default value is !(SCTP_ENABLE_RESET_STREAM_REQ| SCTP_ENABLE_RESET_ASSOC_REQ|SCTP_ENABLE_CHANGE_ASSOC_REQ).
默认值为！（SCTP_启用_重置_流_请求| SCTP_启用_重置_关联_请求| SCTP_启用_变更_关联_请求）。
Please note that using the option does not have any impact on subscribing to any related events.
请注意，使用该选项不会对订阅任何相关事件产生任何影响。
This option allows the user to request the reset of incoming and/or outgoing streams.
此选项允许用户请求重置传入和/或传出流。
To set or get this option, the user fills in the following structure:
要设置或获取此选项，用户需要填写以下结构：
struct sctp_reset_streams {
sctp_assoc_t srs_assoc_id;
uint16_t srs_flags;
uint16_t srs_number_streams;
uint16_t srs_stream_list[];
};
struct sctp_reset_streams {
sctp_assoc_t srs_assoc_id;
uint16_t srs_flags;
uint16_t srs_number_streams;
uint16_t srs_stream_list[];
};
srs_assoc_id: This parameter is ignored for one-to-one style sockets. For one-to-many style sockets, this parameter indicates which association the user is performing an action upon.
srs_assoc_id：对于一对一样式的套接字，忽略此参数。对于一对多样式套接字，此参数指示用户对哪个关联执行操作。
srs_flags: This parameter describes which class of streams is reset. It is formed from the bitwise OR of one or more of the following currently defined flags:
srs_标志：此参数描述重置哪类流。它由以下一个或多个当前定义的标志的按位或组成：
* SCTP_STREAM_RESET_INCOMING
* SCTP_流_重置_传入
* SCTP_STREAM_RESET_OUTGOING
* SCTP_流_重置_传出
srs_number_streams: This parameter is the number of elements in the srs_stream_list. If it is zero, the operation is performed on all streams.
srs_number_streams：此参数是srs_stream_列表中的元素数。如果为零，则对所有流执行该操作。
srs_stream_list: This parameter contains a list of stream identifiers the operation is performed upon. It contains srs_number_streams elements. If it is empty, the operation is performed on all streams. Depending on srs_flags, the identifiers refer to incoming or outgoing streams, or both.
srs_stream_list：此参数包含执行操作的流标识符列表。它包含srs\u number\u streams元素。如果为空，则对所有流执行该操作。根据srs_标志，标识符指的是传入流或传出流，或两者。
This option allows a user to request the reset of the SSN/TSN.
此选项允许用户请求重置SSN/TSN。
To set this option, the user provides an option_value of type sctp_assoc_t.
要设置此选项，用户提供类型为sctp\U assoc\U t的选项值。
On one-to-one style sockets, the option_value is ignored. For one-to-many style sockets, the option_value is the association identifier of the association the action is to be performed upon.
在一对一样式的套接字上，选项_值将被忽略。对于一对多样式套接字，选项_值是要对其执行操作的关联的关联标识符。
This option allows a user to request the addition of a number of incoming and/or outgoing streams.
此选项允许用户请求添加大量传入和/或传出流。
To set this option, the user fills in the following structure:
要设置此选项，用户需要填写以下结构：
struct sctp_add_streams {
sctp_assoc_t sas_assoc_id;
uint16_t sas_instrms;
uint16_t sas_outstrms;
};
struct sctp_add_streams {
sctp_assoc_t sas_assoc_id;
uint16_t sas_instrms;
uint16_t sas_outstrms;
};
sas_assoc_id: This parameter is ignored for one-to-one style sockets. For one-to-many style sockets, this parameter indicates which association the user is performing an action upon.
sas_assoc_id：对于一对一样式的套接字，此参数被忽略。对于一对多样式套接字，此参数指示用户对哪个关联执行操作。
sas_instrms: This parameter is the number of incoming streams to add.
sas_instrms：此参数是要添加的传入流的数量。
sas_outstrms: This parameter is the number of outgoing streams to add.
sas_outsrms：此参数是要添加的传出流的数量。
An endpoint can limit the number of incoming and outgoing streams by using the sinit_max_instreams field in the struct sctp_initmsg{} when issuing an SCTP_INIT socket option, as defined in [RFC6458]. An incoming request asking for more streams than allowed will be denied.
端点可以在发出sctp_INIT socket选项时使用struct sctp_initmsg{}中的sinit_max_instream字段来限制传入和传出流的数量，如[RFC6458]中所定义。请求超过允许范围的流的传入请求将被拒绝。
The SCTP sockets API as described in [RFC6458] exposes the sequence numbers of received DATA chunks to the application. An application might expect them to be monotonically increasing. When using the re-configuration extension, this might no longer be true. Therefore, the applications must enable this extension explicitly before it is used. In addition, applications must subscribe explicitly to notifications related to the re-configuration extension before receiving them.
[RFC6458]中所述的SCTP套接字API向应用程序公开所接收数据块的序列号。应用程序可能期望它们是单调递增的。使用重新配置扩展时，这可能不再正确。因此，应用程序必须在使用此扩展之前显式启用它。此外，应用程序必须在接收与重新配置扩展相关的通知之前明确订阅这些通知。
SCTP associations are protected against blind attackers by using verification tags. This is still valid when using the re-configuration extension. Therefore, this extension does not add any additional security risk to SCTP in relation to blind attackers.
SCTP关联通过使用验证标记来防止盲攻击者的攻击。这在使用重新配置扩展时仍然有效。因此，此扩展不会给SCTP增加任何与盲攻击者相关的额外安全风险。
When both the SSN and TSN are reset, the maximum segment lifetime is used to avoid TSN wrap-around.
当SSN和TSN都重置时，使用最大段生存期来避免TSN环绕。
This document (RFC 6525) is the reference for all registrations described in this section. The changes are described below.
本文件（RFC 6525）是本节所述所有注册的参考文件。下文介绍了这些变化。
A chunk type has been assigned by IANA. The values given in Table 1 have been used. IANA has assigned this value from the pool of chunks with the upper two bits set to '10'.
IANA已分配块类型。已使用表1中给出的值。IANA已从块池中分配此值，上面两位设置为“10”。
This has added a line in the "Chunk Types" registry for SCTP:
这在SCTP的“块类型”注册表中添加了一行：
Chunk Types
块类型
ID Value Chunk Type Reference
----- ---------- ---------
130 Re-configuration Chunk (RE-CONFIG) [RFC6525]
ID Value Chunk Type Reference
----- ---------- ---------
130 Re-configuration Chunk (RE-CONFIG) [RFC6525]
The registration table as defined in [RFC6096] for the chunk flags of this chunk type is empty.
[RFC6096]中为此块类型的块标志定义的注册表为空。
Six chunk parameter types have been assigned by IANA. It the values given in Table 2 have been used. IANA has assigned these values from the pool of parameters with the upper two bits set to '00'.
IANA分配了六种区块参数类型。如果使用了表2中给出的值。IANA已从参数池中分配了这些值，其上两位设置为“00”。
Six additional lines in the "Chunk Parameter Types" registry for SCTP have been added:
SCTP的“区块参数类型”注册表中增加了六行：
Chunk Parameter Types
块参数类型
ID Value Chunk Parameter Type Reference
-------- ------------------------------------------------ ---------
13 Outgoing SSN Reset Request Parameter [RFC6525]
14 Incoming SSN Reset Request Parameter [RFC6525]
15 SSN/TSN Reset Request Parameter [RFC6525]
16 Re-configuration Response Parameter [RFC6525]
17 Add Outgoing Streams Request Parameter [RFC6525]
18 Add Incoming Streams Request Parameter [RFC6525]
ID Value Chunk Parameter Type Reference
-------- ------------------------------------------------ ---------
13 Outgoing SSN Reset Request Parameter [RFC6525]
14 Incoming SSN Reset Request Parameter [RFC6525]
15 SSN/TSN Reset Request Parameter [RFC6525]
16 Re-configuration Response Parameter [RFC6525]
17 Add Outgoing Streams Request Parameter [RFC6525]
18 Add Incoming Streams Request Parameter [RFC6525]
The authors wish to thank Paul Aitken, Gorry Fairhurst, Tom Petch, Kacheong Poon, Irene Ruengeler, Robin Seggelmann, Gavin Shearer, and Vlad Yasevich 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月。
[RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", RFC 4960, September 2007.
[RFC4960]Stewart，R.，Ed.“流控制传输协议”，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月。
[RFC6096] Tuexen, M. and R. Stewart, "Stream Control Transmission Protocol (SCTP) Chunk Flags Registration", RFC 6096, January 2011.
[RFC6096]Tuexen，M.和R.Stewart，“流控制传输协议（SCTP）块标志注册”，RFC 60962011年1月。
[RFC6458] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V. Yasevich, "Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)", RFC 6458, December 2011.
[RFC6458]Stewart，R.，Tuexen，M.，Poon，K.，Lei，P.，和V.Yasevich，“流控制传输协议（SCTP）的套接字API扩展”，RFC 6458，2011年12月。
Please note that this appendix is informational only.
请注意，本附录仅供参考。
The following message flows between Endpoints E-A and E-Z illustrate the described procedures. The time progresses in downward direction.
以下端点E-A和E-Z之间的消息流说明了所描述的过程。时间是向下的。
The following example illustrates E-A resetting streams 1 and 2 for just its outgoing streams.
以下示例说明了E-A仅为其传出流重置流1和2。
E-A E-Z
----------[RE-CONFIG(OUT-REQ:X/1,2)]---------->
<-------------[RE-CONFIG(RESP:X)]--------------
E-A E-Z
----------[RE-CONFIG(OUT-REQ:X/1,2)]---------->
<-------------[RE-CONFIG(RESP:X)]--------------
The following example illustrates E-A resetting streams 1 and 2 for just its incoming streams.
以下示例说明E-A仅为其传入流重置流1和2。
E-A E-Z
-----------[RE-CONFIG(IN-REQ:X/1,2)]---------->
<--------[RE-CONFIG(OUT-REQ:Y,X/1,2)]----------
-------------[RE-CONFIG(RESP:Y)]-------------->
E-A E-Z
-----------[RE-CONFIG(IN-REQ:X/1,2)]---------->
<--------[RE-CONFIG(OUT-REQ:Y,X/1,2)]----------
-------------[RE-CONFIG(RESP:Y)]-------------->
The following example illustrates E-A resetting all streams in both directions.
以下示例说明E-A在两个方向重置所有流。
E-A E-Z
-----[RE-CONFIG(OUT-REQ:X,Y-1|IN-REQ:X+1)]---->
<------[RE-CONFIG(RESP:X|OUT-REQ:Y,X+1)]-------
-------------[RE-CONFIG(RESP:Y)]-------------->
E-A E-Z
-----[RE-CONFIG(OUT-REQ:X,Y-1|IN-REQ:X+1)]---->
<------[RE-CONFIG(RESP:X|OUT-REQ:Y,X+1)]-------
-------------[RE-CONFIG(RESP:Y)]-------------->
The following example illustrates E-A requesting that the streams and TSNs be reset. At completion, E-A has the new sending TSN (selected by the peer) of B, and E-Z has the new sending TSN of A (also selected by the peer).
以下示例说明了请求重置流和TSN的E-A。完成时，E-A具有B的新发送TSN（由对等方选择），E-Z具有A的新发送TSN（也由对等方选择）。
E-A E-Z
------------[RE-CONFIG(TSN-REQ:X)]------------>
<-----[RE-CONFIG(RESP:X/S-TSN=A, R-TSN=B)]-----
E-A E-Z
------------[RE-CONFIG(TSN-REQ:X)]------------>
<-----[RE-CONFIG(RESP:X/S-TSN=A, R-TSN=B)]-----
The following example illustrates E-A requesting the addition of 3 outgoing streams.
以下示例说明E-A请求添加3个传出流。
E-A E-Z
--------[RE-CONFIG(ADD_OUT_STRMS:X/3)]-------->
<-------------[RE-CONFIG(RESP:X)]--------------
E-A E-Z
--------[RE-CONFIG(ADD_OUT_STRMS:X/3)]-------->
<-------------[RE-CONFIG(RESP:X)]--------------
The following example illustrates E-A requesting the addition of 3 incoming streams.
以下示例说明E-A请求添加3个传入流。
E-A E-Z
---------[RE-CONFIG(ADD_IN_STRMS:X/3)]-------->
<----[RE-CONFIG(ADD_OUT_STRMS-REQ:Y,X/3)]------
-------------[RE-CONFIG(RESP:Y)]-------------->
E-A E-Z
---------[RE-CONFIG(ADD_IN_STRMS:X/3)]-------->
<----[RE-CONFIG(ADD_OUT_STRMS-REQ:Y,X/3)]------
-------------[RE-CONFIG(RESP:Y)]-------------->
Authors' Addresses
作者地址
Randall R. Stewart Adara Networks Chapin, SC 29036 USA
Randall R.Stewart Adara Networks Chapin，SC 29036美国
EMail: randall@lakerest.net
EMail: randall@lakerest.net
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
Peter Lei Cisco Systems, Inc. 9501 Technology Blvd. West Office Center Rosemont, IL 60018 USA
Peter Lei思科系统公司，科技大道9501号。美国伊利诺伊州罗斯蒙特西办公中心，邮编：60018
EMail: peterlei@cisco.com
EMail: peterlei@cisco.com