· HIP: Host Identity Protocol SHIM6: Site Multihoming by IPv6 Intermediation ... It is similar...

Fuji Chimera Research

Institute,Inc.

AsiaFI at Beijing, Jan 2009


Institute,Inc.

Mobile Terminals are increased 18.8% (11million people) Mobile becomes majority of the Internet

(57.0%, about 48million people)


Institute,Inc.

Internet

Internet Population Changes to Mobiles

Automobiles (800,000,000), Cell phones (1,500,000,000). People (???)

Covers the entire earth including rural area

Digital communication is on the AIR

from and to anywhere, anybody, anything on the earth.

IP technologies is almost ready for Unwired Internet

Mobile IPv6 , Proxy Mobile IP, Mobile Network,

Mobile Ad-hoc Network

Internet Access in movement

Various Wireless Technologies

3G, WiMAX, WLAN, UWB, bluetooth, satellite

Layered wireless Access

Sensing Technologies

RFID, Sensors, etc

Ubiquitous Sensing


Institute,Inc.

Movement Transparency is required to move on the Internet

Addressing and Routing Problems

Mobile IPv6 (RFC3775)

Host-based Host Mobility Support

Location update is done by a mobile node

WiMAX

Network Mobility (RFC3963)

Host-based Network Mobility Support

Location update is done by a mobile router

Vehicles (automobile, airline, train, etc)

Proxy Mobile IPv6 (RFC5213)

Network-based Mobility Support

Location update is done by an entity (MAG) in a network

3GPP

Cisco 3200 Mobile Router

Wichorus SC1400 Home Agent


Institute,Inc.

backbone

edge node

Home Agent

movement


Institute,Inc.

backbone

edge node

Home Agent

movement

mobile network


Institute,Inc.

LMA: Local Mobility Anchor

MAG: Mobility Anchor Gateway

Backbone

Local Domain


Institute,Inc.

Wireless Access Networks were not fully deployed

WiFi standardized in 1996

HSDPA deployed in 2006

WiMAX soon deployed in 2009

Only10 years since wireless connectivity is available

IPv6 is not deployed

IPv4 is running out

We will shift to IPv6 soon or later

Mobility protocols are based on IPv6, but only few IPv6

access network deployed today

Dual Stack Mobile IPv6


Institute,Inc.

IPv6 Backbone Wired Broadband

Network: FTTH,ADSL

CellulerW-CDMA, CDMA 2000,

Wireless LANIEEE 802.11a,b,g

Wireless MANIEEE 802.16e,802.20

Broadcasting

Mobile Adhoc Network (MANET)Personal Area Network, Vehicle-to-Vehicle

MANET


Institute,Inc.

No application required real mobility support.

Voice application

Most of applications can live with short-session

WEB, MAIL, etc.

Upcoming Applications for mobile nodes

Voice, Telematics, ITS, Streaming, TV, future transporter, etc.

Internet is evolving based on innovative activity in the world


Institute,Inc.

Today’s Portable Internet Access is sufficient for users’ view!?

You can always access to the Internet if you manually connects

to it. (modem, cellular, etc)

PPP based tunnel mechanism provides portable internet access to mobile

node. PPP is well-deployed and well-fitted for accounting, too.

applications can handle service portability

user can access to the same service from anywhere, examples are skype,

google, you tube, messenger.

What will be expected scenarios for mobility?

business incentive?

new business model?

new usage of mobile devices?


Institute,Inc.


Institute,Inc.


Institute,Inc.

http://www.cisco.com/univercd/cc/td/doc/product/wireless/moblwrls/cmx/mmg_sg/cmxgsm.htm


Institute,Inc.

IP address has two meaning

locator

identifier

IP address is changed due to movements

Session Termination

CN cannot identify MN

Requirements to IP Mobility

movement transparency

permanent identifier

Nobody thought about mobility


Institute,Inc.

Network Prefix Interface ID

3ffe:0501:100c:d220 0200:39ff:fe0a:c11c

IPv6 Global Address

Router

Router Advertisement

Interface ID

Generating an address from

the received prefix and MN’s

interface ID

RA including

Network Prefix


Institute,Inc.

IP address has two meaning

locator and identifier

Issues when a node moves

IP address is changed due to the locator change

The following drawbacks are observed

Session Termination

CN cannot identify MN

Requirements to IP Mobility

movement transparency

permanent identifier

