NEMO: Network Mobility Support in IPv6 · PDF fileThierry Ernst - Network Mobility Support in...

Thierry Ernst – Network Mobility Support in IPv6 - June 2005

Network Mobility Support in IPv6(NEMO)

byThierry Ernst

IETF NEMO WG ChairWIDE Nautilus6 WG chair

Keio University

[email protected]

http://www.sfc.wide.ad.jp/~ernst/

Thierry Ernst - Network Mobility Support in IPv6 - June 2005 2

Introduction: The Ubiquitous Internet

Internet

Key issues to achieve the ubiquitous Internetin-vehicle access

mobility in and between access networks

Wireless LAN 802.11

Priva te Internet Ac c ess

Wireless WAN

In-vehic le Internet Ac c essCha nging

ac c ess network

Wired or Wireless LAN(WaveLAN, HiperLAN,..)

Internet Ac c ess a t

Offic e

Pic oc ellula r MAN

Pub lic Internet Ac c ess

Chang ing ac c ess network

Chang ing ac c ess network

(IEEE 802.11b, GPRS, Bluetooth, ...)


MIP6

IPv6

MULTI6(SHIM6)

MANET

NEMO

MIPSHOP

HostMobility

Multihoming

Network Mobility

Signaling and handoffoptimization

IETF: Mobility-related activities

IPv4

MIP4

Monami6 ??

Shim6 ??

MObile Nodes And Multiple Interfaces

in IPv6

Host Mobility Support:Proto: Mobile IP, HMIPv6, FMIPv6

End sysyems that change point of attachment

WG: MIP4, MIP6, MIPSHOP (HMIPv6, FMIPv6)

Network Mobility Support:Proto: NEMO Basic Support

Entire networks that change point of attachment

WG: NEMO

Ad-hoc networks:Routing protocols for infrastructure-less networks

WG: MANET

Multihoming: Monami6 BOF ? / Shim6 BOF

Security: PANA, IPsec, ..


IETF NEMO WG Status http://www.ietf.org/html.charters/nemo-charter.html


Netwok Mobility: IETF NEMO WG

Initial discussion started August 2000 in Mobile IP WG

2 BOFs in March and July 2002Confusion between Mobile Networks and Mobile Ad-Hoc Networks

NEMO (NEtwork MObility) WG created october 2002Chairs: Thierry Ernst / TJ Kniveton

Open Mailing List: +700 subscribersDifferent background:

Car manufacturers/Airline carriers/Army/Public transportation/Network equipment manufacturers/Telecom companies

Most active: Japan, France, Korea

Stepwise ApproachNEMO Basic Support : session maintenance (now)

NEMO Extended Support : performances issues (later)


IP-layer Mobility: Addressing in IPv6

MN

AR

MN

Prefix-1::id_MN

Prefix-1::id_MR

HA

Prefix-X::id_MRPrefix-X::id_MR

BR

Prefix-1

Prefix-2::id_MR

AR Prefix-2

Prefix-2::id_MN

Prefix-X::id_MR

Address must be topologically correctEach interface must have an @ formed after the prefix advertised on the link where it is attached

Change of point of attachment = change of IP subnet

Change of IP subnet = change of @ & routing directive

MN

MN

Prefix-1::id_MN

Prefix-1::id_MR

Prefix-X::id_MRPrefix-X::id_MR

BR

Prefix-1

Prefix-2::id_MR

AR Prefix-2

Prefix-2::id_MN

Prefix-X::id_MR


AR MR-HoA: P1::id_MR

HA

MNP::id_MR MNP::id_MR

BR

HomeLink: P1/48

Network Mobility Support: IETF NEMO Basic Support

AR ForeignLink: P2/64

MNNs

MNP::id_MR

MR-CoA: P2::id_MR

Goal: session maintenance

Initialisation:MNP (Mobile Network Prefix) is assigned to the mobile network

MNNs have their addresses taken from MNP

MR-HoA: MR's egress interface on the home link

Movement to a foreign linkMR retains its HoA

MR obtains a CoA on the foreign link

MNNs retain their initial addresses

MR-HoA: P1::id_MR

MNP::id_MR MNP::id_MR

BR

HomeLink: P1/48

AR ForeignLink: P2/64

MNNs

MNP::id_MR

MR-CoA: P2::id_MR


MNP P1/60

MR


AR

InternetHA

P1/ 60 -> P2::/ 128 (MR-CoA)

Prefix P2/ 64

Prefix P1/ 48

How to maintain sessionsBi-directional tunnel between MR and HA

RegistrationCoA is bound to MNP, not HoA

