DOCSLIB.ORG

Chapter 7 Internet Protocol Version 4 (Ipv4)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Chapter 7 Internet Protocol Version 4 (Ipv4) Chapter 7 Internet Protocol Version 4 (IPv4) Kyung Hee University 1 7.1 Introduction The transmission mechanism used by the TCP/IP Unreliable and connectionless datagram protocol Best-effort delivery service IP packets can be corrupted, lost, arrive out of order, or delayed and may create congestion for the network Each datagram is handled independently Each datagram can follow a different route to destination Datagram sent by the same source to the same destination could arrive out of order. Kyung Hee University 2 Position of IP in TCP/IP protocol suite Kyung Hee University 3 7.2 Datagrams Datagrams are packets in the network layer Datagram is a variable-length packet consisting of header and data. The header is 20 to 60 bytes, contains information essential to routing and delivery It is customary in TCP/IP to show the header in 4-byte section Field in Header Version(VER) – the version of IP protocol (4-bit) Header length(HLEN) – total length of the datagram header in 4-byte words. Kyung Hee University 4 IP Datagram Kyung Hee University 5 IP Datagram TOS(Type of Service) – 8-bit x x x 0 0 0 x x x x x 0 Precedence x x x x 1 1 interpretation x x x x 0 1 Differential service interpretation Category Codepoint Assigning Authority 1 XXXXX0 Internet : 24 services 2 XXXX11 Local 3 XXXX01 Temporary or experiment Kyung Hee University 6 IP Datagram Total Length 16-bit field (limited to 65,535 bytes) Define the total length of the IP datagram in bytes Length of data = total length – header length Encapsulation of a small datagram in an Ethernet frame Figure 7.4 Encapsulation of a small datagram in an Ethernet frame Kyung Hee University 7 IP Datagram Identification – used in fragmentation Flags – used in fragmentation Fragmentation offset – used in fragmentation Time to love – limited life time of datagram Protocol – the higher level protocol that uses the services of the IP layer Fig. 7.5 Multiplexing Kyung Hee University 8 IP Datagram Checksum – Check errors Source address – The IP address of source Destination address – The IP address of destination Kyung Hee University 9 Example 7.1 An IP packet has arrived with the first 8 bit shown: The receiver discards the packet. Why? Solution There is an error in this packet. The 4 left-most bit(0100) show the version, which is correct. The next 4 bit(0010) show the wrong header length(2 × 4 = 8). The minimum number of byte in the header must be 20. The packet has been corrupted in transmission. Kyung Hee University 10 Example 7.2 In an IP packet, the value of HLEN is 1000 in binary. How many byte of option are being carried by this packet? Solution The HLEN value is 8, which means the total number of bytes in the header is 8 × 4 or 32 bytes. The first 20 bytes are the base header, the next 12 bytes are the option. Kyung Hee University 11 Example 7.3 In an IP packet, the value of HLEN is 516 and the value of the total length field is 002816. How many bytes of data are being carried by this packet? Solution The HLEN value is 5, which mean the total number of bytes in the header is 5 × 4 or 20 bytes (no options). The total length is 40 bytes, which means the packet is carrying 20 bytes of data (40 − 20). Kyung Hee University 12 7.3 Fragmentation The format and size of the received frame depend on the protocol used by the physical network When a datagram encapsulated in a frame, the total size of the datagram must be less than MTU(Maximum Transfer Unit) size We must divide the datagram to make it possible to pass through the network; this is called fragmentation Kyung Hee University 13 MTU(Maximum Transfer Unit) IP datagram MTU Header Maximum length of data that can be encapsulated in a frame Trailer Frame Kyung Hee University 14 Fragmentation The value of the MTU differs from one physical network protocol to another Kyung Hee University 15 Fields Related to Fragmentation Identification – All fragments have the same identification value Flag – 3-bit field Fragmentation offset – 13-bit field, the relative position of this fragment with respect to the whole datagram Kyung Hee University 16 Fragmentation Example Offset = 0000/8 = 0 0000 1399 Offset = 1400/8 = 175 1400 2799 Offset = 2800/8 = 350 2800 3999 Kyung Hee University 17 Detailed Fragmentation Example 1420 14,567 1 000 Bytes 0000–1399 820 14,567 1 175 Fragment 1 4020 14,567 0 000 1420 Bytes 1400–2199 14,567 1 175 Fragment 2.1 Bytes 0000–3999 Bytes 1400–2799 Original datagram Fragment 2 1220 14,567 0 350 Bytes 2800–3999 Fragment 3 Kyung Hee University 18 Example 7.5 A packet has arrived with an M bit value of 0. Is this first fragment, or a middle fragment? Do we know if the packet was fragment? Solution If the M bit is 0, it means that there are no more fragment; the fragment is the last one. However, we cannot say if the original packet was fragment or not. A nonfragmented packet is considered the last fragment. Kyung Hee University 19 Example 7.9 A packet has arrived in which the offset value is 100, the value of HLEN is 5 and the value of the total length field is 100. What is the number of the first byte and the last byte? Solution The first byte number is 100 × 8 = 800. The total length is 100bytes and the header length is 20bytes (5 × 4), which means that there are 80 bytes in this datagram. If the first byte number is 800, the last byte number must be 879. Kyung Hee University 20 7.4 Options Type field (8-bit) : Fixed length Copy : Control the presence of the option in fragmentation Class : Define the general purpose of the option Number : Define the type of option Length field (8-bit) : Fixed length The total length of the option Value field : Variable length Contain the data that specific options require Kyung Hee University 21 Option Format 8 bits 8 bits Variable length Type Length Value Number Class 00000 End of option 00001 No operation Copy 00 Datagram control 00011 Loose source route 01 Reserved 00100 Timestamp 0 Copy only in first fragment 10 Debugging and management 00111 Record route 1 Copy into all fragments 11 Reserved 01001 Strict source route Kyung Hee University 22 Categories of Options Kyung Hee University 23 No Operation Option 1-byte option used as a filter between options Kyung Hee University 24 End-of-Option Option 1-byte option used for padding at the end of the option field Kyung Hee University 25 Record-Route Option Used to record the Internet routers that handle the datagram Kyung Hee University 26 Record-Route Concept 7 15 4 7 15 8 7 15 12 7 15 16 140.10.6.3 140.10.6.3 140.10.6.3 200.14.7.9 200.14.7.9 138.6.22.26 67.34.30.6 138.6.25.40 2 6 4 3 2 4 2 9 . 1 . 6 0 5 2 7 . 7 . 1 . 2 0 . 0 . 4 4 1 4 1 6 1 . 1 . 1 . 0 . 0 8 0 0 4 7 4 3 0 0 1 6 1 1 2 2 67.0.0.0/24 140.10.0.0/16 200.14.7.0/24 138.6.0.0/16 Network Network Network Network Kyung Hee University 27 Strict-Source-Route Option Used by source to predetermine a route for the datagram as it travels through the Internet All of routers defined in the option must be visited by the datagram Kyung Hee University 28 Strict-Source-Route Concept Source: 67.34.30.6 Source: 67.34.30.6 Source: 67.34.30.6 Source: 67.34.30.6 Destination: 67.14.10.22 Destination:140.10.5.4 Destination:200.14.7.14 Destination:138.6.25.40 137 15 4 137 15 8 137 15 12 137 15 16 140.10.5.4 67.14.10.22 67.14.10.22 67.14.10.22 200.14.7.14 200.14.7.14 140.10.5.4 140.10.5.4 138.6.25.40 138.6.25.40 138.6.25.40 200.14.7.14 67.34.30.6 138.6.25.40 2 6 4 3 2 4 2 9 . 1 . 6 0 5 2 7 . 7 . 1 . 2 0 . 0 . 4 4 1 4 1 6 1 . 1 . 1 . 0 . 0 8 0 0 4 7 4 3 0 0 1 6 1 1 2 2 67.0.0.0/24 140.10.0.0/16 200.14.7.0/24 138.6.0.0/16 Network Network Network Network Kyung Hee University 29 Loose-Source-Route Option Similar to the strict source route, but it is more relaxed. Each router in the list must be visited, but the datagram can visit other routers as well Kyung Hee University 30 Timestamp Option Used to record the time of datagram processing by a router The time is expressed in miliseconds from Universal Time Kyung Hee University 31 Use of Flag in Timestamp Flag 0 : each router adds only the timestamp in the provided field Flag 1 : each router must add its outgoing IP address and the timestamp Flag 3 : the IP addresses are given, and each router must check the given IP address with its own incoming IP address 1 0 Kyung Hee University 32 Timestamp Concept 68 28 5 0 1 68 28 13 0 1 68 28 21 0 1 68 28 29 0 1 140.10.6.3 140.10.6.3 140.10.6.3 36000000 36000000 36000000 200.14.7.9 200.14.7.9 36000012 36000012 138.6.22.26 36000020 67.34.30.6 2 6 4 3 2 4 2 9 .
Load more

