draft-ietf-tsvwg-sctp-strrst-05.txt   draft-ietf-tsvwg-sctp-strrst-06.txt 
Network Working Group R. Stewart Network Working Group R. Stewart
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track P. Lei Intended status: Standards Track P. Lei
Expires: February 24, 2011 Cisco Systems, Inc. Expires: March 30, 2011 Cisco Systems, Inc.
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
August 23, 2010 September 26, 2010
Stream Control Transmission Protocol (SCTP) Stream Reconfiguration Stream Control Transmission Protocol (SCTP) Stream Reconfiguration
draft-ietf-tsvwg-sctp-strrst-05.txt draft-ietf-tsvwg-sctp-strrst-06.txt
Abstract Abstract
Many applications that desire to use SCTP have requested the ability Many applications that use SCTP want the ability to "reset" a stream.
to "reset" a stream. The intention of resetting a stream is to start The intention of resetting a stream is to set the numbering sequence
the numbering sequence of the stream back at 'zero' with a of the stream back to 'zero' with a corresponding notification to the
corresponding notification to the upper layer that this act as been upper layer that this has been performed. The applications that want
performed. The applications that have requested this feature this feature want it so that they can "re-use" streams for different
normally desire it so that they can "re-use" streams for different purposes but still utilize the stream sequence number so that the
purposes but still utilize the stream sequence number for the application can track the message flows. Thus, without this feature,
application to track the message flows. Thus, without this feature, a new use of an old stream would result in message numbers greater
a new use on an old stream would result in message numbers larger than expected unless there is a protocol mechanism to "reset the
than expected without a protocol mechanism to "start the streams back streams back to zero". This document also includes methods for
at zero". This documents presents also a method for resetting the resetting the transport sequence numbers, adding additional streams
transport sequence numbers, adding additional streams and resetting and resetting all stream sequence numbers.
all stream sequence numbers.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 24, 2011. This Internet-Draft will expire on March 30, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 24
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. New Chunk Type . . . . . . . . . . . . . . . . . . . . . . . . 4 3. New Chunk Type . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. STREAM RESET Chunk . . . . . . . . . . . . . . . . . . . . 5 3.1. STREAM RESET Chunk . . . . . . . . . . . . . . . . . . . . 5
4. New Parameter Types . . . . . . . . . . . . . . . . . . . . . 6 4. New Parameter Types . . . . . . . . . . . . . . . . . . . . . 6
4.1. Outgoing SSN Reset Request Parameter . . . . . . . . . . . 6 4.1. Outgoing SSN Reset Request Parameter . . . . . . . . . . . 6
4.2. Incoming SSN Reset Request Parameter . . . . . . . . . . . 8 4.2. Incoming SSN Reset Request Parameter . . . . . . . . . . . 8
4.3. SSN/TSN Reset Request Parameter . . . . . . . . . . . . . 8 4.3. SSN/TSN Reset Request Parameter . . . . . . . . . . . . . 9
4.4. Stream Reset Response Parameter . . . . . . . . . . . . . 9 4.4. Stream Reset Response Parameter . . . . . . . . . . . . . 9
4.5. Add Outgoing Streams Request Parameter . . . . . . . . . . 10 4.5. Add Outgoing Streams Request Parameter . . . . . . . . . . 11
5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 11 5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. Sender Side Procedures . . . . . . . . . . . . . . . . . . 11 5.1. Sender Side Procedures . . . . . . . . . . . . . . . . . . 12
5.1.1. Sender Side Procedures for the Stream Reset Chunk . . 12 5.1.1. Sender Side Procedures for the Stream Reset Chunk . . 12
5.1.2. Sender Side Procedures for the Outgoing SSN Reset 5.1.2. Sender Side Procedures for the Outgoing SSN Reset
Request Parameter . . . . . . . . . . . . . . . . . . 12
5.1.3. Sender Side Procedures for the Incoming SSN Reset
Request Parameter . . . . . . . . . . . . . . . . . . 13 Request Parameter . . . . . . . . . . . . . . . . . . 13
5.1.3. Sender Side Procedures for the Incoming SSN Reset
Request Parameter . . . . . . . . . . . . . . . . . . 14
5.1.4. Sender Side Procedures for the SSN/TSN Reset 5.1.4. Sender Side Procedures for the SSN/TSN Reset
Request Parameter . . . . . . . . . . . . . . . . . . 14 Request Parameter . . . . . . . . . . . . . . . . . . 14
5.1.5. Sender Side Procedures for the Stream Reset 5.1.5. Sender Side Procedures for the Stream Reset
Response Parameter . . . . . . . . . . . . . . . . . . 14 Response Parameter . . . . . . . . . . . . . . . . . . 15
5.1.6. Sender Side Procedures for the Add Outgoing 5.1.6. Sender Side Procedures for the Add Outgoing
Streams Request Parameter . . . . . . . . . . . . . . 15 Streams Request Parameter . . . . . . . . . . . . . . 15
5.2. Receiver Side Procedures . . . . . . . . . . . . . . . . . 15 5.2. Receiver Side Procedures . . . . . . . . . . . . . . . . . 16
5.2.1. Receiver Side Procedures for the Stream Reset Chunk . 15 5.2.1. Receiver Side Procedures for the Stream Reset Chunk . 16
5.2.2. Receiver Side Procedures for the Outgoing SSN 5.2.2. Receiver Side Procedures for the Outgoing SSN
Reset Request Parameter . . . . . . . . . . . . . . . 16 Reset Request Parameter . . . . . . . . . . . . . . . 16
5.2.3. Receiver Side Procedures for the Incoming SSN 5.2.3. Receiver Side Procedures for the Incoming SSN
Reset Request Parameter . . . . . . . . . . . . . . . 17 Reset Request Parameter . . . . . . . . . . . . . . . 17
5.2.4. Receiver Side Procedures for the SSN/TSN Reset 5.2.4. Receiver Side Procedures for the SSN/TSN Reset
Request Parameter . . . . . . . . . . . . . . . . . . 17 Request Parameter . . . . . . . . . . . . . . . . . . 17
5.2.5. Receiver Side Procedures for the Add Outgoing 5.2.5. Receiver Side Procedures for the Add Outgoing
Streams Request Parameter . . . . . . . . . . . . . . 18 Streams Request Parameter . . . . . . . . . . . . . . 18
5.2.6. Receiver Side Procedures for the Stream Reset 5.2.6. Receiver Side Procedures for the Stream Reset
Response Parameter . . . . . . . . . . . . . . . . . . 18 Response Parameter . . . . . . . . . . . . . . . . . . 18
5.3. Various Examples of the Stream Reset procedures . . . . . 19
5.3. Examples of the Stream Reset procedures . . . . . . . . . 19
6. Socket API Considerations . . . . . . . . . . . . . . . . . . 20 6. Socket API Considerations . . . . . . . . . . . . . . . . . . 20
6.1. Events . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.1. Events . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1.1. Stream Reset Event . . . . . . . . . . . . . . . . . . 21 6.1.1. Stream Reset Event . . . . . . . . . . . . . . . . . . 21
6.1.2. Association Reset Event . . . . . . . . . . . . . . . 22 6.1.2. Association Reset Event . . . . . . . . . . . . . . . 22
6.1.3. Stream Change Event . . . . . . . . . . . . . . . . . 22 6.1.3. Stream Change Event . . . . . . . . . . . . . . . . . 23
6.2. Event Subscription . . . . . . . . . . . . . . . . . . . . 23 6.2. Event Subscription . . . . . . . . . . . . . . . . . . . . 24
6.3. Socket Options . . . . . . . . . . . . . . . . . . . . . . 24 6.3. Socket Options . . . . . . . . . . . . . . . . . . . . . . 25
6.3.1. Enable/Disable Stream Reset 6.3.1. Enable/Disable Stream Reset
(SCTP_ENABLE_STREAM_RESET) . . . . . . . . . . . . . . 25 (SCTP_ENABLE_STREAM_RESET) . . . . . . . . . . . . . . 25
6.3.2. Reset Incoming and/or Outgoing Streams 6.3.2. Reset Incoming and/or Outgoing Streams
(SCTP_RESET_STREAMS) . . . . . . . . . . . . . . . . . 26 (SCTP_RESET_STREAMS) . . . . . . . . . . . . . . . . . 26
6.3.3. Reset SSN/TSN (SCTP_RESET_ASSOC) . . . . . . . . . . . 26 6.3.3. Reset SSN/TSN (SCTP_RESET_ASSOC) . . . . . . . . . . . 27
6.3.4. Add Outgoing Streams (SCTP_ADD_OUT_STREAMS) . . . . . 27 6.3.4. Add Outgoing Streams (SCTP_ADD_OUT_STREAMS) . . . . . 27
7. Security Considerations . . . . . . . . . . . . . . . . . . . 27 7. Security Considerations . . . . . . . . . . . . . . . . . . . 28
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
8.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 28 8.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 28
8.2. Five New Parameter Types . . . . . . . . . . . . . . . . . 28 8.2. Five New Parameter Types . . . . . . . . . . . . . . . . . 29
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
10.1. Normative References . . . . . . . . . . . . . . . . . . . 29 10.1. Normative References . . . . . . . . . . . . . . . . . . . 29
10.2. Informative References . . . . . . . . . . . . . . . . . . 29 10.2. Informative References . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction 1. Introduction
Many applications that desire to use SCTP have requested the ability Many applications that use SCTP want the ability to "reset" a stream.
to "reset" a stream. The intention of resetting a stream is to start The intention of resetting a stream is to start the numbering
the numbering sequence of the stream back at 'zero' with a sequence of the stream back to 'zero' with a corresponding
corresponding notification to the upper layer that this act as been notification to the upper layer that this has been performed. The
performed. The applications that have requested this feature applications that want this feature want to "re-use" streams for
normally desire it so that they can "re-use" streams for different different purposes but still utilize the stream sequence number so
purposes but still utilize the stream sequence number for the that the application can track the message flows. Thus, without this
application to track the message flows. Thus, without this feature, feature, a new use of an old stream would result in message numbers
a new use on an old stream would result in message numbers larger greater than expected unless there is a protocol mechanism to "reset
than expected without a protocol mechanism to "start the streams back the streams back to zero". This document also includes methods for
at zero". This documents presents also a method for resetting the resetting the transport sequence numbers, adding additional streams
transport sequence numbers, adding additional streams and resetting and resetting all stream sequence numbers.
all stream sequence numbers.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. New Chunk Type 3. New Chunk Type
This section defines the new chunk type that will be used to reset This section defines the new chunk type that will be used to reset
streams. Table 1 illustrates the new chunk type. streams. Table 1 illustrates the new chunk type.
+------------+-----------------------------------+ +------------+-----------------------------------+
| Chunk Type | Chunk Name | | Chunk Type | Chunk Name |
+------------+-----------------------------------+ +------------+-----------------------------------+
| 0x82 | Stream Reset Chunk (STREAM_RESET) | | 0x82 | Stream Reset Chunk (STREAM_RESET) |
+------------+-----------------------------------+ +------------+-----------------------------------+
Table 1 Table 1
It should be noted that the STREAM_RESET-chunk format requires the It should be noted that the format of the STREAM_RESET chunk requires
receiver to ignore the chunk if it is not understood and continue the receiver to ignore the chunk if it is not understood and continue
processing all chunks that follow. This is accomplished by the use 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 of the upper bits of the chunk type as described in section 3.2 of
[RFC4960]. [RFC4960].
All transported integer numbers are in "network byte order" a.k.a., All transported integer numbers are in "network byte order" a.k.a.,
Big Endian, unless otherwise noted. Big Endian, unless otherwise noted.
3.1. STREAM RESET Chunk 3.1. STREAM RESET Chunk
This document adds one new chunk type to SCTP. The chunk has the This document adds one new chunk type to SCTP. The chunk has the
skipping to change at page 5, line 35 skipping to change at page 5, line 35
This field is set to 0 by the sender and ignored by the receiver. This field is set to 0 by the sender and ignored by the receiver.
Chunk Length: 2 bytes (unsigned integer) Chunk Length: 2 bytes (unsigned integer)
This field holds the length of the chunk, including the Chunk This field holds the length of the chunk, including the Chunk
Type, Chunk Flags and Chunk Length. Type, Chunk Flags and Chunk Length.
Stream Reset Parameter Stream Reset Parameter
This field holds a Stream Reset Request Parameter or a Stream This field holds a Stream Reset Request Parameter or a Stream
Reset Response Parameter. Reset Response Parameter.
Note each STREAM RESET chunk holds at least one parameter and at most Note that each STREAM RESET chunk holds at least one parameter and at
two parameters. Only the following combinations are allowed: most two parameters. Only the following combinations are allowed:
1. Outgoing SSN Reset Request Parameter. 1. Outgoing SSN Reset Request Parameter.
2. Incoming SSN Reset Request Parameter. 2. Incoming SSN Reset Request Parameter.
3. Outgoing SSN Reset Request Parameter, Incoming SSN Reset Request 3. Outgoing SSN Reset Request Parameter, Incoming SSN Reset Request
Parameter. Parameter.
4. SSN/TSN Reset Request Parameter. 4. SSN/TSN Reset Request Parameter.
5. Add Outgoing Streams Request Parameter. 5. Add Outgoing Streams Request Parameter.
6. Stream Reset Response Parameter. 6. Stream Reset Response Parameter.
7. Stream Reset Response Parameter, Outgoing SSN Reset Request 7. Stream Reset Response Parameter, Outgoing SSN Reset Request
Parameter. Parameter.
8. Stream Reset Response Parameter, Stream Reset Response Parameter. 8. Stream Reset Response Parameter, Stream Reset Response Parameter.
If a sender transmits an unsupported combination, the receiver SHOULD If a sender transmits an unsupported combination, the receiver SHOULD
send an ERROR chunk with a protocol violation cause. send an ERROR chunk with a Protocol Violation cause as defined in
section 3.3.10.13 of [RFC4960]).
4. New Parameter Types 4. New Parameter Types
This section defines the new parameter types that will be used in the This section defines the new parameter types that will be used in the
STREAM_RESET chunk. Table 2 illustrates the new parameter types. STREAM_RESET chunk. Table 2 illustrates the new parameter types.
+----------------+----------------------------------------+ +----------------+----------------------------------------+
| Parameter Type | Parameter Name | | Parameter Type | Parameter Name |
+----------------+----------------------------------------+ +----------------+----------------------------------------+
| 0x000d | Outgoing SSN Reset Request Parameter | | 0x000d | Outgoing SSN Reset Request Parameter |
skipping to change at page 6, line 38 skipping to change at page 6, line 39
stop processing the parameter and not to process any further stop processing the parameter and not to process any further
parameters within the chunk if the parameter type is not recognized. parameters within the chunk if the parameter type is not recognized.
This is accomplished by the use of the upper bits of the parameter This is accomplished by the use of the upper bits of the parameter
type as described in section 3.2.1 of [RFC4960]. type as described in section 3.2.1 of [RFC4960].
All transported integer numbers are in "network byte order" a.k.a., All transported integer numbers are in "network byte order" a.k.a.,
Big Endian, unless otherwise noted. Big Endian, unless otherwise noted.
4.1. Outgoing SSN Reset Request Parameter 4.1. Outgoing SSN Reset Request Parameter
This parameter is used by the sender to request some outgoing streams This parameter is used by the sender to request the reset of some or
to be reset. all outgoing streams.
0 1 2 3 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 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 = 0x000d | Parameter Length | | Parameter Type = 0x000d | Parameter Length = 16 + 2 * N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Reset Request Sequence Number | | Stream Reset Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Reset Response Sequence Number | | Stream Reset Response Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Senders Last Assigned TSN | | Senders Last Assigned TSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number 1 (optional) | Stream Number 2 (optional) | | Stream Number 1 (optional) | Stream Number 2 (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ...... / / ...... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number N-1 (optional) | Stream Number N (optional) | | Stream Number N-1 (optional) | Stream Number N (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) Parameter Type: 2 bytes (unsigned integer)
This field holds the IANA defined parameter type for Stream Reset This field holds the IANA defined parameter type for Stream Reset
Request Parameter. The suggested value of this field for IANA is Request Parameter. The suggested value of this field for IANA is
0x000d. 0x000d.
Parameter Length: 2 bytes (unsigned integer) Parameter Length: 2 bytes (unsigned integer)
This field holds the length of the parameter. This field holds the length in bytes of the parameter; the value
MUST be 16 + 2 * N.
Stream Reset Request Sequence Number: 4 bytes (unsigned integer) Stream Reset Request Sequence Number: 4 bytes (unsigned integer)
This field is used to identify the request. It is a monotonically This field is used to identify the request. It is a monotonically
increasing number that is initialized to the same value as the increasing number that is initialized to the same value as the
Initial TSN number. It is increased by 1. Initial TSN number. It is increased by 1 whenever sending a new
Stream Reset Request parameter.
Stream Reset Response Sequence Number: 4 bytes (unsigned integer) Stream Reset Response Sequence Number: 4 bytes (unsigned integer)
In case that this Outgoing SSN Reset Request Parameter is sent in When this Outgoing SSN Reset Request Parameter is sent in response
response to an Incoming SSN Reset Request Parameter this parameter to an Incoming SSN Reset Request Parameter this parameter is also
is also an implicit response to the incoming request. Then this an implicit response to the incoming request. Then this field
field holds the Stream Reset Request Sequence Number of the holds the Stream Reset Request Sequence Number of the incoming
incoming request. In the other case it holds the next expected request. In other cases it holds the next expected Stream Reset
Stream Reset Request Sequence Number - 1. Request Sequence Number minus 1.
Senders last assigned TSN: 4 bytes (unsigned integer) Senders last assigned TSN: 4 bytes (unsigned integer)
This value holds the next TSN minus 1, in other words the last TSN This value holds the next TSN minus 1, in other words the last TSN
that this sender assigned. that this sender assigned.
Stream Number N: 2 bytes (unsigned integer) Stream Number 1..N: 2 bytes (unsigned integer)
This optional field, if included, is used to indicates specific This optional field, if included, is used to indicates specific
streams that are to be reset. If no streams are listed, then all streams that are to be reset. If no streams are listed, then all
streams are to be reset. streams are to be reset.
This parameter can appear in a STREAM RESET chunk. This parameter This parameter can appear in a STREAM RESET chunk. This parameter
MUST NOT appear in any other chunk type. MUST NOT appear in any other chunk type.
4.2. Incoming SSN Reset Request Parameter 4.2. Incoming SSN Reset Request Parameter
This parameter is used by the sender to request that the peer This parameter is used by the sender to request that the peer resets
requests some of its outgoing streams to be reset. some or all of its outgoing streams.
0 1 2 3 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 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 = 0x000e | Parameter Length | | Parameter Type = 0x000e | Parameter Length = 8 + 2 * N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Reset Request Sequence Number | | Stream Reset Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number 1 (optional) | Stream Number 2 (optional) | | Stream Number 1 (optional) | Stream Number 2 (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ...... / / ...... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Number N-1 (optional) | Stream Number N (optional) | | Stream Number N-1 (optional) | Stream Number N (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) Parameter Type: 2 bytes (unsigned integer)
This field holds the IANA defined parameter type for Stream Reset This field holds the IANA defined parameter type for Stream Reset
Request Parameter. The suggested value of this field for IANA is Request Parameter. The suggested value of this field for IANA is
0x000e. 0x000e.
Parameter Length: 2 bytes (unsigned integer) Parameter Length: 2 bytes (unsigned integer)
This field holds the length of the parameter. This field holds the length in bytes of the parameter; the value
MUST be 8 + 2 * N.
Stream Reset Request Sequence Number: 4 bytes (unsigned integer) Stream Reset Request Sequence Number: 4 bytes (unsigned integer)
This field is used to identify the request. It is a monotonically This field is used to identify the request. It is a monotonically
increasing number that is initialized to the same value as the increasing number that is initialized to the same value as the
Initial TSN number. It is increased by 1. Initial TSN number. It is increased by 1 whenever sending a new
Stream Reset Request parameter.
Stream Number N: 2 bytes (unsigned integer) Stream Number 1..N: 2 bytes (unsigned integer)
This optional field, if included, is used to indicate specific This optional field, if included, is used to indicate specific
streams that are to be reset. If no streams are listed, then all streams that are to be reset. If no streams are listed, then all
streams are to be reset. streams are to be reset.
This parameter can appear in a STREAM RESET chunk. This parameter This parameter can appear in a STREAM RESET chunk. This parameter
MUST NOT appear in any other chunk type. MUST NOT appear in any other chunk type.
4.3. SSN/TSN Reset Request Parameter 4.3. SSN/TSN Reset Request Parameter
This parameter is used by the sender to request to reset the TSN and This parameter is used by the sender to request a reset of the TSN
SSN numbering of all streams. and SSN numbering of all streams.
0 1 2 3 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 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 = 0x000f | Parameter Length | | Parameter Type = 0x000f | Parameter Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Reset Request Sequence Number | | Stream Reset Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) Parameter Type: 2 bytes (unsigned integer)
This field holds the IANA defined parameter type for Stream Reset This field holds the IANA defined parameter type for Stream Reset
Request Parameter. The suggested value of this field for IANA is Request Parameter. The suggested value of this field for IANA is
0x000f. 0x000f.
Parameter Length: 2 bytes (unsigned integer) Parameter Length: 2 bytes (unsigned integer)
This field holds the length of the parameter. This field holds the length in bytes of the parameter; the value
MUST be 8.
Stream Reset Request Sequence Number: 4 bytes (unsigned integer) Stream Reset Request Sequence Number: 4 bytes (unsigned integer)
This field is used to identify the request. It is a monotonically This field is used to identify the request. It is a monotonically
increasing number that is initialized to the same value as the increasing number that is initialized to the same value as the
Initial TSN number. It is increased by 1. Initial TSN number. It is increased by 1 whenever sending a new
Stream Reset Request parameter.
This parameter can appear in a STREAM RESET chunk. This parameter This parameter can appear in a STREAM RESET chunk. This parameter
MUST NOT appear in any other chunk type. MUST NOT appear in any other chunk type.
4.4. Stream Reset Response Parameter 4.4. Stream Reset Response Parameter
This parameter is used by the receiver of a stream reset request This parameter is used by the receiver of a stream reset request
parameter to respond to the stream reset request. parameter to respond to the stream reset request.
0 1 2 3 0 1 2 3
skipping to change at page 10, line 6 skipping to change at page 10, line 25
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receiver's next TSN (optional) | | Receiver's next TSN (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) Parameter Type: 2 bytes (unsigned integer)
This field holds the IANA defined parameter type for Stream Reset This field holds the IANA defined parameter type for Stream Reset
Response Parameter. The suggested value of this field for IANA is Response Parameter. The suggested value of this field for IANA is
0x0010. 0x0010.
Parameter Type Length: 2 bytes (unsigned integer) Parameter Type Length: 2 bytes (unsigned integer)
This field holds the length of the parameter. 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.
Stream Reset Response Sequence Number: 4 bytes (unsigned integer) Stream Reset Response Sequence Number: 4 bytes (unsigned integer)
This value is copied from the request parameter and is used by the This value is copied from the request parameter and is used by the
receiver of the Stream Reset Response Parameter to tie the receiver of the Stream Reset Response Parameter to tie the
response to the request. response to the request.
Result: 4 bytes (unsigned integer) Result: 4 bytes (unsigned integer)
This value describes the result of the processing of the request. This value describes the result of the processing of the request.
It is encoded as given by the following table It is encoded as given by the following table
skipping to change at page 10, line 30 skipping to change at page 11, line 5
| 0 | Nothing to do | | 0 | Nothing to do |
| 1 | Performed | | 1 | Performed |
| 2 | Denied | | 2 | Denied |
| 3 | Error - Wrong SSN | | 3 | Error - Wrong SSN |
| 4 | Error - Request already in progress | | 4 | Error - Request already in progress |
| 5 | Error - Bad Sequence Number | | 5 | Error - Bad Sequence Number |
+--------+-------------------------------------+ +--------+-------------------------------------+
Table 3 Table 3
Sender's next TSN: 4 bytes (unsigned integer) This field holds the Sender's next TSN: 4 bytes (unsigned integer)
TSN the sender of the Response will use to send the next DATA This field holds the TSN the sender of the Response will use to
chunk. The field is only applicable in responses to SSN/TSN reset send the next DATA chunk. The field is only applicable in
requests. responses to SSN/TSN reset requests.
Receiver's next TSN: 4 bytes (unsigned integer) This field holds the Receiver's next TSN: 4 bytes (unsigned integer)
TSN the receiver of the response must use to send the next DATA This field holds the TSN the receiver of the response must use to
chunk. The field is only applicable in responses to SSN/TSN reset send the next DATA chunk. The field is only applicable in
requests. responses to SSN/TSN reset requests.
This parameter can appear in a STREAM RESET chunk. This parameter This parameter can appear in a STREAM RESET chunk. This parameter
MUST NOT appear in any other chunk type. MUST NOT appear in any other chunk type.
4.5. Add Outgoing Streams Request Parameter 4.5. Add Outgoing Streams Request Parameter
This parameter is used by the sender to request an additional number This parameter is used by the sender to request that an additional
of outgoing streams (i.e. the receiver's incoming streams) be added number of outgoing streams (i.e. the receiver's incoming streams) be
to the association. added to the association.
0 1 2 3 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 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 = 0x0011 | Parameter Length=12 | | Parameter Type = 0x0011 | Parameter Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Reset Request Sequence Number | | Stream Reset Request Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of new streams | Reserved | | Number of new streams | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Type: 2 bytes (unsigned integer) Parameter Type: 2 bytes (unsigned integer)
This field holds the IANA defined parameter type for the Add This field holds the IANA defined parameter type for the Add
Streams Parameter. The suggested value of this field for IANA is Streams Parameter. The suggested value of this field for IANA is
0x0011. 0x0011.
Parameter Length: 2 bytes (unsigned integer) Parameter Length: 2 bytes (unsigned integer)
This field holds the length of the parameter, a fixed value of 12 This field holds the length in bytes of the parameter; the value
MUST be found in this field. MUST be 12.
Stream Reset Request Sequence Number: 4 bytes (unsigned integer) Stream Reset Request Sequence Number: 4 bytes (unsigned integer)
This field is used to identify the request. It is a monotonically This field is used to identify the request. It is a monotonically
increasing number that is initialized to the same value as the increasing number that is initialized to the same value as the
Initial TSN number. It is increased by 1. Initial TSN number. It is increased by 1 whenever sending a new
Stream Reset Request parameter.
Number of new streams: 2 bytes (unsigned integer) This value holds Number of new streams: 2 bytes (unsigned integer)
the number of additional outgoing streams the sender would like This value holds the number of additional outgoing streams the
added to the association. Streams are added in order and are sender requests to be added to the association. Streams are added
consecutive, e.g. if an association has four outgoing streams in order and are consecutive, e.g. if an association has four
(0-3) and a requested is made to add 3 streams then the new outgoing streams (0-3) and a requested is made to add 3 streams
streams will be 4, 5 and 6. then the new streams will be 4, 5 and 6.
Reserved: 2 bytes (unsigned integer) This field is reserved. It Reserved: 2 bytes (unsigned integer)
SHOULD be set to 0 by the sender and ignored by the receiver. This field is reserved. It SHOULD be set to 0 by the sender and
ignored by the receiver.
This parameter can appear in a STREAM RESET chunk. This parameter This parameter MAY appear in a STREAM RESET chunk. This parameter
MUST NOT appear in any other chunk type. MUST NOT appear in any other chunk type.
5. Procedures 5. Procedures
This section defines the procedures used by both the sender and This section defines the procedures used by both the sender and
receiver of a stream reset. We also give various example stream receiver of a stream reset. We also give various example stream
reset scenarios. reset scenarios.
5.1. Sender Side Procedures 5.1. Sender Side Procedures
This section describes the procedures related to the sending of This section describes the procedures related to the sending of
Stream Reset Chunks. A Stream Reset Chunk is a composition of a Type Stream Reset Chunks. A Stream Reset Chunk is composed of a Type
Length Value (TLV) parameters. Length Value (TLV) parameters.
5.1.1. Sender Side Procedures for the Stream Reset Chunk 5.1.1. Sender Side Procedures for the Stream Reset Chunk
This SCTP extension uses the Supported Extensions Parameter defined This SCTP extension uses the Supported Extensions Parameter defined
in [RFC5061] for negotiating the support of it. in [RFC5061] for negotiating the support for it.
An SCTP endpoint supporting this extension MUST include the chunk An SCTP endpoint supporting this extension MUST include the chunk
type of the STREAM_RESET chunk in the Supported Extensions Parameter type of the STREAM_RESET chunk in the Supported Extensions Parameter
in either the INIT or INIT-ACK. Before sending a Stream Reset Chunk in either the INIT or INIT-ACK. Before sending a Stream Reset Chunk
the sender MUST ensure that the peer advertised support for the the sender MUST ensure that the peer advertised support for the
stream reset extension. If the chunk type of the STREAM_RESET chunk stream reset extension. If the chunk type of the STREAM_RESET chunk
does NOT appear in the supported extensions list of chunks, then the does not appear in the supported extensions list of chunks, then the
sender MUST NOT send any stream reset request to the peer and any sender MUST NOT send any stream reset request to the peer and any
request by the application for such service SHOULD be responded to request by the application for such service SHOULD be responded to
with an appropriate error indicating the peer SCTP stack does not with an appropriate error indicating the peer SCTP stack does not
support the stream reset extension. support the stream reset extension.
After packaging the Stream Reset Chunk and sending it to the peer the After packaging the Stream Reset Chunk and sending it to the peer the
sender MUST start a 'Stream Reset Timer' when the STREAM RESET chunk sender MUST start a 'Stream Reset Timer' if the STREAM RESET chunk
contains at least one request parameter. If it contains no request contains at least one request parameter. If it contains no request
parameter, the Stream Reset Timer MUST NOT be started. This timer parameter, the Stream Reset Timer MUST NOT be started. This timer
MUST use the same value as SCTP's Data transmission timer (i.e. the MUST use the same value as SCTP's Data transmission timer (i.e. the
RTO timer) and MUST use exponential backoff doubling the value at RTO timer) and MUST use exponential backoff doubling the value at
every expiration. If the timer does expire, besides doubling the every expiration. If the timer expires, besides doubling the value,
value, the sender MUST retransmit the Stream Reset Chunk, increment the sender MUST retransmit the Stream Reset Chunk, increment the
the appropriate error counts (both for the association and the appropriate error counts (both for the association and the
destination), and do threshold management possibly destroying the destination), and perform threshold management possibly destroying
association if SCTP retransmission thresholds are surpassed. the association if SCTP retransmission thresholds are exceeded.
5.1.2. Sender Side Procedures for the Outgoing SSN Reset Request 5.1.2. Sender Side Procedures for the Outgoing SSN Reset Request
Parameter Parameter
When an SCTP sender wants to reset the SSNs of some or all outgoing When an SCTP sender wants to reset the SSNs of some or all outgoing
streams it can send an Outgoing SSN Reset Request Parameter if the streams it can send an Outgoing SSN Reset Request Parameter provided
Stream Reset Timer is not running. The following steps MUST be that the Stream Reset Timer is not running. The following steps MUST
followed: be followed:
A1: The sender MUST stop assigning new SSNs to new user data A1: The sender MUST stop assigning new SSNs to new user data
provided by the upper layer. This is because it is unknown as provided by the upper layer. This is because it is not known
to if the receiver of the request will accept or deny it and whether the receiver of the request will accept or deny it and
more so, a lost request might cause an out-of-sequence error in moreover, a lost request might cause an out-of-sequence error in
a stream that the receiver is not yet prepared to handle. a stream that the receiver is not yet prepared to handle.
A2: The sender MUST assign the next stream reset request sequence A2: The sender MUST assign the next stream reset request sequence
number and put it into the Stream Reset Request Sequence Number number and put it into the Stream Reset Request Sequence Number
field of the Outgoing SSN Reset Request Parameter. After field of the Outgoing SSN Reset Request Parameter. The next
assigning it the next stream reset request sequence number MUST stream reset request sequence number MUST then be incremented by
be incremented by '1'. 1.
A3: If this Outgoing SSN Reset Request Parameter is sent in response
to an Incoming SSN Request Parameter, the Stream Numbers between
the Outgoing and the Incoming parameters MUST match. If the
Outgoing SSN Reset Request Parameter is sent on request of the
upper layer the Stream Reset Response Sequence Number is the
next expected Stream Reset Request Sequence Number of the peer -
3.
A4: The sender fills in the TSN it has assigned last. A3: The sender fills in the TSN it last assigned.
A5: If this Outgoing SSN Reset Request Parameter is sent in response A4: If this Outgoing SSN Reset Request Parameter is sent in response
to an Incoming SSN Request Parameter the Stream Numbers are to an Incoming SSN Reset Request Parameter the Stream Numbers
copied from the Incoming SSN Request Parameter to the Outgoing are copied from the Incoming SSN Reset Request Parameter to the
SSN Reset Request Parameter. If this Outgoing SSN Reset Request Outgoing SSN Reset Request Parameter. The Stream Reset Response
Parameter is sent on request of the upper layer and the sender Sequence Number of the Outgoing SSN Reset Request Parameter is
wants all outgoing streams to be reset no Stream Numbers MUST be the Stream Reset Request Sequence Number of the Incoming SSN
put into the Outgoing SSN Reset Request Parameter. If the Reset Request Parameter. If this Outgoing SSN Reset Request
sender wants only some outgoing streams to be reset these Stream Parameter is sent at the request of the upper layer and the
Numbers MUST be filled in the Outgoing SSN Reset Request sender requests all outgoing streams to be reset no Stream
Parameter. Numbers MUST be put into the Outgoing SSN Reset Request
Parameter. If the sender requests only some outgoing streams to
be reset these Stream Numbers MUST be placed in the Outgoing SSN
Reset Request Parameter. Stream Reset Response Sequence Number
is the next expected Stream Reset Request Sequence Number of the
peer minus 1.
A6: The Outgoing SSN Reset Request Parameter is put into a STREAM A5: The Outgoing SSN Reset Request Parameter is put into a STREAM
RESET Chunk. It MAY be put together with an Incoming SSN Reset RESET Chunk. It MAY be put together with either an Incoming SSN
Request Parameter or an Stream Reset Response Parameter and MUST Reset Request Parameter or an Stream Reset Response Parameter
NOT be put together with any other parameter. but not both, and MUST NOT be put together with any other
parameter.
A7: The STREAM RESET Chunk is sent following the rules given in A6: The STREAM RESET Chunk is sent following the rules given in
Section 5.1.1 Section 5.1.1.
5.1.3. Sender Side Procedures for the Incoming SSN Reset Request 5.1.3. Sender Side Procedures for the Incoming SSN Reset Request
Parameter Parameter
When an SCTP sender wants to reset the SSNs of some or all incoming When an SCTP sender wants to reset the SSNs of some or all incoming
streams it can send an Incoming SSN Reset Request Parameter if the streams it can send an Incoming SSN Reset Request Parameter provided
Stream Reset Timer is not running. The following steps MUST be that the Stream Reset Timer is not running. The following steps MUST
followed: be followed:
B1: The sender MUST assign the next stream reset request sequence B1: The sender MUST assign the next stream reset request sequence
number and put it into the Stream Reset Request Sequence Number number and put it into the Stream Reset Request Sequence Number
field of the Incoming SSN Reset Request Parameter. After field of the Incoming SSN Reset Request Parameter. After
assigning it the next stream reset request sequence number MUST assigning it the next stream reset request sequence number MUST
be incremented by '1'. be incremented by 1.
B2: If the sender wants all incoming streams to be reset no Stream B2: If the sender wants all incoming streams to be reset no Stream
Numbers MUST be put into the Incoming SSN Reset Request Numbers MUST be put into the Incoming SSN Reset Request
Parameter. If the sender wants only some incoming streams to be Parameter. If the sender wants only some incoming streams to be
reset these Stream Numbers MUST be filled in the Incoming SSN reset these Stream Numbers MUST be filled in the Incoming SSN
Reset Request Parameter. Reset Request Parameter.
B3: The Incoming SSN Reset Request Parameter is put into a STREAM B3: The Incoming SSN Reset Request Parameter is put into a STREAM
RESET Chunk. It MAY be put together with an Outgoing SSN Reset RESET Chunk. It MAY be put together with an Outgoing SSN Reset
Request Parameter and MUST NOT be put together with any other Request Parameter but MUST NOT be put together with any other
parameter. parameter.
B4: The STREAM RESET Chunk is sent following the rules given in B4: The STREAM RESET Chunk is sent following the rules given in
Section 5.1.1 Section 5.1.1.
5.1.4. Sender Side Procedures for the SSN/TSN Reset Request Parameter 5.1.4. Sender Side Procedures for the SSN/TSN Reset Request Parameter
When an SCTP sender wants to reset the SSNs and TSNs it can send a When an SCTP sender wants to reset the SSNs and TSNs it can send a
SSN/TSN Reset Request Parameter if the Stream Reset Timer is not SSN/TSN Reset Request Parameter provided that the Stream Reset Timer
running. The following steps MUST be followed: is not running. The following steps MUST be followed:
C1: The sender MUST assign the next stream reset request sequence C1: The sender MUST assign the next stream reset request sequence
number and put it into the Stream Reset Request Sequence Number number and put it into the Stream Reset Request Sequence Number
field of the SSN/TSN Reset Request Parameter. After assigning field of the SSN/TSN Reset Request Parameter. After assigning
it the next stream reset request sequence number MUST be it the next stream reset request sequence number MUST be
incremented by '1'. incremented by 1.
C2: The sender MUST queue any user data suspending any new C2: The sender MUST queue any user data suspending any new
transmissions and TSN assignment until the reset procedure is transmissions and TSN assignment until the reset procedure is
finished by the peer either acknowledging or denying the finished by the peer either acknowledging or denying the
request. request.
C3: The SSN/TSN Reset Request Parameter is put into a STREAM RESET C3: The SSN/TSN Reset Request Parameter is put into a STREAM RESET
Chunk. There MUST NOT be any other parameter in this chunk. Chunk. There MUST NOT be any other parameter in this chunk.
C4: The STREAM RESET Chunk is sent following the rules given in C4: The STREAM RESET Chunk is sent following the rules given in
Section 5.1.1 Section 5.1.1.
There SHOULD NOT be sent more than one SSN/TSN Reset Request within a Only one SSN/TSN Reset Request SHOULD be sent within a maximum
maximum segment lifetime. segment lifetime, the IP MSL.
5.1.5. Sender Side Procedures for the Stream Reset Response Parameter 5.1.5. Sender Side Procedures for the Stream Reset Response Parameter
When an implementation receives a request parameter it MUST respond When an implementation receives a reset request parameter it MUST
with a Stream Reset Response Parameter in the following manner: respond with a Stream Reset Response Parameter in the following
manner:
D1: The Stream Reset Request Sequence number of the incoming request D1: The Stream Reset Request Sequence number of the incoming request
is copied to the Stream Reset Response Sequence Number field of is copied to the Stream Reset Response Sequence Number field of
the Stream Reset Response Parameter. the Stream Reset Response Parameter.
D2: The result of the processing of the incoming request is filled D2: The result of the processing of the incoming request is placed
in the Result field of the Stream Reset Response Parameter in the Result field of the Stream Reset Response Parameter.
D3: If the incoming request is a SSN/TSN reset requests, the D3: If the incoming request is a SSN/TSN reset request, the Sender's
Sender's next TSN field is filled with the next TSN the sender next TSN field is filled with the next TSN the sender of this
of this Stream Reset Response Parameter will assign. For other Stream Reset Response Parameter will assign. For other requests
requests the Sender's next TSN field is not filled. the Sender's next TSN field is not filled in.
D4: If the incoming request is a SSN/TSN reset request, the D4: If the incoming request is a SSN/TSN reset request, the
Receiver's next TSN field is filled with a TSN such that the Receiver's next TSN field is filled with a TSN such that the
sender of the Stream Reset Response Parameter can be sure it can sender of the Stream Reset Response Parameter can be sure it can
discard received DATA chunks with smaller TSNs. A good value discard received DATA chunks with smaller TSNs. The value
for this is the highest TSN it has seen plus some delta. For should be the smallest TSN not acknowledged by the receiver of
other requests the Sender's next TSN field is not filled. the request plus 2^31. For other requests the Receiver's next
TSN field is not filled in.
5.1.6. Sender Side Procedures for the Add Outgoing Streams Request 5.1.6. Sender Side Procedures for the Add Outgoing Streams Request
Parameter Parameter
When an SCTP sender wants to increase the number of outbound streams When an SCTP sender wants to increase the number of outbound streams
it is able to send to, it may add a Add Streams parameter to the to which it is able to send, it may add an Add Outgoing Streams
STREAM RESET chunk. Upon sending the request the sender MUST await a Request parameter to the STREAM RESET chunk. Upon sending the
positive acknowledgment (Success) before using any additional stream request the sender MUST await a positive acknowledgment (Success)
added by this request. Note that new streams are added adjacent to before using any additional stream added by this request. Note that
the previous steams with no gaps. This means that if a request is new streams are added adjacent to the previous streams with no gaps.
made to add 2 streams to an association that has already 5 (0-4) then This means that if a request is made to add 2 streams to an
the new streams, upon successful completion, are streams 5 and 6. association that has already 5 (0-4) then the new streams, upon
Any new stream MUST number its first message to be stream sequence 0. successful completion, are streams 5 and 6. A new stream MUST use
for its first ordered message the stream sequence number 0.
5.2. Receiver Side Procedures 5.2. Receiver Side Procedures
5.2.1. Receiver Side Procedures for the Stream Reset Chunk 5.2.1. Receiver Side Procedures for the Stream Reset Chunk
Upon reception of a Stream Reset Chunk each parameter within it Upon reception of a Stream Reset Chunk each parameter within it
should be processed. If some parameters have to be sent back, they SHOULD be processed. If multiple parameters have to be returned,
MUST all be put into one STREAM RESET chunk. If the received STREAM they MUST be put into one STREAM RESET chunk. If the received STREAM
RESET chunk contains at least one request parameter, a SACK chunk RESET chunk contains at least one request parameter, a SACK chunk
SHOULD be sent back and MAY be bundled with the STREAM RESET chunk. SHOULD be sent back and MAY be bundled with the STREAM RESET chunk.
If the received STREAM RESET chunk contains at least one request and If the received STREAM RESET chunk contains at least one request and
based on the analysis of the Stream Reset Request Sequence Numbers based on the analysis of the Stream Reset Request Sequence Numbers
this is the last received STREAM RESET chunk (i.e. a retransmission), this is the last received STREAM RESET chunk (i.e. a retransmission),
the same STREAM RESET chunk has to be sent back in response as the same STREAM RESET chunk MUST to be sent back in response as was
earlier. earlier.
The decision to deny a stream reset request is an administrative The decision to deny a stream reset request is an administrative
decision and may be user configurable even after the association has decision and may be user configurable even after the association has
formed. If for whatever reason the endpoint does NOT wish to process formed. If for whatever reason the endpoint does not wish to process
a received request parameter it MUST send a corresponding response a received request parameter it MUST send a corresponding response
parameter as described in Section 5.1.5 with an appropriate Result parameter as described in Section 5.1.5 with an appropriate Result
field. field.
Implementation Note: A SACK is recommended to be bundled with any Implementation Note: A SACK is recommended to be bundled with any
stream reset response so that any retransmission processing that stream reset response so that any retransmission processing that
needs to occur can be expedited. A SACK chunk is not required for 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 this feature to work, but it will in effect help minimize the delay
in completing a stream reset operation in the face of any data loss. in completing a stream reset operation in the face of any data loss.
5.2.2. Receiver Side Procedures for the Outgoing SSN Reset Request 5.2.2. Receiver Side Procedures for the Outgoing SSN Reset Request
Parameter Parameter
In the case that the endpoint is willing to perform a stream reset In the case that the endpoint is willing to perform a stream reset
the following steps SHOULD be followed: the following steps MUST be followed:
E1: If the Senders Last Assigned TSN number is greater than the E1: If the Senders Last Assigned TSN number is greater than the
cumulative acknowledgment point, then the endpoint MUST enter cumulative acknowledgment point, then the endpoint MUST enter
"deferred reset processing". In this mode, any data arriving "deferred reset processing". In this mode, any data arriving
with a TSN number larger than the 'senders last assigned TSN' with a TSN number larger than the 'senders last assigned TSN'
for the effected stream(s) MUST be queued locally and held until for the affected stream(s) MUST be queued locally and held until
the Cumulative Acknowledgment point reaches the 'senders last the Cumulative Acknowledgment point reaches the 'senders last
assigned TSN number'. When the Cumulative Acknowledgment point assigned TSN number'. When the Cumulative Acknowledgment point
reaches the last assigned TSN number then proceed to the next reaches the last assigned TSN number then proceed to the next
step. Note that the receiver of a stream reset that causes it step. Note that the receiver of a stream reset that causes it
to entered deferred reset processing does NOT withhold the to entered deferred reset processing does not withhold the
stream reset acknowledgment from the peer. This also means that stream reset acknowledgment from the peer. This also means that
the receiver will need to queue up any additional stream reset the receiver will need to queue up any additional stream reset
requests received including the one that caused the receiver to requests received including the one that caused the receiver to
enter deferred reset processing. This is because once the enter deferred reset processing. This is because once the
acknowledgement is received by the sender, the sender is free to acknowledgement is received by the sender, the sender is free to
send a new stream reset. send a new stream reset.
E2: If the Stream Reset Timer is running for the Stream Reset E2: If the Stream Reset Timer is running for the Stream Reset
Request Sequence Number indicated in the Stream Reset Response Request Sequence Number indicated in the Stream Reset Response
Sequence Number field, mark the Stream Reset Request Sequence Sequence Number field, the Stream Reset Request Sequence Number
Number as acknowledged. If all Stream Reset Request Sequence MUST be marked as acknowledged. If all Stream Reset Request
Numbers the Stream Reset Timer is running for are acknowledged, Sequence Numbers the Stream Reset Timer is running for are
stop the Stream Reset Timer. acknowledged, the Stream Reset Timer MUST be stopped.
E3: If no Stream Numbers are listed in the parameter, then all E3: If no Stream Numbers are listed in the parameter, then all
incoming streams MUST be reset to '0' as the next expected incoming streams MUST be reset to 0 as the next expected stream
stream sequence number. If specific Stream Numbers are listed, sequence number. If specific Stream Numbers are listed, then
then only these specific streams MUST be reset to '0' and all only these specific streams MUST be reset to 0 and all other
other non-listed stream sequence numbers remain unchanged. non-listed stream sequence numbers remain unchanged.
E4: Optionally an Upper Layer Notification SHOULD be sent to inform E4: Optionally an Upper Layer Notification should be sent to inform
the local endpoint that the inbound streams have been reset. the local endpoint that the inbound streams have been reset.
E5: Any queued TSN's (queued at step E1) should now be released and E5: Any queued TSN's (queued at step E1) MUST now be released and
processed normally. processed normally.
E6: A Stream Reset Response Parameter is put into a STREAM RESET E6: A Stream Reset Response Parameter is put into a STREAM RESET
chunk indicating successful processing. chunk indicating successful processing.
E7: The STREAM RESET chunk is sent after the incoming STREAM RESET E7: The STREAM RESET chunk is sent after the incoming STREAM RESET
chunk is processed completely. chunk is processed completely.
5.2.3. Receiver Side Procedures for the Incoming SSN Reset Request 5.2.3. Receiver Side Procedures for the Incoming SSN Reset Request
Parameter Parameter
In the case that the endpoint is willing to perform a stream reset In the case that the endpoint is willing to perform a stream reset
the following steps SHOULD be followed: the following steps MUST be followed:
F1: An Outgoing Stream Reset Request Parameter MUST be put into an F1: An Outgoing Stream Reset Request Parameter MUST be put into an
STREAM RESET chunk according to Section 5.1.2. STREAM RESET chunk according to Section 5.1.2.
F2: The STREAM RESET chunk is sent after the incoming STREAM RESET F2: The STREAM RESET chunk is sent after the incoming STREAM RESET
chunk is processed completely. chunk is processed completely.
5.2.4. Receiver Side Procedures for the SSN/TSN Reset Request Parameter 5.2.4. Receiver Side Procedures for the SSN/TSN Reset Request Parameter
In the case that the endpoint is willing to perform a SSN/TSN reset In the case that the endpoint is willing to perform a SSN/TSN reset
the following steps SHOULD be followed: the following steps MUST be followed:
G1: Compute an appropriate value for the Receiver's next TSN, the G1: Compute an appropriate value for the Receiver's next TSN, the
TSN the peer should use to send the next DATA chunk. The value TSN the peer should use to send the next DATA chunk. The value
SHOULD be the smallest TSN not acknowledged by the receiver of should be the smallest TSN not acknowledged by the receiver of
the request plus 2^31. the request plus 2^31.
G2: Compute an appropriate value for the local endpoints next TSN, G2: Compute an appropriate value for the local endpoints next TSN,
i.e. the receiver of the SSN/TSN reset chunks next TSN to be i.e. the receiver of the SSN/TSN reset chunks next TSN to be
assigned. The value SHOULD be the highest TSN sent by the assigned. The value should be the highest TSN sent by the
receiver of the request plus 1. receiver of the request plus 1.
G3: Do the same processing as if a SACK chunk with no gap report and G3: Do the same processing as if a SACK chunk with no gap report and
a cumulative TSN ACK of Sender's next TSN - 1 was received. a cumulative TSN ACK of Sender's next TSN minus 1 was received.
G4: Do the same processing as if an FWD-TSN chunk with all streams G4: Do the same processing as if an FWD-TSN chunk with all streams
affected and a new cumulative TSN ACK of Receiver's next TSN - 1 affected and a new cumulative TSN ACK of Receiver's next TSN
was received. minus 1 was received.
G5: All incoming and outgoing streams MUST be reset to '0' as the G5: The next expected and outgoing stream sequence numbers MUST be
next expected and outgoing stream sequence numbers, reset to 0 for all incoming and outgoing streams.
respectively.
G6: A Stream Reset Response Parameter is put into a STREAM RESET G6: A Stream Reset Response Parameter is put into a STREAM RESET
chunk indicating successful processing. chunk indicating successful processing.
G7: The STREAM RESET chunk is sent after the incoming STREAM RESET G7: The STREAM RESET chunk is sent after the incoming STREAM RESET
chunk is processed completely. chunk is processed completely.
5.2.5. Receiver Side Procedures for the Add Outgoing Streams Request 5.2.5. Receiver Side Procedures for the Add Outgoing Streams Request
Parameter Parameter
When an SCTP endpoint receives a stream reset request adding When an SCTP endpoint receives a stream reset request adding
additional streams, it MUST send a response parameter either additional streams, it MUST send a response parameter either
acknowledging or rejecting the request. If the response is acknowledging or denying the request. If the response is successful
successful the receiver MUST add the requested number of inbound the receiver MUST add the requested number of inbound streams to the
streams to the association, initializing the next expected stream association, initializing the next expected stream sequence number to
sequence number to be 0. be 0.
5.2.6. Receiver Side Procedures for the Stream Reset Response Parameter 5.2.6. Receiver Side Procedures for the Stream Reset Response Parameter
On receipt of a Stream Reset Response Parameter the following MUST be On receipt of a Stream Reset Response Parameter the following MUST be
performed: performed:
H1: If the Stream Reset Timer is running for the Stream Reset H1: If the Stream Reset Timer is running for the Stream Reset
Request Sequence Number indicated in the Stream Reset Response Request Sequence Number indicated in the Stream Reset Response
Sequence Number field, mark the Stream Reset Request Sequence Sequence Number field, mark the Stream Reset Request Sequence
Number as acknowledged. If all Stream Reset Request Sequence Number as acknowledged. If all Stream Reset Request Sequence
Numbers the Stream Reset Timer is running for are acknowledged, Numbers the Stream Reset Timer is running for are acknowledged,
stop the Stream Reset Timer. If the timer was not running for stop the Stream Reset Timer. If the timer was not running for
the Stream Reset Request Sequence Number, the processing of the the Stream Reset Request Sequence Number, the processing of the
Stream Reset Response Parameter is complete. Stream Reset Response Parameter is complete.
H2: If the Result field does not indicate successful processing an H2: If the Result field does not indicate successful processing an
Upper Layer Notification SHOULD be sent to inform the local Upper Layer Notification should be sent to inform the local
endpoint of the failure to reset its outbound streams. endpoint of the failure to reset its outbound streams.
Afterwards processing of this response is complete. Afterwards processing of this response is complete.
H3: If the request was an Outgoing Stream Reset Request the affected H3: If the request was an Outgoing Stream Reset Request the affected
streams should now be reset and all queued data should be streams should now be reset and all queued data should be
processed now and assigning of stream sequence numbers is processed now and assigning of stream sequence numbers is
allowed again. Optionally an Upper Layer Notification SHOULD be allowed again. Optionally an Upper Layer Notification should be
sent to inform the local endpoint that the outbound streams have sent to inform the local endpoint that the outbound streams have
been reset. been reset.
H4: If the request was a SSN/TSN Reset Request new DATA should be H4: If the request was a SSN/TSN Reset Request new DATA should be
sent from Receiver's next TSN and beginning with stream sequence sent from Receiver's next TSN and beginning with stream sequence
number '0' for all outgoing streams. All incoming streams are number 0 for all outgoing streams. All incoming streams are
also reset to '0' as the next expected stream sequence number. also reset to 0 as the next expected stream sequence number.
The peer will send DATA chunks starting with Sender's next TSN. The peer will send DATA chunks starting with Sender's next TSN.
H5: If the request was to add outgoing streams and the result was H5: If the request was to add outgoing streams and the result was
successful, the endpoint should add the additional streams to successful, the endpoint should add the additional streams to
the association. Note that an implementation may allocate the the association. Note that an implementation may allocate the
memory at the time of the request, but it MUST NOT use the memory at the time of the request, but it MUST NOT use the
streams until the peer has responded with a positive streams until the peer has responded with a positive
acknowledgment. acknowledgment.
5.3. Various Examples of the Stream Reset procedures 5.3. Examples of the Stream Reset procedures
The following message flows between an Endpoint A and an Endpoint Z
illustrate the described procedures. The time progresses in downward
direction.
The following example illustrates an Endpoint A resetting stream 1 The following example illustrates an Endpoint A resetting stream 1
and 2 for just its outgoing streams. and 2 for just its outgoing streams.
E-A E-Z E-A E-Z
----------[STR_RESET(OUT-REQ:X/1,2)]----------> ----------[STR_RESET(OUT-REQ:X/1,2)]---------->
<-------------[STR_RESET(RESP:X)]-------------- <-------------[STR_RESET(RESP:X)]--------------
The following example illustrates an Endpoint A resetting stream 1 The following example illustrates an Endpoint A resetting stream 1
and 2 for just its incoming streams. and 2 for just its incoming streams.
E-A E-Z E-A E-Z
-----------[STR_RESET(IN-REQ:X/1,2)]----------> -----------[STR_RESET(IN-REQ:X/1,2)]---------->
<-----------[STR_RESET(OUT-REQ:Y,X)]----------- <--------[STR_RESET(OUT-REQ:Y,X/1,2)]----------
-------------[STR_RESET(RESP:Y)]--------------> -------------[STR_RESET(RESP:Y)]-------------->
The following example illustrates an Endpoint A resetting all streams The following example illustrates an Endpoint A resetting all streams
in both directions. in both directions.
E-A E-Z E-A E-Z
-----[STR_RESET(OUT-REQ:X,Y-1)|IN-REQ:X+1]----> -----[STR_RESET(OUT-REQ:X,Y-1)|IN-REQ:X+1]---->
<------[STR_RESET(RESP:X|OUT-REQ:Y,X+1)]------- <------[STR_RESET(RESP:X|OUT-REQ:Y,X+1)]-------
-------------[STR_RESET(RESP:Y)]--------------> -------------[STR_RESET(RESP:Y)]-------------->
The following example illustrates an Endpoint A requesting the The following example illustrates an Endpoint A requesting the
streams and TSN's be reset. At the completion E-A has the new streams and TSN's be reset. At the completion E-A has the new
skipping to change at page 20, line 13 skipping to change at page 20, line 31
The following example illustrates an Endpoint A requesting to add 3 The following example illustrates an Endpoint A requesting to add 3
additional outgoing streams. additional outgoing streams.
E-A E-Z E-A E-Z
--------[STR_RESET(ADD_OUT_STRMS:X/3)]--------> --------[STR_RESET(ADD_OUT_STRMS:X/3)]-------->
<-------------[STR_RESET(RESP:X)]-------------- <-------------[STR_RESET(RESP:X)]--------------
6. Socket API Considerations 6. Socket API Considerations
This section describes how the socket API defined in This section describes how the socket API defined in
[I-D.ietf-tsvwg-sctpsocket] SHOULD be extended to make the features [I-D.ietf-tsvwg-sctpsocket] needs to be extended to make the features
of SCTP stream reset available to the application. of SCTP stream reset available to the application.
Please note that this section is informational only.
6.1. Events 6.1. Events
The union sctp_notification {} is extended by containing three new The union sctp_notification {} is extended to contain three new
fields: sn_strreset_event, sn_assocreset_event, and fields: sn_strreset_event, sn_assocreset_event, and
sn_strchange_event: sn_strchange_event:
union sctp_notification { union sctp_notification {
struct { struct {
uint16_t sn_type; uint16_t sn_type;
uint16_t sn_flags; uint16_t sn_flags;
uint32_t sn_length; uint32_t sn_length;
} sn_header; } sn_header;
... ...
skipping to change at page 21, line 36 skipping to change at page 22, line 19
SCTP_STREAM_RESET_OUTGOING_SSN: The stream identifiers given in SCTP_STREAM_RESET_OUTGOING_SSN: The stream identifiers given in
strreset_stream_list[] refers to outgoing streams of the strreset_stream_list[] refers to outgoing streams of the
endpoint. endpoint.
SCTP_STREAM_RESET_DENIED: The corresponding request was denied by SCTP_STREAM_RESET_DENIED: The corresponding request was denied by
the peer. the peer.
SCTP_STREAM_RESET_FAILED: The corresponding request failed. SCTP_STREAM_RESET_FAILED: The corresponding request failed.
At least one of SCTP_STREAM_RESET_INCOMING_SSN and At least one of SCTP_STREAM_RESET_INCOMING_SSN and
SCTP_STREAM_RESET_OUTGOING_SSN are set. SCTP_STREAM_RESET_DENIED SCTP_STREAM_RESET_OUTGOING_SSN is set. SCTP_STREAM_RESET_DENIED
and SCTP_STREAM_RESET_FAILED are mutual exclusive. If the request and SCTP_STREAM_RESET_FAILED are mutually exclusive. If the
was successful, none of these are set. request was successful, none of these are set.
strreset_length: This field is the total length of the delivered strreset_length: This field is the total length of the delivered
event, including the header. event, including the header.
strreset_assoc_id: The association id field, holds the identifier strreset_assoc_id: The association id field, holds the identifier
for the association. All notifications for a given association for the association. All notifications for a given association
have the same association identifier. For one-to-one style have the same association identifier. For one-to-one style
socket, this field is ignored. socket, this field is ignored.
strreset_stream_list: The list of stream identifiers this event strreset_stream_list: The list of stream identifiers this event
skipping to change at page 24, line 8 skipping to change at page 24, line 39
expanded their data structure for this API to include the stream expanded their data structure for this API to include the stream
reset subscriptions. The new API is to use a setsockopt with the reset subscriptions. The new API is to use a setsockopt with the
SCTP_SET_EVENT socket option. This option takes a structure that SCTP_SET_EVENT socket option. This option takes a structure that
defines the association, the event type (using the same value found defines the association, the event type (using the same value found
in the event type field) and a on/off boolean. This newer API is the in the event type field) and a on/off boolean. This newer API is the
preferred method but we define both methods for compatibility. preferred method but we define both methods for compatibility.
For some implementations the structure now takes on the form: For some implementations the structure now takes on the form:
struct sctp_event_subscribe { struct sctp_event_subscribe {
uint8_t sctp_data_io_event; uint8_t sctp_data_io_event;
uint8_t sctp_association_event; uint8_t sctp_association_event;
uint8_t sctp_address_event; uint8_t sctp_address_event;
uint8_t sctp_send_failure_event; uint8_t sctp_send_failure_event;
uint8_t sctp_peer_error_event; uint8_t sctp_peer_error_event;
uint8_t sctp_shutdown_event; uint8_t sctp_shutdown_event;
uint8_t sctp_partial_delivery_event; uint8_t sctp_partial_delivery_event;
uint8_t sctp_adaptation_layer_event; uint8_t sctp_adaptation_layer_event;
uint8_t sctp_authentication_event; uint8_t sctp_authentication_event;
uint8_t sctp_sender_dry_event; uint8_t sctp_sender_dry_event;
uint8_t sctp_stream_reset_event; uint8_t sctp_stream_reset_event;
uint8_t sctp_assoc_reset_event; uint8_t sctp_assoc_reset_event;
uint8_t sctp_stream_change_event; uint8_t sctp_stream_change_event;
}; };
For those implementations that support this method simply putting a 1 For those implementations that support this method simply putting a 1
or 0 in the sctp_stream_reset_event and setting the SCTP_EVENTS or 0 in the sctp_stream_reset_event and setting the SCTP_EVENTS
socket option will work. However not all implementations support socket option will work. However not all implementations support
this method. this method.
The preferred method is to use the SCTP_SET_EVENT socket option and The preferred method is to use the SCTP_SET_EVENT socket option and
fill in the structure sctp_set_event structure. fill in the structure sctp_set_event structure.
struct sctp_set_event { struct sctp_set_event {
sctp_assoc_t se_assoc_id; sctp_assoc_t se_assoc_id;
uint16_t se_type; uint16_t se_type;
uint8_t se_on; uint8_t se_on;
}; };
Using this method, the user fill in the se_type with the same value Using this method, the user fills in the se_type with the same value
found in strreset_type field i.e. SCTP_STREAM_RESET_EVENT. The user found in strreset_type field i.e. SCTP_STREAM_RESET_EVENT. The user
will also fill in the se_assoc_id field with either the association 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 to set this event on (this field is ignored for one-to-one style
sockets) or one of the reserved constant values defined in the socket sockets) or one of the reserved constant values defined in the socket
API document. Finally the se_on field is set with a 1 to enable the API document. Finally the se_on field is set with a 1 to enable the
event or a 0 to disable the event. event or a 0 to disable the event.
6.3. Socket Options 6.3. Socket Options
The following table describes the new socket options which make the The following table describes the new socket options which make the
skipping to change at page 25, line 21 skipping to change at page 25, line 48
| SCTP_ADD_OUT_STREAMS | struct sctp_assoc_value | | X | | SCTP_ADD_OUT_STREAMS | struct sctp_assoc_value | | X |
+--------------------------+---------------------------+-----+-----+ +--------------------------+---------------------------+-----+-----+
Table 5 Table 5
6.3.1. Enable/Disable Stream Reset (SCTP_ENABLE_STREAM_RESET) 6.3.1. Enable/Disable Stream Reset (SCTP_ENABLE_STREAM_RESET)
This option allows a user to control whether the SCTP implementation This option allows a user to control whether the SCTP implementation
processes or denies incoming requests in STREAM_RESET chunks. processes or denies incoming requests in STREAM_RESET chunks.
The default is not to process incoming requests. The default is to deny incoming requests.
To set or get this option the user fills in the following structure: To set or get this option the user fills in the following structure:
struct sctp_assoc_value { struct sctp_assoc_value {
sctp_assoc_t assoc_id; sctp_assoc_t assoc_id;
uint32_t assoc_value; uint32_t assoc_value;
}; };
assoc_id: This parameter is ignored for one-to-one style sockets. assoc_id: This parameter is ignored for one-to-one style sockets.
For one-to-many style sockets this parameter indicates which For one-to-many style sockets this parameter indicates which
skipping to change at page 25, line 49 skipping to change at page 26, line 29
SCTP_DENY_RESET_OUT_STREAM_REQ: Deny received Outgoing SSN Reset SCTP_DENY_RESET_OUT_STREAM_REQ: Deny received Outgoing SSN Reset
Requests if this flag is set, process it if not. Requests if this flag is set, process it if not.
SCTP_DENY_RESET_ASSOC_REQ: Deny received SSN/TSN Reset Requests SCTP_DENY_RESET_ASSOC_REQ: Deny received SSN/TSN Reset Requests
if this flag is set, process it if not. if this flag is set, process it if not.
SCTP_DENY_CHANGE_ASSOC_REQ: Deny received Add Outgoing Streams SCTP_DENY_CHANGE_ASSOC_REQ: Deny received Add Outgoing Streams
Requests if this flag is set, process it if not. Requests if this flag is set, process it if not.
The default value is ~(SCTP_DENY_IN_STREAM_RESET| The default value is SCTP_DENY_IN_STREAM_RESET|
SCTP_DENY_OUT_STREAM_RESET|SCTP_DENY_ASSOC_RESET| SCTP_DENY_OUT_STREAM_RESET|SCTP_DENY_ASSOC_RESET|
SCTP_DENY_ASSOC_CHANGE) SCTP_DENY_ASSOC_CHANGE.
Please note that using the option does not have any impact on Please note that using the option does not have any impact on
subscribing to any related events. subscribing to any related events.
6.3.2. Reset Incoming and/or Outgoing Streams (SCTP_RESET_STREAMS) 6.3.2. Reset Incoming and/or Outgoing Streams (SCTP_RESET_STREAMS)
This option allows the user to request the reset incoming and/or This option allows the user to request the reset of incoming and/or
outgoing streams. outgoing streams.
To set or get this option the user fills in the following structure: To set or get this option the user fills in the following structure:
struct sctp_reset_streams { struct sctp_reset_streams {
sctp_assoc_t srs_assoc_id; sctp_assoc_t srs_assoc_id;
uint16_t srs_flags; uint16_t srs_flags;
uint16_t srs_number_streams; uint16_t srs_number_streams;
uint16_t srs_stream_list[]; uint16_t srs_stream_list[];
}; };
skipping to change at page 26, line 46 skipping to change at page 27, line 28
streams. streams.
srs_stream_list: This parameter contains a list of stream srs_stream_list: This parameter contains a list of stream
identifiers on which the operation is performed on. It contains identifiers on which the operation is performed on. It contains
srs_number_streams elements. If it is empty, the operation is srs_number_streams elements. If it is empty, the operation is
performed on all streams. Depending on srs_flags the identifiers performed on all streams. Depending on srs_flags the identifiers
refer to incoming or outgoing streams or both. refer to incoming or outgoing streams or both.
6.3.3. Reset SSN/TSN (SCTP_RESET_ASSOC) 6.3.3. Reset SSN/TSN (SCTP_RESET_ASSOC)
This option allows a user to request the reset the SSN/TSN. This option allows a user to request the reset of the SSN/TSN.
To set this option the user provides an option_value of type To set this option the user provides an option_value of type
sctp_assoc_t. sctp_assoc_t.
On one-to-one style sockets the option_value is ignored. For one-to- 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 many style sockets the option_value is the association identifier of
the association on which the action is to be performed on. the association on which the action is to be performed on.
6.3.4. Add Outgoing Streams (SCTP_ADD_OUT_STREAMS) 6.3.4. Add Outgoing Streams (SCTP_ADD_OUT_STREAMS)
skipping to change at page 27, line 48 skipping to change at page 28, line 34
8. IANA Considerations 8. IANA Considerations
[NOTE to RFC-Editor: [NOTE to RFC-Editor:
"RFCXXXX" is to be replaced by the RFC number you assign this "RFCXXXX" is to be replaced by the RFC number you assign this
document. document.
] ]
This document (RFCXXX) is the reference for all registrations This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed in described in this section. The suggested changes are described
the document available at sctp-parameters [1]. The suggested changes below.
are described below.
8.1. A New Chunk Type 8.1. A New Chunk Type
A chunk type has to be assigned by IANA. It is suggested to use the A chunk type has to be assigned by IANA. It is suggested to use the
values given in Table 1. The value MUST be from the pool of chunks values given in Table 1. IANA shoal assign this value from the pool
with the upper two bits set to '10'. of chunks with the upper two bits set to '10'.
This requires an additional line in the "CHUNK TYPES" table of sctp- This requires an additional line in the "CHUNK TYPES" table for SCTP:
parameters [1]:
CHUNK TYPES CHUNK TYPES
ID Value Chunk Type Reference ID Value Chunk Type Reference
----- ---------- --------- ----- ---------- ---------
130 Stream Reset Chunk (STREAM_RESET) [RFCXXXX] 130 Stream Reset Chunk (STREAM_RESET) [RFCXXXX]
The registration table as defined in
[I-D.ietf-tsvwg-sctp-chunk-flags] for the chunk flags of this chunk
type is empty.
8.2. Five New Parameter Types 8.2. Five New Parameter Types
Five parameter types have to be assigned by IANA. It is suggested to Five parameter types have to be assigned by IANA. It is suggested to
use the values given in Table 2. The values MUST be from the pool of use the values given in Table 2. IANA shoal assign this value from
parameters with the upper two bits set to '00'. the pool of parameters with the upper two bits set to '00'.
This requires an addition to the "CHUNK PARAMETER TPYES" tables in This requires an additional table in the "CHUNK PARAMETER TYPES"
sctp-parameters [1]: An Entry for "STREAM RESET Chunk Parameter tables for SCTP: An Entry for "STREAM RESET Chunk Parameter Types"
Types" has to be made with the following initial contents: has to be made with the following initial contents:
--STREAM RESET Chunk Parameter Types --STREAM RESET Chunk Parameter Types
Chunk Parameter Type Value Chunk Parameter Type Value
-------------------- ---------- -------------------- ----------
Outgoing SSN Reset Request Parameter 13 (0x000d) Outgoing SSN Reset Request Parameter 13 (0x000d)
Incoming SSN Reset Request Parameter 14 (0x000e) Incoming SSN Reset Request Parameter 14 (0x000e)
SSN/TSN Reset Request Parameter 15 (0x000f) SSN/TSN Reset Request Parameter 15 (0x000f)
Stream Reset Response Parameter 16 (0x0010) Stream Reset Response Parameter 16 (0x0010)
Add Outgoing Streams Request Parameter 17 (0x0011) Add Outgoing Streams Request Parameter 17 (0x0011)
9. Acknowledgments 9. Acknowledgments
The authors wish to thank Paul Aitken, Kacheong Poon, Irene The authors wish to thank Paul Aitken, Gorry Fairhurst, Tom Pelch,
Ruengeler, Robin Seggelmann, and Vlad Yasevich for there invaluable Kacheong Poon, Irene Ruengeler, Robin Seggelmann, and Vlad Yasevich
comments. for there invaluable comments.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007. RFC 4960, September 2007.
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. [RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.
Kozuka, "Stream Control Transmission Protocol (SCTP) Kozuka, "Stream Control Transmission Protocol (SCTP)
skipping to change at page 29, line 17 skipping to change at page 29, line 49
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007. RFC 4960, September 2007.
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. [RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.
Kozuka, "Stream Control Transmission Protocol (SCTP) Kozuka, "Stream Control Transmission Protocol (SCTP)
Dynamic Address Reconfiguration", RFC 5061, Dynamic Address Reconfiguration", RFC 5061,
September 2007. September 2007.
[I-D.ietf-tsvwg-sctp-chunk-flags]
Tuexen, M. and R. Stewart, "Stream Control Transmission
Protocol (SCTP) Chunk Flags Registration",
draft-ietf-tsvwg-sctp-chunk-flags-01 (work in progress),
September 2010.
10.2. Informative References 10.2. Informative References
[I-D.ietf-tsvwg-sctpsocket] [I-D.ietf-tsvwg-sctpsocket]
Stewart, R., Poon, K., Tuexen, M., Yasevich, V., and P. Stewart, R., Poon, K., Tuexen, M., Yasevich, V., and P.
Lei, "Sockets API Extensions for Stream Control Lei, "Sockets API Extensions for Stream Control
Transmission Protocol (SCTP)", Transmission Protocol (SCTP)",
draft-ietf-tsvwg-sctpsocket-23 (work in progress), draft-ietf-tsvwg-sctpsocket-23 (work in progress),
July 2010. July 2010.
URIs
[1] <http://www.iana.org/assignments/sctp-parameters>
Authors' Addresses Authors' Addresses
Randall R. Stewart Randall R. Stewart
Huawei Huawei
Chapin, SC 29036 Chapin, SC 29036
USA USA
Phone: Phone:
Email: rstewart@huawei.com Email: rstewart@huawei.com
 End of changes. 119 change blocks. 
263 lines changed or deleted 280 lines changed or added

This html diff was produced by rfcdiff 1.39. The latest version is available from http://tools.ietf.org/tools/rfcdiff/