Registration with HA: MNP -> MR-CoA instead of MR-HoA-> MR-CoA

HA records a network-specific route instead of host-specific

MR-CoA = next hop to MNP

MNPS:MR D:HA

MNP P1/60

MR


MNP P1/60

MR


AR

InternetHA

Prefix 1/ 60 ->MR -CoA

S:CN D:LFN

S:CN D:LFNS:HA D:MR-CoA

S:CN D:LFN

P2/ 64

P1/ 48

RoutingEncapsulation between HA and MR in BOTH directions

Not optimal solution, but guarantee mobile networks are supported with minimal effort


NEMO Basic Suport: IPRIPR Page at the IETF

https://datatracker.ietf.org/public/ipr_disclosure.cgi

Enter 3963 in the RFC search engine

Cisco IPR statementNew (2004/10/25)

http://www.ietf.org/ietf/IPR/cisco-ipr-draft-ietf-nemo-basic-support-03.txt

https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=497

Former (2003/06/30)


Nokia IPR statement2003/07/01http://www.ietf.org/ietf/IPR/nokia-ipr-draft-ietf-nemo-basic-support.txt



IETF NEMO Basic Support: Home Network Models

NEMO WG draft-ietf-nemo-home-network-model

Extends the concept of home linkMR's HoA could be configured on the ingress interface (MNP) or on the egress interface (home link)

Extended home model: home link is contiguous to the NEMO

Aggregated home model: home link overlaps the NEMOs

Home link can be virtual

HAA:B:C:0/64

MR1 MRn

A:B:C:1/64 A:B:C:n/64

HA

A:B:C:/48MR1 MRn

A:B:C:1/64 A:B:C:n/64


NEMO: Prefix Delegation: Motivations and Requirements

Pb: How the MNP is allocated to the NEMOStatic or Dynamic ; Manual or Automatic

When: Bootstrapping

Renumbering

Requirements for large scale deploymentDynamic and Automatic

Allocation both on the home link, or from the access network

Authorization (when the MR claims a MNP)


NEMO: Prefix Delegation: Solutions

Based on DHCPv6 Prefix Delegation [RFC 3633]draft-droms-nemo-dhcpv6-pd-02.txt (issued Aug.04)

Role of DR (Delegating Router): HA

HA and DR functions must be co-located

Role of RR (Requesting Router): MR

NEMO BS Extensions draft-kniveton-nemo-prefix-delegation-00.txt (issued Dec.04)

Bootstrapping ; Expired MNPs ; New MNPs

4 steps: Provisioning ; Request ; Authorization ; Delegation

New Options: MNP Request ; MNP Confirmation

MiscAd-hoc

draft-chelius-nemo-router-autoconf-00.txt (issued Jan.04)


NEMO: IPv4/NAT traversal

The mobile network may be IPv6, but no guarantee that access networks will be IPv6 compliant

IPv4 traversal and NAT traveral is necessary to guarantee deployment and an Internet of wide spread and reach

Design team set up in May 2005Span MIP6 and NEMO WG activities

Problem Statement to be issued in July 2005

Possible solutions might also be proposed at the same time

Mailing [email protected]

Archives will be made available when work is concluded


Internet

AR

MR

Multihomed Mobile Network ConfigurationsA MR has multiple egress interfaces (heterogeneous access medias)

Multiple MRs

Result: Simultaneous Internet access via more than one egress interface

AR

Multiple interfaces Multiple MRs MR

AR

Network Mobility & Multihoming


NEMO & Multihoming: Motivations & benefits

Motivations for Multihoming:No technology or operator can provide an Internet access of wide spread and reach

The user/application has preferences/needs

price, bandwidth, politics, security, ...

Mobility = wireless links

Scarce bandwidth and higher delays

Link Failures arise more frequently

More errors and losses

Tunnel is a single point of failure

Requirements for NEMO: Keep a permanent and un-interrupted access to the Internet

Connect (simultaneously) to the Internet via several access networks

Switch to the best available access technology


NEMO Basic Support & Multihoming: Motivations & Benefits

Benefits:Redundancy

link failures arise frequently in mobile environments

1 tunnel = single point of failure

Ubiquity

Wide-area coverage, permanent and un-interrupted connectivity

Flexibility

specific policies from user/application

Price (competition between providers)

Load Sharing

Scarce bandwidth, higher delays, losses

Load Balacing

Bi-casting


For a Mobile Node (MN: MIPv6, MR: NEMO BS)Multiple interfaces or multiple prefixes on foreign link:

multiple CoAs

Multiple interfaces, multiple HAs or multiple prefixes on home link:

