This section includes documents that are common to the Signalling User
Adaptation Layers. Some are only applicable to SS7, some are not.
|
draft-ietf-sigtran-sctp-mib |
-10.txt
-09.txt
-08.txt
-07.txt
-06.txt
-05.txt
-04.txt
-03.txt
-02.txt
-01.txt
-00.txt
|
The Stream Control Transmission Protocol (SCTP) is a reliable
transport protocol operating on top of a connectionless packet network
such as IP. It is designed to transport PSTN signaling messages over
the connectionless packet network, but is capable of broader
applications.
This memo defines the Management Information Base (MIB) module which
describes the minimum set of objects needed to manage the
implementation of the SCTP.
|
|
|
draft-stewart-tsvwg-prsctp |
-00.txt
-05.txt
-04.txt
-03.txt
-02.txt
-01.txt
-00.txt
|
This memo describes an extension to the Stream Control Transmission
Protocol (SCTP) RFC2960 [5] that allows an SCTP endpoint to signal to
its peer that it should move the cumulative ack point forward. When
both sides of an SCTP association support this extension, it can be
used by an SCTP implementation to provide partially reliable data
transmission service to an upper layer protocol. This memo describes
(1) the protocol extensions, which consist of a new parameter for INIT
and INIT ACK, and a new FORWARD TSN chunk type (2) one example
partially reliable service that can be provided to the upper layer via
this mechanism.
|
|
draft-ietf-tsvwg-addip-sctp |
-07.txt
-06.txt
-05.txt
-04.txt
-03.txt
-02.txt
-01.txt
-00.txt
|
This document describes extensions to the Stream Control Transmission
Protocol (SCTP) [RFC2960] that provides a method to reconfigure IP
address information on an existing association.
|
|
draft-ietf-tsvwg-sctpimpguide |
-08.txt
-07.txt
-06.txt
-05.txt
-04.txt
-03.txt
-02.txt
-01.txt
-00.txt
|
This document contains a compilation of all defects found up until the
publishing of this document for the Stream Control Transmission
Protocol (SCTP) RFC2960 [5]. These defects may be of an editorial or
technical nature. This document may be thought of as a companion
document to be used in the implementation of SCTP to clarify errors in
the original SCTP document.
This document updates RFC2960 [5] and text within this document
supersedes the text found in RFC2960 [5].
|
|
rfc3309 |
.txt
|
Stream Control Transmission Protocol (SCTP) Checksum Change
Stream Control Transmission Protocol (SCTP) currently uses an Alder-32
checksum. For small packets Adler-32 provides weak detection of
errors. This document changes that checksum and updates SCTP to use a
32 bit CRC checksum.
|
|
rfc2960 |
.txt
|
Stream Control Transmission Protocol (SCTP)
This document describes the Stream Control Transmission Protocol
(SCTP). SCTP is designed to transport PSTN signaling messages over IP
networks, but is capable of broader applications.
SCTP is a reliable transport protocol operating on top of a
connectionless packet network such as IP. It offers the following
services to its users: acknowledged error-free non-duplicated transfer
of user data, data fragmentation to conform to discovered path MTU
size, sequenced delivery of user messages within multiple streams,
with an option for order-of-arrival delivery of individual user
messages, optional bundling of multiple user messages into a single
SCTP packet, and network-level fault tolerance through supporting of
multi-homing at either or both ends of an association.
The design of SCTP includes appropriate congestion avoidance behavior
and resistance to flooding and masquerade attacks.
|
|