The Network Layer and the Transport Layer. IP, TCP and UDP

Size: px

Start display at page:

Download "The Network Layer and the Transport Layer. IP, TCP and UDP"

Barbara Arline Briggs
6 years ago
Views:

1 The Network Layer and the Transport Layer IP, TCP and UDP

2 Verkkokerros Internet-protokolla (IP) toteuttaa verkkokerroksen Tietoliikennepaketit välitetään erilaisten fyysisten kerrosten ylitse koneelta koneelle IP tarjoaa "best effort"-tyyppisen epäluotettavan välityspalvelun Ylemmät kerrokset välittävät datan oikealle sovellukselle, IP tuo sen vain koneelle Verkkokerroksen osoiteavaruus on globaali Toimiakseen verkkokerros tarvitsee: Kehystyksen linkkikerrokselta Lähiverkoissa muunnoksen IP-osoitetta vastaavaan MACosoitteeseen (ARP) Point-to-point -verkoissa tiedon linkkien takana sijaitsevista IPverkoista (reititysprotokollat) Konfiguraatiotiedot (DHCP) 2

3 IP IP = The Internet Protocol Defined in RFC 791 IP sends simple datagrams over network. It provides unreliable and connectionless delivery service. unreliable = no guarantees, ICMP error messages connectionless = each packet is treated as a separate case Large IP packets may be fragmented and reassembled in transmission In practice path MTU discovery is used instead Maximum Transmission Unit 3

4 IP Packet Format 0 16 bits 31 Vers TTL Hdr length Identification TOS Protocol Options... Source IP address Destination IP address Data Flags Total length Fragment offset Header checksum Padding Normal size for IP header is 20 bytes, plus options & padding. 4

5 IP Addresses IP address identifies a network interface. A host can have several interfaces. Current length is 32 bits (IPv4). Future length is 128 bits (IPv6). General syntax: 4 components separated by dots ("dotted quad") decimal numbers (0-255) for example: Addresses have two components, the network id and the host id. 5

6 CIDR (Classless Inter Domain Routing) Arbitrary length host and network fields instead of A, B and C classes Commonly used to make superblocks of C classes for routing (a.k.a. supernetting) In the future may be used to split unused A classes Network mask marks the boundary For example /22 netmask is The number after the slash (/) tells how many bits in the mask are 1, the rest are 0 Host IP address AND network mask = network's IP address RFC 1518,

7 Special Addresses is used for "any" or "no" IP address is local broadcast address 127 followed by hostid is the loopback address E.g NetID followed by all zeros is the network address E.g /24 NetID followed by all ones is network broadcast address E.g /24 7

8 Special Addresses On the Internet there is an agreement that some addresses are not routed to the backbone / / /12 These addresses are called private networks and used for NAT (Network Address Translation) 8

9 Subnetting Large networks are often divided into smaller units Subnetting hides the details of internal network organization for example, /16 ( hosts) could be subnetted to /24 (28 subnets with hosts in each) Host IP address AND network mask = network IP address NetID SubnetID HostID Default netmask Subnet mask 9

10 IP on LAN Usually one physical segment = one IP network Each IP network has a network address and a broadcast address Problem: IP addresses only make sense to the TCP/IP protocol suite, not to the hardware interface Solution: ARP maps IP addresses to hardware addresses If a booting host doesn t know its IP address, DHCP (or RARP, BOOTP) can be used 10

11 IP on LAN Host interfaces must be activated Loopback interface: ifconfig lo Ethernet interface: ifconfig eth broadcast \ netmask Other interfaces Default route route add default

12 ARP (Address Resolution Protocol) A host finds other hosts by broadcasting an ARP query for the IP address The host with correct IP address replies with its hardware address The address pair is added to receivers dynamic ARP cache Features: proxy ARP, gratuitous ARP RFC

