|This article needs additional citations for "verification. (October 2015) ("Learn how and when to remove this template message)|
|"Internet protocol suite|
In "computer networking, the transport layer is a conceptual division of methods in the layered architecture of protocols in the network stack in the "Internet Protocol Suite and the "Open Systems Interconnection (OSI). The protocols of the layer provide host-to-host communication services for applications. It provides services such as "connection-oriented "data stream support, "reliability, "flow control, and "multiplexing.
The details of implementation and semantics of the Transport Layer of the "TCP/IP model (RFC 1122), which is the foundation of the "Internet, and the "Open Systems Interconnection "(OSI) model of general networking, are easily compared. In the OSI model the transport layer is most often referred to as Layer 4 or L4, while numbered layers are not used in TCP/IP.
The best-known transport protocol of TCP/IP is the "Transmission Control Protocol (TCP), and lent its name to the title of the entire suite. It is used for connection-oriented transmissions, whereas the connectionless "User Datagram Protocol (UDP) is used for simpler messaging transmissions. TCP is the more complex protocol, due to its stateful design incorporating reliable transmission and data stream services. Other prominent protocols in this group are the "Datagram Congestion Control Protocol (DCCP) and the "Stream Control Transmission Protocol (SCTP).
Transport layer services are conveyed to an application via a programming interface to the transport layer protocols. The services may include the following features:
The transport layer is responsible for delivering data to the appropriate application process on the host computers. This involves "statistical multiplexing of data from different application processes, i.e. forming data segments, and adding source and destination port numbers in the header of each transport layer data segment. Together with the source and destination IP address, the port numbers constitutes a "network socket, i.e. an identification address of the process-to-process communication. In the OSI model, this function is supported by the "session layer.
Some transport layer protocols, for example TCP, but not UDP, support "virtual circuits, i.e. provide "connection oriented communication over an underlying packet oriented "datagram network. A byte-stream is delivered while hiding the packet mode communication for the application processes. This involves connection establishment, dividing of the data stream into packets called segments, segment numbering and reordering of out-of order data.
Finally, some transport layer protocols, for example TCP, but not UDP, provide end-to-end reliable communication, i.e. "error recovery by means of "error detecting code and "automatic repeat request (ARQ) protocol. The ARQ protocol also provides "flow control, which may be combined with "congestion avoidance.
UDP is a very simple protocol, and does not provide virtual circuits, nor reliable communication, delegating these functions to the "application program. UDP packets are called "datagrams, rather than segments.
TCP is used for many protocols, including "HTTP web browsing and email transfer. UDP may be used for "multicasting and "broadcasting, since retransmissions are not possible to a large amount of hosts. UDP typically gives higher "throughput and shorter latency, and is therefore often used for real-time multimedia communication where packet loss occasionally can be accepted, for example IP-TV and IP-telephony, and for online computer games.
Many non-IP-based networks, such as "X.25, "Frame Relay and "ATM, implement the connection-oriented communication at the network or data link layer rather than the transport layer. In X.25, in telephone network modems and in wireless communication systems, reliable node-to-node communication is implemented at lower protocol layers.
The OSI connection-mode transport layer protocol specification defines five classes of transport protocols: TP0, providing the least error recovery, to TP4, which is designed for less reliable networks.
|Feature Name||"UDP||"UDP-Lite||"TCP||"Multipath TCP||"SCTP||"DCCP||"RUDP|
|Packet header size||8 bytes||8 bytes||20–60 bytes||50–90 bytes||12 bytes||12 or 16 bytes||6+ bytes|
|Transport layer packet entity||Datagram||Datagram||Segment||Segment||Datagram||Datagram||Datagram|
|Preserve message boundary||Yes||Yes||No||No||Yes||Yes||Yes|
|Checksum size (bits)||16||16||16||16||32||16||16|
|"Explicit Congestion Notification||No||No||Yes||Yes||Yes||Yes|
|Bundling / "Nagle||No||No||Yes||Yes||Yes||No||Unsure|
ISO/IEC 8073/ITU-T Recommendation X.224, "Information Technology - Open Systems Interconnection - Protocol for providing the connection-mode transport service", defines five classes of connection-mode transport protocols designated class 0 (TP0) to class 4 (TP4). Class 0 contains no error recovery, and was designed for use on network layers that provide error-free connections. Class 4 is closest to TCP, although TCP contains functions, such as the graceful close, which OSI assigns to the session layer. All OSI connection-mode protocol classes provide expedited data and preservation of record boundaries. Detailed characteristics of the classes are shown in the following table:
|Connection oriented network||Yes||Yes||Yes||Yes||Yes|
|Concatenation and separation||No||Yes||Yes||Yes||Yes|
|Segmentation and reassembly||Yes||Yes||Yes||Yes||Yes|
|Reinitiate connection (if an excessive number of "PDUs are unacknowledged)||No||Yes||No||Yes||No|
|multiplexing and demultiplexing over a single "virtual circuit||No||No||Yes||Yes||Yes|
|Explicit flow control||No||No||Yes||Yes||Yes|
|Retransmission on timeout||No||No||No||No||Yes|
|Reliable Transport Service||No||Yes||No||Yes||Yes|
There is also a connectionless transport protocol, specified by ISO/IEC 8602/ITU-T Recommendation X.234.
|Wikiversity has learning resources about Transport layer|