TCP, like our rdt protocol in Principles of Reliable Data Transfer, uses a timeout/retransmit mechanism to recover from lost segments. Though this is conceptually simple, many subtle issues arise when we implement a timeout/retransmit mechanism in an actual protocol such
Having briefly examined the TCP connection, let's look at the TCP segment structure. The TCP segment comprises header fields and a data field. The data field includes a chunk of application data. As mentioned above, the MSS limits the maximum size of a segments data field.
We have studied the underlying principles of reliable data transfer, let's examine TCP - the Internet's transport-layer, connection-oriented, reliable transport protocol. In this section, we'll see that in order to provide reliable data transfer, TCP relies on many of the underlying
The GBN protocol allows the sender to potentially "fill the pipeline" in Pipelined Reliable Data Transfer Protocols Figure 2 with packets, therefore avoiding the channel utilization problems we noted with stop-and-wait protocols. There are, on the other hand, scenarios in which
In a Go-Back-N (GBN) protocol, the sender is allowed to transmit several packets (when available) without waiting for an acknowledgment, but is constrained to have no more than some maximum allowable number, N, of unacknowledged packets in the pipeline. We describe the
Protocol rdt3.0 is a functionally correct protocol, but it is doubtful that anyone would be happy with its performance, especially in todays high-speed networks. At the heart of rdt.3.0s performance problem is the fact that it is a stop-and-wait protocol.
We first examine the simplest case, in which the underlying channel is completely reliable. The protocol itself, which we'll call rdt1.0, is trivial. The finite-state machine (FSM) definitions for the rdt1.0 sender and receiver are shown in Figure 1. The FSM in Figure 1(a) defines the
In this section, we look at the problem of reliable data transfer in a general context. This is appropriate since the problem of implementing reliable data transfer takes place not only at the transport layer, but also at the link layer and the application layer as well. The common
The application data shown in Figure 1 occupies the data field of the UDP segment. For instance, for DNS, the data field includes either a query message or a response message. For a streaming audio application, audio samples fill the data field. The UDP header has only four
In this section, we'll examine UDP, how it works, and what it does. We encourage you to refer back to Principles of Network Applications, which contains an overview of the UDP service model, and to Socket Programming with UDP, which discusses socket programming using