Network Prefix Interface ID＋

3ffe:0501:100c:d220 0200:39ff:fe0a:c11cFormat of IPv6 Global Address

Router

Router Advertisement

Interface ID

Generating an address fromthe received prefix and MN’s

interface ID

RA including Network Prefix

Address Auto-Configuration


Institute,Inc.

Movement Transparency

Session Continuity regardless of

movements

Session is terminated because

most of transport protocols use IP

address as session managements

Incoming Capability

Node cannot be identified with

frequent IP address changes

Nobody can initiates session to a

mobile node without permanent

identifier

ex. if your mobile phone number is

frequently changed, nobody can

reach you

？

移動 Movements

Connection Termination

Identifier is changed


Institute,Inc.

Physical

Data Link

Network

Transport

Session

Presentation

Application

MAC Address

IPv4/v6

FQDN, ENUM, SIP

URI, USER/PASSWD,

Process ID, File ID Process Migration,

Application Mobility

Service Migration

Session Mobility

IP/Terminal Mobility

Roaming

per s

essio

n

per n

ode

Layer Scattered Identifier Mobility per Identifier


Institute,Inc.

Infosystems

ITS

Broadcast

Cellular


Institute,Inc.

Infosystems

ITS

Broadcast

Cellular


Institute,Inc.

MEXT: Mobility Extensions for IPv6

MIPSHOP: Mobility for IP: Performance, Signaling and Handoff Optimization

NETLMM:Network-based Localized Mobility Management

HIP: Host Identity Protocol

SHIM6: Site Multihoming by IPv6 Intermediation

MANET:Mobile Ad-hoc Networks

AUTOCONF:Ad-Hoc Network Autoconfiguration

6LOWPAN:IPv6 over Low power WPAN

ROLL: Routing over Low Power and Lossy Networks

16ng: IP over IEEE 802.16 Networks

MOBIKE: IKEv2 Mobility and Multihoming Working Group (MOBIKE)

MIP6: Mobile IPv6

NEMO: Network Mobility

Monami6: Mobile Nodes and Multiple Interfaces in IPv6


Institute,Inc.

Mobility Protocol

MIP6 NEMO

MONAMI6

MIPSHOP

SHIM6

MOBIKE

Multihoming

HIP

New Name

Space

16ng 6lowpan

Device Oriented

Extension

MANET

MANET

AUTOCONF Localized

Mobility

NETLMM

MEXT

ROLL


Institute,Inc.

Base Specifications are ready

Mobile IPv6 RFC3775 was published at June 2004

NEMO: Network Mobility RFC3963 was published at January 2005

Proxy Mobile IPv6 RFC5213 will be published soon

Developments and Deployments

Open Source Implementations KAME(SHISA) project for BSD platform

USAGI project for LINUX platform

Several major vendors implemented IP mobility protocols

Deployments Scenarios WiMAX forum adapted CMIP and PMIP

3GPP adapted PMIP


Institute,Inc.

Mobile IPv6 (CMIP6) (Node mobility

mobility management at a host)

Proxy Mobile IPv6(PMIP6) (Host mobility,

no client modification,

mobility management in a network)

Network Mobility (NEMO) (an extension to CMIP6)

Dual Stack Mobile IP (DSMIP)

IPv4 attachment and IPv4 HoA assignment Support

Multiple Care-of Address (MCoA)

Multihoming Extensions

Extension and its applicability

Hierarchical Mobile IP (HMIP)

Reduction of signaling overhead

Fast Handover (FMIP)

Improvement of Handover latency


Institute,Inc.


Institute,Inc.

Addressing

Identifier: Home address (MIP), Mobile Network Prefix

(NEMO), Home Prefix (PMIP)

The identifier is delegated from MN’s home network where Home Agent

is located.

Locator: Care-of address

Locator is obtained at the mobile node’s visiting network.

Binding as Mapping of ID and locator

Home Agent is an anchor point to rendezvous end nodes.

Home Agent manages this binding.

*Note that PMIP uses Local Mobility Anchor as Home Agent


Institute,Inc.


Institute,Inc.

MN sends Binding Update to

update its locator whenever it

moves


Institute,Inc.


Institute,Inc.

MN establishes an IP-in-IP

tunnel with HA.

All the traffic can be routed to

the tunnel


Institute,Inc.


Institute,Inc.

MN can notifies its locator to a

