This section includes documents that are common to the Signalling User
Adaptation Layers. Some are only applicable to SS7, some are not.
|
rfc4960 |
.txt
|
Stream Control Transmission Protocol (SCTP)
This document obsoletes RFC 2960 and RFC 3309. It 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.
|
|
rfc3873 |
.txt
|
Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)
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 public switched telephone network (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-ietf-sigtran-sctp-mib |
11.txt 10.txt 09.txt 08.txt 07.txt 06.txt 05.txt 04.txt 03.txt 02.txt 01.txt 00.txt
|
Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)
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.
|
|
|
rfc3758 |
.txt
|
Stream Control Transmission Protocol (SCTP) Partial Reliability Extension
This memo describes an extension to the Stream Control Transmission Protocol (SCTP) 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 the protocol extensions, which consist
of a new parameter for INIT and INIT ACK, and a new FORWARD TSN chunk type, and provides
one example of a partially reliable service that can be provided to the upper layer via
this mechanism.
|
|
draft-ietf-tsvwg-prsctp |
04.txt 03.txt 02.txt 01.txt 00.txt
|
Stream Control Transmission Protocol (SCTP) Partial Reliability Extension
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-stewart-tsvwg-prsctp |
05.txt 04.txt 03.txt 02.txt 01.txt 00.txt
|
Stream Control Transmission Protocol (SCTP) Partial Reliability Extension
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 |
12.txt 11.txt 08.txt 07.txt 06.txt 05.txt 04.txt 03.txt 02.txt 01.txt 00.txt
|
Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration
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 |
16.txt 15.txt 14.txt 13.txt 12.txt 10.txt 09.txt 08.txt 07.txt 06.txt 05.txt 04.txt 03.txt 02.txt 01.txt 00.txt
|
Stream Control Transmission Protocol (SCTP) Specification Errata and Issues
This document is a compilation of issues found during six interoperability events and 5
years of experience with implementing, testing, and using SCTP along with the suggested
fixes. This document provides deltas to RFC 2960 and is organized in a time based way.
The issues are listed in the order they were brought up. Because some text is changed
several times the last delta in the text is the one which should be applied. In
addition to the delta a description of the problem and the details of the solution are
also provided.
|
|
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.
|
|
rfc3257 |
.txt
|
Stream Control Transmission Protocol Applicability Statement
This document describes the applicability of the Stream Control Transmission Protocol
(SCTP). It also contrasts SCTP with the two dominant transport protocols, User Datagram
Protocol (UDP) & Transmission Control Protocol (TCP), and gives some guidelines for
when best to use SCTP and when not best to use SCTP.
|
|
draft-ietf-sigtran-sctp-applicability |
08.txt 07.txt 06.txt 05.txt 04.txt 03.txt 02.txt 01.txt 00.txt
|
Stream Control Transmission Protocol Applicability Statement
This document describes the applicability of the Stream Control Transmission Protocol
(SCTP)[RFC2960]. It also contrasts SCTP with the two dominant transport protocols, UDP
& TCP, and gives some guidelines for when best to use SCTP and when not best to use
SCTP.
|
|
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.
|
|