1. Internet Protocol-IP

2. Objective l TCP/IP vs. OSI models l CO vs. CL protocols l IP Features »Fragmentation »Routing l IP Datagram Format l IPv6

3. Terminology l A Datagram consists of a header and data parts. l A layer provides services to the layer above it. l A protocol is a set of rules or conventions governing the ways in which two entities (layers or applications) cooperate to exchange information. l List of protocols (one protocol per layer) is called a protocol stack.

4. OSI vs. TCP/IP model

5. TCP/IP Protocol Architecture Model

6. Some Protocols in TCP/IP Suite

7. CO vs. CL l CO – Connection Oriented »Modeled after the telephone system »When PDU are sequenced, I.e. logical connection l CL – Connectionless »Modeled after the postal system »When PDUs are not sequenced. Each PDU is treated independently from each other. l IP is a CL protocol!

8. CL Internetworking l Advantages »Flexibility »Robust »No unnecessary overhead l Unreliable »Not guaranteed delivery –packets can be lost, duplicated, damaged. »Not guaranteed order of delivery –Packets can take different routes »Reliability is responsibility of next layer up (e.g. TCP)

9. IP Features l The primary IP function is to accept data from TCP or UDP (User Datagram Protocol), create a datagram, route it through the network, and deliver it to recipient host. l IP is a network layer protocol that contains addressing information and some control information that enables packets to be routed. l IP relies on two tools to help it route datagrams: »Subnet mask »IP routing table

10. IP Features l If source and destination network and subnet parts are the same, then the destination host is in the same network and the routing is direct. l The datagram is wrapped in a frame and transmitted directly to its destination on the local LAN. l The destination address that is placed in the frame header must be the physical address of the destination. l ARP (Address Resolution Protocol) will be used to find the physical address of the destination.

11. IP Features l If destination is not on the local subnet, IP must consult its local routing table. l In such a case, the datagram is sent to the router specified in the routing table. l If no router (or default gateway) is found in the routing table, report error.

12. IP Features l Handling Incoming Datagrams: »The network interface software delivers a packet, stripped of its frame header, to the IP layer. »If it is a host machine, IP layer delivers it to the upper layer. »If the IP does not match that of its own, the host discards it and initiates an ICMP packet to the source of the packet. »If it is gateway, it re-routes the packet.

13. IP Features l IP has two primary responsibilities: »Providing CL, best-effort delivery of datagrams through an internetwork; and »Providing fragmentation and reassembly of datagrams to support data links with different maximum transmission unit (MTU) sizes.

14. IP Features »Each LAN and WAN technology imposes a different size limit on its frames. –For example, the maximum frame size of Ethernet (MTU) is 1500 bytes, which is far below the maximum size of an IP datagram. –Maximum IP packet size is (65536) or 2 16 bytes. »IP solves the size problem by chopping the datagram into several smaller datagrams called fragments. –According to the IP, the gateways must be able to handle datagrams of size of at least 576 bytes. »It is up to IP in the destination host to gather up the incoming fragments and rebuild the original datagram, before passing it to the upper layer. »Fragmentation most often is performed in a router. »Fragmentation is a performance killer.

15. IP Features l When to re-assemble »At destination –Results in packets getting smaller as data traverses internet »Intermediate re-assembly –Need large buffers at routers –Buffers may fill with fragments –All fragments must go through same router l Inhibits dynamic routing l IP re-assembles at destination only

16. IP Fragmentation l Uses fields in header »Data Unit Identifier (ID) –Identifies end system originated datagram l Source and destination address l Protocol layer generating data (e.g. TCP) l Identification supplied by that layer »Data length –Length of user data in octets »Offset –Position of fragment of user data in original datagram –In multiples of 64 bits (8 octets) »More flag –Indicates that this is not the last fragment

17. Fragmentation Example

18. Dealing with Failure l Re-assembly may fail if some fragments get lost l Need to detect failure l Re-assembly time out »Assigned to first fragment to arrive »If timeout expires before all fragments arrive, discard partial data l Use packet lifetime (time to live in IP) »If time to live runs out, kill partial data

19. IP: Datagram format

20. Header Fields (1) l Version »Currently 4 »IP v6 - see later l Internet header length »In 32 bit words »Including options l Type of service l Total length »Of datagram, in octets

21. Header Fields (2) l Identification »Sequence number »Used with addresses and user protocol to identify datagram uniquely l Flags »More bit »Don’t fragment l Fragmentation offset l Time to live l Protocol »Next higher layer to receive data field at destination

22. Header Field (3) l Header checksum »Reverified and recomputed at each router »16 bit ones complement sum of all 16 bit words in header »Set to zero during calculation l Source address l Destination address l Options l Padding »To fill to multiple of 32 bits long

23. Type of Service l Precedence »Measurement of packet’s relative importance. »8 levels l Reliability »Try not to drop the packet. »Normal or high l Delay »Try to minimize the delay for this packet. »Normal or low l Throughput »Choose a network with high bandwidth. »Normal or high

24. Options l Security »Attach classified information level to packet. For DOD military application. RFC 1108. l Source routing »List of all routers. l Route recording »List of routers visited. l Stream identification »For special handling of voice and data l Timestamping »Add a timestamp at each router

25. Data Field l Carries user data from next layer up l Integer multiple of 8 bits long (octet) l Max length of datagram (header plus data) 65,535 octets

26. IPv6 l IP v 1-3 defined and replaced l IP v4 - current version l IP v5 - streams protocol l IP v6 - replacement for IP v4 »During development it was called IPng »Next Generation

27. Why Change IP l Address space exhaustion »2 32 different addresses gives over 4 billion addresses is not enough! »Due to growth of wireless, PDA, and Internet. l Other enhancements

28. IPv6 vs. IPv4 l The changes from IPv4 to IPv6 are primarily in: »expanded addressing capabilities; »header format simplification; »improved support for extensions, options, and QoS; »flow labeling capability; and »consolidated authentication and privacy capabilities.

29. Status of IPv6 l Smooth transition is key factor in success of IPv6 !!! l In reality, we have a slow adoption of IPv6. This is due to the invention of NAT. l NAT may work only with certain styles of applications, but not adequate for say IP telephony. Also, it does not scale very well. l The urge is not there yet, but surely growing!

30. Summary l IP is a network layer protocol l IP is a best-effort, CL protocol. l The main two responsibilities of IP is fragmentation and routing. l Deployment of IPv6 has been slowed down by NAT techniques.

31. BREAK