Control Transmission

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 361398 Experts worldwide ranked by ideXlab platform

Randall Stewart - One of the best experts on this subject based on the ideXlab platform.

  • Stream Control Transmission Protocol (SCTP) Network Address Translation Support
    2020
    Co-Authors: Irene Ruengeler, Randall Stewart
    Abstract:

    The Stream Control Transmission Protocol (SCTP) provides a reliable communications channel between two end-hosts in many ways similar to the Transmission Control Protocol (TCP). With the widespread deployment of Network Address Translators (NAT), specialized code has been added to NAT for TCP that allows multiple hosts to reside behind a NAT and yet share a single IPv4 address, even when two hosts (behind a NAT) choose the same port numbers for their connection. This additional code is sometimes classified as Network Address and Port Translation (NAPT). This document describes the protocol extensions required for the SCTP endpoints and the mechanisms for NAT devices necessary to provide similar features of NAPT in the single point and multi point traversal scenario. Finally, a YANG module for SCTP NAT is defined.

  • stream Control Transmission protocol errata and issues in rfc 4960
    RFC, 2019
    Co-Authors: Randall Stewart, Maksim Proshin
    Abstract:

    This document is a compilation of issues found since the publication of RFC4960 in September 2007 based on experience with implementing, testing, and using SCTP along with the suggested fixes. This document provides deltas to RFC4960 and is organized in a time ordered 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.

  • stream schedulers and user message interleaving for the stream Control Transmission protocol
    RFC, 2017
    Co-Authors: Robin Seggelmann, Randall Stewart, Salvatore Loreto
    Abstract:

    The Stream Control Transmission Protocol (SCTP) is a message-oriented transport protocol supporting arbitrarily large user messages. This document adds a new chunk to SCTP for carrying payload data. This allows a sender to interleave different user messages that would otherwise result in head-of-line blocking at the sender. The interleaving of user messages is required for WebRTC data channels. Whenever an SCTP sender is allowed to send user data, it may choose from multiple outgoing SCTP streams. Multiple ways for performing this selection, called stream schedulers, are defined in this document. A stream scheduler can choose to either implement, or not implement, user message interleaving.

  • Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension
    2015
    Co-Authors: Michael Tuexen, Randall Stewart, Robin Seggelmann, Salvatore Loreto
    Abstract:

    This document defines two additional policies for the Partially Reliable Stream Control Transmission Protocol (PR-SCTP) extension. These policies allow limitation of the number of reTransmissions and prioritization of user messages for more efficient usage of the send buffer.

  • Stream Control Transmission Protocol (SCTP) Network Address Translation
    2013
    Co-Authors: Irene Ruengeler, Randall Stewart, Michael Tuxen
    Abstract:

    Stream Control Transmission Protocol [RFC4960] provides a reliable communications channel between two end-hosts in many ways similar to TCP [RFC0793]. With the widespread deployment of Network Address Translators (NAT), specialized code has been added to NAT for TCP that allows multiple hosts to reside behind a NAT and yet use only a single globally unique IPv4 address, even when two hosts (behind the NAT) choose the same port numbers for their connection. This additional code is sometimes classified as Network Address and Port Translation or NAPT. To date, specialized code for SCTP has NOT yet been added to most NAT's so that only pure NAT is available. The end result of this is that only one SCTP capable host can be behind a NAT. This document describes an SCTP specific variant of NAT which provides similar features of NAPT in the single point and multi-point traversal scenario.