multiple HoAs

Result: multiple bi-directional tunnels between {HoA, CoA} pairs

For a MNN1 or multiple multihomed MR(s): multiple routes

Multiple MNPs: multiple addresses

Additional mechanisms will be necessary to take advantage of being multihomed

Multiple paths setup

Path survival

Path selection

NEMO Basic Support & Multihoming: Impact


IETF Monami6 BOF

Devices are more and more equipped with multiple interfaces

Very useful in mobile environmentsUbiquitous computing

Redundancy

Load Sharing

Etc

Mobile Ipv6 and NEMO Basic Support do not presently allow to use them simultaneously

MIP6: multiple (HoAs, CoAs) pairs

NEMO BS: multiple (MNPs, CoAs) pairs

Monami6: MObiles NOdes And Multiples Interfaces in Ipv6http://www.nautilus6.org/ietf

Mailing list, BOF description, draft charter, agenda

Next IETF meeting: **PARIS** August 1-5 2005.


IETF NEMO WG: Extended Support

Objective: Address Performance IssuesNested bi-directional tunnels

Route Optimization between CNs and MNNs

Many new cases introdruced by nested mobility

Seamless Mobility

Scalabilityetc, ...

WG not yet chartered to propose a solution to the performance problems

More investigation in the solution space is neededBased on some analysis the WG will decide to pursue (update charter) or to close the WG


IETF NEMO WG: Status as of June 2005NEMO RO Problem Statement

The WG is chartered to produce a problem statement document (analysis of the solution space)

Several draftsdraft-watari-nemo-nested-cn-01.txt

draft-thubert-nemo-ro-taxonomy-03.txt

draft-zhao-nemo-ro-ps-00.txt

draft-clausen-nemo-ro-problem-statement-00.txt

2 docs will be issued: Problem Statement, and Analysisdrraft-thubert to serve as the base input for the new docs


IETF NEMO WG: Status as of June 2005The WG will decide what to do next based on the results of the analysis

it may be re-chartered, or close down.

May be good to at least do some kind of optimization, like:Reducing overhead of the nested tunnels

Adapting Mobile IPv6 for VMNs

Avoiding routing within the infrastructure when both peers are in the same NEMO

Non-MIP6 approaches won't be done in the NEMO WG


Host Mobility (MIP6)vs

Network Mobility (NEMO)vs

Mobile Ad-hoc NETwork (MANET)


HA

AR

CN

Mobility Support: Host Mobility and Network Mobility

MR

Internet

MR

AR

HA

CN

Host Mobility SupportSingle Mobile Host (MH)

MH changes its point of attachment

MH must obtain a topologically correct address

Handled by MIP6 Working Group MH

MH

Network Mobility SupportEntire network mobile as a unit and attached to the Internet via a Mobile Router (MR)

One or more IP-subnets

One or more Mobile Router

MR changes its point of attachment

Only MR changes its IP address

Nodes behind MR don't change their own point of attachment

Handled by NEMO WG


Benefit of network mobility support over host mobility support

NEMO Basic Support

The vehicle changes its point of attachment to the InternetHost Mobility: each node maintains Internet access

Each host must perform Mobile IPv6

Network Mobility: only the mobile router (MR) maintains Internet access

Standards IPv6 nodes can be located behind the MR: no mobility support

Mobile IPv6


NEMO vs MANET

MANET: Mobile Ad-hoc networks

A network of mobile nodes

No fixed infrastructure

Highly dynamic topologies

All nodes are mobile routers

Purpose of MANET

Routing between mobile nodes

Does not seek to provide Internet access handovers from AR to AR

NEMO: NEtwork which is MObile

A network of nodes relatively fixed with respect to the mobile router

Focus on maintaing connectivity between MR and the fixed infrastructure

un-interrupted Internet access: handover from AR to AR

AB

CD

E

F


NEMO vs MANET: MANET made of NEMOs

HARenault

HomeLink: P_RenaulRoad/64

Each node in a MANET is a NEMO-enabled MR supporting an entire network

MANET protocol maintains routing between the NEMOse.g.: Each car is a NEMO, and the fleet of cars forms a MANET

AR

Road-side ForeignLink: P_Road/64

MR1

MR2

MR3

MR_CoA:P_Road::id_MR

P_Renault_1::id_MR


NEMO vs MANET: NEMO made of MANET nodes

HATrain

Home Link

Some MNNs in the NEMO can be MANET nodes

NEMO BS allows the MANET to change its gateway to the Internet

Routing between MANET-enabled MNNs is performed by a MANET protocol

e.g.: the train is a NEMO, but a group of passengers traveling together form a MANET.