correspondent node so that the

packets can be routed directly

(bypassing HA)

Return Routability (HoTI/

CoTI/HoT/CoT) is used to

confirm reachability of both

addresses


Institute,Inc.


Institute,Inc.


Institute,Inc.

MR has two identifiers, Home

Address and Mobile Network

Prefix

MR notifies its binding (Home

address, Mobile Network

Prefix and Care-of address) to

HA as Mobile IPv6 does


Institute,Inc.

MR establishes an IP-in-IP

tunnel with HA.

All the traffic destined to its

identifier (mobile network

prefix and home address) can

be routed to the tunnel

No Route Optimization

is supported


Institute,Inc.


Institute,Inc.

Although mobility protocols are designed for IPv6, access networks are still not ready for IPv6

mobile nodes cannot roam to the IPv6 network…

IPv6 networks are not suddenly deployed.

The Lack of Dual Stack Mobility Support

If mobile nodes want to communicate with both IPv4 and IPV6, they need to run Mobile IPv4 and Mobile IPv6 at the same time.


Institute,Inc.

IPv6

IPv4

(global)

IPv4

(NAT)

IPv6-IPv6 tunnel

IPv4-IP

v6 tu

nnel

Home Agent

MN and HA are dual stack

Any types of IP address can be

treated as a locator (CoA) and

registered to HA as a binding

•IPv6 address

•IPv4 address

•IPv4 private address

Supporting different types of Locator Address


Institute,Inc.

MN sends Binding Update with UDP tunnel to create a

session cache at NAT device.

If HA detects that the source address of the UDP-tunneled

Binding Update is different from the CoA in the IPv4 CoA

option. If the address is different, HA treats that MN is

behind NAT and uses the NAT-device’s global address as

MN’s CoA.

It is similar approach of NAT traversal for Mobile IPv4.


Institute,Inc.

Home Agent

MN can obtain IPv4 home address

during IPv6 binding update and

use it for communication.

Supporting different types of Identifier

MN sending BU with

IPv4 HoA option(0.0.0.0)

HA replying BA with IPv4 HoA option(a.b.c.d)

All the traffic from home addresses (v4/v6) are

tunneled to a bi-directional tunnel between MN and HA


Institute,Inc.

Home Agent

Providing both IPv4 and IPv6 Prefix

With DSMIP, MR can connects

to any networks and also

provides both v4 and v6

connectivity to its mobile

network

Supporting attachments to

IPv4 (global/private) and IPv6

Mobile Router


Institute,Inc.

Home Agent

MIP/NEMO has multihoming capability(Monami6 WG, draft-ietf-monami6-multiplecoa-11.txt).

Multihomed Dual Stack Access Routerby NEMO + DSMIP + MCoA

Mobile Router

``Multi-homing for small scale fixed network Using Mobile IP and NEMO'', RFC4908 (Experimental), Internet Engineering Task Force, June 2007.


Institute,Inc.


Institute,Inc.

Characteristics

LMA: Local Mobility Anchor (similar to HA on Mobile IP

MAG: Mobile Access Gateway

MN’s default router

MN: Mobile Node

No modification is required for PMIP. Regular IPv4 and IPv6 nodes

Assumptions

PMIP supports only P2P link (no shared link) between a mobile node

and a mobile access gateway

In PMIP, each MN obtains a home prefix instead of a home address

we cannot assign an address to multiple clients, because of multi-

subnet split issue


Institute,Inc.

LMA: Local Mobility Anchor (similar to HA on Mobile IP

MAG: Mobile Access Gateway

MN’s default router

MN: Mobile Node

No modification is required for PMIP. Regular IPv4 and IPv6 nodes

In PMIP, each MN obtains a home prefix instead of a home address

we cannot assign an address to multiple clients, because of multilink subnet split

issue

LMA: Local Mobility Anchor

MAG: Mobility Anchor Gateway

Backbone

Local Domain


Institute,Inc.

Internet

LMA

MAG3

MAG2

MAG1

MN

1) attachment

2)Proxy Binding Update 3)Proxy Binding Acknowledgement

4)b

i-directional tu

nnel

5)Providing address/Prefix

to MN by DHCP or RA

CN

MN is a regular IPv6 node

MAG sends a proxy

binding update on behalf

of MN

MN can roam only within

its local domain where

MAGs are deployed


Institute,Inc.

Two features for IPv4 support

