User Datagram Protocol

Transcription

1 Topics Transport Layer TCP s three-way handshake TCP s connection termination sequence TCP s TIME_WAIT state TCP and UDP buffering by the socket layer 2

2 Introduction UDP is a simple, unreliable datagram protocol TCP is a sophisticated, reliable byte-stream protocol Understanding these protocols help you make better decisions when developing applications that utilize the transport layer Additionally, understanding services provided by these protocols enables you know what must be handled in the application 3

3 The Big Picture 4

4 User Datagram Protocol Simple, unreliable, connectionless, datagram service Application writes a message to the UDP socket, the message is encapsulated in an UDP packet, then further encapsulated in an IP datagram, and sent to its destination NO guarantee UDP will reach its destination or that the packet order will be preserved Extra functionality can be built into the application: acknowledgments, timeouts, retransmissions, etc. UDP differs from TCP in that it has a specified length. TCP is a byte-stream protocol with no record boundaries 5

5 Transmission Control Protocol TCP provides connections between clients and servers Typical communication: 1) TCP client establishes connection; 2) exchanges data; 3) terminates connection TCP provides reliability: -When TCP sends data it requires an acknowledgement (ACK) -If an ACK is not received, TCP retransmits the data and increases the timeout window -After several retransmissions TCP will give up 6

6 Transmission Control Protocol (Continued) TCP DOES NOT guarantee that the data will be received by the other endpoint That s impossible! It delivers data to the other endpoint if possible, and notifies the user if it is not possible (by giving up on retransmissions) Thus, TCP can t be described as a 100% reliable protocol; it provides reliable delivery of data or a reliable notification of failure 7

7 Transmission Control Protocol (Continued) TCP contains algorithms to dynamically estimate the round-trip-time (RTT) between a client and a server This tells TCP how long to wait for an ACK Which is greater - the RTT of a LAN or WAN? TCP continuously estimates the RTT of a given connection, because the RTT is affected by traffic variations TCP also sequences data by associating sequence numbers with ever byte it sends 8

8 Transmission Control Protocol (Continued) For Example: If an application writes 2,048 bytes to a TCP socket, causing TCP to send two segments: first with sequence number 1-1,024 and the second with sequence numbers 1,025 2,048 If the segment arrives out of order, the receiving TCP will reorder the segments based on sequence number before passing them up to the application layer Sequence numbers also protects against processing duplicate segments 9

9 Transmission Control Protocol (Continued) TCP provides a full-duplex connection with flow control TCP tells its peer exactly how many bytes of data it is willing to accept from the peer at any one time This is called the advertised window At any time, the window is the amount of room currently available in the receive buffer This guarantees that the sender can t overflow the receiver s buffer As data is received by the sender, the window size decreases, but as the receiving application reads data from the buffer, the window size increases A window size of 0 implies that that the receive buffer is full and waiting for the application to read data 10

10 TCP Connection Establishment: Three Way Handshake The minimum number of packets required for this exchange is three The acknowledgment number in an ACK is the next expected sequence number for the end sending the ACK 11

11 TCP Connection Establishment: Three Way Handshake Consider the following scenario when a TCP connection is established: Server must be prepared to accept connection usually done by calling socket, bind, and listen (this is called a passive open) Client issues an active open by calling connect. This causes the TCP client to send a synchronize segment (SYN) This tells the server the clients initial sequence number Normally contains no data, just and IP header, a TCP header, and possibly options The server must acknowledge (ACK) the client s SYN and the server must also send its own SYN (this is done in one segment) Contains the initial sequence number for the data that the server will send The Client must acknowledge the server s SYN 12

12 TCP Connection Establishment: Three Way Handshake - Ethereal 13

13 TCP Connection Termination 15

14 TCP Connection Termination Since a FIN and ACK are required in both directions, four segments are normally used Steps 2 and 3 may be combined Between steps 2 and 3 it is possible for data to flow from the end doing the passive close to the end doing the active close. This is called a halfclose The sending of each FIN occurs when a socket is closed 16

15 TCP Connection Termination - Ethereal 17

16 TCP State Transition Diagram 18