13 ARP, an Example gato tsilven 15$ arp -a jalopeno.nixu.fi ( ) at 08:00:20:74:F1:2C [ether] on eth0 fajitas.nixu.fi ( ) at 08:00:20:18:06:14 [ether] on eth0 tapas.nixu.fi ( ) at 08:00:09:6D:B6:44 [ether] on eth0 gato tsilven 16$ ping PING ( ): 56 data bytes 64 bytes from : icmp_seq=0 ttl=64 time=3.0 ms 64 bytes from : icmp_seq=1 ttl=64 time=0.7 ms ping statistics packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0.7/1.8/3.0 ms gato tsilven 17$ arp -a jalopeno.nixu.fi ( ) at 08:00:20:74:F1:2C [ether] on eth0 sueno.nixu.fi ( ) at 00:60:08:54:2D:D9 [ether] on eth0 fajitas.nixu.fi ( ) at 08:00:20:18:06:14 [ether] on eth0 tapas.nixu.fi ( ) at 08:00:09:6D:B6:44 [ether] on eth0 13

14 ARP, an Example bash-2.02# tcpdump -i eth0 -n -t -q\ host tcpdump: listening on eth0 arp who-has tell arp reply is-at 0:60:8:54:2d:d > : icmp: echo request > : icmp: echo reply > : icmp: echo request > : icmp: echo reply 6 packets received by filter 0 packets dropped by kernel 14

15 Bootstrapping an IP Host in the LAN RARP (Reverse ARP), a host broadcasts its hardware address and receives an IP address to use as its own BOOTP (Bootstrap Protocol) is better: IP address and other information can be given Both now replaced by DHCP (Dynamic Host Configuration Protocol) 15

16 DHCP DHCP (Dynamic Host Configuration Protocol) extends BOOTP: automatic assignment of (permanent) IP addresses dynamic assignment for a limited time Extends vendor-specific area from 64 to 312 bytes RFC 1531 Supports distributed configuration Message forwarding or local servers Not a trivial service to configure for large installations 16

17 DHCP Messages are sent using UDP over IP Server in port 67, client in port 68 The DHCP server on the LAN segment is found using a broadcast First packet to from (client does not know its own address) Message types: DISCOVER, OFFER, REQUEST, DECLINE, ACK, NAK, RELEASE The server returns all necessary information IP address, netmask, gateway to the client DNS server s address also Address assignment for limited time or permanently The IP address can be from a pool or static 17

18 DHCP Event Diagram Server1 Client Server 2 DHCPDISCOVER DHCPDISCOVER DHCPOFFER DHCPREQUEST DHCPOFFER DHCPREQUEST DHCPACK DHCPRELEASE 18

19 Static Routing When host has an IP datagram to send, it checks the routing table for the correct destination When a host receives an IP datagram, it checks datagram s destination address if there is a match, IP layer delivers the datagram to correct protocol module else the datagram is silently discarded A (Unix) system can be configured to act as a router in addition to acting as a host routers can forward IP datagrams from one of its interfaces to another 19

20 Router Router is a network component, which passes traffic between networks Two or more network interfaces connected to networks or to other routers For each and every given destination address, router must be able to make routing decision Where (to what interface) I send this packet? Routing decision might also be: No such destination, cannot send This applies also to workstations and servers even though they usually have only one network interface Routing decisions are based on routing table Data structure, which contains information about possible destinations 20

21 Routing table Can be fixed (configured by hand to each device) Static routing Common at the edges of the network, workstations, servers Not feasible on big and redundant networks Usually very robust Can also be dynamic Configured by hand at some point of the network distributed automatically Routers exchange information using routing protocols Routing protocol events (routing updates) affect directly to routing table. This causes interesting dynamic problems Debugging can be painful 21

22 Routing table Internet s0 R e /24 Common case: LAN connected to Internet using serial line Routing table is very simple, a typical case for static routing: Destination /24 * Next hop e0 s0 Comment Local LAN (Ethernet) Serial line to Internet (default route) 22

23 ...Routing table When amount of routers and redundant links increase to non-trivial numbers, something more flexible is needed Static routing can not handle redundant links nor link faults Except on some environments (and even there unreliable) /24 Inet L2, 2Mbps R1 L1, 2 Mbps s0 s1 R3 R2 L2, 64 kbps e /25 23

24 ...Routing table Routing table for router R3 Destination Next hop Cost Comment /24 e0 0 Directly connected /24 s0 1 Fastest route /24 s1 10 Backup via R2 * s0 1 Fastest route via R1 * s1 10 Slower Cost added to routing table, prioritization of redundant routes How we can know which links are up? Routing protocol again! 24

