1 15-744 Computer Networking Review 2 – Transport Protocols Announcements • Project proposal • Due 9/24 • Roughly 1/3 on each of problem statement, state-of-art, work plan/milestones • ~1pg total • HW1 • Out today, due 9/27 2 Outline • Transport introduction • Error recovery & flow control • TCP flow control/connection setup/data transfer • TCP reliability • Congestion sources and collapse • Congestion control basics 3 4 Transport Protocols • Lowest level end-to-end protocol. • Header generated by sender is interpreted only by the destination • Routers view transport header as part of the payload • Not always true… • Firewalls 7 6 5 7 6 5 Transport IP Datalink Physical Transport IP Datalink Physical IP router 2 2 1 12 5 Functionality Split • Network provides best-effort delivery • End-systems implement many functions • Reliability • In-order delivery • Demultiplexing • Message boundaries • Connection abstraction • Congestion control • … 6 Transport Protocols • UDP provides just integrity and demux • TCP adds… • Connection-oriented • Reliable • Ordered • Byte-stream • Full duplex • Flow and congestion controlled • DCCP, RTP, SCTP -- not widely used. 7 UDP: User Datagram Protocol [RFC 768] • “No frills,” “bare bones” Internet transport protocol • “Best effort” service, UDP segments may be: • Lost • Delivered out of order to app • Connectionless: • No handshaking between UDP sender, receiver • Each UDP segment handled independently of others Why is there a UDP? • No connection establishment (which can add delay) • Simple: no connection state at sender, receiver • Small header • No congestion control: UDP can blast away as fast as desired 8 UDP, cont. • Often used for streaming multimedia apps • Loss tolerant • Rate sensitive • Other UDP uses (why?): • DNS • Reliable transfer over UDP • Must be at application layer • Application-specific error recovery Source port # Dest port # 32 bits Application data (message) UDP segment format Length Checksum Length, in bytes of UDP segment, including header3 9 UDP Checksum Sender: • Treat segment contents as sequence of 16-bit integers • Checksum: addition (1’s complement sum) of segment contents • Sender puts checksum value into UDP checksum field Receiver: • Compute checksum of received segment • Check if computed checksum equals checksum field value: • NO - error detected • YES - no error detected But maybe errors nonetheless? Goal: detect “errors” (e.g., flipped bits) in transmitted segment – optional use! 10 High-Level TCP Characteristics • Protocol implemented entirely at the ends • Fate sharing (on IP) • Protocol has evolved over time and will continue to do so • Nearly impossible to change the header • Use options to add information to the header • Change processing at endpoints • Backward compatibility is what makes it TCP 11 TCP Header Source port Destination port Sequence number Acknowledgement Advertised window HdrLen Flags 0 Checksum Urgent pointer Options (variable) Data Flags: SYN FIN RESET PUSH URG ACK 12 Evolution of TCP 1975 1980 1985 1990 1982 TCP & IP RFC 793 & 791 1974 TCP described by Vint Cerf and Bob Kahn In IEEE Trans Comm 1983 BSD Unix 4.2 supports TCP/IP 1984 Nagel’s algorithm to reduce overhead of small packets; predicts congestion collapse 1987 Karn’s algorithm to better estimate round-trip time 1986 Congestion collapse observed 1988 Van Jacobson’s algorithms congestion avoidance and congestion control (most implemented in 4.3BSD Tahoe) 1990 4.3BSD Reno fast retransmit delayed ACK’s 1975 Three-way handshake Raymond Tomlinson In SIGCOMM 754 13 TCP Through the 1990s 1993 1994 1996 1994 ECN (Floyd) Explicit Congestion Notification 1993 TCP Vegas (Brakmo et al) delay-based congestion avoidance 1994 T/TCP (Braden) Transaction TCP 1996 SACK TCP (Floyd et al) Selective Acknowledgement 1996 Hoe NewReno startup and loss recovery 1996 FACK TCP (Mathis et al) extension to SACK Outline • Transport introduction • Error recovery & flow control • TCP flow control/connection setup/data transfer • TCP reliability • Congestion sources and collapse • Congestion control basics 14 Stop and Wait • ARQ • Receiver sends acknowledgement (ACK) when it receives packet • Sender waits for ACK and timeouts if it does not arrive within some time period • Simplest ARQ protocol • Send a packet, stop and wait until ACK arrives • Performance • Can only send one packet per round trip 15 Time Packet ACK Timeout Sender Receiver 16 Recovering from Error Packet ACK Timeout Packet ACK Timeout Packet Timeout Packet ACK Timeout Time Packet ACK Timeout Packet ACK Timeout ACK lost Packet lost Early timeout DUPLICATE PACKETS!!!5 17 How to Recognize Resends? • Use sequence numbers • both packets and acks • Sequence # in packet is finite How big should it be? • For stop and wait? • One bit – won’t send seq #1 until received ACK for seq #0 Pkt 0 ACK 0 Pkt 0 ACK 1 Pkt 1 ACK 0 18 How to Keep the Pipe Full? • Send multiple packets without waiting for first to be acked • Number of pkts in flight = window: Flow control • Reliable, unordered delivery • Several parallel stop & waits • Send new packet after each ack • Sender keeps list of unack’ed packets; resends after timeout • Receiver same as stop & wait • How large a window is needed? • Suppose 10Mbps link, 4ms delay, 500byte pkts • 1? 10? 20? • Round trip delay * bandwidth = capacity of pipe 19 Sliding Window • Reliable, ordered delivery • Receiver has to hold onto a packet until all prior packets have arrived • Why might this be difficult for just parallel stop & wait? • Sender must prevent buffer overflow at receiver • Circular buffer at sender and receiver • Packets in transit ≤ buffer size • Advance when sender and receiver agree packets at beginning have been received 20 Receiver Sender Sender/Receiver State … … Sent & Acked Sent Not Acked OK to Send Not Usable … … Max acceptable Receiver window Max ACK received Next seqnum
View Full Document
Unlocking...