SYZYGY Engineering 1 Mobile Networking Mobile-IP Mobile Networking Ad Hoc Network ACP/WG N Meeting 06 WGN06 – IP13 ACP/WG N/SG N1 WP904 (APC) WP-N1-IP-701.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Correspondent which does not know the care-of address
Correspondent which knows the care-of address
Source Routing
Tunneling
Mobile Node
Access Router Access Router
Home Agent
“ ”
Corresponding Node
Internet or Intranet
Mobile-IPv6 using Reverse Tunneling
Source – Will Ivancic
Mobile Node
Access Router Access Router
Home Agent
“ ”
Corresponding Node
Internet or Intranet
Mobile-IPv6 using Route Optimization
Source – Will Ivancic
Mobile Node
Access Router Access Router
Home Agent
“ ”
Corresponding Node
Internet or Intranet
Mobile-IPv6 Binding Updates
xBindingUpdates
Link UPThe number of
Binding Updates isA Scalability Problem
forMobile Networks
Source – Will Ivancic
40
SYZYGY Engineering
Mobile IPv6 Security
• Binding Updates use IPsec extension headers, or by the use of the Binding Authorization Data option
• Prefix discovery is protected through the use of IPsec extension headers
• Mechanisms related to transporting payload packets - such as the Home Address destination option and type 2 routing header have been specified in a manner which restricts their use in attacks
Source – Will Ivancic
41
SYZYGY Engineering
NEMO
NEtworks in Motionhttp://www.ietf.org/html.charters/nemo-
charter.html
http://www.nal.motlabs.com/nemo/
Source – Will Ivancic
42
SYZYGY Engineering
Networks In Motion (NEMO)
• Working Group established in IETF in December 2002
• Concerned with managing the mobility of an entire network, which changes, as a unit, its point of attachment tothe Internet and thus its reachability in the topology.
Source – Will Ivancic
43
SYZYGY Engineering
Goals
• Standardizing some basicsupport mechanisms based on the bidirectional tunneling approach– Competed January 2005
• Study the possible approaches and issues with providing more optimal routing – Ongoing as of January 2006
Source – Will Ivancic
44
SYZYGY Engineering
Network Mobility (NEMO) Basic Support Protocol
(RFC 3963)
• The basic solution MUST use bi-directional tunnels • MNNs MUST be reachable at a permanent IP address and name. • MUST maintain continuous sessions (both unicast and multicast)
between MNNs and arbitrary CNs after IP handover of (one of) the MRs.
• The solution MUST not require modifications to any node other than MRs and HAs.
• The solution MUST support fixed nodes, mobile hosts and mobile routers in the mobile network.
• The solution MUST not prevent the proper operation of Mobile IPv6 (i.e. the solution MUST support MIPv6-enabled MNNs and MUST also allow MNNs to receive and process Binding Updates from arbitrary Mobile Nodes.)
• The solution MUST treat all the potential configurations the same way (whatever the number of subnets, MNNs, nested levels of MRs, egress interfaces, ...)
• The solution MUST support mobile networks attaching to other mobile networks (nested mobile networks).
• Multiple Home Agents from different Service Providers– Security Issues– Desirable for some applications (i.e. air traffic
control, airline maintenance, entertainment)
Source – Will Ivancic
Mobile Network
Access Router Access Router
Home Agent
Corresponding Node
Internet or Intranet
Basic Mobile Network Support for IPv6
xLink UP
Mobile Network
NodesBindingUpdate
Source – Will Ivancic
47
SYZYGY Engineering
Mobile Nodes and Multiple Interfaces in IPv6 (monami6)
48
SYZYGY Engineering
monami6
• Produce standard track specifications to thestraight-forward problems associated with the simultaneous use of multiple addresses for either mobile hosts using Mobile IPv6 or mobile routers using NEMO Basic Support and their variants (FMIPv6, HMIPv6, etc)
• Provide standardized support forsimultaneous differentiated use of multiple access technologies
– 802.11*, 802.16, 802.20, UMTS, Bluetooth and others • WG Deliverables:
– Documentation of motivations for a node using multipleinterfaces and the scenarios where it may end up with multipleglobal addresses on its interfaces [Informational]
– Analysis document explaining what are the limitations formobile hosts using multiple simultaneous Care-of Addresses and HomeAgent addresses using Mobile IPv6, whether issues are specific toMobile IPv6 or not [Informational].
– A protocol extension to Mobile IPv6 (RFC 3775) and NEMO BasicSupport (RFC 3963) to support the registration of multiple Care-ofAddresses at a given Home Agent address [Standard Track].
– A "Flow/binding policies exchange" solution for an exchange ofpolicies from the mobile host/router to the Home Agent and from theHome Agent to the mobile host/router influencing the choice of theCare-of Address and Home Agent address [Standard Track].
49
SYZYGY Engineering
High speed link
int2
int3
Routing Policy
Routing Policy
int1Low latency link
Reliable linkATC
ATCATC
ATC
AOC
AOCAOC
AOC
P-DATA
P-DATA
P-DATA
P-DATA
P-DATAP-DATAHomeAgent
Policy-Base RoutingAirline Example
P-DATA: Passenger Data (Non-Critical Information)AOC: Airline Operations Control (2nd Highest Priority)ATC: Air Traffic Management (Highest Priority - Safety of Flight)
50
SYZYGY Engineering
High speed link
int2
int3
Routing Policy
Routing Policy
int1Low latency link
Reliable linkATC
ATCATC
ATCAOC
AOC
P-DATA
P-DATA
P-DATAHomeAgent
Policy-Base Routing Airline Example
P-DATA: Passenger Data (Non-Critical Information)AOC: Airline Operations Control (2nd Highest Priority)ATC: Air Traffic Management (Highest Priority - Safety of Flight)
51
SYZYGY Engineering
High speed link
int2
int3
Routing Policy
Routing Policy
HomeAgentint1
Low latency link
Reliable link
ATC
ATC
ATC
AOC
AOCAOC
P-DATA
P-DATA
P-DATA
P-DATA
P-DATAP-DATA
Policy-Base Routing Airline Example
P-DATA: Passenger Data (Non-Critical Information)AOC: Airline Operations Control (2nd Highest Priority)ATC: Air Traffic Management (Highest Priority - Safety of Flight)
• What is Mobile Ad-Hoc Networking (MANET)– Self-configuring and self-organizing network of mobile nodes usually connected
via wireless links– Consists of mobile platforms / nodes (e.g., a router with multiple hosts) which are
free to move about arbitrarily.– Initial research and development based on mutual trust and cooperation– MANET routing is a layer-3, network layer technology.
• Dynamic, changing,random, multi-hop topologies may require traversing multiple links to reach a destination
• May have frequent network partitions and merging• Routing may change because of mobility (or wireless link
dynamics – fading)• Routing functionality need to support robust and efficient
operation• May require energy-constrained operation
Source: Albert Young - Boeing
54
SYZYGY Engineering
MANET Characteristics
• Bandwidth constrained,variable capacity wireless links• Effective throughput is much less than a radio maximum
transmission rate after accounting for the effects of multiple access, fading, noise, propagation path loss and interference
• Limited physical security– Increased possibility of eavesdropping, spoofing, and denial-of-service attacks
• Ad-hoc network clusters can operate autonomously or be attached at some point(s) to the fixed Internet –Stub network
• The decentralized nature of network control in MANETs provides additional robustness against the single points of failure of more centralized approaches.
• Equipped with wireless transceivers using antennas which may be omni-directional (broadcast),directional (point-to-point), possibly electronically steerable or a combination.
• Inexpensive alternatives or enhancements to cell-based mobile network infrastructures.
• Military networking for robust, IP-compliant data services within mobile wireless communication networks consist of highly-dynamic autonomous topology segments.
• Homeland Security– Scenarios requiring rapidly-deployable communications with survivable,
– Develop a scoped forwarding protocol that can efficiently flood data packets to all participating MANET nodes. The primary purpose of this mechanism is a simplified best effort multicast forwarding function.
• Ad hoc On Demand Distance Vector (AODV) – http://www.nmsl.cs.ucsb.edu/~krishna/aodv-linksys/– http://w3.antd.nist.gov/wctg/aodv_kernel/– http://crl.se/?go=aodv6
• Optimized Link State Routing Protocol (OLSR) – Navy Research Lab, INRIA (fr), NIIGATA (jp), GRC, LRI (fr), Communication
Research Centre in Canada, UniK University• URL for all sources: http://hipercom.inria.fr/olsr/#code• http://www.olsr.org/
• One Size Does Not Fit All! No single routing protocol works well in all environments – Which approach to choose depends on the traffic and mobility patterns,
and QoS requirements– Proactive routing protocols Optimized Link State Routing (OLSR), Open
Shortest Path First (OSPF) extension• Applicable for relatively stable networks• Suitable for large and dense networks
– Reactive routing protocol Ad Hoc On-Demand Distance Vector (AODV), Dynamic Source Routing protocol (DSR), Dynamic MANET On-demand (DYMO)
• Enables reactive, multihop routing between participating nodes that wish to communicate.
• Applicable to highly dynamic networks– Motivation is for interoperability with the wired– Modification (e.g. neighbor establishment) and scalability enhancements
to OSPFv3 that is designed for IPv6 – Specifically in reducing the size of Hello packets, and optimizing flooding
• IPv6 couple together with MANET offers ease and speed of deployment, and decreased dependence on infrastructure
• Provide End-to-End Global Addressing• Autoconfiguration of link-local addresses• Possible End-to-End Security with integrated IPSec• Support for source routing• Full support of mobility• No broadcast traffic to hamper wireless network
efficiency• Potential support of real-time delivery of data with QoS• Potential to utilize Anycast addressing