25 ...Routing table What if we can not have default route at all? Internet "backbone" Multihomed network Internet connections from many (> 1) ISPs In this case routing table will be very big And it changes practically all the time Practical example on Internet router ( ) prefixes (routes) Routes consume 16MB of memory Realistic minimum memory for router 64MB 25

26 Routing protocols Routers can talk to other routers and find out the network topology Which paths are available to which networks Which path should be preferred Routing protocols transport information, not IP packets Routing protocols can be divided by algorithm or by area By algorithm: No routing protocol (static routes) Link state protocols (SPF) Distance vector protocols (Bellman-Ford) By area: Routing protocols used internally by one AS, Interior Gateway Protocols Routing protocols used between ASes, Exterior Gateway Protocols 26

27 IPv6 A new version of the Internet Protocol exists The major advantage is longer address fields 128 bits long Some minor advantages More streamlined header structure Support for IPSec security Deployment has started Asian operators have a shortage of IPv4 addresses 3G telephone networks are designed to use IPv6 3GPP R5 defines all IPv6 network Supported by almost all new network software/hardware 27

28 The Transport Layer Part 1

29 Kuljetuskerroksen tehtävä Kuljetuskerros yhdistää sovelluksia Verkkokerros välittää viestejä koneelta toiselle Kuljetuskerros lisää tarkemman osoitteen koneen sisällä Kuljetuskerros toteutetaan eri protokollilla, jotka ovat vaihtoehtoisia TCP tarjoaa luotettavan tavuvirran palveluna sovellukselle UDP tarjoaa epäluotettavan viestinvälityksen palveluna 29

30 UDP UDP = User Datagram Protocol Defined in RFC-768 UDP packet syntax Source port Length Data Destination port UDP checksum Port is a 16-bit application identifier number. Checksum is calculated over both the header and the data. UDP checksum is optional. 30

31 UDP UDP datagram is encapsulated into an IP datagram. IP header UDP header UDP data Unreliable datagram-oriented transportation layer protocol offers little extra functionality besides port numbers simple, fast, light-weight, easy to implement Applications using UDP: DNS, Radius, NTP, SNMP 31

32 A UDP (DNS) Session Snoop 23 $ dig a ;; got answer: ;; QUESTIONS: ;; tapas.nixu.fi, type = A, class = IN ;; ANSWERS: tapas.nixu.fi A ;; AUTHORITY RECORDS: nixu.fi NS ns2.tele.fi. nixu.fi NS ns.nixu.fi. nixu.fi NS ns.tele.fi. ;; ADDITIONAL RECORDS: ns2.tele.fi A ns.nixu.fi A ns.tele.fi A ns.tele.fi A ;; Total query time: 88 msec ;; FROM: mole.nixu.fi to SERVER: ;; MSG SIZE sent: 31 rcvd: riku@mole $ 32

33 DNS Query, Ethernet Header ETHER: Packet 1 arrived at 11:19:24.80 ETHER: Packet size = 73 bytes ETHER: Destination = 8:0:20:74:f1:2c, Sun ETHER: Source = 0:0:3b:80:e:93, ETHER: Ethertype = 0800 (IP) 33

34 DNS Query, IP Header IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx.... = 0 (precedence) IP: = normal delay IP: = normal throughput IP: = normal reliability IP: Total length = 59 bytes IP: Identification = IP: Flags = 0x4 (do not fragment) IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 7e65 IP: Source address = , mole.nixu.fi IP: Destination address = , jalopeno.nixu.fi IP: No options 34

35 DNS Query, UDP Header UDP: Source port = UDP: Destination port = 53 (DNS) UDP: Length = 39 UDP: Checksum = E34A 35

36 DNS Query, Headers and Data 0: f12c b80 0e t.,..;...e. 16: 003b 8b ff11 7e65 c2c : b e34a 000a v...5.'.j... 48: e tapas.nix 64: u.fi... From now on only relevant portions of the headers will be displayed 36

37 DNS Reply Headers ETHER: Packet size = 217 bytes ETHER: Destination = 0:0:3b:80:e:93, ETHER: Source = 8:0:20:74:f1:2c, Sun ETHER: Ethertype = 0800 (IP) IP: Total length = 203 bytes IP: Flags = 0x4 (do not fragmnet) IP: Protocol = 17 (UDP) IP: Header checksum = 8ed6 IP: Source address = , jalopeno.nixu.fi IP: Destination address = , mole.nixu.fi UDP: Source port = 53 UDP: Destination port = UDP: Length = 183 UDP: Checksum = AD48 37

