Your Perfect Assignment is Just a Click Away

We Write Custom Academic Papers

From as Little as $6

100% Original, Plagiarism Free, Customized to your instructions!


Reliable Data Transmission protocols RDT 2.1 Python Project

Reliable Data Transmission protocols RDT 2.1 Python Project

Question Description


During this project, you will implement the Reliable Data Transmission protocols RDT 2.1, and RDT 3.0 discussed in class and the textbook, by extending an RDT 1.0 implementation.

Starting Code

The starting code for this project provides you with the implementation of several network layers that cooperate to achieve end-to-end communication.


The client sends messages to the server, which converts them to pig latin and transmits them back. The client and the server send messages to each other through the transport layer provided by an RDT implementation using the rdt_1_0_send and rdt_1_0_receive functions. The starting provides only the RDT 1.0 version of the protocol, which does not tolerate packet corruption, or loss. The RDT protocol uses udt_send and udt_receive provided by to transfer bytes between the client and server machines. The network layer may corrupt packets or lose packets altogether. relies on the Packet class (in the same file) to form transport layer packets.

Your job will be to extend to tolerate packet corruption and loss. The provided code lists prototype send and receive functions for these protocols. You may need to modify/extend the Packet class to transmit the necessary information for these functions to work correctly. The provided implementation of is reliable, but we will test your code with non-zero probability for packet corruption and loss by changing the values of prob_pkt_loss and prob_byte_corr of the NetworkLayer class. You should change those variables yourself to test your code and show that your protocol implementations tolerate corruption and loss in your demonstration videos.

Program Invocation

To run the starting code you may run:

python 5000


python localhost 5000

in separate terminal windows. Be sure to start the server first, to allow it to start listening on a socket, and start the client soon after, before the server times out.