draft-ietf-tsvwg-sctp-strrst-06.txt   draft-ietf-tsvwg-sctp-strrst-07.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: March 30, 2011 Cisco Systems, Inc. Expires: April 28, 2011 Cisco Systems, Inc.
M. Tuexen M. Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
September 26, 2010 October 25, 2010
Stream Control Transmission Protocol (SCTP) Stream Reconfiguration Stream Control Transmission Protocol (SCTP) Stream Reconfiguration
draft-ietf-tsvwg-sctp-strrst-06.txt draft-ietf-tsvwg-sctp-strrst-07.txt
Abstract Abstract
Many applications that use SCTP want the ability to "reset" a stream. Many applications that use SCTP want the ability to "reset" a stream.
The intention of resetting a stream is to set the numbering sequence The intention of resetting a stream is to set the numbering sequence
of the stream back to 'zero' with a corresponding notification to the of the stream back to 'zero' with a corresponding notification to the
upper layer that this has been performed. The applications that want upper layer that this has been performed. The applications that want
this feature want it so that they can "re-use" streams for different this feature want 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 so that the
application can track the message flows. Thus, without this feature, application can track the message flows. Thus, without this feature,
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 March 30, 2011. This Internet-Draft will expire on April 28, 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 39 skipping to change at page 2, line 39
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 . . . . . . . . . . . . . . . . . . 13 Request Parameter . . . . . . . . . . . . . . . . . . 13
5.1.3. Sender Side Procedures for the Incoming SSN Reset 5.1.3. Sender Side Procedures for the Incoming SSN Reset
Request Parameter . . . . . . . . . . . . . . . . . . 14 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 . . . . . . . . . . . . . . . . . . 15 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 . . . . . . . . . . . . . . 16
5.2. Receiver Side Procedures . . . . . . . . . . . . . . . . . 16 5.2. Receiver Side Procedures . . . . . . . . . . . . . . . . . 16
5.2.1. Receiver Side Procedures for the Stream Reset Chunk . 16 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 . . . . . . . . . . . . . . . . . . 18
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. Examples of the Stream Reset procedures . . . . . . . . . 19 6. Socket API Considerations . . . . . . . . . . . . . . . . . . 19
6. Socket API Considerations . . . . . . . . . . . . . . . . . . 20 6.1. Events . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1. Events . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.1.1. Stream Reset Event . . . . . . . . . . . . . . . . . . 20
6.1.1. Stream Reset Event . . . . . . . . . . . . . . . . . . 21 6.1.2. Association Reset Event . . . . . . . . . . . . . . . 21
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) . . . . . . . . . . . . . . 24
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) . . . . . . . . . . . . . . . . . 25
6.3.3. Reset SSN/TSN (SCTP_RESET_ASSOC) . . . . . . . . . . . 27 6.3.3. Reset SSN/TSN (SCTP_RESET_ASSOC) . . . . . . . . . . . 26
6.3.4. Add Outgoing Streams (SCTP_ADD_OUT_STREAMS) . . . . . 27 6.3.4. Add Outgoing Streams (SCTP_ADD_OUT_STREAMS) . . . . . 26
7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7. Security Considerations . . . . . . . . . . . . . . . . . . . 27
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
8.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 28 8.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 28
8.2. Five New Parameter Types . . . . . . . . . . . . . . . . . 29 8.2. Five New Parameter Types . . . . . . . . . . . . . . . . . 28
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Appendix A. Examples of the Stream Reset procedures . . . . . . . 29
10.1. Normative References . . . . . . . . . . . . . . . . . . . 29 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30
10.1. Normative References . . . . . . . . . . . . . . . . . . . 30
10.2. Informative References . . . . . . . . . . . . . . . . . . 30 10.2. Informative References . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction 1. Introduction
Many applications that use SCTP want the ability to "reset" a stream. Many applications that use SCTP want the ability to "reset" a stream.
The intention of resetting a stream is to start the numbering The intention of resetting a stream is to set the numbering sequence
sequence of the stream back to 'zero' with a corresponding of the stream back to 'zero' with a corresponding notification to the
notification to the upper layer that this has been performed. The upper layer that this has been performed. The applications that want
applications that want this feature want to "re-use" streams for this feature want to "re-use" streams for different purposes but
different purposes but still utilize the stream sequence number so still utilize the stream sequence number so that the application can
that the application can track the message flows. Thus, without this track the message flows. Thus, without this feature, a new use of an
feature, a new use of an old stream would result in message numbers old stream would result in message numbers greater than expected
greater than expected unless there is a protocol mechanism to "reset unless there is a protocol mechanism to "reset the streams back to
the streams back to zero". This document also includes methods for zero". This document also includes methods 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.
The socket API for SCTP defined in [I-D.ietf-tsvwg-sctpsocket]
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 socket API for TCP.
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
skipping to change at page 4, line 46 skipping to change at page 5, line 6
Table 1 Table 1
It should be noted that the format of the STREAM_RESET chunk requires It should be noted that the format of the STREAM_RESET chunk requires
the 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.
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
following format: following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x82 | Chunk Flags | Chunk Length | | Type = 0x82 | Chunk Flags | Chunk Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Reset Parameter | | Stream Reset Parameter |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Stream Reset Parameter (optional) | | Stream Reset Parameter (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Chunk Type: 1 byte (unsigned integer) Chunk Type: 1 byte (unsigned integer)
This field holds the IANA defined chunk type for the STREAM RESET This field holds the IANA defined chunk type for the STREAM RESET
chunk. chunk. The suggested value of this field for IANA is 0x82.
Chunk Flags: 1 byte (unsigned integer) Chunk Flags: 1 byte (unsigned integer)
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 in bytes, including the
Type, Chunk Flags and Chunk Length. Chunk 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 that each STREAM RESET chunk holds at least one parameter and at Note that each STREAM RESET chunk holds at least one parameter and at
most 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.
skipping to change at page 6, line 35 skipping to change at page 6, line 40
Table 2 Table 2
It should be noted that the parameter format requires the receiver to It should be noted that the parameter format requires the receiver to
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.
4.1. Outgoing SSN Reset Request Parameter 4.1. Outgoing SSN Reset Request Parameter
This parameter is used by the sender to request the reset of some or This parameter is used by the sender to request the reset of some or
all outgoing streams. 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 = 16 + 2 * N | | 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 | | Sender's 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
skipping to change at page 7, line 46 skipping to change at page 7, line 46
Stream Reset Request parameter. Stream Reset Request parameter.
Stream Reset Response Sequence Number: 4 bytes (unsigned integer) Stream Reset Response Sequence Number: 4 bytes (unsigned integer)
When this Outgoing SSN Reset Request Parameter is sent in response When this Outgoing SSN Reset Request Parameter is sent in response
to an Incoming SSN Reset Request Parameter this parameter is also to an Incoming SSN Reset Request Parameter this parameter is also
an implicit response to the incoming request. Then this field an implicit response to the incoming request. Then this field
holds the Stream Reset Request Sequence Number of the incoming holds the Stream Reset Request Sequence Number of the incoming
request. In other cases it holds the next expected Stream Reset request. In other cases it holds the next expected Stream Reset
Request Sequence Number minus 1. Request Sequence Number minus 1.
Senders last assigned TSN: 4 bytes (unsigned integer) Sender's 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 1..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 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.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 resets This parameter is used by the sender to request that the peer resets
some or all of its outgoing streams. some or all of its outgoing streams.
skipping to change at page 10, line 41 skipping to change at page 10, line 41
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
+--------+-------------------------------------+ +--------+-------------------------------------+
| Result | Description | | Result | Description |
+--------+-------------------------------------+ +--------+-------------------------------------+
| 0 | Nothing to do | | 0 | Success - Nothing to do |
| 1 | Performed | | 1 | Success - 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 |
| 6 | In progress |
+--------+-------------------------------------+ +--------+-------------------------------------+
Table 3 Table 3
Sender's next TSN: 4 bytes (unsigned integer) Sender's next TSN: 4 bytes (unsigned integer)
This field holds the TSN the sender of the Response will use to This field holds the TSN the sender of the Response will use to
send the next DATA chunk. The field is only applicable in send the next DATA chunk. The field is only applicable in
responses to SSN/TSN reset requests. responses to SSN/TSN reset requests.
Receiver's next TSN: 4 bytes (unsigned integer) Receiver's next TSN: 4 bytes (unsigned integer)
This field holds the TSN the receiver of the response must use to This field holds the TSN the receiver of the response must use to
send the next DATA chunk. The field is only applicable in send the next DATA chunk. The field is only applicable in
responses to SSN/TSN reset requests. responses to SSN/TSN reset requests.
Either both optional fields (Sender's next TSN and Receiver's next
TSN) MUST be present or none.
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 that an additional This parameter is used by the sender to request that an additional
number of outgoing streams (i.e. the receiver's incoming streams) be number of outgoing streams (i.e. the receiver's incoming streams) be
added to the association. added to the association.
0 1 2 3 0 1 2 3
skipping to change at page 12, line 23 skipping to change at page 12, line 28
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 composed of a Type Stream Reset Chunks. A Stream Reset Chunk is composed of one or two
Length Value (TLV) parameters. Type 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 for 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' if 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
skipping to change at page 13, line 12 skipping to change at page 13, line 16
the sender MUST retransmit the Stream Reset Chunk, increment the the sender MUST retransmit the Stream Reset Chunk, increment the
appropriate error counts (both for the association and the appropriate error counts (both for the association and the
destination), and perform threshold management possibly destroying destination), and perform threshold management possibly destroying
the association if SCTP retransmission thresholds are exceeded. 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 provided streams it can send an Outgoing SSN Reset Request Parameter provided
that the Stream Reset Timer is not running. The following steps MUST that the Stream Reset Timer is not running. The following steps must
be 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 not known provided by the upper layer for the affected streams and queue
whether the receiver of the request will accept or deny it and it. This is because it is not known whether the receiver of the
moreover, a lost request might cause an out-of-sequence error in request will accept or deny it and moreover, a lost request
a stream that the receiver is not yet prepared to handle. might cause an out-of-sequence error in 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 MUST put it into the Stream Reset Request Sequence
field of the Outgoing SSN Reset Request Parameter. The next Number field of the Outgoing SSN Reset Request Parameter. The
stream reset request sequence number MUST then be incremented by next stream reset request sequence number MUST then be
1. incremented by 1.
A3: The sender fills in the TSN it last assigned. A3: The Sender's Last Assigned TSN MUST be set to the next TSN the
sender assigns minus 1.
A4: 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 Reset Request Parameter the Stream Numbers to an Incoming SSN Reset Request Parameter the Stream Numbers
are copied from the Incoming SSN Reset Request Parameter to the MUST be copied from the Incoming SSN Reset Request Parameter to
Outgoing SSN Reset Request Parameter. The Stream Reset Response the Outgoing SSN Reset Request Parameter. The Stream Reset
Sequence Number of the Outgoing SSN Reset Request Parameter is Response Sequence Number of the Outgoing SSN Reset Request
the Stream Reset Request Sequence Number of the Incoming SSN Parameter MUST be the Stream Reset Request Sequence Number of
Reset Request Parameter. If this Outgoing SSN Reset Request the Incoming SSN Reset Request Parameter. If this Outgoing SSN
Parameter is sent at the request of the upper layer and the Reset Request Parameter is sent at the request of the upper
sender requests all outgoing streams to be reset no Stream layer and the sender requests all outgoing streams to be reset
Numbers MUST be put into the Outgoing SSN Reset Request Stream Numbers SHOULD NOT be put into the Outgoing SSN Reset
Parameter. If the sender requests only some outgoing streams to Request Parameter. If the sender requests only some outgoing
be reset these Stream Numbers MUST be placed in the Outgoing SSN streams to be reset these Stream Numbers MUST be placed in the
Reset Request Parameter. Stream Reset Response Sequence Number Outgoing SSN Reset Request Parameter. Stream Reset Response
is the next expected Stream Reset Request Sequence Number of the Sequence Number is the next expected Stream Reset Request
peer minus 1. Sequence Number of the peer minus 1.
A5: The Outgoing SSN Reset Request Parameter is put into a STREAM A5: The Outgoing SSN Reset Request Parameter MUST be put into a
RESET Chunk. It MAY be put together with either an Incoming SSN STREAM RESET Chunk. The Outgoing SSN Reset Request Parameter
Reset Request Parameter or an Stream Reset Response Parameter MAY be put together with either an Incoming SSN Reset Request
but not both, and MUST NOT be put together with any other Parameter or an Stream Reset Response Parameter but not both.
parameter. It MUST NOT be put together with any other parameter as
described in Section 3.1.
A6: The STREAM RESET Chunk is sent following the rules given in A6: The STREAM RESET Chunk MUST be 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 provided streams it can send an Incoming SSN Reset Request Parameter provided
that the Stream Reset Timer is not running. The following steps MUST that the Stream Reset Timer is not running. The following steps must
be 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 MUST put it into the Stream Reset Request Sequence
field of the Incoming SSN Reset Request Parameter. After Number 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 SHOULD 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 MUST be put into a
RESET Chunk. It MAY be put together with an Outgoing SSN Reset STREAM RESET Chunk. It MAY be put together with an Outgoing SSN
Request Parameter but MUST NOT be put together with any other Reset Request Parameter but MUST NOT be put together with any
parameter. other parameter.
B4: The STREAM RESET Chunk is sent following the rules given in B4: The STREAM RESET Chunk MUST be 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 an
SSN/TSN Reset Request Parameter provided that the Stream Reset Timer SSN/TSN Reset Request Parameter provided that the Stream Reset Timer
is not 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 MUST be put into a STREAM
Chunk. There MUST NOT be any other parameter in this chunk. RESET 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 MUST be sent following the rules given in
Section 5.1.1. Section 5.1.1.
Only one SSN/TSN Reset Request SHOULD be sent within a maximum Only one SSN/TSN Reset Request SHOULD be sent within 30 seconds,
segment lifetime, the IP MSL. which is considered a maximum 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 reset request parameter it MUST When an implementation receives a reset request parameter it must
respond with a Stream Reset Response Parameter in the following respond with a Stream Reset Response Parameter in the following
manner: 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 MUST be copied to the Stream Reset Response Sequence Number
the Stream Reset Response Parameter. field of the Stream Reset Response Parameter.
D2: The result of the processing of the incoming request is placed D2: The result of the processing of the incoming request according
in the Result field of the Stream Reset Response Parameter. to Table 3 MUST be placed in the Result field of the Stream
Reset Response Parameter.
D3: If the incoming request is a SSN/TSN reset request, the Sender's D3: If the incoming request is an SSN/TSN reset request, the
next TSN field is filled with the next TSN the sender of this Sender's next TSN field MUST be filled with the next TSN the
Stream Reset Response Parameter will assign. For other requests sender of this Stream Reset Response Parameter will assign. For
the Sender's next TSN field is not filled in. other requests the Sender's next TSN field, which is optional,
MUST NOT be used.
D4: If the incoming request is a SSN/TSN reset request, the D4: If the incoming request is an SSN/TSN reset request, the
Receiver's next TSN field is filled with a TSN such that the Receiver's next TSN field MUST be filled with a TSN such that
sender of the Stream Reset Response Parameter can be sure it can the sender of the Stream Reset Response Parameter can be sure it
discard received DATA chunks with smaller TSNs. The value can discard received DATA chunks with smaller TSNs. 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. For other requests the Receiver's next the request plus 2^31. For other requests the Receiver's next
TSN field is not filled in. TSN field, which is optional, MUST NOT be used.
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
to which it is able to send, it may add an Add Outgoing Streams to which it is able to send, it may add an Add Outgoing Streams
Request parameter to the STREAM RESET chunk. Upon sending the Request parameter to the STREAM RESET chunk. Upon sending the
request the sender MUST await a positive acknowledgment (Success) request the sender MUST await a positive acknowledgment (Success)
before using any additional stream added by this request. Note that before using any additional stream added by this request. Note that
new streams are added adjacent to the previous streams with no gaps. 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 This means that if a request is made to add 2 streams to an
association that has already 5 (0-4) then the new streams, upon association that has already 5 (0-4) then the new streams, upon
successful completion, are streams 5 and 6. A new stream MUST use successful completion, are streams 5 and 6. A new stream MUST use
for its first ordered message the stream sequence number 0. the stream sequence number 0 for its first ordered message.
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 multiple parameters have to be returned, SHOULD be processed. If multiple parameters have to be returned,
they MUST 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.
skipping to change at page 16, line 37 skipping to change at page 16, line 51
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 MUST be followed: the following steps must be followed:
E1: If the Senders Last Assigned TSN number is greater than the E1: If the Stream Reset Timer is running for the Stream Reset
Request Sequence Number indicated in the Stream Reset Response
Sequence Number field, the Stream Reset Request Sequence Number
MUST be marked as acknowledged. If all Stream Reset Request
Sequence Numbers the Stream Reset Timer is running for are
acknowledged, the Stream Reset Timer MUST be stopped.
E2: If the Sender's 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 affected 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. If the endpoint enters "deferred reset processing", it
to entered deferred reset processing does not withhold the MUST put a Stream Reset Response Parameter into a STREAM RESET
stream reset acknowledgment from the peer. This also means that chunk indicating 'In progress' and MUST send the STREAM RESET
the receiver will need to queue up any additional stream reset chunk.
requests received including the one that caused the receiver to
enter deferred reset processing. This is because once the
acknowledgement is received by the sender, the sender is free to
send a new stream reset.
E2: If the Stream Reset Timer is running for the Stream Reset
Request Sequence Number indicated in the Stream Reset Response
Sequence Number field, the Stream Reset Request Sequence Number
MUST be marked as acknowledged. If all Stream Reset Request
Sequence Numbers the Stream Reset Timer is running for are
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 stream incoming streams MUST be reset to 0 as the next expected stream
sequence number. If specific Stream Numbers are listed, then sequence number. If specific Stream Numbers are listed, then
only these specific streams MUST be reset to 0 and all other only these specific streams MUST be reset to 0 and all 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: Any queued TSN's (queued at step E1) MUST now be released and
the local endpoint that the inbound streams have been reset.
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 E5: A Stream Reset Response Parameter MUST be put into a STREAM
chunk indicating successful processing. RESET chunk indicating successful processing.
E7: The STREAM RESET chunk is sent after the incoming STREAM RESET E6: The STREAM RESET chunk MUST be sent after the incoming STREAM
chunk is processed completely. RESET 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 MUST be followed: the following steps must be followed:
F1: An Outgoing Stream Reset Request Parameter MUST be put into an F1: An Outgoing SSN 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 MUST be sent after the incoming STREAM
chunk is processed completely. RESET 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 an SSN/TSN reset
the following steps MUST 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 endpoint's 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 chunk 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: The same processing as if a SACK chunk with no gap report and a
a cumulative TSN ACK of Sender's next TSN minus 1 was received. cumulative TSN ACK of Sender's next TSN minus 1 was received
MUST be performed.
G4: Do the same processing as if an FWD-TSN chunk with all streams G4: The same processing as if a FWD-TSN chunk as defined in
affected and a new cumulative TSN ACK of Receiver's next TSN [RFC3758] with all streams affected and a new cumulative TSN ACK
minus 1 was received. of Receiver's next TSN minus 1 was received MUST be performed.
G5: The next expected and outgoing stream sequence numbers MUST be G5: The next expected and outgoing stream sequence numbers MUST be
reset to 0 for all incoming and outgoing streams. reset to 0 for all incoming and outgoing streams.
G6: A Stream Reset Response Parameter is put into a STREAM RESET G6: A Stream Reset Response Parameter MUST be put into a STREAM
chunk indicating successful processing. RESET chunk indicating successful processing.
G7: The STREAM RESET chunk is sent after the incoming STREAM RESET G7: The STREAM RESET chunk MUST be sent after the incoming STREAM
chunk is processed completely. RESET 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 denying the request. If the response is successful acknowledging or denying the request. If the response is successful
the receiver MUST add the requested number of inbound streams to the the receiver MUST add the requested number of inbound streams to the
association, initializing the next expected stream sequence number to association, initializing the next expected stream 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, 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. If the timer was not running for acknowledged, the Stream Reset Timer MUST be stopped. If the
the Stream Reset Request Sequence Number, the processing of the timer was not running for the Stream Reset Request Sequence
Stream Reset Response Parameter is complete. Number, the processing of the Stream Reset Response Parameter is
complete.
H2: If the Result field does not indicate successful processing an H2: If the Result field indicates 'In progress', the timer for the
Upper Layer Notification should be sent to inform the local Stream Reset Request Sequence Number is started again. If the
endpoint of the failure to reset its outbound streams. timer runs off, the Stream Reset Chunk MUST be retransmitted but
Afterwards processing of this response is complete. the corresponding error counters MUST NOT be incremented.
H3: If the request was an Outgoing Stream Reset Request the affected H3: If the Result field does not indicate successful processing the
streams should now be reset and all queued data should be processing of this response is complete.
H4: If the request was an Outgoing SSN Reset Request the affected
streams MUST 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.
sent to inform the local endpoint that the outbound streams have
been reset.
H4: If the request was a SSN/TSN Reset Request new DATA should be H5: If the request was an SSN/TSN Reset Request new data MUST 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 MUST be
also reset to 0 as the next expected stream sequence number. reset to 0 as the next expected stream sequence number. The
The peer will send DATA chunks starting with Sender's next TSN. peer will send DATA chunks starting with Sender's next TSN.
H5: If the request was to add outgoing streams and the result was
successful, the endpoint should 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.
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
and 2 for just its outgoing streams.
E-A E-Z
----------[STR_RESET(OUT-REQ:X/1,2)]---------->
<-------------[STR_RESET(RESP:X)]--------------
The following example illustrates an Endpoint A resetting stream 1
and 2 for just its incoming streams.
E-A E-Z
-----------[STR_RESET(IN-REQ:X/1,2)]---------->
<--------[STR_RESET(OUT-REQ:Y,X/1,2)]----------
-------------[STR_RESET(RESP:Y)]-------------->
The following example illustrates an Endpoint A resetting all streams
in both directions.
E-A E-Z
-----[STR_RESET(OUT-REQ:X,Y-1)|IN-REQ:X+1]---->
<------[STR_RESET(RESP:X|OUT-REQ:Y,X+1)]-------
-------------[STR_RESET(RESP:Y)]-------------->
The following example illustrates an Endpoint A requesting the
streams and TSN's be reset. At the 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).
E-A E-Z
------------[STR_RESET(TSN-REQ:X)]------------>
<-----[STR_RESET(RESP:X/S-TSN=A, R-TSN=B)]-----
The following example illustrates an Endpoint A requesting to add 3
additional outgoing streams.
E-A E-Z H6: If the request was to add outgoing streams, the endpoint MUST
--------[STR_RESET(ADD_OUT_STRMS:X/3)]--------> add the additional streams to the association. Note that an
<-------------[STR_RESET(RESP:X)]-------------- 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.
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] needs to 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. Please note that this section is informational only.
6.1. Events 6.1. Events
When the SCTP_ASSOC_CHANGE notification is delivered and both peers
support the extension described in this document,
SCTP_ASSOC_SUPPORTS_STREAM_RESET should be listed in the sac_info
field.
The union sctp_notification {} is extended to contain 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 45 skipping to change at page 21, line 4
The event delivered has the following structure: The event delivered has the following structure:
struct sctp_stream_reset_event { struct sctp_stream_reset_event {
uint16_t strreset_type; uint16_t strreset_type;
uint16_t strreset_flags; uint16_t strreset_flags;
uint32_t strreset_length; uint32_t strreset_length;
sctp_assoc_t strreset_assoc_id; sctp_assoc_t strreset_assoc_id;
uint16_t strreset_stream_list[]; uint16_t strreset_stream_list[];
}; };
strreset_type: It should be SCTP_STREAM_RESET_EVENT. strreset_type: It should be SCTP_STREAM_RESET_EVENT.
strreset_flags: This field is formed from the bitwise OR of one or strreset_flags: This field is formed from the bitwise OR of one or
more of the following currently defined flags: more of the following currently defined flags:
SCTP_STREAM_RESET_INCOMING_SSN: The streams identifiers given in SCTP_STREAM_RESET_INCOMING_SSN: The stream identifiers given in
strreset_stream_list[] refers to incoming streams of the strreset_stream_list[] refer to incoming streams of the
endpoint. endpoint.
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[] refer 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 is set. SCTP_STREAM_RESET_DENIED SCTP_STREAM_RESET_OUTGOING_SSN is set. SCTP_STREAM_RESET_DENIED
and SCTP_STREAM_RESET_FAILED are mutually exclusive. If the and SCTP_STREAM_RESET_FAILED are mutually exclusive. If the
request 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 in bytes of the
event, including the header. delivered 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. sockets, this field is ignored.
strreset_stream_list: The list of stream identifiers this event strreset_stream_list: The list of stream identifiers this event
refers to. An empty list identifies all streams as being reset. refers to. An empty list identifies all streams as being reset.
Depending on strreset_flags the identifiers refer to incoming or Depending on strreset_flags the identifiers refer to incoming or
outgoing streams or both. outgoing streams or both.
6.1.2. Association Reset Event 6.1.2. Association Reset Event
The event delivered has the following structure: The event delivered has the following structure:
skipping to change at page 23, line 18 skipping to change at page 22, line 18
SCTP_ASSOC_RESET_DENIED: The corresponding outgoing request was SCTP_ASSOC_RESET_DENIED: The corresponding outgoing request was
denied by the peer. denied by the peer.
SCTP_ASSOC_RESET_FAILED: The corresponding outgoing request SCTP_ASSOC_RESET_FAILED: The corresponding outgoing request
failed. failed.
SCTP_ASSOC_RESET_DENIED and SCTP_ASSOC_RESET_FAILED are mutual SCTP_ASSOC_RESET_DENIED and SCTP_ASSOC_RESET_FAILED are mutual
exclusive. If the request was successful, none of these are set. exclusive. If the request was successful, none of these are set.
assocreset_length: This field is the total length of the delivered assocreset_length: This field is the total length in bytes of the
event, including the header. delivered event, including the header.
assocreset_assoc_id: The association id field, holds the identifier assocreset_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. sockets, this field is ignored.
assocreset_local_tsn: The next TSN used by the endpoint. assocreset_local_tsn: The next TSN used by the endpoint.
assocreset_remote_tsn: The next TSN used by the peer. assocreset_remote_tsn: The next TSN used by the peer.
6.1.3. Stream Change Event 6.1.3. Stream Change Event
The event delivered has the following structure: The event delivered has the following structure:
struct sctp_stream_change_event { struct sctp_stream_change_event {
skipping to change at page 24, line 10 skipping to change at page 23, line 10
more of the following currently defined flags: more of the following currently defined flags:
SCTP_STREAM_CHANGE_DENIED: The corresponding request was denied SCTP_STREAM_CHANGE_DENIED: The corresponding request was denied
by the peer. by the peer.
SCTP_STREAM_CHANGE_FAILED: The corresponding request failed. SCTP_STREAM_CHANGE_FAILED: The corresponding request failed.
SCTP_STREAM_CHANGE_DENIED and SCTP_STREAM_CHANGE_FAILED are mutual SCTP_STREAM_CHANGE_DENIED and SCTP_STREAM_CHANGE_FAILED are mutual
exclusive. If the request was successful, none of these are set. exclusive. If the request was successful, none of these are set.
strchange_length: This field is the total length of the delivered strchange_length: This field is the total length in bytes of the
event, including the header. delivered event, including the header.
strchange_assoc_id: The association id field, holds the identifier strchange_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. sockets, this field is ignored.
strchange_instrms: The number of streams that the peer is allowed to strchange_instrms: The number of streams that the peer is allowed to
use outbound. use outbound.
strchange_outstrms: The number of streams that the endpoint is strchange_outstrms: The number of streams that the endpoint is
allowed to use outbound. allowed to use outbound.
6.2. Event Subscription 6.2. Event Subscription
There are two methods defined in the SCTP socket API to subscribe to There are two methods defined in the SCTP socket API to subscribe to
events. The original method defined was an events structure with the events. The original method defined was an events structure with the
socket option SCTP_EVENTS. Some implementations may have already socket option SCTP_EVENTS. Some implementations may have already
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() call with
SCTP_SET_EVENT socket option. This option takes a structure that the 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 an on/off boolean. This newer API is
preferred method but we define both methods for compatibility. the 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;
skipping to change at page 27, line 8 skipping to change at page 26, line 8
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[];
}; };
srs_assoc_id: This parameter is ignored for one-to-one style srs_assoc_id: This parameter is ignored for one-to-one style
sockets. For one-to-many style sockets this parameter indicates sockets. For one-to-many style sockets this parameter indicates
which association the user is performing an action upon. which association the user is performing an action upon.
srs_flags: This parameter describes which class of streams are srs_flags: This parameter describes which class of streams is reset.
reset. It is formed from the bitwise OR of one or more of the It is formed from the bitwise OR of one or more of the following
following currently defined flags: currently defined flags:
* SCTP_STREAM_RESET_INCOMING * SCTP_STREAM_RESET_INCOMING
* SCTP_STREAM_RESET_OUTGOING * SCTP_STREAM_RESET_OUTGOING
srs_number_streams: This parameter is the number of elements in the 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 srs_stream_list. If it is zero, the operation is performed on all
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 the operation is performed upon. 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 of 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 the action is to be performed upon.
6.3.4. Add Outgoing Streams (SCTP_ADD_OUT_STREAMS) 6.3.4. Add Outgoing Streams (SCTP_ADD_OUT_STREAMS)
This option allows a user to request the addition a number of This option allows a user to request the addition of a number of
outgoing streams. outgoing streams.
To set this option the user fills in the following structure: To set 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
association the user is performing an action upon. association the user is performing an action upon.
assoc_value: This parameter is the number of outgoing streams to assoc_value: This parameter is the number of outgoing streams to
add. add.
An endpoint can limit the number of incoming streams by using the An endpoint can limit the number of incoming streams by using the
sinit_max_instreams field in the struct sctp_initmsg{} when issuing sinit_max_instreams field in the struct sctp_initmsg{} when issuing
an SCTP_INIT socket option, as defined in an SCTP_INIT socket option, as defined in
[I-D.ietf-tsvwg-sctpsocket]. An incoming request asking for more [I-D.ietf-tsvwg-sctpsocket]. An incoming request asking for more
streams than allow will be denied. streams than allowed will be denied.
7. Security Considerations 7. Security Considerations
Having the ability to reset a stream should not pose any additional The SCTP socket API as described in [I-D.ietf-tsvwg-sctpsocket]
security risk to SCTP. An attacker that can successfully inject a exposes the sequence numbers of received DATA chunks to the
stream reset would also be able to inject data or other malicious application. An application might expect them to be monotonically
information into an association such as an ABORT. increasing. When using the stream reset extension this might no
longer be true. Therefore the application must enable this extension
explicitly before it is used. In addition, application must
subscribe explicitly to notifications related to the stream reset
extension before receiving them.
SCTP associations are protected against blind attackers by using the
verification tags. This is still valid when using the stream reset
extension. Therefore this extension does not add any additional
security risk to SCTP in relation to blind attackers.
When the both sequence numbers are reset, the maximum segment
lifetime is used to avoid the wrap-around for the TSN.
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 [NOTE to RFC-Editor:
The suggested values for the chunk type and the chunk parameter
types are tentative and to be confirmed by IANA.
]
This document (RFCXXXX) is the reference for all registrations
described in this section. The suggested changes are described described in this section. The suggested changes are described
below. 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. IANA shoal assign this value from the pool values given in Table 1. IANA should assign this value from the pool
of chunks 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 for SCTP: This requires an additional line in the "CHUNK TYPES" table for SCTP:
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 The registration table as defined in
[I-D.ietf-tsvwg-sctp-chunk-flags] for the chunk flags of this chunk [I-D.ietf-tsvwg-sctp-chunk-flags] for the chunk flags of this chunk
type is empty. 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 IANA is requested to create a new sub-registry, "STREAM RESET Chunk
use the values given in Table 2. IANA shoal assign this value from Parameter Types" with the following initial contents, taken from
the pool of parameters with the upper two bits set to '00'. Table 2 of this document:
This requires an additional table in the "CHUNK PARAMETER TYPES"
tables for SCTP: An Entry for "STREAM RESET Chunk Parameter Types"
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, Gorry Fairhurst, Tom Pelch, The authors wish to thank Paul Aitken, Gorry Fairhurst, Tom Pelch,
Kacheong Poon, Irene Ruengeler, Robin Seggelmann, and Vlad Yasevich Kacheong Poon, Irene Ruengeler, Robin Seggelmann, and Vlad Yasevich
for there invaluable comments. for there invaluable comments.
Appendix A. Examples of the Stream Reset procedures
Please note that this appendix is informational only.
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
and 2 for just its outgoing streams.
E-A E-Z
----------[STR_RESET(OUT-REQ:X/1,2)]---------->
<-------------[STR_RESET(RESP:X)]--------------
The following example illustrates an Endpoint A resetting stream 1
and 2 for just its incoming streams.
E-A E-Z
-----------[STR_RESET(IN-REQ:X/1,2)]---------->
<--------[STR_RESET(OUT-REQ:Y,X/1,2)]----------
-------------[STR_RESET(RESP:Y)]-------------->
The following example illustrates an Endpoint A resetting all streams
in both directions.
E-A E-Z
-----[STR_RESET(OUT-REQ:X,Y-1)|IN-REQ:X+1]---->
<------[STR_RESET(RESP:X|OUT-REQ:Y,X+1)]-------
-------------[STR_RESET(RESP:Y)]-------------->
The following example illustrates an Endpoint A requesting the
streams and TSNs be reset. At the 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).
E-A E-Z
------------[STR_RESET(TSN-REQ:X)]------------>
<-----[STR_RESET(RESP:X/S-TSN=A, R-TSN=B)]-----
The following example illustrates an Endpoint A requesting to add 3
additional outgoing streams.
E-A E-Z
--------[STR_RESET(ADD_OUT_STRMS:X/3)]-------->
<-------------[STR_RESET(RESP:X)]--------------
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.
[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.
Conrad, "Stream Control Transmission Protocol (SCTP)
Partial Reliability Extension", RFC 3758, May 2004.
[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] [I-D.ietf-tsvwg-sctp-chunk-flags]
Tuexen, M. and R. Stewart, "Stream Control Transmission Tuexen, M. and R. Stewart, "Stream Control Transmission
Protocol (SCTP) Chunk Flags Registration", Protocol (SCTP) Chunk Flags Registration",
draft-ietf-tsvwg-sctp-chunk-flags-01 (work in progress), draft-ietf-tsvwg-sctp-chunk-flags-02 (work in progress),
September 2010. October 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.
Authors' Addresses Authors' Addresses
Randall R. Stewart Randall R. Stewart
Huawei Huawei
Chapin, SC 29036 Chapin, SC 29036
USA USA
Phone:
Email: rstewart@huawei.com Email: rstewart@huawei.com
Peter Lei Peter Lei
Cisco Systems, Inc. Cisco Systems, Inc.
8735 West Higgins Road 8735 West Higgins Road
Suite 300 Suite 300
Chicago, IL 60631 Chicago, IL 60631
USA USA
Phone:
Email: peterlei@cisco.com Email: peterlei@cisco.com
Michael Tuexen Michael Tuexen
Muenster University of Applied Sciences Muenster University of Applied Sciences
Stegerwaldstr. 39 Stegerwaldstr. 39
48565 Steinfurt 48565 Steinfurt
Germany Germany
Email: tuexen@fh-muenster.de Email: tuexen@fh-muenster.de
 End of changes. 99 change blocks. 
265 lines changed or deleted 300 lines changed or added

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