NEMO: Network Mobility in IPv6 Applicability to Intelligent … · 2007-11-30 · Hnd-ovr Secur MAC...

Thierry Ernst – Global IPv6 Summit – Mexico - November 2007

NEMO: Network Mobility in IPv6-

Applicability toIntelligent Transport Systems (ITS)

[email protected]

IETF NEMO WG & MonAmi6 WG Chair

INRIA IMARA project-team / JRU LARA

http://www.lara.prd.fr

http://www.lara.prd.fr/

Thierry Ernst – Global IPv6 Summit – Mexico - November 2007 2

Introduction: IPv6 Mobility Needs and UsagesIPv6 is the opportunity to use the Internet differently

New usages that nobody would ever think of in IPv4New usages = new services = new equipments = new business

End systems are becoming mobilePDAs, Mobile Phones, Laptops, Vehicles

Networks are becoming mobileSensor networks in vehiclesAccess networks in vehicles (bus, aircraft, taxi)PANs (Personal Area Networks): emergency units, army, everyone

Usages:Health-care (elderly or disabled people)Telematic/ITS (emergency call, fleet management, navigation, ...)Emergency units (Army / Police / Fire Crew)Education / Journalism / Tourism


ITS Usage: Need for communicationsITS: Intelligent Transportation Systems

Benefits of communicationsCollision avoidance (time critical)Vehicular congestion avoidance (time critical)Automatic driving (time critical)Fleet managementRemote Control & MonitoringOn-board entertainment

Communication protocol architecture from ISO TC204WG16 (CALM)

Based on IPv6 and mobility features (NEMO, etc)IETF is defining the standardsISO is defining the architectureOther bodies are validating the concept

Europe: CVIS - http://www.cvisproject.orgJapan

http://www.cvisproject.org/


IP-Layer Mobility: Various communication medium

Internet

HA

V2V & V2I communication crucial for ITSIn-vehicle devices will require (continuous) Internet connectivityInternet connectivity will be provided transparently to theapplications through a range of access technologiesGPRS/3G, IEEE 802.11 a/b/g, IEEE 802.11p, DSRC, ...


IP-layer Mobility: In-vehicle network

Internet

HA

Vehicles will be fully networkedIn-vehicle networkPrefix (MNP: Mobile Network Prefix) is assigned to the mobilenetworkOn-board units (MNNs) have their addresses taken from MNP


IP-layer Mobility: Addressing in IPv6

AR Prefix-1::id_MR

HA

BR

Prefix-1

Prefix-2::id_MR

AR Prefix-2

Prefix-X::id_MR

Address must be topologically correctEach interface must have an @ formed after the prefix advertised on thelink where it is attachedChange of point of attachment = change of IP subnetChange of IP subnet = change of @ & routing directive

ProblemChanging IP address breaks connectionsRetaining IP address breaks routing

Mobility support mechanismsneeded to maintain ongoing sessions

Prefix-X::id_MR


IP-Layer Mobility: Network Mobility Support

HA

NEMO Basic Support manages mobility of the entire network.Only the Mobile Router manages mobilityCurrent address recorded at the HA (dedicated server)Nodes inside the moving network do not need to participatein mobility management


MNP P1/60

MR

NEMO: NEtwork MObility Basic Support (RFC 3963)

AR

InternetHA

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

Prefix P2/64

Prefix P1/48

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

Movement to a foreign linkMR and MNNs retain their initial addressesMR obtains a CoA on the foreign link

Registration with HAMNP -> MR-CoA instead of MR-HoA-> MR-CoA

RoutingEncapsulation between HA and MR

MNPS:MR D:HA

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


Network Mobility Support: Benefit

NEMO Basic Support

Network complexity brought back to the routerOnly the mobile router manages mobility and maintains Internet accessthrough ore or several access technologiesNodes behind the mobile router are standard IPv6 nodes with no mobilitysupport mechanisms

Mobile IPv6


MONAMI6: MObile Nodes And Multiple Interfaces in IPv6Charter: http://www.ietf.org/html.charters/monami6-charter.html

Path Set Up: How to establish multiple tunnels simultaneously ?MN/MR Must be able to register multiple CoAs

Path Selection: How to select the appropriate tunnel ?Policies must be exchanged between the HA and MN/MR

HA (Central System)HA (Central System)

MR (Vehicle System)MR (Vehicle System)

3::13::11::11::1

2::12::11::11::1

CoACoAHoAHoA

Binding CacheBinding Cache

InternetInternet