38 DNS Reply Headers and Data 0: b80 0e f12c ;... t.,..e. 16: 00cb 7a ff11 8ed6 c2c : b5 00b7 ad48 000a v..5...h... 48: e tapas.nix 64: c0 0c u.fi some reply data deleted : 087b db00 04c1 d f.{... 38

39 TCP TCP = Transmission Control Protocol Defined in RFC-793 Connection-oriented, reliable, byte-stream service Application data is broken into segments, which are sent as IP datagrams. Features: Checksums, timeouts and flow control Segment reassembly in correct order, discarding duplicate packets Applications using TCP: SMTP, HTTP (WWW), NNTP (News),... 39

40 TCP Segment Format Source port number Destination port number Sequence number Acknowledgment number Hdrlen Reserv. Flags Window size TCP checksum Urgent pointer Options (if any) Data (if any) Ports identify source and destination applications. Sequence number identifies the first byte of the segment. Acknowledge number is the next expected sequence number for incoming data. 40

41 TCP Segment Format Flags URG validates the urgent pointer. ACK acknowledges the synchronization. PSH marks that the data buffer should be flushed to the receiving application. Sometimes considered outdated. RST resets the connection. SYN marks the synchronization phase of connection. FIN ends connection. 41

42 TCP Segment Format Window Size is the number of bytes the receiver is willing to accept Urgent pointer points to the last byte of urgent data. Urgent data feature is used, for example, when a user presses the interrupt key during a telnet session. Options contain often maximum segment size at the start of connection, options can be also used to discover path MTU or to set window scale factor. 42

43 TCP Data Flow Receiver sends acknowledgment for each segment. If a packet gets lost, timeout will ensure it s retransmitted Client Server waiting for ack packet gets lost retransmission ACK 43

44 TCP Data Flow Normally a sliding window technique The window size is changeable, default size is around couple dozen kilobytes depending on the implementation. waiting for ack Client packet 1 packet 2 packet 3 ACK 1 & 2 ACK 3 Server 44

45 Establishing a TCP Connection The three-way handshake active open Client SYN SYN + ACK ACK Server passive open 45

46 Closing a TCP Connection Client Server active close FIN ACK FIN ACK passive close There may be data between the middle ACK and FIN So called half-close is utilized by some applications. Client says I am done sending data but I still want to receive 46

47 TCP shortcomings Window size Maximum window size 64 kb Max bandwidth = max window size / round trip time Error handling TCP assumes that lost packets are lost due to network congestion Internet is built on high-quality fixed trunk connections and LANs The solution is to make the sending window smaller than maximum size On modern wireless networks data is often lost to radio errors The correct solution would be to resend the same data again as soon as possible Instead TCP starts to send slower 47

48 A Snooped SMTP Session 24 $ telnet jalopeno 25 Trying Connected to jalopeno. Escape character is '^]'. 220-jalopeno.nixu.fi ESMTP Sendmail / ready at Sat, 5 Oct :24: ESMTP spoken here QUIT 221 jalopeno.nixu.fi closing connection Connection closed by foreign host. 25 riku@mole $ 48

49 1. SYN Client->Server (Ethernet Header) ETHER: Packet 1 arrived at 10:58:0.62 ETHER: Packet size = 60 bytes ETHER: Destination = 8:0:20:74:f1:2c, Sun ETHER: Source = 0:0:3b:80:e:93, ETHER: Ethertype = 0800 (IP) 49

50 1. SYN Client->Server (IP Header) IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx.... = 0 (precedence) IP: = normal delay IP: = normal throughput IP: = normal reliability IP: Total length = 44 bytes IP: Identification = IP: Flags = 0x4 (do not fragment) IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 6 (TCP) IP: Header checksum = 1188 IP: Source address = , mole.nixu.fi IP: Destination address = , jalopeno.nixu.fi IP: No options 50

51 1. SYN Client->Server (TCP Header) TCP: Source port = TCP: Destination port = 25 (SMTP) TCP: Sequence number = TCP: Acknowledgement number = 0 TCP: Data offset = 24 bytes TCP: Flags = 0x02 TCP: = No urgent pointer TCP: = No acknowledgement TCP: = No push TCP: = No reset TCP: = Syn TCP: = No Fin TCP: Window = 8760 TCP: Checksum = 0x17a1 TCP: Urgent pointer = 0 TCP: Options: (4 bytes) TCP: - Maximum segment size = 1460 bytes 51

52 1. SYN Client->Server (SMTP Data) SMTP: "" From now on only relevant portions of the headers will be displayed 52

53 2. SYN+ACK Server->Client ETHER: Destination = 0:0:3b:80:e:93, ETHER: Source = 8:0:20:74:f1:2c, Sun ETHER: Ethertype = 0800 (IP) IP: Flags = 0x4 (do not fragment) IP: Protocol = 6 (TCP) IP: Source address = , jalopeno.nixu.fi IP: Destination address = , mole.nixu.fi TCP: Source port = 25 TCP: Destination port = TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x12 (ACK, SYN) TCP: Options: (4 bytes) TCP: - Maximum segment size = 1460 bytes SMTP: "" 53

54 3. ACK Client->Server ETHER: Destination = 8:0:20:74:f1:2c, Sun ETHER: Source = 0:0:3b:80:e:93, ETHER: Ethertype = 0800 (IP) IP: Flags = 0x4 (do not fragment) IP: Protocol = 6 (TCP) IP: Source address = , mole.nixu.fi IP: Destination address = , jalopeno.nixu.fi TCP: Source port = TCP: Destination port = 25 (SMTP) TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x10 (ACK) TCP: No options SMTP: "" 54

55 4. Data Server->Client ETHER: Destination = 0:0:3b:80:e:93, ETHER: Source = 8:0:20:74:f1:2c, Sun ETHER: Ethertype = 0800 (IP) IP: Flags = 0x4 (do not fragment) IP: Protocol = 6 (TCP) IP: Source address = , jalopeno.nixu.fi IP: Destination address = , mole.nixu.fi TCP: Source port = 25 TCP: Destination port = TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x18 (ACK, PSH) SMTP: "220-jalopeno.nixu.fi ESMTP Sendmail / ready" 55

56 5. Reply Client->Server ETHER: Destination = 8:0:20:74:f1:2c, Sun ETHER: Source = 0:0:3b:80:e:93, ETHER: Ethertype = 0800 (IP) IP: Flags = 0x4 (do not fragment) IP: Protocol = 6 (TCP) IP: Source address = , mole.nixu.fi IP: Destination address = , jalopeno.nixu.fi IP: No options TCP: Source port = TCP: Destination port = 25 (SMTP) TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x10 (ACK) SMTP: "" 56

57 6. Data Client->Server ETHER: Destination = 8:0:20:74:f1:2c, Sun ETHER: Source = 0:0:3b:80:e:93, ETHER: Ethertype = 0800 (IP) IP: Flags = 0x4 (do not fragment) IP: Protocol = 6 (TCP) IP: Source address = , mole.nixu.fi IP: Destination address = , jalopeno.nixu.fi TCP: Source port = TCP: Destination port = 25 (SMTP) TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x18 (ACK, PSH) SMTP: "QUIT\r\n" 57

58 7. Ack Server->Client (Containing Data) ETHER: Destination = 0:0:3b:80:e:93, ETHER: Source = 8:0:20:74:f1:2c, Sun ETHER: Ethertype = 0800 (IP) IP: Flags = 0x4 (do not fragment) IP: Protocol = 6 (TCP) IP: Source address = , jalopeno.nixu.fi IP: Destination address = , mole.nixu.fi TCP: Source port = 25 TCP: Destination port = TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x18 (ACK, PSH) SMTP: "221 jalopeno.nixu.fi closing connection\r\n" 58

59 8. Server Starts Closing ETHER: Destination = 0:0:3b:80:e:93, ETHER: Source = 8:0:20:74:f1:2c, Sun ETHER: Ethertype = 0800 (IP) IP: Protocol = 6 (TCP) IP: Source address = , jalopeno.nixu.fi IP: Destination address = , mole.nixu.fi TCP: Source port = 25 TCP: Destination port = TCP: Sequence number = TCP: Acknowledgement number = TCP: Data offset = 20 bytes TCP: Flags = 0x11 (ACK, FIN) SMTP: "" 59

60 9. Client Acks Previous Data ETHER: Destination = 8:0:20:74:f1:2c, Sun ETHER: Source = 0:0:3b:80:e:93, ETHER: Ethertype = 0800 (IP) IP: Protocol = 6 (TCP) IP: Source address = , mole.nixu.fi IP: Destination address = , jalopeno.nixu.fi TCP: Source port = TCP: Destination port = 25 (SMTP) TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x10 (ACK) SMTP: "" 60

61 10. Client Starts Closing as Well ETHER: Destination = 8:0:20:74:f1:2c, Sun ETHER: Source = 0:0:3b:80:e:93, ETHER: Ethertype = 0800 (IP) IP: Protocol = 6 (TCP) IP: Source address = , mole.nixu.fi IP: Destination address = , jalopeno.nixu.fi TCP: Source port = TCP: Destination port = 25 (SMTP) TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x11 (ACK, FIN) SMTP: "" 61

62 11.Server Acks Closing ETHER: Destination = 0:0:3b:80:e:93, ETHER: Source = 8:0:20:74:f1:2c, Sun ETHER: Ethertype = 0800 (IP) IP: Flags = 0x4 (do not fragment) IP: Protocol = 6 (TCP) IP: Source address = , jalopeno.nixu.fi IP: Destination address = , mole.nixu.fi TCP: Source port = 25 TCP: Destination port = TCP: Sequence number = TCP: Acknowledgement number = TCP: Flags = 0x10 (ACK) SMTP: "" 62

63 Automatic Repeat Request

64 Reliable Communications with Retransmission How to transport data units over an unreliable data link in a reliable way? End to End E.g.. TCP Hop by Hop E.g..X.25, HDLC Answer: ARQ Automatic Repeat Request ARQ is an abstract concept, not a protocol itself Used in many protocols for reliable transmission There are several different versions of the basic concept 64

65 Basic ARQ Data (SDUs) is divided/packaged to packets (PDUs) that contain a header and checksum These are called information frames There are also empty packets called control frames And there is a timeout mechanism Sender 1. A packet is sent 3. A packet is re-sent after a timeout Packets in transit 2. A packet is lost Receiver 4. A simple acknowledgment is sent Problem: what if a frame is received and acknowledged after the timeout at sender s end? 65

66 ARQ Sequence Numbers It is possible for the sender and receiver to get out of synchronization A problem that all protocols must address Sender and receiver can be synchronized by having a sequence number in each frame In theory one bit sequence number would be sufficient for stop-and-wait ARQ Stop-and-wait means that only one frame is in transmission at one time One bit sequence number is not sufficient if the network may duplicate frames Stop and wait is not very efficient in most cases Larger sequence numbers allow multiple frames to be in transit 66

67 ARQ Control Frames ACK, acknowledgment NAK, negative acknowledgment ENQ, enquiry 67

68 ARQ Stop-and-Wait Frame Loss Handling One frame is sent at a time Rule: the information (data transporting) frames are ACKed, control frames not When a frame is lost: 1) Sender retransmits after timeout or 2) ENQ is replied with the last frame sent Sender sends ENQ after timeout Receiver sends last ACK sent Enables re-synchronization 68

69 Go-Back-N ARQ Frame Loss Handling A sufficiently large sequence number and a sliding window are used Receiver ACKs only frames in sequence When an information frame is lost, it and all frames sent after it must be retransmitted Frame loss is recognized either from timeout or the receiver sends a NAK when it receives a frame out of sequence The receiver requires a buffer the size of one frame The sender has to have a buffer that holds all frames that have been transmitted but not ACKed If the ACK control frame is lost, a later ACK can replace it This increases the efficiency of bandwidth usage compared to stop-and-wait ARQ Latency is a problem for stop-and-wait ARQ TCP implements this 69

70 Selective Repeat ARQ Frame Loss Handling When the receiver receives a frame out of sequence, it sends a NAK for the missing frame and that frame only is resent More complex for the receiver, requires a larger receive buffer This is more efficient for channels with large error rates than Go-Back-N ARQ 70

The Transport Layer. Part 1

The Transport Layer. Part 1 The Transport Layer Part 1 2 OVERVIEW Part 1 User Datagram Protocol Transmission Control Protocol ARQ protocols Part 2 TCP congestion control Mowgli XTP SCTP WAP 3 Transport Layer Protocols Connect applications