17 TCP State Transition Diagram (Continued) The operation of TCP with regard to connection establishment and connection termination can be specified with a state transition diagram Total of 11 different states Rules of TCP dictate the transitions from one state to another Example: An application performs an active open in the CLOSED state TCP sends a SYN and the new state is SYN_SENT. If TCP next receives a SYN with an ACK, it sends and ACK an the new state is ESTABLISHED. The two arrows leaving from the ESTABLISHED state deal with the termination of a connection If an application calls close before receiving a FIN (an active close), the transition is to the FIN_WAIT_1 state If an application receives a FIN while in the ESTABLISHED (a passive close), the transition is to the CLOSE_WAIT state 19

18 Watching The Packets 20

19 Watching The Packets Example: client announces am MSS of 536 and server announces MSS of 1460 it s okay for the MSS to be different in each direction A MSS of 1460 is common for IPv4 on Ethernet A connection is established and a request is sent to the server It is assumed that the request fits into a single TCP segment The server processes the request and sends a reply (again assuming that it fits in a single TCP segment) Notice that the acknowledgement of the request is sent with the server s reply this is called piggybacking Piggybacking normally takes place when the time it takes the server to process the request and generate the reply is less than 200ms Finally, the connection is closed with four segments notice that the client enters the TIME_WAIT state How would this diagram look if it were UDP? 21

20 TIME_WAIT State The duration that an endpoint remains in this state is twice the maximum segment lifetime (MSL), sometimes called 2MSL Every implementation of TCP must choose a value for the MSL Normally between 30 seconds and 2 minutes MSL is the maximum amount of time that any given IP datagram can live in a network This time is bounded because of the 8-bit hop limit in the IP header, the time-to-live (TTL) field A packet can get lost in the network as a result of routing anomalies: routers crashing If the packet gets lost, and is retransmitted due a timeout, and suddenly the packet is found and transmitted to the destination, the duplicate is called a lost duplicate or a wandering duplicate. TCP must handle these scenarios 22

21 TIME_WAIT State (Continued) Two reasons for the TIME_WAIT state: 1) To implement TCP s full-duplex connection termination reliably : To Illustrate this, let s assume that the final ACK was lost The server will resend the final FIN, so the client must maintain state information, allowing it to resend the final ACK If it did not maintain state, the client would respond with a reset, which would be interpreted by the server as an error In order to terminate both directions cleanly, TCP musts correctly handle the loss of any of the four connection termination sessions This example shows why the end that does the active close, is the end that goes into the TIME_WAIT state because it may have to retransmit the final ACK 23

22 TIME_WAIT State (Continued) Two reasons for the TIME_WAIT state: 2) To allow old duplicate segments to expire in the network To Illustrate this, let s assume we have a TCP connection between :1500 and :21. This connection is closed and some time later another connection is made using the exact same IP addresses and ports The later connection is called an incarnation of the previous connection TCP must prevent old duplicates from a connection from reappearing at some later time and being misinterpreted as belonging to a new incarnation of the same connection To do this TCP will not initiate a new incarnation of a connection if it is in the TIME_WAIT state This ensures that all duplicates from precious incarnations of the connection have expired in the network 24

23 Buffer Sizes and Limitations Certain limits affect the size of IP datagrams: The maximum size of an IPv4 datagram is 65,536 bytes due to its 16-but total length field Many networks have a maximum transmission unit (MTU) which can be dictated by hardware. For example, the Ethernet MTU is 1500 bytes. The minimum link MTU for IPv4 is 68 bytes. The smallest MTU in the path between two hosts is called the path MTU. Normally, the Ethernet MTU of 1500 bytes is the path MTU. When an IP datagram is to be sent out an interface, if the size of the datagram exceeds the link MTU, fragmentation is performed. Fragments are normally reassembled until they reach their final destination. If the don t fragment (DF) bit is set in the IPv4 header, it specifies that the data must not be fragmented. A router receives this packet and has a link with a smaller MTU sends an ICMP error back to sender. 31

24 Buffer Sizes and Limitations (Continued) TCP has a maximum segment size (MSS) that announced to the peer TCP the maximum amount of TCP data that the peer can send per segment The MSS is usually set to the interface MTU minus the fixed sizes of the IP ad TCP headers On Ethernet it s