Michael Tuxen - One of the best experts on this subject based on the ideXlab platform.

  • Stream Control Transmission Protocol (SCTP) Network Address Translation
    2013
    Co-Authors: Irene Ruengeler, Randall Stewart, Michael Tuxen
    Abstract:

    Stream Control Transmission Protocol [RFC4960] provides a reliable communications channel between two end-hosts in many ways similar to TCP [RFC0793]. With the widespread deployment of Network Address Translators (NAT), specialized code has been added to NAT for TCP that allows multiple hosts to reside behind a NAT and yet use only a single globally unique IPv4 address, even when two hosts (behind the NAT) choose the same port numbers for their connection. This additional code is sometimes classified as Network Address and Port Translation or NAPT. To date, specialized code for SCTP has NOT yet been added to most NAT's so that only pure NAT is available. The end result of this is that only one SCTP capable host can be behind a NAT. This document describes an SCTP specific variant of NAT which provides similar features of NAPT in the single point and multi-point traversal scenario.

  • Stream Control Transmission protocol: Past, current, and future standardization activities
    IEEE Communications Magazine, 2011
    Co-Authors: Thomas Dreibholz, Michael Tuxen, Irene Rungeler, Erwin P. Rathgeb, Robin Seggelmann, R R Stewart
    Abstract:

    The Stream Control Transmission Protocol (SCTP) is a general-purpose transport layer protocol providing a service similar to TCP - plus a set of advanced features to utilize the enhanced capabilities of modern IP networks and to support increased application requirements. Nowadays, there are SCTP implementations for all major operating systems. While SCTP was standardized as an RFC several years ago, there is still significant ongoing work within the IETF to discuss and standardize further features in the form of protocol extensions. In this article, we first introduce the SCTP base protocol and already standardized extensions. After that, we focus on the ongoing SCTP standardization progress in the IETF and give an overview of activities and challenges in the areas of security and concurrent multipath transport.

  • Network Address Translation for the Stream Control Transmission Protocol
    IEEE Network, 2008
    Co-Authors: Michael Tuxen, Irene Rungeler, Randall Stewart, Erwin P. Rathgeb
    Abstract:

    Network address translation is widely deployed in the Internet and supports the Transmission Control protocol and the user datagram protocol as transport layer protocols. Although part of the kernels of all recent Linux distributions, namely, the FreeBSD 7 and the Solaris 10 operating systems, the new Internet Engineering Task Force transport protocol - stream Control Transmission protocol - is not supported on most NAT middleboxes yet. This article discusses the deficiencies of using existing NAT methods for SCTP and describes a new SCTP-specific NAT concept. This concept is analyzed in detail for several important network scenarios, including peer-to-peer, transport layer mobility, and multihoming.

  • datagram transport layer security for stream Control Transmission protocol
    2007
    Co-Authors: Eric Rescorla, Michael Tuxen
    Abstract:

    This document describes the usage of the Datagram Transport Layer Security (DTLS) protocol over the Stream Control Transmission Protocol (SCTP). The user of DTLS over SCTP can take advantage of all features provided by SCTP and its extensions, especially support of o multiple streams to avoid head of line blocking. o multi-homing to provide network level fault tolerance. o unordered delivery. o partial reliable data transfer.

  • das simple Control Transmission protocol sctp ein neues protokoll zum transport von signalisierungsmeldungen uber ip basierte netze
    Elektrotechnik Und Informationstechnik, 2000
    Co-Authors: A Jungmaier, Michael Schopp, Michael Tuxen
    Abstract:

    Derzeit wird im Rahmen der Internet Engineering Task Force (IETF) unter der Bezeichnung SCTP ein neues Protokoll zum Transport von Signalisierungsmeldungen uber IP-basierte Netze definiert. Dieser Beitrag beschreibt das Protokoll und die Mechanismen, die es fur den sicheren und effizienten Transport von Signalisierungsmeldungen den klassischen Protokollen TCP oder UDP uberlegen machen. Des Weiteren werden mogliche Anwendungsszenarien und Interworkingfalle mit klassischen Netzen beschrieben.

Michael Tuexen - One of the best experts on this subject based on the ideXlab platform.

  • Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension
    2015
    Co-Authors: Michael Tuexen, Randall Stewart, Robin Seggelmann, Salvatore Loreto
    Abstract:

    This document defines two additional policies for the Partially Reliable Stream Control Transmission Protocol (PR-SCTP) extension. These policies allow limitation of the number of reTransmissions and prioritization of user messages for more efficient usage of the send buffer.

  • UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets for End-Host to End-Host Communication
    2013
    Co-Authors: Michael Tuexen, Randall Stewart
    Abstract:

    This document describes a simple method of encapsulating Stream Control Transmission Protocol (SCTP) packets into UDP packets and its limitations. This allows the usage of SCTP in networks with legacy NATs that do not support SCTP. It can also be used to implement SCTP on hosts without directly accessing the IP layer, for example, implementing it as part of the application without requiring special privileges. Please note that this document only describes the functionality required within an SCTP stack to add on UDP encapsulation, providing only those mechanisms for two end-hosts to communicate with each other over UDP ports. In particular, it does not provide mechanisms to determine whether UDP encapsulation is being used by the peer, nor the mechanisms for determining which remote UDP port number can be used. These functions are out of scope for this document. This document covers only end-hosts and not tunneling (egress or ingress) endpoints.

  • stream Control Transmission protocol sctp stream reconfiguration
    RFC, 2012
    Co-Authors: Michael Tuexen, Peter Lei, Randall Stewart
    Abstract:

    Many applications that use 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 upper layer that this has been performed. The applications that want this feature want it so that they can "re-use" 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 transport sequence numbers, adding additional streams and resetting all stream sequence numbers.

  • sockets api extensions for stream Control Transmission protocol sctp
    2011
    Co-Authors: Michael Tuexen, Randall Stewart, Kacheong Poon, Vladislav Yasevich, Peter Lei
    Abstract:

    This document describes a mapping of the Stream Control Transmission Protocol SCTP into a sockets API. The benefits of this mapping include compatibility for TCP applications, access to new SCTP features and a consolidated error and event notification scheme.

  • sockets api extensions for the stream Control Transmission protocol sctp
    RFC, 2011
    Co-Authors: Michael Tuexen, Randall Stewart, Kacheong Poon, Vladislav Yasevich, Peter Lei
    Abstract:

    This document describes a mapping of the Stream Control Transmission Protocol SCTP into a sockets API. The benefits of this mapping include compatibility for TCP applications, access to new SCTP features and a consolidated error and event notification scheme.