IPv4 Home Address Mobility Support

transport can be either IPv4 or IPv6

IPv4 Transport Support

IPv4 support specification for PMIP follows DSMIP [draft-

ietf-mip6-nemo-v4traversal]


Institute,Inc.

MAG

LMA

Internet

MN can be either- Dual stack- IPv6 only- IPv4 only


Institute,Inc.

Supporting IPv4 only and dual-stack MN

IPv4 Home Address Assignment

Statically assignment

Dynamic assignment

From LMA

PBU/PBA extension for supporting options specified in

DSMIP


Institute,Inc.

(DHCP Server) *No Address Pool

(DHCP Client)

2)PBU (0.0.0.0) 3) PBA (A.B.C.D)

4) DHCP OFFER(A.B.C.D) 1)DHCP DISCOVERY

MN

LMA

MAG (DHCP Relay)

(DHCP Client)

2)PBU(0.0.0.0) 3) PBA(A.B.C.D)

5) DHCP OFFER(A.B.C.D) 1)DHCP DISCOVERY

MN

LMA

MAG

DHCP Server

4) Relaying DHCPDISCOVERY(A.B.C.D)

DHCP-Server is located at MAG DHCP-Relay is located at MAG and

DHCP-server is located in PMIP domain(maybe co-located with LMA)


Institute,Inc.

MAG

LMA

Internet

IPv6IPv4

IPv4 NAT

LMA and MAG are dual stack

Decreasing the initial investmentsto deploy the PMIP


Institute,Inc.

Supporting all the features specified in DSMIP

NAT support

TLV negotiation (for the next version)

No protocol modifications to DSMIP except

UDP tunnel is an optional, since an operator can easily

pre-know no NAT in his PMIP domain. NAT detection

can be completely turned off in such scenarios.


Institute,Inc.


Institute,Inc.


Institute,Inc.

Co-located Care-of Address (Co-located CoA)

MN obtains its care-of address from its visiting network

as Mobile IPv6 does.

Foreign Agent Care-of Address (FA CoA)

MN uses an address of Foreign Agent. It request FA to

run binding registration on behalf of MN.

All the MNs under FA shares the same CoA (FA CoA)

It is not necessary to prepare for address pools for

visiting MNs. IPv4 address pool is expensive.


Institute,Inc.

MN obtains its CoA (named

co-located CoA) at visiting

network and registers the CoA

to HA by Registration Request


Institute,Inc.

Tunnel is established

between MN and HA as

Mobile IPv6


Institute,Inc.

MN attempts binding

registration to FA. FA relays

all the binding registration

messages to/from MN.


Institute,Inc.

Tunnel is established between

FA and HA.

MN does not need to tunnel

packets.

FA takes care of encapsulation

and decapsulation.


Institute,Inc.


Institute,Inc.

Mobile nodes often have multiple

network interfaces (802.11a,b,g,h,

CDMA1x, GPRS, etc)

Limitations

Mobile IP inhibits using all of active

interface simultaneously

Multiple CoAs can not be bound to a

single home address

Always-on Internet Connectivity

Communication efficiency

Low bandwidth, Less reliability, Cost

performance, Lost user’s decision/

intention

QoS, Multihoming, Redundancy,

Fault Tolerance, Fast Vertical Hand-

off, bandwidth

Multiple Care-of

Addresses Registration

MN Registering all the

CoAs bound for same home

address to HA (or/and CN)

Setup multiple bi-

directional tunnels per

interface if needed

draft-ietf-monami6-

multiplecoa-11.txt


Institute,Inc.

Binding: HoA vs. CoA1, CoA2, CoAn

Binding Identification Number (BID) to

distinguish multiple bindings for single

HoA

Care-of Address Information sub-option

MN CN

Binding CacheHoA -> CoA1

MN CN

Binding CacheHoA/IFID->CoA1

HoA/IFID->CoA2

drop

MN

CoAn

CN

Binding CacheHoA/IFID->CoAn

HoA/IFID->CoA1

CoA1

CoA1

CoA2

CoA2

CoA1

CDMA/1x

CDMA/1x

DSRC 802.11

CDMA/1x

DSRC


Institute,Inc.

Multiple CoAs are bound to single HoA

Upper layers are unaware of multihoming

Session continuously while interface switching

Mobile IPv6/NEMO extensions

Binding Identification Number (BID)