Recommended publications
  • IP Datagram ICMP Message Format ICMP Message Types
    ICMP Internet Control Message Protocol ICMP is a protocol used for exchanging control messages. CSCE 515: Two main categories Query message Computer Network Error message Programming Usage of an ICMP message is determined by type and code fields ------ IP, Ping, Traceroute ICMP uses IP to deliver messages. Wenyuan Xu ICMP messages are usually generated and processed by the IP software, not the user process. Department of Computer Science and Engineering University of South Carolina IP header ICMP Message 20 bytes CSCE515 – Computer Network Programming IP Datagram ICMP Message Format 1 byte 1 byte 1 byte 1 byte VERS HL Service Total Length Datagram ID FLAG Fragment Offset 0781516 31 TTL Protocol Header Checksum type code checksum Source Address Destination Address payload Options (if any) Data CSCE515 – Computer Network Programming CSCE515 – Computer Network Programming ICMP Message Types ICMP Address Mask Request and Reply intended for a diskless system to obtain its subnet mask. Echo Request Id and seq can be any values, and these values are Echo Response returned in the reply. Destination Unreachable Match replies with request Redirect 0781516 31 Time Exceeded type(17 or 18) code(0) checksum there are more ... identifier sequence number subnet mask CSCE515 – Computer Network Programming CSCE515 – Computer Network Programming ping Program ICMP Echo Request and Reply Available at /usr/sbin/ping Test whether another host is reachable Send ICMP echo_request to a network host -n option to set number of echo request to send
    [Show full text]
  • Transport Layer Chapter 6
    Transport Layer Chapter 6 • Transport Service • Elements of Transport Protocols • Congestion Control • Internet Protocols – UDP • Internet Protocols – TCP • Performance Issues • Delay-Tolerant Networking Revised: August 2011 CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 The Transport Layer Responsible for delivering data across networks with the desired Application reliability or quality Transport Network Link Physical CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 Transport Service • Services Provided to the Upper Layer » • Transport Service Primitives » • Berkeley Sockets » • Socket Example: Internet File Server » CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 Services Provided to the Upper Layers (1) Transport layer adds reliability to the network layer • Offers connectionless (e.g., UDP) and connection- oriented (e.g, TCP) service to applications CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 Services Provided to the Upper Layers (2) Transport layer sends segments in packets (in frames) Segment Segment CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice Hall and D. Wetherall, 2011 Transport Service Primitives (1) Primitives that applications might call to transport data for a simple connection-oriented service: • Client calls CONNECT, SEND, RECEIVE, DISCONNECT • Server calls LISTEN, RECEIVE, SEND, DISCONNECT Segment CN5E by Tanenbaum & Wetherall, © Pearson Education-Prentice
    [Show full text]
  • Internet Protocol Suite
    InternetInternet ProtocolProtocol SuiteSuite Srinidhi Varadarajan InternetInternet ProtocolProtocol Suite:Suite: TransportTransport • TCP: Transmission Control Protocol • Byte stream transfer • Reliable, connection-oriented service • Point-to-point (one-to-one) service only • UDP: User Datagram Protocol • Unreliable (“best effort”) datagram service • Point-to-point, multicast (one-to-many), and • broadcast (one-to-all) InternetInternet ProtocolProtocol Suite:Suite: NetworkNetwork z IP: Internet Protocol – Unreliable service – Performs routing – Supported by routing protocols, • e.g. RIP, IS-IS, • OSPF, IGP, and BGP z ICMP: Internet Control Message Protocol – Used by IP (primarily) to exchange error and control messages with other nodes z IGMP: Internet Group Management Protocol – Used for controlling multicast (one-to-many transmission) for UDP datagrams InternetInternet ProtocolProtocol Suite:Suite: DataData LinkLink z ARP: Address Resolution Protocol – Translates from an IP (network) address to a network interface (hardware) address, e.g. IP address-to-Ethernet address or IP address-to- FDDI address z RARP: Reverse Address Resolution Protocol – Translates from a network interface (hardware) address to an IP (network) address AddressAddress ResolutionResolution ProtocolProtocol (ARP)(ARP) ARP Query What is the Ethernet Address of 130.245.20.2 Ethernet ARP Response IP Source 0A:03:23:65:09:FB IP Destination IP: 130.245.20.1 IP: 130.245.20.2 Ethernet: 0A:03:21:60:09:FA Ethernet: 0A:03:23:65:09:FB z Maps IP addresses to Ethernet Addresses
    [Show full text]
  • The Internet Protocol, Version 4 (Ipv4)
    Today’s Lecture I. IPv4 Overview The Internet Protocol, II. IP Fragmentation and Reassembly Version 4 (IPv4) III. IP and Routing IV. IPv4 Options Internet Protocols CSC / ECE 573 Fall, 2005 N.C. State University copyright 2005 Douglas S. Reeves 1 copyright 2005 Douglas S. Reeves 2 Internet Protocol v4 (RFC791) Functions • A universal intermediate layer • Routing IPv4 Overview • Fragmentation and reassembly copyright 2005 Douglas S. Reeves 3 copyright 2005 Douglas S. Reeves 4 “IP over Everything, Everything Over IP” IP = Basic Delivery Service • Everything over IP • IP over everything • Connectionless delivery simplifies router design – TCP, UDP – Dialup and operation – Appletalk – ISDN – Netbios • Unreliable, best-effort delivery. Packets may be… – SCSI – X.25 – ATM – Ethernet – lost (discarded) – X.25 – Wi-Fi – duplicated – SNA – FDDI – reordered – Sonet – ATM – Fibre Channel – Sonet – and/or corrupted – Frame Relay… – … – Remote Direct Memory Access – Ethernet • Even IP over IP! copyright 2005 Douglas S. Reeves 5 copyright 2005 Douglas S. Reeves 6 1 IPv4 Datagram Format IPv4 Header Contents 0 4 8 16 31 •Version (4 bits) header type of service • Functions version total length (in bytes) length (x4) prec | D T R C 0 •Header Length x4 (4) flags identification fragment offset (x8) 1. universal 0 DF MF s •Type of Service (8) e time-to-live (next) protocol t intermediate layer header checksum y b (hop count) identifier •Total Length (16) 0 2 2. routing source IP address •Identification (16) 3. fragmentation and destination IP address reassembly •Flags (3) s •Fragment Offset ×8 (13) e t 4. Options y IP options (if any) b •Time-to-Live (8) 0 4 ≤ •Protocol Identifier (8) s e t •Header Checksum (16) y b payload 5 •Source IP Address (32) 1 5 5 6 •Destination IP Address (32) ≤ •IP Options (≤ 320) copyright 2005 Douglas S.
    [Show full text]
  • The Original Version of This Chapter Was Revised: the Copyright Line Was Incorrect
    The original version of this chapter was revised: The copyright line was incorrect. This has been corrected. The Erratum to this chapter is available at DOI: 10.1007/978-0-387-35516-0_20 H. Ural et al. (eds.), Testing of Communicating Systems © IFIP International Federation for Information Processing 2000 114 TESTING OF COMMUNICATING SYSTEMS protocols in TTCN mainly by ETSI and ITU-T. Most of the telecom vendor companies use TTCN in their internal test procedures because of its usefulness in protocol testing. Tools exist supporting the writing and execution of TTCN test cases as well as generating them from formal specifications written in SDL (Specification Description Language) or MSC (Message Sequence Chart). Telecom service providers are also executing conformance testing on the products they buy to check if it fulfills the requirements described in the protocol standards. This is a main step assuring the interoperability of the heterogeneous products built in their network. In the datacom world this kind of strict testing is not applied though interoperability of products of different vendors is becoming to be as important as for telecom networks with the growing number of datacom product vendors and the growing reliability requirements. The interoperability events use ad hoc test scenarios, and no test results are really available for the potential customers to support their decision which product to buy. This paper presents an application of the conformance testing methodology on IPv6 testing. In section two we present the main features of IPv6. Section 3 summarizes ideas why conformance testing would be useful for the Internet protocols.
    [Show full text]
  • 14. TCP/IP Protocol Suite Contents
    11/10/2010 14. TCP/IP Protocol Suite Contents a. TCP/IP – Internet – OSI b. Network level – IP protocol c. Addressing and sub-networks d. Other network-level protocols e. Transport level 1 11/10/2010 a. TCP/IP – Internet – OSI b. Network level – IP protocol 2 11/10/2010 Position of IPv4 in TCP/IP protocol suite IPv4 datagram format 3 11/10/2010 Service type or differentiated services The precedence subfield was part of version 4, but never used. 4 11/10/2010 Types of service Default types of service 5 11/10/2010 Values for codepoints The total length field defines the total length of the datagram including the header. 6 11/10/2010 Encapsulation of a small datagram in an Ethernet frame Protocol field and encapsulated data 7 11/10/2010 Protocol values Example 1 An IPv4 packet has arrived with the first 8 bits as shown: 01000010 Thereceiver discar ds the packtket. Why? Solution There is an error in this packet. The 4 leftmost bits (0100) show the version, which is correct. The next 4 bits (0010) show an invalid header length (2 × 4 = 8). The minimum number of bytes in the header must be 20. The packet has been corrupted in transmission. 8 11/10/2010 Example 2 In an IPv4 packet, the value of HLEN is 1000 in binary. How many bytes of options are being carried by this packet? Solution The HLEN value is 8, which means the total number of bytes in the header is 8 × 4, or 32 bytes. The first 20 bytes are the base header, the next 12 bytes are the options.
    [Show full text]
  • (DAB); Internet Protocol (IP) Datagram Tunnelling
    ETSI TS 101 735 V1.1.1 (2000-07) Technical Specification Digital Audio Broadcasting (DAB); Internet Protocol (IP) datagram tunnelling European Broadcasting Union Union Européenne de Radio-Télévision EBU·UER 2 ETSI TS 101 735 V1.1.1 (2000-07) Reference DTS/JTC-DAB-12 Keywords audio, broadcasting, DAB, data, digital, internet, IP, protocol ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.:+33492944200 Fax:+33493654716 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/ If you find errors in the present document, send your comment to: [email protected] Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © European Telecommunications Standards Institute 2000. © European Broadcasting Union 2000.
    [Show full text]
  • Higher Layer Protocols: UDP, TCP, ATM, MPLS
    Higher Layer Protocols: UDP, TCP, ATM, MPLS Eytan Modiano Massachusetts Institute of Technology Eytan Modiano Slide 1 The TCP/IP Protocol Suite • Transmission Control Protocol / Internet Protocol • Developed by DARPA to connect Universities and Research Labs Four Layer model Applications Telnet, FTP, email, etc. Transport TCP, UDP Network IP, ICMP, IGMP Link Device drivers, interface cards TCP - Transmission Control Protocol UDP - User Datagram Protocol IP - Internet Protocol Eytan Modiano Slide 2 User Datagram Protocol (UDP) • Transport layer protocol – Delivery of messages across network • Datagram oriented – Unreliable No error control mechanism – Connectionless – Not a “stream” protocol • Max packet length 65K bytes • UDP checksum – Covers header and data – Optional Can be used by applications • UDP allows applications to interface directly to IP with minimal additional processing or protocol overhead Eytan Modiano Slide 3 UDP header format IP Datagram IP header UDP header data 16 bit source port number 16 bit destination port number 16 bit UDP length 16 bit checksum Data • The port numbers identifie the sending and receiving processes – I.e., FTP, email, etc.. – Allow UDP to multiplex the data onto a single stream • UDP length = length of packet in bytes – Minimum of 8 and maximum of 2^16 - 1 = 65,535 bytes • Checksum covers header and data – Optional, UDP does not do anything with the checksum Eytan Modiano Slide 4 Transmission Control Protocol (TCP) • Transport layer protocol – Reliable transmission of messages • Connection oriented
    [Show full text]
  • Controlling Gpios on Rpi Using Ping Command
    Ver. 3 Department of Engineering Science Lab – Controlling PI Controlling Raspberry Pi 3 Model B Using PING Commands A. Objectives 1. An introduction to Shell and shell scripting 2. Starting a program at the Auto-start 3. Knowing your distro version 4. Understanding tcpdump command 5. Introducing tshark utility 6. Interfacing RPI to an LCD 7. Understanding PING command B. Time of Completion This laboratory activity is designed for students with some knowledge of Raspberry Pi and it is estimated to take about 5-6 hours to complete. C. Requirements 1. A Raspberry Pi 3 Model 3 2. 32 GByte MicroSD card à Give your MicroSD card to the lab instructor for a copy of Ubuntu. 3. USB adaptor to power up the Pi 4. Read Lab 2 – Interfacing with Pi carefully. D. Pre-Lab Lear about ping and ICMP protocols. F. Farahmand 9/30/2019 1 Ver. 3 Department of Engineering Science Lab – Controlling PI E. Lab This lab has two separate parts. Please make sure you read each part carefully. Answer all the questions. Submit your codes via Canvas. 1) Part I - Showing IP Addresses on the LCD In this section we learn how to interface an LCD to the Pi and run a program automatically at the boot up. a) Interfacing your RPI to an LCD In this section you need to interface your 16×2 LCD with Raspberry Pi using 4-bit mode. Please note that you can choose any type of LCD and interface it to your PI, including OLED. Below is the wiring example showing how to interface a 16×2 LCD to RPI.
    [Show full text]
  • Ip Address and Ipv4 Header
    IP Address: Each computer in a TCP/IP network must be given a unique identifier, or IP address. This address, which operates at Layer 3, allows one computer to locate another computer on a network. All computers also have a unique physical address, which is known as a MAC address. These are assigned by the manufacturer of the NIC. MAC addresses operate at Layer 2 of the OSI model. An IP address (IPv4) is a 32-bit sequence of ones and zeros.To make the IP address easier to work with, it is usually written as four decimal numbers separated by periods. For example, an IP address of one computer is 192.168.1.2. Another computer might have the address 128.10.2.1. This is called the dotted decimal format. Each part of the address is called an octet because it is made up of eight binary digits. For example, the IP address 192.168.1.8 would be 11000000.10101000.00000001.00001000 in binary notation. The dotted decimal notation is an easier method to understand than the binary ones and zeros method. This dotted decimal notation also prevents a large number of transposition errors that would result if only the binary numbers were used. Ipv4 Header: Version:(4 bits): Indicates the version number, to allow evolution of the protocol. Internet Header Lenght(IHL 4 bits): Length of header in 32 bit words. The minimum value is five for a minimum header length of 20 octets. Type-of-Service : The Type-of-Service field contains an 8-bit binary value that is used to determine the priority of each packet.
    [Show full text]
  • Transport Layer
    Transport Layer INF3190 Foreleser: Carsten Griwodz Email: [email protected] (Including slides from Michael Welzl) Transport Layer Function Transport layer tasks 5 Application Application Application 5 Layer 1. Addressing Transport Transport Transport 4 Layer Application 4 Layer Layer Layer Network Network Layer Transport Network 3 3 Layer Layer Layer Network 1-2 Layer 1-2 INF3190 - Data Communication Transport Layer Function Transport layer tasks 5 Application Application 5 1. Addressing Transport Transport 4 4 Layer Layer Network 2. End-to-end connection management Network 3 3 Layer Layer 1-2 3. Transparent data transfer 1-2 between end points 4. Quality of service • Error recovery • Reliability • Flow control • Congestion control INF3190 - Data Communication Transport Service: Terminology § Nesting of messages, packets, and frames Packet header Message header Frame header Message Payload Packet Payload Frame Payload TCP/IP Message ISO TPDU Layer Data Unit (transport protocol Transport Message data unit) Network Packet Data link Frame TCP name for Message Payload: Segment Physical Bit/symbol (bitstream) UDP name for Message: Datagram INF3190 - Data Communication Internet terminology § TCP segment could be divided across multiple IP packets (fragmentation) • hence different words used § In practice, this is inefficient and not often done § hence normally message = packet • and in everyday work, although obviously not the same: packet ≈ message or packet ≈ segment • distinction from context INF3190 - Data Communication Transport Service:
    [Show full text]
  • 07-Fragmentation+Ipv6+NAT Posted.Pptx
    IP Fragmentation & Reassembly Network links have MTU (maximum transmission unit) – the largest possible link-level frame Computer Networks • different link types, different MTUs • not including frame header/trailer fragmentation: • in: one large datagram but including any and all headers out: 3 smaller datagrams above the link layer Large IP datagrams are split up reassembly Lecture 7: IP Fragmentation, (“fragmented”) in the network IPv6, NAT • each with its own IP header • fragments are “reassembled” only at final destination (why?) • IP header bits used to identify and order related fragments IPv4 Packet Header Format IP Fragmentation and Reassembly 4 bits 4 bits 8 bits 16 bits Example: 4000-byte datagram unique per datagram hdr len Type of Service MTU = 1500 bytes usually IPv4 version per source (bytes) (TOS) Total length (bytes) 3-bit One large datagram length ID IP fragmentation use Identification 13-bit Fragment Offset fragflag offset flags becomes several =4000 =x =0 =0 upper layer protocol 20-byte to deliver payload to, Time to Protocol Header Checksum Header smaller datagrams e.g., ICMP (1), UDP (17), Live (TTL) 1480 bytes in offset = TCP (6) • all but the last fragments data field 1480/8 Source IP Address must be in multiple of 8 length ID fragflag offset Destination IP Address bytes =1500 =x =MF =0 e.g. timestamp, • offsets are specified in record route, Options (if any) length ID fragflag offset source route unit of 8-byte chunks =1500 =x =MF =185 • IP header = 20 bytes (1 Payload (e.g., TCP/UDP packet, max size?) length ID fragflag offset
    [Show full text]