ARForeign Link

MR

A B

C DE

F


WIDE Nautilus6 WG http://www.nautilus6.org

http://demo.nautilus6.org (Demo and IPv6 Test)


NEMO Related Activities: Nautilus

Nautilus6 WG @ WIDEObjective: Demonstrate IP-layer mobility and proceed to deployment

Main page: http://www.nautilus6.org

Demonstration page: http://demo.nautilus6.org

NEMO Basic Support implementation Completed on BSD variants (KAME NetBSD)

Ongoing on Linux (2.6 / MIPL 2.0 / USAGI IPv6 Kernel)

Demonstration of NEMO usages other than transportationGoal: demonstrate combination of network mobility with other features

PAN-like scenarios;

Multihoming / Nested configurations


NEMO Related Activities: Nautilus6: Demonstration Platform

MR:Soekris mother card (BSD), or Vaio type U (Linux)

LFNs: 4 IPv6 sensors designed by WIDEtemperature/humidity; direction; 2-axis acceleration; GPS

MIB, accessed by SNMPv1/UDP/IPv6

Powered by a modified PoE switch

Overall system powered with 8 ZR6 batteries or Slim60 external battery

Values displayed using MRTG or a JAVA application

egress interfaces2 of {WIFI, AirH, B-mobile, 3G, GPRS, ethernet}

Interface switching (vertical and horizontal handoffs), multiple CoAs

VMNs: VAIO U (operates MIPv6 or NEMO BS)

Webcam

Navigation tool


NEMO related activities: Nautilus6: Demonstration Platform

PAN Testbed designed so that it's easy to carry it to conferences

attractive demonstration

Generic usagese-bicycle

e-rickshaw

e-wheelchair

e-backpack

IPv6 sensor

Mobile Router

Webcam

PDA


NEMO related activities: Nautilus6: Network Features

Current:Permanent Access to Internet: NEMO BS

Nested mobility: Mobile IPv6 or NEMO BS

Vertical handoffs: preference settings

Multiple CoAs

Tunneling over IPv4 networks: DTCP

Coming soon:AAA (Diameter, EAP)

FMIPv6

NEMO Prefix Delegation

More multihoming features: HA-HA, ...

NEMO RO

Adaptive streaming


e-bicycle: for sport and tourismSport training: monitoring of the performance / health condition of the cyclist

Tourism: assist people in visiting cities (e.g. Bicycle rental at Kamakura) with navigation, historical guidance, etc

Sport competition / rallyes: live monitoring of progress, keep the cyclist informed (VoIP)

NEMO Related Activities: Nautilus : e-bicycle


NEMO Related Activities: Nautilus6: Monitoring: CN side


NEMO Related Activities: Nautilus6: Monitoring: MNN side

Follow and participate to next live sessionhttp://demo.nautilus6.org

If no live demo (most likely – since we ALSO work ;-)There is a FIXED permanent session


e-wheelchair: for people with disabilities and the elderly

Remote communication between wheelchair and third party (hospital, doctor, family)

Health monitoring

Increased dependance

Scenario: Live video streaming and health monitoring between wheelchair and hospital, using distinct access mediums, without disruption of service. Flow(s) is adapted to bandwidth.

How:Nested mobile network

1st PAN of equipement on the wheelchair

MR, IPv6 camera / IPv6 GPS / PDA

2nd PAN of sensors on the body

PDA, IPv6 Heart-beat sensor / IPv6 temperature sensor

NEMO Related Activities: Nautilus : E-Wheelchair Demo

IPv6 Sensor

Mobile Routeur PDA

Webcam

PAN


NEMO related activities: Nautilus6: e-wheelchair: PAN in a PAN

IPv6 Sensor

Mobile Routeur PDA

Webcam

PAN

Heart-beat SensorPub lic Internet Ac c ess

On-Body PAN

Wireless Lan

Pub lic Internet Ac c ess


Questions ?Thierry Ernst

[email protected]

http://www.sfc.wide.ad.jp/~ernst/

http://www.nautilus6.org

IETF NEMO WG: http://www.ietf.org/html.charters/nemo-charter.html

NEMO Additional IETF page: http://www.mobilenetworks.org/nemo

Nautilus6 (NEMO-related activity): http://www.nautilus6.org

Book: 20000 Leagues Under the Sea (Jules Verne)

NEMO: Network Mobility Support in IPv6 · PDF fileThierry Ernst - Network Mobility Support in...

Documents

Transcript of NEMO: Network Mobility Support in IPv6 · PDF fileThierry Ernst - Network Mobility Support in...