Erwin P. Rathgeb - One of the best experts on this subject based on the ideXlab platform.

  • Stream Control Transmission protocol: Past, current, and future standardization activities
    IEEE Communications Magazine, 2011
    Co-Authors: Thomas Dreibholz, Michael Tuxen, Irene Rungeler, Erwin P. Rathgeb, Robin Seggelmann, R R Stewart
    Abstract:

    The Stream Control Transmission Protocol (SCTP) is a general-purpose transport layer protocol providing a service similar to TCP - plus a set of advanced features to utilize the enhanced capabilities of modern IP networks and to support increased application requirements. Nowadays, there are SCTP implementations for all major operating systems. While SCTP was standardized as an RFC several years ago, there is still significant ongoing work within the IETF to discuss and standardize further features in the form of protocol extensions. In this article, we first introduce the SCTP base protocol and already standardized extensions. After that, we focus on the ongoing SCTP standardization progress in the IETF and give an overview of activities and challenges in the areas of security and concurrent multipath transport.

  • Network Address Translation for the Stream Control Transmission Protocol
    IEEE Network, 2008
    Co-Authors: Michael Tuxen, Irene Rungeler, Randall Stewart, Erwin P. Rathgeb
    Abstract:

    Network address translation is widely deployed in the Internet and supports the Transmission Control protocol and the user datagram protocol as transport layer protocols. Although part of the kernels of all recent Linux distributions, namely, the FreeBSD 7 and the Solaris 10 operating systems, the new Internet Engineering Task Force transport protocol - stream Control Transmission protocol - is not supported on most NAT middleboxes yet. This article discusses the deficiencies of using existing NAT methods for SCTP and describes a new SCTP-specific NAT concept. This concept is analyzed in detail for several important network scenarios, including peer-to-peer, transport layer mobility, and multihoming.

Irene Rungeler - One of the best experts on this subject based on the ideXlab platform.

  • Stream Control Transmission protocol: Past, current, and future standardization activities
    IEEE Communications Magazine, 2011
    Co-Authors: Thomas Dreibholz, Michael Tuxen, Irene Rungeler, Erwin P. Rathgeb, Robin Seggelmann, R R Stewart
    Abstract:

    The Stream Control Transmission Protocol (SCTP) is a general-purpose transport layer protocol providing a service similar to TCP - plus a set of advanced features to utilize the enhanced capabilities of modern IP networks and to support increased application requirements. Nowadays, there are SCTP implementations for all major operating systems. While SCTP was standardized as an RFC several years ago, there is still significant ongoing work within the IETF to discuss and standardize further features in the form of protocol extensions. In this article, we first introduce the SCTP base protocol and already standardized extensions. After that, we focus on the ongoing SCTP standardization progress in the IETF and give an overview of activities and challenges in the areas of security and concurrent multipath transport.

  • Network Address Translation for the Stream Control Transmission Protocol
    IEEE Network, 2008
    Co-Authors: Michael Tuxen, Irene Rungeler, Randall Stewart, Erwin P. Rathgeb
    Abstract:

    Network address translation is widely deployed in the Internet and supports the Transmission Control protocol and the user datagram protocol as transport layer protocols. Although part of the kernels of all recent Linux distributions, namely, the FreeBSD 7 and the Solaris 10 operating systems, the new Internet Engineering Task Force transport protocol - stream Control Transmission protocol - is not supported on most NAT middleboxes yet. This article discusses the deficiencies of using existing NAT methods for SCTP and describes a new SCTP-specific NAT concept. This concept is analyzed in detail for several important network scenarios, including peer-to-peer, transport layer mobility, and multihoming.

Related terms

Control Transmission - 15 days free trial to Access Experts & Abstracts