Stream Control Transmission Protocol Stream Reconfiguration
RFC 6525, “Stream Control Transmission Protocol Stream Reconfiguration”, is a Proposed Standard document published in March 2012 by R. Stewart, M. Tuexen, P. Lei. The canonical text is published by the RFC Editor.
Abstract
Many applications that use the Stream Control Transmission Protocol (SCTP) want the ability to "reset" a stream. The intention of resetting a stream is to set the numbering sequence of the stream back to 'zero' with a corresponding notification to the application layer that the reset has been performed. Applications requiring this feature want it so that they can "reuse" streams for different purposes but still utilize the stream sequence number so that the application can track the message flows. Thus, without this feature, a new use of an old stream would result in message numbers greater than expected, unless there is a protocol mechanism to "reset the streams back to zero". This document also includes methods for resetting the transmission sequence numbers, adding additional streams, and resetting all stream sequence numbers. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6525 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6526 IP Flow Information Export Per Stream Control Transmission Protocol Stream
- RFC 6527 Definitions of Managed Objects for Virtual Router Redundancy Protocol Version 3
- RFC 6522 The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages
- RFC 6528 Defending against Sequence Number Attacks
- RFC 6521 Home Agent-Assisted Route Optimization between Mobile IPv4 Networks
- RFC 6529 Host/Host Protocol for the ARPA Network
- RFC 6520 Transport Layer Security and Datagram Transport Layer Security Heartbeat Extension
- RFC 6530 Overview and Framework for Internationalized Email