Mobile Edge Multihoming: IETF MonAmi6

802.11 interface: CoA 2::1 GPRS interface: CoA 3::1

http://www.ietf.org/html.charters/monami6-charter.html


MIP6

IPv6

MULTI6

NEMO

MIPSHOP

HostMobility

Multihoming

NetworkMobility

Signaling and handoffoptimization

IETF: IPv6 Mobility Activities

MobileIP

MIP4

MonAmi6

Shim6

MObile Nodes AndMultiple Interfaces

in IPv6

Host Mobility SupportProto: Mobile IP,HMIPv6, FMIPv6End sysyems that change point ofattachmentWG: MIP4, MIP6, MIPSHOP (+ IRTFMobOps)

Network Mobility SupportProto: NEMO Basic SupportEntire networks that change point ofattachmentWG: NEMO

Ad-hoc networksRouting protocols for infrastructure-less networksWG: MANET

MultihomingWG: MonAmi6, Shim6


IETF NEMO WG: Status

Charter: http://www.ietf.org/html.charters/nemo-charter.html

Aug. 2000: Initial discussion started in Mobile IP WGOct.2002: NEMO (NEtwork MObility) WG created

Chairs: Thierry Ernst / TJ Kniveton2002-2006 missionsdefine terminolog & requirementsstandardize a basic solution for network mobility supportissue problem statement for RO and multihoming

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



Document StatusRFC 3963: NEMO Basic SupportRFC 4885: NEMO TerminologyRFC 4886: NEMO Goals and RequirementsRFC 4887: NEMO Home Network ModelsRFC 4888: NEMO Route Optimization Pb StatementRFC 4889: NEMO Route Optimization Sol. Space AnalysisRFC 4980: NEMO Multihoming AnalysisNEMO MIB: ongoingNEMO Prefix Delegation: ongoing

Related documents in MIP6 WGProblem Statement: Dual Stack MobilityMobile IPv6 Support for Dual Stack Hosts and Routers (DSMIPv6)



2007 missionsGather NEMO requirements from 3 use casesAutomobileAviationPersonal mobile router

68th IETF presentation materialhttp://www3.ietf.org/proceedings/07mar/index.html

July 2007: Moving forwardNEMO, MonAmi6 and MIP are merging into a single WGMobility EXTensions for IPv6 (MEXT)

http://www3.ietf.org/proceedings/07mar/index.html


IETF MonAmi6 WG: StatusMONAMI6: MObile Nodes And Multiple Interfaces in IPv6

Charter: http://www.ietf.org/html.charters/monami6-charter.htmlInitial discussion started in the Mobile IP WG

Need and solutions to support multiple & simultaneous interfacesNeeded for NEMO and Mobile IP deployment

Oct. 2005: MONAMI6 WG createdChairs: Thierry Ernst / Nicolas Montavont

DeliverablesMotivations for a node using multiple interfaces and thescenarios where it may end up with multiple addressesAnalysis explaining what are the limitations for mobile hostshaving multiple addressesA protocol extension to Mobile IPv6 (RFC 3775) and NEMOBasic Support (RFC 3963) to support multiple registrationsA "Flow/binding policies exchange" solution for an exchangeof policies between mobile host/router and Home Agent

http://www.ietf.org/html.charters/monami6-charter.html


ISO TC204 WG16: CALMISO TechnicalCommittee 204: Currently 12 active WGs

http://www.iso.org/iso/iso_technical_committee.html?commid=54706

WG 16: Wide Area CommunicationsSince Y 2000 / Led by Russell Shields (Ygomi)CALM: Communication Architecture for Land Mobile

Renamed from Communications Air-interface, Long and Medium rangeDocs:

Web: http://www.calm.huCALM Handbook

7 sub-WGsSWG 16.0: CALM ArchitectureSWG 16.1: CALM MediaSWG 16.2: CALM NetworkSWG 16.3: Probe DataSWG 16.4: Application ManagementSWG 16.5: Emergency notifications (eCall)SWG 16.6: CALM ad-hoc subsystem

http://www.iso.org/iso/iso_technical_committee.html?commid=54706


ISO TC204 WG16: 7 Sub Working Groups


Variable Message Sign

Hot-Spot(Wireless LAN)

Terrestrial BroadcastRDS, DAB

UMTSWiMAX

Beacon•CALM-M5•CEN-DSRC•CALM-IR

GPS, Galileo

Info-Broadcaster

BroadcastTransmitter

Vehicle-to-Vehicle (M5, IR, MM)