25 TCP Output Every TCP socket has a send buffer, and we can change the size of it using the SO_SNDBUF option When an application calls write, the kernel copies all the data to from the application buffer to the send buffer If there is insufficient room in the send buffer for all the application s data, the process is put to sleep 33

26 TCP Output (Continued) The kernel does not return from the write until every byte of the application data has been written into the send buffer TCP takes the data in the socket send buffer and sends it to the peer TCP. The peer TCP must acknowledge the data, and as the ACKs arrive from the peer, only then can our TCP discard the acknowledged data from the socket send buffer TCP sends the data in MSS-sized chunks or smaller, adding a TCP header to each segment 34

27 UDP Output With UDP the socket send buffer doesn t exist It has a socket send buffer size, but this is just an upper limit on the maximum-sized UDP datagram Since UDP is unreliable it does not need to keep a copy of the applications data in a buffer UDP packets are more likely to get fragmented than TCP 35

28 TCP Header Bit ( 32 Bits) SOURCE PORT DESTINATION PORT 20 BYTES HEADER LENGTH UNUSED SEQUENCE NUMBER ACKNOWLEDGEMENT NUMBER U R G A C K FLAGS P S H R S T S Y N F I N WINDOW CHECKSUM URGENT POINTER OPTIONS + PADDING 38

29 TCP Header - Ethereal 39

30 TCP Header Details Source Port (16 bits) source TCP user Destination Port (16 bits) destination TCP user Sequence Number (32 bits) sequence number of the first data octet in this segment except when SYN flag is set. If SYN is set this field is the initial sequence number (ISN) Acknowledgement Number (32 bits) a piggybacked acknowledgement, contains the sequence number of the next data octet that the TCP entity expects to receive Header Length (4 bits) number of 32 bit words in the header Unused (6 bits) unused 40

31 TCP Header Details (Continued) Flags (6 bits) URG urgent pointer field significant. ACK - acknowledgement field significant. * PSH push function. RST reset the connection. SYN synchronize the sequence numbers. FIN - no more data from sender. Window (16 bits) flow control credit allocation contains the number of data octets beginning with the one indicated in the acknowledgement field that the receiver is willing to accept. Checksum (16 bits) an error detection calculated over header and data. Urgent Pointer (16 bits) points to the last BYTE in a sequence of urgent data. Options (variable) optional features. * Data Stream Push Note: Normally TCP decides when sufficient data has accumulated to form a segment for transmission. The user can require TCP to transmit all outstanding data up to and including that labeled with a push flag. 41

32 Figure TCP Options TCP/IP Protocol Suite 90

33 TCP OPTIONS SINGLE BYTE: END OF OPTION (Only one may be used and is only necessary if the very last byte of the last 32 bit word is not already the end of an option) NO OPERATION (Used for Padding/aligning an option on a 16 bit or a 32 bit boundary) MULTIPLE BYTE: MAXIMUM SEGMENT SIZE: ID CODE LENGTH WINDOW SCALE FACTOR: BYTE VALUE BYTE VALUE TIMESTAMP (USED IN ROUND TRIP TIME CALCULATIONS): 42

34 Figure End-of-option option TCP/IP Protocol Suite 91

35 TCP Options Each SYN can contain TCP options. Commonly used options include the following: MSS option TCP sending the SYN announces its maximum segment size. That is, the maximum amount of data that it is willing to accept in each TCP segment, on this connection. It s possible to set it using the TCP_MAXSEG socket option. Window Scale option The maximum TCP window size available is 65, 535, because of the corresponding field in the header occupies 16 bits. High-speed and high-delay links need a larger window size to maximize throughput. This options says that the window in the TCP header must be scaled. Up to 14 more bits can be used, scaling the window to about 1 GB Timestamp option - Used in high-speed connections to prevent possible data corruption caused by old, delayed, or duplicated segments. 14

36 Summary We discussed the transport layer in detail Specifics about the TCP s three-way handshake were covered Specifics about TCP s connection termination sequence were discussed We discussed the TCP s TIME_WAIT state We also covered the TCP and UDP buffering by the socket layer 43