1 / 13

NEtwork MObility (NEMO)

Explore NEMO, a mobile network protocol, moving functionality to routers for seamless connectivity. Learn about basic support, routing, applications, and terminology. Dive into references and RFCs for further insights.

meir
Download Presentation

NEtwork MObility (NEMO)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NEtwork MObility (NEMO) Houcheng Lee

  2. Main Idea • NEMO works by moving the mobility functionality from Mobile IP mobile nodes to a mobile router. The router is able to change its attachment point to the Internet in a manner that is transparent to attached nodes

  3. Basic Support

  4. Basic Support (RFC3963) • A mobile Network is a network segment or subnet that can move and attach to arbitrary points in the routing infrastructure • The Mobile Router is the default gateway for the Mobile Network • A Mobile Network can comprise of nested subnets, but the overhead is heavy • A Mobile Router has a unique registered Home Address with its Home Agent. The Home Address is configured from a prefix aggregated and advertised by its Home Agent. • When Mobile Router acquires a Care-of Address from Foreign Agent, it sends a Binding Update to its Home Agent, and Home Agent creates a cache entry binding the Mobile Router’s Home Address to its Care-of Address. • If the Mobile Router Seeks to act as a Mobile Router and provide connectivity to nodes in the Mobile Network, it indicates this to the Home Agent by setting a flag (R) in the Binding Update • Mobile Router MAY include information about one or multiple Mobile Network Prefix in the Binding Update • The Home Agent acknowledges the Binding Update by sending a Binding Acknowledge to the Mobile Router. A positive acknowledgement with the Mobile Router Flag (R) set means that the Home Agent has set up forwarding for the Mobile Network. • Once the binding process finishes, a bi-directional tunnel is established between the Home Agent and the Mobile Router, and the end points of the tunnel are the MR’s CoA and HA’s address. • The packets sourced from MN are sent to HA through the reverse-tunnels which is done by using IP-in-IP encapsulation, and then HA decapsulates the packets and forward it to the CN. • Before MR decapsulates the packets sent from HA via tunnel, MR has to check whether the Source address on the outer IPv6 header is the Home Agent’s address, but this check is not necessary if the packet is protected by IPsec in tunnel mode. • The MR and HA can run a routing protocol through the bi-directional tunnel. In this case, the MR need not include prefix information in the Binding Update. Instead the HA uses the routing protocol updates to set up forwarding for the Mobile Network. The MR should be configured not to send any routing protocol messages on its egress interface when it is away from he home link and connected to a visited link.

  5. Route Optimization

  6. Multihoming

  7. Applications - Airplanes

  8. Applications - Automobiles

  9. Applications - Personal Area Networks (PANs)

  10. Terminology • Access Router (AR) • Care-of Address (CoA) • Correspondent Node (CN) • Foreign Agent (FA) • Home Agent (HA) • Home Network (HN) • Mobility Agent (MA) • Mobility Network Node (MNN) • Mobile Node (MN) • Mobile Router (MR)

  11. Reference • E.Perera, V.Sivaraman, and A.Seneviratne, “Survey on Network Mobility Support”, ACM SIGMOBILE Mobile Computer and Communications Review, Volume 8, Number 2, 2004 • Paul Moceri, “Enabling Network Mobility: A Survey of NEMO” • Devarapalli, V.,R. Wakikawa, A. Petrescu P. Thubert. “RFC 3963: Network Mobility (NEMO) Basic Support Protocol,” IETF, NEMO Working Group, January, 2005 • Leung, K.,G.Dommety, V.Narayana, A. Petrescu. “IPv4 Network Mobility (NEMO) Basic Support Protocol,” IETF, NEMO Working Group, February 24, 2006 • C. Perkins, Ed. “RFC 3344: IP Mobility Support for IPv4,” IETF Network Working Group, August, 2002 • Ernst, T. “Network Mobility Support Goals and Requirements,” NEMO Working Group, Internet-Draft, October 24, 2005 • Ernst, T.,H-Y. Lach. “Network Mobility Support Terminology,” NEMO Working Group, March 6, 2006 • Ng, C., F. Zhao, M. Watari, P. Thubert. “Netowrk Mobility Route Optimization Solution Space Analysis,” IETF, NEMO Working Group, Febraruy 10, 2006 • Ng. C.,F. Zhao, M. Watari, P. Thubert. “Network Mobility Route Optimization Problem Statement,” IETF, NEMO Working Group, December 28, 2005 • Ng. C., E. Paik, T. Ernst, M. Bagnulo, “Analysis of Multihoming in Network Mobility Support,” IETF, NEMO Working Group, February 23, 2006 • “Nautilus6 – Network Mobility Website,” 2005. Nautilus6, WIDE, April, 2006 • “Nautilus6 – NEPL Enhancement Website,” November 11, 2005. Nautilus6, WIDE, April 2006

  12. Reference (RFC) • RFC 3963: draft-ietf-nemo-basic-support • RFC 4887: draft-ietf-nemo-home-network-models • RFC 4980: draft-ietf-nemo-multihoming-issues • RFC 4886: draft-ietf-nemo-requirements • RFC 4888: draft-ietf-nemo-ro-problem-statement • RFC 4889: draft-ietf-nemo-ro-space-analysis • RFC 4885: draft-ietf-nemo-terminology

More Related