networks.ppt - Overview


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Robust : Ability to remain functional under extreme conditions caused by either physical damage or heavy traffic. When you send a packet, does it get there intact? Efficient : Allows timely transmission of data packets as well as timely delivery. How long do I wait to transmit or receive? Simple : Is there a lot of overhead in setting up or expanding the network? Scalable : Does the performance take a big hit as the number of nodes increases?
  • Machine address conflict in normal MPI. New MPI release will include the changes done at UK. Dynamic Solution still pending. Channel bonding in Linux Kernel to be modified.
  • Give Disclaimer! The following segment is (mainly) for entertainment purposes.
  • Network book p305.
  • Terminology A home link is the link on which a specific node should be located; that is the link, which has been assigned the same network-prefix as the node’s IP address A foreign link is any link other than a node’s home link – that is, any link whose network-prefix differs from that of the node’s IP address Host-specific route is a routing-table with Prefix-Length of 32 bits, it will provide a match for exactly one IP Destination Address; namely, the address specified in the Target field Mobility is the ability of a node to change its point of attachment from one link to another while maintaining all existing communications and using the same IP address at its new link
  • networks.ppt - Overview

    1. 1. Networks <ul><li>Overview ( Lei You ) </li></ul><ul><li>Overview of Local Network Topology </li></ul><ul><li>( Ryan McKenzie ) </li></ul><ul><li>Internetworking Protocol ( Benjamin A Pullen ) </li></ul><ul><li>Mobile IP ( Hui Tan ) </li></ul>
    2. 2. Overview
    3. 3. What is a Network? <ul><li>Two or more computers are connected together by a medium and are sharing resources. These resources can be files, printers, hard­drives, or CPU number-crunching power. </li></ul><ul><li>A network can consist of two computers connected together on a desk, or it can consist of many Local Area Networks (LANs) connected together to form a Wide Area Network (WAN) across a continent. </li></ul>
    4. 4. The Big Picture <ul><li>Many individuals have asked to see the &quot;Big Picture&quot; of networking: How does everything . Where does Microsoft NT fit in with routers and the OSI layers? What about UNIX, Linux and Novell? </li></ul><ul><li>The big picture in the following slide attempts to show all areas of networking and how they tie into each other. </li></ul>
    5. 6. Graphical Symbols Used in the Big Picture <ul><li>Circles ­ Network Operating Systems </li></ul><ul><li>Squares ­ Communication & cabling protocols (OSI Transport to Physical Layer) </li></ul><ul><li>Storm Clouds ­ Telecommunications media or Information Providers that connect to the Internet </li></ul><ul><li>Machine symbol ­ Network &quot;linker&quot; can be a bridge, router, brouter or gateway </li></ul><ul><li>Jagged haphazard dotted line - the Internet </li></ul>
    6. 7. Telecommunications Components of The Big Picture <ul><li>ISDN ­ Integrated Services Digital Network </li></ul><ul><li>Private Branch Exchanges ­ PBXs, Key Systems </li></ul><ul><li>Telcos ­ AT&T, Bell Telephone, Sprint, Telus </li></ul><ul><li>DataPac & DataRoute ­ Packet switching and analog switching WAN protocols </li></ul><ul><li>Cell Relay ­ Digital packet switching WAN protocol </li></ul><ul><li>Frame Relay ­ Digital packet switching WAN protocol </li></ul><ul><li>X.25 ­ Analog packet switching WAN protocol </li></ul><ul><li>ATM ­ Asynchronous Transfer Mode WAN protocol </li></ul><ul><li>World Wide Web ­ Hypertext-based multimedia system </li></ul><ul><li>ADSL ­ Asymmetrical Digital Subscriber Line </li></ul>
    7. 8. ISO/OSI Model <ul><li>The International Standards Organization (ISO) Open Systems Interconnect (OSI) is a standard set of rules describing the transfer of data between each layer in a network operating system. Each layer has a specific function. For example, the physical layer deals with the electrical and cable specifications. </li></ul><ul><li>The OSI Model clearly defines the interfaces between each layer. This allows different network operating systems and protocols to work together by having each manufacturer adhere to the standard interfaces. The application of the ISO OSI model has allowed the modern multi­protocol networks that exist today. </li></ul>
    8. 9. Seven Layers in the OSI Model <ul><li>7. Application Layer (Top Layer) </li></ul><ul><li>6. Presentation Layer </li></ul><ul><li>5. Session Layer </li></ul><ul><li>4. Transport Layer </li></ul><ul><li>3. Network Layer </li></ul><ul><li>2. Data Link Layer </li></ul><ul><li>1. Physical Layer (Bottom Layer) </li></ul>
    9. 10. ISO/OSI Model … <ul><li>The OSI model provides the basic rules that allow multi protocol networks to operate. Understanding the OSI model is instrumental in understanding how the many different protocols fit into the networking jigsaw puzzle. </li></ul>
    10. 11. The Big Picture can be broken up according to its protocols into the following four areas: <ul><li>Local Loops </li></ul><ul><li>LANs </li></ul><ul><li>MANs </li></ul><ul><li>WANs </li></ul>
    11. 12. The Local Loop <ul><li>The Local Loop is often called &quot;the last mile&quot;, and it refers to the last mile of analog phone line that goes from the telephone company's central office (CO) to your house. </li></ul>
    12. 13. The Local Loop …
    13. 14. Typical Local Loop Protocols <ul><li>Voice Lines </li></ul><ul><li>Modem Connections – 56 kbps </li></ul><ul><li>ISDN (Integrated Services Digital Network) - 2 x 64 kbps digital lines </li></ul><ul><li>ADSL (Asymmetrical Digital Subscriber Line) - up to 8 Mbps </li></ul><ul><li>* Cable Modems - up to 30 Mbps </li></ul>
    14. 15. <ul><li>Cable m odems are not part of the local loop but do fall into the category of the last mile, or how high speed digital communication gets to the premises (home). It would incredibly expensive to replace the existing cabling structure. And because this cabling was designed for voice communications rather than digital, all of these protocols are needed to overcome the existing cabling limitations in the local loop and provide high speed digital data transmission. </li></ul>
    15. 16. Local Area Networks (LANS) <ul><li>A Local Area Network is a system of computers that share resources such as disk drives, printers, data, CPU power, fax/modem, applications, etc. They usually have distributed processing, which means that there are many desktop computers distributed around the network and that there is no central processor machine (mainframe). </li></ul>
    16. 17. Local Area Networks (LANS) …
    17. 18. Components Used by LANs <ul><li>C abling standards </li></ul><ul><li>Hardware </li></ul><ul><li>Protocols </li></ul>
    18. 19. LANS: C abling Standards <ul><li>Cat 3, 4 and 5 cables </li></ul><ul><li>IBM Type 1-9 cabling standards </li></ul><ul><li>EIA568A and 568B </li></ul><ul><li>Ethernet cabling standards: IEEE 802.3 (10Base5), IEEE 802.3a (10Base2), IEEE 802.3i (10BaseT) </li></ul><ul><li>Unshielded Twisted Pair (UTP) </li></ul><ul><li>Shielded Twisted Pair (STP) </li></ul><ul><li>Connectors: RJ45, RJ11, Hermaphroditic connectors, RS-232, DB-25, BNC, TEE </li></ul>
    19. 20. LANS: H ardware Devices <ul><li>Network Interface Cards (NICs) </li></ul><ul><li>Repeaters </li></ul><ul><li>Ethernet Hubs or multi port repeaters </li></ul><ul><li>Token Ring Multi Station Access Units (MSAUs), Control Access Units (CAUs) and Lobe Access Modules (LAMs) </li></ul><ul><li>Bridges </li></ul>
    20. 21. LANS: H ardware Devices … <ul><li>Brouters </li></ul><ul><li>Routers </li></ul><ul><li>Gateways </li></ul><ul><li>Print servers </li></ul><ul><li>File servers </li></ul><ul><li>Switches </li></ul>
    21. 22. LANS: Examples of Protocols <ul><li>Ethernet frame types: Ethernet_II, Ethernet_SNAP, Ethernet_802.2, Ethernet_802.3 </li></ul><ul><li>Media Access Control layer (MAC layer) </li></ul><ul><li>Token Ring: IBM and IEEE 802.5 </li></ul><ul><li>Logical Link Control Layer (LLC) IEEE 802.2 </li></ul><ul><li>TCP/IP </li></ul><ul><li>IPX/SPX </li></ul><ul><li>Asynchronous Transfer Mode (ATM) </li></ul>
    22. 23. Metropolitan Area Networks (MANs) <ul><li>A Metropolitan Area Network is a system of LANs connected throughout a city or metropolitan area. MANs have the requirement of using telecommunication media such as voice channels or data channels. Branch offices are connected to head offices through MANs. Examples of organizations that use MANs are universities and colleges, grocery chains, and banks. </li></ul>
    23. 24. Metropolitan Area Networks (MANs)…
    24. 25. Metropolitan Area Networks (MANs)… <ul><li>The main criterion for a MAN is that the connection between LANs is through a local exchange carrier (the local phone company). The protocols that are used for MANs are quite different from those used for LANs (except for ATM, which can be used for both under certain conditions). </li></ul>
    25. 26. Examples of MAN Protocols <ul><li>RS­232, V­35 </li></ul><ul><li>X.25 (56kbps), PADs </li></ul><ul><li>Frame Relay (up to 45 Mbps), FRADs </li></ul><ul><li>Asynchronous Transfer Mode (ATM) </li></ul><ul><li>ISDN (Integrated Services Digital Network) PRI and BRI </li></ul><ul><li>Dedicated T­1 lines (1.544 Mbps) and Fractional T­1 </li></ul><ul><li>T­3 (45 Mbps) and OC­3 lines (155 Mbps) </li></ul><ul><li>ADSL (Asymmetrical Digital Subscriber Line) ­ up to 8 Mbps </li></ul><ul><li>XDSL (many different types of Digital Subscriber Lines) </li></ul>
    26. 27. Wide Area Networks (WANS) <ul><li>WANs connect LANs together between cities </li></ul>
    27. 28. Wide Area Networks (WANS) … <ul><li>The main difference between a MAN and a WAN is that the WAN uses Long Distance Carriers. Otherwise the same protocols and equipment are used as a MAN. </li></ul>
    28. 29. References <ul><li>1. Introduction to Networking and Data Communications </li></ul><ul><li>Eugene Blanchard </li></ul><ul><li>Edited by Joshua Drake, Bill Randolph and Phuong Ma </li></ul><ul><li>2. Computer Networking: A Top-Down Approach Featuring the Internet </li></ul><ul><li>Jim Kurose & Keith Ross </li></ul><ul><li>3. Internetworking Technology Overview </li></ul><ul><li>Cisco Systems </li></ul><ul><li>4. Internetworking Case Studies </li></ul><ul><li>Cisco Systems </li></ul>
    29. 30. Network Topology Overview of Network Topology and Case Study of Flat Neighborhoods
    30. 31. Goals in Topology Design <ul><li>Reliable and Robust </li></ul><ul><li>Fast and Efficient </li></ul><ul><li>Simple and Scalable </li></ul><ul><li>Examples of well known designs follow this slide, we shall assume all topologies are using 100 Mbit Ethernet as the medium and rate them on design categories. </li></ul>
    31. 32. Bus Topology <ul><li>Robustness </li></ul><ul><li>Efficiency </li></ul><ul><li>Simplicity </li></ul><ul><li>Scalability </li></ul>
    32. 33. Bus Topology <ul><li>Robustness </li></ul><ul><li>Good </li></ul><ul><li>Efficiency </li></ul><ul><li>Good </li></ul><ul><li>Simplicity </li></ul><ul><li>Excellent </li></ul><ul><li>Scalability </li></ul><ul><li>Fair </li></ul>
    33. 34. Ring Topology <ul><li>Robustness </li></ul><ul><li>Efficiency </li></ul><ul><li>Simplicity </li></ul><ul><li>Scalability </li></ul>
    34. 35. Ring Topology <ul><li>Robustness </li></ul><ul><li>Poor </li></ul><ul><li>Efficiency </li></ul><ul><li>Good </li></ul><ul><li>Simplicity </li></ul><ul><li>Very Good </li></ul><ul><li>Scalability </li></ul><ul><li>Poor </li></ul>
    35. 36. Star Topology <ul><li>Robustness </li></ul><ul><li>Efficiency </li></ul><ul><li>Simplicity </li></ul><ul><li>Scalability </li></ul>
    36. 37. Star Topology <ul><li>Robustness </li></ul><ul><li>Very Good </li></ul><ul><li>Efficiency </li></ul><ul><li>Very Good </li></ul><ul><li>Simplicity </li></ul><ul><li>Poor </li></ul><ul><li>Scalability </li></ul><ul><li>Excellent </li></ul>
    37. 38. A New Topology is Born <ul><li>In the past, it has been standard to come up with a topology first, and then adapt it to certain tasks. Modern design philosophy has changed this practice. Now a subset of problems or needs gives rise to special task network designs. One such design has been conceived right here at UK. </li></ul>
    38. 39. The Flat Neighborhood Network <ul><li>Brought about by the need to build a large cluster supercomputer from common networking components. </li></ul><ul><li>Driven to evolve from the need for (more) efficient communication between cluster nodes. </li></ul>
    39. 40. The Basics of FNN’s <ul><li>This example shows how one could construct a FNN for 6 PCs using just two NICs/PC and three 4-port switches. Note that every PC has at least one single-switch latency path to every other PC; some PC pairs have more than one such path. </li></ul>
    40. 41. Some NEW Design Problems <ul><li>Design of Subnets </li></ul><ul><li>Routing and Addressing </li></ul><ul><li>Wiring Scheme </li></ul><ul><li>Efficient use of Bandwidth </li></ul>Multiple small, interleaved subnets link each machine by a number of one-switch latency paths. Any machine can belong to as many subnets as it has network cards onboard. Sounds simple, but several problems arise from the design.
    41. 42. The Solutions: Subnets and Wiring <ul><li>The wiring scheme and subnets can now be designed by a piece of software developed in the KAOS lab. This problem appears to be NP Complete (Very Bad) and must be solved using a genetic search algorithm. A simplified version allows you to design your own FNN on the web. </li></ul><ul><li> </li></ul>
    42. 43. The Solutions: Genetic Search Algorithm <ul><li>Generate 256 random networks. </li></ul><ul><li>Evaluate and rate each based on… </li></ul><ul><ul><li>Latency, Bandwidth Balance, Comm. Patterns </li></ul></ul><ul><li>Throw out bottom 2/3 results and replace with mutations thereof. </li></ul><ul><li>Merge Subnets of pairs in top 1/3 results. </li></ul><ul><li>Re-Evaluate and rate accordingly </li></ul>
    43. 44. The Solutions: Basic Routing <ul><li>Each machine in the cluster swaps unique identifiers with all of its neighbors at boot up. Address resolution is done locally using the table that this swap generates. </li></ul><ul><li>Non-Dynamic Solution </li></ul>
    44. 45. The Implementation: KLAT2 <ul><li>Assembled on April 11, 2000 in the KAOS lab by Dr. Dietz and Mr. Mattox </li></ul><ul><li>Fully Functional on April 16 </li></ul><ul><li>The first working implementation of an FNN </li></ul>
    45. 46. The Main Event: KLAT2 vs. Superdome
    46. 47. KLAT2 vs. Superdome Round 1: Cost <ul><li>KLAT2 </li></ul><ul><ul><li>Total Value: $41,205 </li></ul></ul><ul><ul><li>Peak Performance: </li></ul></ul><ul><ul><li>64 GFlops </li></ul></ul><ul><ul><li>$643.83 / GF </li></ul></ul><ul><li>Superdome </li></ul><ul><ul><li>Total Value: $1.5M / yr </li></ul></ul><ul><ul><li>Peak Performance: </li></ul></ul><ul><ul><li>672 GFlops </li></ul></ul><ul><ul><li>$2,232.14 / GF / yr </li></ul></ul><ul><li>Advantage </li></ul><ul><ul><li>KLAT2 </li></ul></ul>
    47. 48. KLAT2 vs. Superdome Round 2: Upgrading <ul><li>KLAT2 </li></ul><ul><ul><li>Purchase new Nodes </li></ul></ul><ul><ul><li>Upgrade the Old Nodes </li></ul></ul><ul><ul><li>Recompute Scheme </li></ul></ul><ul><ul><li>Rewire EVERYTHING </li></ul></ul><ul><li>Superdome </li></ul><ul><ul><li>Purchase a new Cabinet </li></ul></ul><ul><ul><li>Plug and Play </li></ul></ul><ul><li>Advantage </li></ul><ul><ul><li>Superdome </li></ul></ul>
    48. 49. The Lowdown <ul><li>FNN’s provide wonderful cost efficiency, but are plagued by limitations. </li></ul><ul><ul><li>Number if NIC’s in each node </li></ul></ul><ul><ul><li>PCI Bus Speed </li></ul></ul><ul><ul><li>Increased Physical Distance </li></ul></ul><ul><ul><li>Complexity of Design </li></ul></ul>
    49. 50. Use of KLAT2 <ul><li>KLAT2 is mainly a lab experiment, thus its practical uses are limited : </li></ul><ul><ul><li>Insufficient Non-Volatile Storage </li></ul></ul><ul><ul><li>Weak Back-Up System </li></ul></ul><ul><ul><li>Slow Internet Connection to the WAN </li></ul></ul><ul><ul><li>Limited Application Compatability </li></ul></ul><ul><li>With further R+D, the FNN cluster may evetually bring about a “supercomputer in every home” movement. </li></ul>
    50. 51. Summary <ul><li>Topology Development Philosophy has Evolved </li></ul><ul><li>Special Purpose Topologies use Networks to Solve Specific Problems </li></ul><ul><li>Network Topologies are Always Expanding </li></ul><ul><ul><li>More Topologies Being Concieved </li></ul></ul><ul><ul><li>Faster, More Advanced Media </li></ul></ul>
    51. 52. The Credits <ul><li>Dr. Hank Dietz, (859) 257-4701 </li></ul><ul><ul><li> </li></ul></ul><ul><li>Mr. Tim Mattox at the KAOS Lab, (859) 257-9695 </li></ul><ul><ul><li> </li></ul></ul><ul><li>KAOS Lab Documentation and Publications on FNN’s </li></ul><ul><ul><li> </li></ul></ul><ul><li>Dr. Craig Douglas, (859) 257-2326 </li></ul><ul><ul><li> </li></ul></ul><ul><li>Mr. John Connolly at the UK Center for Computational Sciences </li></ul><ul><ul><li> </li></ul></ul><ul><li>UK SDX Home Page </li></ul><ul><ul><li> </li></ul></ul>
    52. 53. Internetworking Protocol Version 4 (IPv4)
    53. 54. Topics: <ul><li>Why? </li></ul><ul><li>What? </li></ul><ul><li>How? </li></ul>
    54. 55. Why IP? <ul><li>Why do we build networks? </li></ul><ul><li>Why do we need inter-networks? </li></ul>
    55. 60. What is IP? <ul><li>Protocol suit defining an interface between lower level hardware functionality and higher level application oriented protocols. </li></ul><ul><li>Provides a “least common denominator” for all network hardware. </li></ul><ul><li>Provides best effort service for datagram delivery from host to host. </li></ul>
    56. 62. How?
    57. 63. How?
    58. 64. Fields <ul><li>Version(4 bits) – 4 </li></ul><ul><li>Header Length(4 bits) – Size of the header in 4 byte words. </li></ul><ul><li>Type of Service(8 bits) – Mostly unused. </li></ul><ul><li>Length(16 bits) – Total length of IP datagram in bytes. </li></ul>
    59. 65. Fields continued <ul><li>Identification(16 bits) – ‘unique’ identifier </li></ul><ul><li>Flags(3 bits) – 0, Don’t fragment, More fragments. </li></ul><ul><li>Fragment Offset(13 bits) – Offset of fragment in 8 byte words. </li></ul>
    60. 66. Fields continued, again <ul><li>Time To Live (8 bits) – Hop count. </li></ul><ul><li>Protocol(8 bits) – Higher level protocol address. </li></ul><ul><li>Header Checksum – One’s compliment sum of all 16 bit words in IP header. </li></ul>
    61. 67. Fields, more? <ul><li>Source Address(32 bits) – Where it came from. </li></ul><ul><li>Destination Address(32 bits) – Ummm, you know. </li></ul>
    62. 68. Fields, will it ever end!? <ul><li>Options – options. </li></ul><ul><li>Padding – even out to 32 bit words. </li></ul>
    63. 69. Fragmentation <ul><li>IP only requires ~500 byte MTU from hardware layer but allows for packet sizes up to 65535 bytes. </li></ul><ul><li>IP datagrams can be fragmented into smaller packets to travel over various networks then reassembled at the destination. </li></ul>
    64. 70. Fragmentation <ul><li>Fragments from the same datagram carry the same identifier field. </li></ul><ul><li>All fragments except the last have the More Fragments bit set. </li></ul><ul><li>The Offset Field is an index into the original datagram payload. </li></ul>
    65. 71. IP Addressing <ul><li>Hierarchical (cuz that’s what CS people do) </li></ul><ul><li>32 Bits long. </li></ul><ul><li>Globally unique (most of the time.) </li></ul><ul><li>Assigned to network adapter, not host. </li></ul><ul><li>Composed of network part and host part. </li></ul><ul><li>Hosts on the same physical network have the same network address. </li></ul>
    66. 72. IP Addressing <ul><li>Class A - [0][7 Bit Network][24 Bit Host] </li></ul><ul><li>Class B - [10][14 Bit Network][16 Bit Host] </li></ul><ul><li>Class C - [110][21 Bit Network][8 Bit Host] </li></ul>
    67. 73. IP Addressing <ul><li>Classless IP addressing (the way it really is.) </li></ul><ul><li>Arbitrarily long network portion followed by host portion. </li></ul><ul><li>Can not tell dividing line from IP address. </li></ul><ul><li>A netmask is used to divide the address. </li></ul>
    68. 74. IP Forwarding <ul><li>Each host has a table with tuples of network addresses, address length, next hop information, and interface information. </li></ul><ul><li>To forward an IP packet, find the longest network address that matches destination address. </li></ul><ul><li>Send the packet out the corresponding interface to the next hop (may be local.) </li></ul>
    69. 75. IP Forwarding Example: Interface0 = Interface1 = Address/Length Next Hop Interface Local Interface0 Interface0 Local Interface1 Interface1
    70. 76. What’s Next? <ul><li>IPv6 </li></ul><ul><li>128 bit addressing (more people can play quake.) </li></ul><ul><li>Fewer fields for simplicity </li></ul>
    71. 77. Overview <ul><li>Mobility in the Internet </li></ul><ul><li>Basic Mobile IP Protocol </li></ul><ul><li>IMHP : Route Optimization in Mobile IP </li></ul><ul><li>Other Issues </li></ul>
    72. 78. Mobile Computers’ Characteristics <ul><li>May change point of network connection frequently </li></ul><ul><li>May be in use as point of network connection changes </li></ul><ul><li>Usually have less powerful CPU, less memory and disk space </li></ul><ul><li>Less secure physically </li></ul><ul><li>Limited battery power </li></ul>
    73. 79. Current State of Mobile Computing <ul><li>Mobile computers are one of the fastest growing segments of the PC market </li></ul><ul><li>Short-range wireless networks (Bluetooth) available from IBM, Toshiba, Dell, HP… </li></ul><ul><li>High-speed (11 Mbps) wireless LAN products are now easily and cheaply available (IEEE 802.11a, IEEE 802.11b) </li></ul><ul><li>Low speed (currently 128 Kbps) Metropolitan Area Wireless Network services are available in some cities and spreading (Metricom’s Ricochet) </li></ul>
    74. 80. Mobility in the Internet <ul><li>Problem with current IP </li></ul><ul><li>.It assumes that a node’s IP address uniquely identifies its point of attachment to the Internet </li></ul><ul><li>Mobility alternatives without Mobile IP </li></ul><ul><li>.On moving, change IP address </li></ul><ul><li>Use host-specific routes(using LSR) to reach mobile hosts </li></ul><ul><li>.Mobility vs. Portability </li></ul>
    75. 81. Functional Entities in Mobile IP <ul><li>Functional Entities in Mobile IP : </li></ul><ul><li>-Mobile Node </li></ul><ul><li>-Home Agent </li></ul><ul><li>-Foreign Agent </li></ul><ul><li>Each mobile node is assigned a unique home address within its home network </li></ul><ul><li>When away from home network, it is assigned a care-of address either by : </li></ul><ul><li>-Registering with a Foreign Agent </li></ul><ul><li>-Obtaining a temporary IP address </li></ul>
    76. 82. Basic Mobile IP F.A. M.H. H.A. Correspondent node
    77. 83. Protocol Overview <ul><li>Agent Discovery </li></ul><ul><li>Registration </li></ul><ul><li>Tunneling </li></ul>
    78. 84. Agent Discovery <ul><li>Extension of ICMP Router Discovery protocol </li></ul><ul><li>Used by mobile nodes to discover Foreign Agents and to detect movement from one subnet to another </li></ul><ul><li>Mobility Agents (H.A.s and F.A.s) periodically broadcast agent advertisements </li></ul>
    79. 85. Agent Discovery (...contd.) <ul><li>Mobile node expects to receive periodic advertisements </li></ul><ul><li>If it doesn’t receive them, it deduces that either </li></ul><ul><li>-it has moved OR </li></ul><ul><li>-its agent has failed </li></ul><ul><li>Mobile node can also broadcast Agent Solicitation messages </li></ul>
    80. 86. Registration <ul><li>Mechanism by which M.H. communicates reachability info to its H.A. </li></ul><ul><li>Registration messages create or modify a mobility binding at a H.A., which is then valid for a certain lifetime period </li></ul><ul><li>Uses 2 control messages sent over UDP </li></ul><ul><li>-Registration Request </li></ul><ul><li>-Registration Reply </li></ul>
    81. 87. Registration Authentication (..contd.) <ul><li>Replay Protection : Needed to ensure that registration messages are not replayed by a malicious host. Done using : </li></ul><ul><li>-Nonces OR </li></ul><ul><li>-Timestamps </li></ul>
    82. 88. Registration Authentication <ul><li>Concern : Forged registrations permit malicious hosts to remotely redirect packets destined for the mobile host </li></ul><ul><li>Default authentication between M.H. and H.A. uses MD-5 with a shared secret key </li></ul><ul><li>No authentication between M.H. and F.A. </li></ul>
    83. 89. Delivering Datagrams : <ul><li>When the mobile host is away, H.A. intercepts packets addressed to the M.H. and tunnels them to the M.H.s care-of address </li></ul><ul><li>The tunneling scheme could use either of : </li></ul><ul><li>- IP-in-IP Encapsulation </li></ul><ul><li>-‘Minimal’ Encapsulation </li></ul>
    84. 90. Delivering Datagrams (..contd.) <ul><li>Broadcast Datagrams </li></ul><ul><li>-A H.A. forwards a broadcast datagram only if the M.H. requested forwarding of broadcast datagrams (in the registration request) </li></ul><ul><li>Multicast Datagrams </li></ul><ul><li>-M.H. can use a local multicast router </li></ul><ul><li>-M.H. can use a bidirectional tunnel to its H.A. </li></ul>
    85. 91. IMHP <ul><li>Extension to the basic Mobile IP protocol that features : </li></ul><ul><li>-Route Optimization </li></ul><ul><li>-Authentication of Management packets </li></ul><ul><li>Defines four entities : </li></ul><ul><li>-Mobile Hosts </li></ul><ul><li>-Local Agents </li></ul><ul><li>-Cache Agents </li></ul><ul><li>-Home Agents </li></ul>
    86. 92. Route Optimization (IMHP) <ul><li>Triangle Routing in basic Mobile IP </li></ul><ul><li>-Limits performance transparency </li></ul><ul><li>-Creates bottleneck at Home Agent </li></ul>H.A. F.A. M.H. Correspondent Node
    87. 93. Route Optimization <ul><li>Eliminates triangle routing </li></ul><ul><li>Any correspondent node </li></ul><ul><li>can maintain a binding cache </li></ul><ul><li>Correspondent node tunnels </li></ul><ul><li>datagrams directly to the </li></ul><ul><li>care-off address of the </li></ul><ul><li>mobile host </li></ul>F.A. H.A. M.H. Correspondent Node
    88. 94. Binding Management <ul><li>Four message types : </li></ul><ul><li>-Binding Warning </li></ul><ul><li>-Binding Request </li></ul><ul><li>-Binding Update </li></ul><ul><li>-Binding Acknowledge </li></ul><ul><li>Lazy notifications are used (except MH to HA and previous FA) </li></ul>
    89. 95. Foreign Agent Smooth Handoff <ul><li>As part of registration, M.H. requests its new F.A. to notify its previous F.A. </li></ul><ul><li>New F.A. sends binding update to prev F.A. </li></ul><ul><li>Previous F.A. updates its binding cache entry for the M.H. and sends a binding ack. </li></ul><ul><li>Authentication of binding update is based on a shared registration key </li></ul>
    90. 96. Special Tunnels <ul><li>When a F.A. receives a tunneled datagram for a M.H. for which it has no entry, it is tunneled back to the H.A. in a special tunnel </li></ul><ul><li>Gives the datagram one more chance of successful delivery </li></ul><ul><li>Avoids possible routing loops </li></ul>
    91. 97. Authentication in IMHP <ul><li>IMHP </li></ul><ul><li>has simple authentication procedures which preserve the level of security in today’s Internet </li></ul><ul><li>is defined to make use of strong authentication </li></ul>
    92. 98. Authentication in IMHP (..contd.) <ul><li>M.H. to H.A. authentication </li></ul><ul><li>-strong authentication based on a shared secret </li></ul><ul><li>General Authentication </li></ul><ul><li>-a random number specified in binding request is echoed in the reply by the H.A. </li></ul>