GSM-GPRS

Sat-Comm

PDA,SmartPhone

The generic Comm ArchitectureThe generic Comm Architectureis CALMis CALM

ISO TC204 WG16: CALM Communication Media


ISO TC204 WG16: CALM Communication MediaCommunication architecture allowing V2V, V2I andcontinuous Internet access through multiple radiotechnologies (potentially used simultaneously)

Media:Cellular (CALM 2G/3G) – cf CD 21212 & CD 21213Infrared light (IR) – cf CD 21214Microwave (CALM M5) – cf CD 21215

IEEE 802.11 a/b/g (WIFI)IEEE 802.11p (mobile WIFI)

Millimeter waves (CALM MM) – cf CD 21216Microwaves CEN DSRC

IPv6:Internet connectivityUnification layer of underlying technologiesStandardized at the IETF to replace IPv4 (current version)2128 available global addresses (instead of 232)


ISO TC204 WG16: Communication Scenarios


ISO TC204 WG16: CALM Architecture

CALMARCHITECTURECALMARCHITECTURE

- Standards thatareoutsideCALMscope- Standards thatareoutsideCALMscope SAP - ServiceAccessPoint–DataTransfer

SAP - ServiceAccessPoint–Management

MediaFunctionblocksshownabovemaybepartof amorecomprehensivecommunicationsdevice.

2Gcellularstdbyreference

CALM2GManagerISO21212

SAP



SAP

NetworkingManagementISO21210-3

CALMsystem

ManagementEntity(CME)

ISO21210-2

NETWORKINTERFACERoutingandMediaSwitchingbasedon IPv6

ISO21210-1

Non-CALM-awarePoint-to-pointAPPLICATIONS

Convergence LayerISO15628/ISO21210-5

SAP

CALM-AwareAPPLICATIONS

Layer5-7INTERNETSTANDARDS

SAP

SAP SAP

CommonStation,PHY, MAC,LLCManagersISO21210-4

SAP

SAP

SAP

SAP

DirectoryServicesISO21210-5 SAP

SAP

Non-CALM-awareIP (Internet)

APPLICATIONS

Convergence LayerIPsocket/ISO21210-5

SAP

SAPSAP

SAP

CALMMM

CALMMMManagerISO21216

SAP

CALMMM

CALMMMManagerISO21216

SAP

CALMM5

CALMM5ManagerISO21215

SAP

CALMM5

CALMM5ManagerISO21215

SAP

CALMIR

CALMIRManagerISO21214

SAP

CALMIR

CALMIRManagerISO21214

SAP



SAP



SAP

In- VehicleNetwork

LowerLayers

In-VehicleNetConvergenceISO212??

SAP


ProprietaryProtocolB

Proprietaryor

DedicatedRadioInterface

ProprietaryProtocolC

Proprietaryor


ProprietaryProtocolA

Proprietaryor


App. 1 App. 2 App. 3ALL ITS

APPLICATIONS

TCP UDP

Stream &RealtimeProtocols

ISODSRCL7

HTTP/SMTPProtocols

MAC

802.11pWAVE

InitHnd-ovrSecur

MAC

2G/3GGSM

InitHnd-ovrSecur

MAC

IR

InitHnd-ovrSecur

L2/UDP

…

IPv6 layer

ServiceQoS

InterfaceSelection

Handover

InterfaceQoS

ISO TC204 WG16: CALM Architecture


ISO TC204 WG16: CALM NetworkingCALM Networking: ISO 21210

21210-1: Internet Connectivity (Committee Draft)21210-2: Fast Application (draft)

Medium Selection & SwitchingHorizontal handover: between access points using the same mediaVertical handover: heterogeneous handoversPurpose: Continuous communication during handoffSelect the most appropriate media based on application needs

IP & non-IP servicesBased on IPv6 and mobility features (NEMO, MIPv6, etc)IPv6 not considered for time critical applications (collision avoidance)


CVIS: FP6 Integrated Project (IP)Cooperative Vehicle-Infrastructure System

http://www.cvisproject.orgFrom Feb. 2006 till Feb. 201061 partners / 12 countries / Total Budget: 41 Millions Euros

ObjectivesDevelop, trial & demonstrate

Inter-operable architecture for vehicular communicationsNovel applications for:

Cooperative traffic and road network monitoringCooperative road & traffic network management & controlCooperative logistics & fleet managementCooperative public transport & intermodality

VisionUse and extend existing standardsProduce open design and softwareOutput intended to be reused by other EC projects

