* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download 3rd Edition: Chapter 2
Parallel port wikipedia , lookup
Computer network wikipedia , lookup
TCP congestion control wikipedia , lookup
Airborne Networking wikipedia , lookup
Deep packet inspection wikipedia , lookup
Network tap wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Internet protocol suite wikipedia , lookup
Recursive InterNetwork Architecture (RINA) wikipedia , lookup
CPE 400 / 600 Computer Communication Networks Lecture 8 Chapter 3 Transport Layer slides are modified from J. Kurose & K. Ross Chapter 3: Transport Layer Goals:  understand principles behind transport layer services:     multiplexing/demultiplexing reliable data transfer flow control congestion control  learn about transport layer protocols in the Internet:  UDP: connectionless transport  TCP: connection-oriented transport  TCP congestion control Transport Layer 2 Lecture 8 outline  3.1 Transport-layer services  3.2 Multiplexing and demultiplexing  3.3 Connectionless transport: UDP Transport Layer 3 Transport services and protocols  provide logical communication between app processes running on different hosts  transport protocols run in end systems  send side: breaks app messages into segments, passes to network layer  rcv side: reassembles segments into messages, passes to app layer  more than one transport protocol available to apps  Internet: TCP and UDP application transport network data link physical application transport network data link physical Transport Layer 4 Transport vs. network layer  network layer: logical communication between hosts  transport layer: logical communication between processes  relies on, enhances, network layer services Household analogy: 12 kids sending letters to 12 kids  processes = kids  app messages = letters in envelopes  hosts = houses  transport protocol = Ann and Bill  network-layer protocol = postal service Transport Layer 5 Internet transport-layer protocols  reliable, in-order delivery (TCP)    congestion control flow control connection setup  unreliable, unordered delivery (UDP)  no-frills extension of “besteffort” IP application transport network data link physical network data link physical network data link physical network data link physical network network data link physical data link physical network data link physical application transport network data link physical  services not available:  delay guarantees  bandwidth guarantees Transport Layer 6 Lecture 8 outline  3.1 Transport-layer services  3.2 Multiplexing and demultiplexing  3.3 Connectionless transport: UDP Transport Layer 7 Multiplexing/demultiplexing Demultiplexing at rcv host: delivering received segments to correct socket = socket = process P3 application P1 P1 application transport transport network network link link physical physical host 1 host 2 Multiplexing at send host: gathering data from multiple sockets, enveloping data with header (later used for demultiplexing) P2 P4 application transport network link physical host 3 Transport Layer 8 How demultiplexing works  host receives IP datagrams    each datagram has source IP address, destination IP address each datagram carries 1 transport-layer segment each segment has source, destination port number  host uses IP addresses & port numbers to direct segment to appropriate socket 32 bits source port # dest port # other header fields application data (message) TCP/UDP segment format Transport Layer 9 Connectionless demultiplexing  Create sockets with port numbers: DatagramSocket mySocket1 = new DatagramSocket(12534); DatagramSocket mySocket2 = new DatagramSocket(12535);  UDP socket identified by two-tuple: (dest IP address, dest port number)  When host receives UDP segment:  checks destination port number in segment  directs UDP segment to socket with that port number  IP datagrams with different source IP addresses and/or source port numbers directed to same socket Transport Layer 10 Connectionless demux (cont) DatagramSocket serverSocket = new DatagramSocket(6428); P2 P1 P1 P3 SP: 6428 SP: 6428 DP: 9157 DP: 5775 SP: 9157 client IP: A DP: 6428 SP: 5775 server IP: C DP: 6428 Client IP:B SP provides “return address” Transport Layer 11 Connection-oriented demux  TCP socket identified by 4-tuple:  source IP address  source port number  dest IP address  dest port number  recv host uses all four values to direct segment to appropriate socket  Server may support many simultaneous TCP sockets:  each socket identified by its own 4-tuple  Web servers have different sockets for each connecting client  non-persistent HTTP will have different socket for each request Transport Layer 12 Connection-oriented demux (cont) P2 P1P3 P4 P5 P6 P1 SP: 5775 DP: 80 S-IP: B D-IP:C SP: 9157 client IP: A DP: 80 S-IP: A D-IP:C SP: 9157 server IP: C DP: 80 S-IP: B D-IP:C Client IP:B Transport Layer 13 Connection-oriented demux: Threaded Web Server P1 P2 P1P3 P4 SP: 5775 DP: 80 S-IP: B D-IP:C SP: 9157 client IP: A DP: 80 S-IP: A D-IP:C SP: 9157 server IP: C DP: 80 S-IP: B D-IP:C Client IP:B Transport Layer 14 Lecture 8 outline  3.1 Transport-layer services  3.2 Multiplexing and demultiplexing  3.3 Connectionless transport: UDP Transport Layer 15 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 segment header  no congestion control: UDP can blast away as fast as desired Transport Layer 16 UDP: more  often used for streaming multimedia apps  loss tolerant  rate sensitive  other UDP uses  DNS  SNMP Length, in bytes of UDP segment, including header  reliable transfer over UDP: add reliability at application layer  application-specific error recovery! 32 bits source port # dest port # length checksum Application data (message) UDP segment format Transport Layer 17 UDP checksum Goal: detect “errors” (e.g., flipped bits) in transmitted segment Sender: Receiver:  treat segment contents as  compute checksum of sequence of 16-bit integers  checksum: addition (1’s complement sum) of segment contents  sender puts checksum value into UDP checksum field received segment  check if computed checksum equals checksum field value:  NO - error detected  YES - no error detected. But maybe errors nonetheless? More later …. Transport Layer 18 Internet Checksum Example  Note  When adding numbers, a carryout from the most significant bit needs to be added to the result  Example: add two 16-bit integers 1 1 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 wraparound 1 1 0 1 1 1 0 1 1 1 0 1 1 1 0 1 1 sum 1 1 0 1 1 1 0 1 1 1 0 1 1 1 1 0 0 checksum 1 0 1 0 0 0 1 0 0 0 1 0 0 0 0 1 1 Transport Layer 19 Lecture 8 summary  Transport-layer services  UDP  TCP  Multiplexing and demultiplexing  UDP: Dest IP, Dest port  TCP: Src IP, Src port, Dest IP, Dest port  Connectionless transport: UDP  segment format  checksum Transport Layer 20
 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
									 
                                             
                                             
                                             
                                             
                                             
                                             
                                             
                                             
                                            