to distinguish multiple bindings for single HoA

Care-of Address Information sub-option

to carry BID to home agent and correspondent node

CoA1 BID1CoA2 BID2

Binding Cache HoA + BID1 – CoA1

HoA + BID2－CoA2

MN/MR

Internet HA

1. Binding Update

2. Binding Acknowledgement

IP header HoA BU (M) BID Info IPsec


Institute,Inc.

Dividing flows and distributing to each interface

per policy: Policy Based Care-of Address Selection

per priority: Priority Based care-of address selection

MN registering flow binding to direct particular flow to

desired care-of address

draft-ietf-mext-flow-binding-00.txt


Institute,Inc.


Institute,Inc.

Route Optimization

Internet

Bi-directional Tunnel Home Agent

Mobile Host/Router Dog-leg/Triangular routing

longer routes, bigger delay, ...

Restricted position

the HA is located where the home prefix is announced to the Internet

single point of failure

Constraints for the home link

scalability issues: bandwidth, ND queries/replies

Correspondent Node

HA introduces several drawbacksLarge latency

Longer Route pathUnreliability

High-overload


Institute,Inc.

MIP6 has Route Optimization in RFC3775

Privacy

Revealing CoA to correspondent nodes

Modification of end-nodes

Required to support MIP6 on end nodes

Complexity

Return Routability needs 4 messages exchange before BU

Servers overload

Servers cannot manage binding cache for all the clients


Institute,Inc.

1. HA Distribution:

Place and Activate multiple HAs simultaneously regardless of topology

Use Anycast Type of Routing

2. Global Mobile eXchange Point (GMX):

Consierating fact that MN dominates the Internet, traffic exchange between mobile nodes are extremely important.

GMX is rendezvous point for home agents served by different operators.

similar to IXP of the current Internet

GMX Advantages

Providing best-effort route path without any end operations

Easy mobile traffic engineering


Institute,Inc.

HA distribution

Regular HA


Institute,Inc.

GMX1 GMX2

Operator-A

Operator-B

Operator-C

MN-A1 MN-A2

MN-B

MN-C


Institute,Inc.

MobileIPv6

HA migration

GMX


Institute,Inc.

proprietary &

Confidential

connecting ISPs and exchange the traffic

ISP

ISP

ISP

ISP

ISP

IX


Institute,Inc.

proprietary &

Confidential

Rendezvous point of Mobile Service Provider (MSP)

exchange the mobile nodes’ traffic at GMX

MSP/CSN

MSP/CSN

MSP/CSN

MSP/CSN

MSP/CSN

GMX


Institute,Inc.

GMX-SF

GMX-NY

GMX-IN

GMX-EU

GMX-JP


Institute,Inc.

2001:200::/16

2001:200::/16

2001:200::/16

2001:200::/16

2001:200::/16

Each GMX is expected to be physically connected with high speed link

Each HAs are virtually connected each other by tunneling (IP-in-IP, L2TP, etc).

Creating virtual overlay backbone for mobility services. (HA as a Rendezvous

point)


Institute,Inc.

About Interop Experimentation

http://www.mobileip.jp/interop2008/in_English.html

Implementation

SHISA: Mobile IPv6 Implementation on BSD-platform http://sourceforge.net/projects/shisa/

Papers

Ryuji wakikawa, Guillaume Valadon, Jun Murai., "Migrating Home Agents towards Internet-Scale Mobility Deployments", ACM 2nd CoNEXT Conference on Future Networking Technologies, Lisboa, Portugal. 4-7 December 2006

Ryuji Wakikawa, Yasuhiro Ohara, Jun Murai, :``Virtual Mobility Control Domain for Enhancements of Mobility Protocols‘’, The 8th IEEE Global Internet Symposium 2005, Miami FL, USA, March 17-18, 2005 , Vol4, 2792 - 2797, ISSN: 0743-166X

Internet Drafts

draft-wakikawa-mext-haha-interop2008-00.txt

draft-thubert-mext-global-haha-00.txt

draft-wakikawa-mip6-nemo-haha-spec-01.txt

draft-wakikawa-mip6-nemo-haha-spec

draft-thubert-nemo-global-haha

draft-wakikawa-mip6-nemo-haha

draft-ietf-mip6-hareliability (WG Document and Design Team was formed)


Institute,Inc.


Institute,Inc.

No reliability scheme is provided to HA, though MIP6 and

