2000
DOI: 10.17487/rfc2960
|View full text |Cite
|
Sign up to set email alerts
|

Stream Control Transmission Protocol

Abstract: The MPEG-4 standard encodes a video stream in 3 different frames, I, P and B, where the P and B frames depend on the I frame. Loosing an I frame is especially bad. In this paper we exploit the Partial Reliability features of the SCTP transport protocol to selectively retransmit I frames in presence of congestion, obtaining a better quality of the decoded stream.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

2
793
0
10

Year Published

2003
2003
2017
2017

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 757 publications
(805 citation statements)
references
References 1 publication
(1 reference statement)
2
793
0
10
Order By: Relevance
“…Doing so also avoids issues that protocols using a new IP protocol number face when being deployed over the Internet, where middleboxes that only support TCP and UDP are sometimes present. Consequently, the RECOMMENDED alternative to the UDP usage described in the remainder of this section is the use of an IETF transport protocol such as TCP [RFC793], Stream Control Transmission Protocol (SCTP) [RFC4960], and SCTP Partial Reliability Extension (SCTP-PR) [RFC3758] If used correctly, these more fully featured transport protocols are not as "heavyweight" as often claimed. For example, the TCP algorithms have been continuously improved over decades, and they have reached a level of efficiency and correctness that custom application-layer mechanisms will struggle to easily duplicate.…”
Section: Udp Usage Guidelinesmentioning
confidence: 99%
“…Doing so also avoids issues that protocols using a new IP protocol number face when being deployed over the Internet, where middleboxes that only support TCP and UDP are sometimes present. Consequently, the RECOMMENDED alternative to the UDP usage described in the remainder of this section is the use of an IETF transport protocol such as TCP [RFC793], Stream Control Transmission Protocol (SCTP) [RFC4960], and SCTP Partial Reliability Extension (SCTP-PR) [RFC3758] If used correctly, these more fully featured transport protocols are not as "heavyweight" as often claimed. For example, the TCP algorithms have been continuously improved over decades, and they have reached a level of efficiency and correctness that custom application-layer mechanisms will struggle to easily duplicate.…”
Section: Udp Usage Guidelinesmentioning
confidence: 99%
“…TCP, yang merupakan protocol transport yang banyak digunakan saat ini; memiliki beberapa kelemahan yang mendasar, antara lain: packet latency yang cenderung panjang, head of line blocking (HOL), denial of service yang disebabkan oleh mekanisme three-way-handshake dan pengurutan informasi yang ketat Sedangkan UDP (User Datagram Protocol), merupakan protokol yang connectionless yang tidak memiliki mekanisme congestion control dan memperbaiki kesalahan. Untuk memperbaiki kelemahan itu, Internet Engineering Task Force (IETF) mengembangkan protokol baru sebagai protokol alternatif, yaitu SCTP [3]. SCTP dirancang sebagai protokol yang handal, connection-oriented seperti TCP akan tetapi memiliki kemampuan-kemampuan: fast recovery, fast retransmit, Selective Acknowledgement (SACK), multihoming dan multistreaming.…”
Section: Pendahuluanunclassified
“…SCTP yang dirancang oleh IETF diformulasikan dalam dokumen Draft Proposed Standard SCTP berupa Request for Comments (RFC) 2960 pada Oktober 2000 [3]. SCTP dirancang sebagai protokol lapisan transport yang berbasis pada aplikasi message-oriented.…”
Section: Metodeunclassified
See 1 more Smart Citation
“…Differ from other multipath transport protocols such as Stream Control Transmission Protocol (SCTP) [3], MPTCP is easy to be deployed in practice. Application developers can use traditional APIs of TCP and do not require any modifications to their products.…”
mentioning
confidence: 99%