Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Stream Control Transmission Protocol (SCTP) Stream Reconfiguration (RFC6525)

IP.com Disclosure Number: IPCOM000215474D
Original Publication Date: 2012-Feb-01
Included in the Prior Art Database: 2012-Mar-01
Document File: 68 page(s) / 73K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Stewart: AUTHOR [+3]

Abstract

Many applications that use SCTP as defined in [RFC4960] want the ability to "reset" a stream. The intention of resetting a stream is to set the Stream Sequence Numbers (SSNs) of the stream back to 'zero' with a corresponding notification to the application layer that the reset has been performed. Applications requiring this feature want to "reuse" streams for different purposes but still utilize the SSN so that the application can track the message flows. Thus, without this feature, a new use of an old stream would result

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Internet Engineering Task Force (IETF)                        R. Stewart Request for Comments: 6525                                Adara Networks Category: Standards Track                                      M. Tuexen ISSN: 2070-1721                         Muenster Univ. of Appl. Sciences                                                                   P. Lei                                                      Cisco Systems, Inc.                                                            February 2012

    Stream Control Transmission Protocol (SCTP) Stream Reconfiguration

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6525.

Stewart, et al.              Standards Track                    [Page 1]
 RFC 6525               SCTP Stream Reconfiguration         February 2012

 Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review thes...