NEMO rely on home agent availability

Hardware based solutions are still possible, but a

protocol based solution is also required

Providing redundancy and reliability to home agent without

the mobile node being aware of it

Two modes are proposed in the draft

Home Agent Virtual Switch

Home Agent Hard Switch


Institute,Inc.

Assumptions

The IPsec states are synchronized

among a redundancy home agent set

(HA1 and HA2)

The HA address is shared among

the redundancy home agent set

1) MN establishes IPsec SA with HA

and sends BU

2) HA exchange binding and IPsec

SA states with backup-HA

3) When the HA fails, backup-HA

automatically takes over the failed

HA

2001::abackup2001::a

2) SA and Binding States Exchange

1) BU

HA1 HA2

How to synchronize IPsec is out of scope


Institute,Inc.

Assumptions

IPsec SA states are not synchronized among a redundancy home agent set

Each HA has distinct IP address

1) MN pre-establishes IPsec SAs with all the HAs

2) MN sends BU to one of HA as RFC3775

3) Binding States are exchanged among HAs

4) If HA fails, backup-HA sends a HA switch message to MNs by using the pre-established SA.

5) MN then re-associates with the backup HA by:

sending BU to backup-HA

update binding information and tunnel endpoints with new HA

2001::abackup2001::b

3) Binding States Exchange

1) IPsec SA pre-establishment to both HAs

2)BU

4)HA switch

5)BU

HA1 HA2


Institute,Inc.


Institute,Inc.

SAE has been standardized at 3GPP

Cellular network will be all IP network.

Proxy Mobile IPv6 is used as a mobility protocol

Non-Roaming Architecture for 3GPP Accesses within EPS using PMIP-based S5

from 3GPP TS 23.402


Institute,Inc.

ASNASN GW CSN

HA

Internet

MS CSN ASN-GW BS R1 R3

PHY PHY PHY PHY

PHY PHY MAC MAC

LNK LNK LNK LNK

IP-CS IP-CS IP IP

IPv6 IPv6 GRE GRE

IPv6 IPv6

ASN GW is the 1st hopRouter for the MS

R6

IPv6 link

WiMAX architecture is designed as IP friendly.

WiMAX supports Mobile IP and Proxy Mobile IP as mobility protocols.


Institute,Inc.

ICAO considers to use NEMO for aviation networks

Daniel Medina, Christian Bauer, Serkan Ayaz German Aerospace Center (DLR), Munich, Germany


Institute,Inc. Globally Scale Mobility Support

Daniel Medina, Christian Bauer, Serkan Ayaz German Aerospace Center (DLR), Munich, Germany


Institute,Inc.


Institute,Inc.

InternetHA

MR MRMR


Institute,Inc.

Personal Area Network

Internet


Institute,Inc.

INTERNET

MR MR

MRMR

MR

AR

MR

MR

MRMR

MR

AR

MR

MR

AR

MRMR MR

MRMR

MR

AR

Wireless Stub Network is a cloud of Mobile

Routers connected by wireless or wired links.

It is a stub at the edge of the Internet,

interconnecting various types of devices

which discover each other and form a

network in an ad-hoc fashion to provide

Internet connectivity to one another.

NEMO (RFC3775) defines a "Mobile

Router" carrying a mobile network with a

permanent prefix.

When NEMO is deployed, wireless clouds

will be appeared at the edge of the Internet.

NEMO can be attached to any networks

including mobile networks unless it has

reachability to the Internet.

This wireless cloud is called "Wireless Fringe

Stub"

When Wireless Fringe Stub is appeared,

several NEMO RO problems are raised.

MANEMO is aimed to design to solve the

problems


Institute,Inc.

Seven problems listed in

draft-ietf-nemo-ro-problem-statement-03.txt

2. NEMO Route Optimization Problem Statement 2.1. Sub-Optimality with NEMO Basic Support

2.2. Bottleneck in Home Network

2.3. Amplified Sub-Optimality in Nested Mobile Networks (pinball effect)

2.4. Sub-Optimality with Combined Mobile IPv6 Route Optimization

2.5. Security Policy Prohibiting Traffic From Visiting Nodes

2.6. Instability of Communications within a Nested Mobile Network (Loss of global connectivity prevents neighborhood communications)

2.7. Stalemate with a Home Agent Nested in a Mobile Network (HA behind MR)


Institute,Inc.