CVIS: FP6 Integrated Project (IP)

http://www.cvisproject.org/


CVIS: FP6 Integrated Project (IP)Communication Sub-Project (SP 2.1 COMM): Vehicle-Infrastructure communications

± 23 partnersApprox 23% of CVIS overall budgetSpecify & Implement communication architectureLiaison with other EU-funded projects / ISO / IETF / C2C-CC

Communication architecture inspired from ISO TC 204WG16 'CALM' architecture

CALM is adapted and simplified

CALM: Communications Air-interface, Long and Mediumrange

CALM Handbook: http://www.calm.hu

http://www.calm.hu/


CVISHost

CVISRouter

Antenna

OEMGateway

SENS

SENS

CtrlCtrl

CVIS: Vehicle ConfigurationIn-vehicle IPv6 subnet

CVIS Router: Mobile Router maintaining Internet Access throughseveral physical interfacesCVIS Host: run dedicated ITS applicationsOEM: Gateway between IP and CAN


Roadside System

Vehicle System

CVIS: IPv6 Communications between subsystems

Internet

Central System

TunneledIPv6

(MNN)

VehicleHost

MobileRouter

Antenna

VehicleGateway

SENS

SENS

CtrlCtrl

Service

Centre

Control

Centre

Internet

Authority

Databases

HomeAgent

CentralHost

Gate-way

BorderRouter

CentralHost

Gate-way

BorderRouter

CentralHost

Gate-way

BorderRouter

VMS Ant

SENSCtrl

AccessRouter

RoadsideHost

RoadsideGateway

BorderRouter


Standard Automotive PC Hardware + RTLinux

AdvancedRouting

Antenna(Roof Layer)

Media HW

PlatformCore

Functions

CALM SWExtensions

5 +MDSRC

/GPSGalileo 2 /3G G IR

COMMManager

Rooftop Antenna IR

-Media plug in Manager

CVIS Router Platform Layers


FOAMHMI Security Vehicle API Mntg Agent

Operating System and Hardware

-Real timeapps

COMOserver

POMAMapping server

( )native JVM

( )Runtime environment OSGi

ParkBooking

SmartAccess

.DangGoods

CooperativeDriving

CooperativeGuidance

Apps

Services

PlatformCore

Functions

CALM Manager

Middleware

9

CVIS Router Platform Layers


CVIS: Communication Architecture Key FeaturesNEMO: Maintain Internet access

Continuous communication during handoffHorizontal handover: between access points using the same mediaVertical handover: heterogeneous handovers

MonAmi6: Mobile Edge multihomingManage simultaneous access to the Internet (multiple interfaces)

Medium Selection & SwitchingSelect the most appropriate media based on application needs

IPv4-IPv6 TransitionAllow IPv6 communications over IPv4 access networksAllow CVIS nodes to communicate with IPv4

IP & non-IP servicesIP not considered for time critical applications (e.g. collisionavoidance)


ITS Usage: Related Activities MonAmi6 WIDE

ICAR


ITS Usage: Related ActivitiesWIDEICAR

MonAmi6


ITS Usage: Self-Driving Cars (INRIA IMARA / LARA)IMARA Current Activities and Plans

Studying V2V and V2I communications under specific vehiculartraffic and IP access network patterns (experiment & simulation)Integrating NEMO & MANET (MANEMO)Using CVIS implementation

We are now actively pushing for ... ... IPv6


NEMO Usage: Emergency Units (PAN + Telematic)Techno

Wearable devices (IP phone, laptop, carrried by emergency doctor) +devices kept in vehicle (heartbeat sensor, GPS, ...)Vehicle maintains access to the Internet (multiple technologies) andprovides connectivity to wearable devices (WIFI)

ServicesVideo/Images transmitted from the accident to the headquarters (so far,dialogue with headquarters was made using a cellular phone)Heartbeat and temperature provided by sensors

Mobile ER Pilot Test in Japan (NAIST)http://www.ipv6style.jp/en/special/20051031_2/index.shtml

http://www.ipv6style.jp/en/special/20051031_2/index.shtml


NEMO Usages: ValidationConformance and Interoperability testing

ETSIIPv6 test specifications and methodology (based on TTCN3 newtesting language)Plugtests

TAHI IPv6 and Moonv6 interoperability eventsEuropean Commission and associated projects

STFs (236, 256, 276)Go4IT, ANEMONE projects, …

IPv6 Logo Program Word-Wide Initiative5 teams in the technical committee (v6LC) linked to the IETF: Asia(TAHI, BII, TTA), USA (IOL-UNH),NEMO Basic Support in Gold logo

