Skip to main content

Stream Control Transmission Protocol (SCTP) Stream Reconfiguration

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Randall R. Stewart , Peter Lei , Michael Tüxen
Last updated 2009-02-16
Replaced by RFC 6525
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tsvwg-sctp-strrst
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Many applications that desire to use SCTP have requested the ability to "reset" a stream. The intention of resetting a stream is to start the numbering sequence of the stream back at 'zero' with a corresponding notification to the upper layer that this act as been performed. The applications that have requested this feature normally desire it so that they can "re-use" streams for different purposes but still utilize the stream sequence number for the application to track the message flows. Thus, without this feature, a new use on an old stream would result in message numbers larger than expected without a protocol mechanism to "start the streams back at zero". This documents presents also a method for resetting the transport sequence numbers and all stream sequence numbers.


Randall R. Stewart
Peter Lei
Michael Tüxen

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)