MR1

MR2

AR

MR3 MR4

INTERNET

HA1 HA2 HA3

HA4 A mechanism to route packets over nested

NEMO without multiple IP encapsulations

and ping-pong routing among HAs

Required Functionalities:

PATH from a MR to the AR

PATH from the AR to a MR

Bypassing HAs and Tunnels as many as

possible

CN


Institute,Inc.

AR1

MR1

MR2

MR3

MR4

INTERNETMR1

MR2

MR3

MR4

Multiple Tunnels (UM-CoA)

Single Tunnels (AC-CoA)


Institute,Inc.

MR1

MR2

AR

MR3 MR4

INTERNET

HA1 HA2 HA3

HA4 A mechanism to exchange "Mobile Network Prefix" inside a nested NEMO and to provide certain optimized path.

The Path From MR1 to MR4 MR1->AR->HA1->HA4->HA2->HA1->AR->MR1->MR2->MR4

The Path from MR3 to MR4 MR3->MR2->MR1->AR->HA1->HA2->HA3->HA4->HA2->HA1->AR->MR1->MR2->MR4

Required Functionalities:

Bypassing HAs and Tunnels

PATH from a MR to the AR

PATH from the AR to a MR

or

PATH between two MRs


Institute,Inc.

MR1

MR2

AR

When a MR attaches to a visiting network, it does not know whether the loop can be occurred or not.

The Mobile Network can be seen as a normal IPv6 link

Required Functionalities

Loop Prevention

MR1

MR2

MR3

MR3


Institute,Inc.

MR

MR

MR

INTERNET

AR

?

connected-NEMO

disconnected-NEMO

Regular-IPv6-network

Three RAs

Two Mobile Network Types

Connected Mobile Network

The MR's binding is registered to the HA and the bi-directional tunnel is established

Disconnected Mobile Network The binding registration is not yet completed due to no CoA, network troubles, etc.

In NEMO (RFC3963),

MR can send RA regardless of its binding status

even for the disconnected mobile network, MR still sends RA to its mobile network

MNNs may be connected to disconnected NEMO, which is not desired…

No NEMO indication in MR's RA

For MNN, no differentiation whether the access network is NEMO-enabled or not


Institute,Inc.

a light-weight protocol to solve the MANEMO problems

MANEMO players Mobile Router (RFC3963)

Mobile Node (RFC3775)

IPv6 Node, Wireless/Wired Access Router

Basic functionalities Topology formation (tree)

Local routing of mobile network prefixes along the tree

Exit Router Discovery along the tree

Path setup to and from Exit Router

Routing inside a nested NEMO!?

A care-of address is

generated from a mobile network prefix

of an upper mobile router

assigned to an egress interface MR4 MH

MR2 MR1

MR3

INTERNET

AR

MNP2 MNP1

MNP1::MR3

MNP1::MR1

MNP3

MNP3::MR4

MNP3::MR3

MNP3::MH


Institute,Inc.

Proposed solutions:Tree Discovery,

RRH,

NANO/ NINO,

MANET?

Internet


Institute,Inc.

Special kinds of MANETs, supporting both safety and non-safety applications

Single, short-range dedicated technology (802.11p draft) in basic systems

Additional technologies (especially 802.11) in extended systems

Peculiarities: High mobility

High number of nodes

Costs restrictions to allow for high deployability

Internet-based applications Beneficial for safety purposes

Fundamental for non-safety purposes


Institute,Inc.

102


Institute,Inc.

103


Institute,Inc.

“Sensor dust” spread over a

territory

Sensors assume a fixed arbitrary

geographical distribution

numerous sensors with limited

capabilities (LFN == RFD*)

A limited number of relays (MR

== FFD*)

Few uplinks (MR with backhaul

capability)

Mobile Sensors, mobile Sinks


Institute,Inc.

Mesh Network (ex. Fleet in motion)

• Global motion plus relative mobility

• Managed hierarchy

• Secured uplink to base

• Local connectivity

• Movement Aware peer selection

• Wireless dynamic coverage extension by moving ships


Institute,Inc.


Institute,Inc.


Institute,Inc.

Thank youQuestions?

Date post:	28-May-2018
Category:	Documents
Upload:	duongliem
View:	214 times
Download:	0 times

· HIP: Host Identity Protocol SHIM6: Site Multihoming by IPv6 Intermediation ... It is similar...

Documents