Current trend in EC projects is towards IPv6 (& NEMO)a testbed is needed for evaluating scenarios and solutions in real-life conditionssetting up required components of testbed is cumbersome


NEMO Validation Testbed: ANEMONEFP6 STREP

First large-scale IPv6 mobility-oriented testbed in Europehttp://www.ist-anemone.eu

Variety of test sitesWide-area outdoor & IndoorTypes: Campus / Metropolitan

Multiple IPv6 access technologies802.11 a/b/g, HiperLan, UMTS, GPRS

Mobility servicesNEMO / MIP6 / MCoAHA

IPv6 multimedia servicesWeb, Voice over IP, IP TV, Video on DemandExperimental IP Multimedia Subsystem

Security & Access control mechanismsTLS / IPsec

http://www.ist-anemone.eu/


NEMO Validation Testbed: ANEMONE


Conclusion: NEMO from Research to DeploymentIETF is in charge of IPv6 protocols standardization (bricks)

WGs NEMO / MonAmi6 / MIP6 / etc.

Complete architecture are defined somewhere elsee.g. ISO for ITS (ISO TC204 WG16 – CALM)

NEMO implementations & products:SHISA (BSD), NEPL (Linux), CISCO, etc.

Test & ValidationANEMONE (EC IST 6th Framework http://www.ist-anemone.eu/)Proof of Concept: Progressing technical know-how (e.g. CVIS)Conformance test & interoperability

Deployment:coming soon


Conclusions: ITSISO is defining the CALM architecture

Uses IETF standards (IPv6, NEMO, etc)CVIS is validating the CALM architecture conceptCVIS know-how can improve ISO standards and help the IETF todevelop new standards needed for ITS communications

IP is the convergence layerwill allow interoperability between V2V and V2I architectureswill allow interoperability between dedicated ITS applications andother Internet usageswill save costs and boost innovation

IPv6 is not an option for wide development of IP-based ITSapplications

ITS needs the advanced features provided by IPv6 (NEMO, etc)ITS needs a large address space: millions of vehicles with multipledevices each requiring a public global address

Toomany vehicles for NAT


Conclusions: The ITS WorldThe ITS world

Well-marketed and organized industryExisting businesses very reluctant to new technologiesStrong inertia to changeProprietary communication systemsLimited IP-based solutions / use cellular networks

The IST world and IPv6Only discovering IPv6No experience in IPv6 development and operationDoesn't know what are the benefits of IPv6 and the limits of IPv4The more informed ones think that the transition from IPv4 to IPv6is transparent to their businessIPv6 not an option for wide development of IP-based ITSapplicationsNot considering IPv6 from the early design will bring costs


Conclusions: IPv6 FactsWhen do we need to start to think about IPv6 ? NOW !

DeploymentNot considering IPv6 from the early design will bring costsIPv6 is currently being deployed (not an utopia) and doesn'trequired to shut down IPv4IPv6 will be the norm by the time new usages get deployedMake sure applications deployed today are IPv6-compliant

IPv4 address space exhaustion date recently revisedIANA count down set to Dec. 2009http://www.potaroo.net/tools/ipv4/http://xkcd.com/c195.htmlhttp://www.arin.net/statistics/statistics.pdfhttp://www.arin.net/announcements/20070521.html


Conclusion: France and IPv6A long history

INRIA involved in IETF specifications since the first dayINRIA developed first IPv6 stack

G6Association set up 10 years ago to deploy an IPv6 testbed betweena number of universities –IPv6 fully operational within RenaterIPv6 training (tutorials, etc)IPv6 book

IPv6 Task Force FranceLaunched at the Sénat in Sept.2002Part of the G6 since 2007: http://www.g6.asso.fr/tffNot enough involvment from the industryMostly academia

http://www.g6.asso.fr/tff

Thierry Ernst – Global IPv6 Summit – Mexico - November 2007

Questions ?

[email protected]

IETF NEMO WG & MonAmi6 WG Chair

INRIA IMARA project-team / JRU LARA

http://www.lara.prd.fr

mailto:[email protected]

http://www.lara.prd.fr/

NEMO: Network Mobility in IPv6 Applicability to Intelligent … · 2007-11-30 · Hnd-ovr Secur MAC...

Documents

Transcript of NEMO: Network Mobility in IPv6 Applicability to Intelligent … · 2007-11-30 · Hnd-ovr Secur MAC...