1 Multi-Domained, Multi-Homed Mobile Networks Mobile Platform Internet (MPI) mailing

1

Multi-Domained, Multi-Homed Mobile Networks

Mobile Platform Internet (MPI) http://www.multicasttech.com/mpi/

mailing list: [email protected]

Terry Davis – Boeing ([email protected])Will Ivancic – NASA Glenn ([email protected])

2

Common Sectors

• Aviation

• Maritime

• Trains

• Trucking (Shipping)

• Automotive

• Others ???

3

High Speed SatCom Network• Globally Available • Affected by Weather• Higher Bandwidth• High Latency• High Cost

Low Speed SatCom Network• Globally Available• Low Bandwidth• High Latency• Very High Cost• Redundant

High Speed LOS Network• Globally Available • High Bandwidth• Low Latency• Lower Security• Moderate Cost

High Speed Terrestrial• Not Available when Mobile • High Bandwidth• Low latency• Lower Cost

OperationsCommand and

Control

Mobile Network

How do you decide which path the data should take?How do you cause the network(s) to route the data via this path?

Destination Network(for Operations)

Destination Network(for Command & Control)

Internet

Entertainment

How Do You Select and Implement the Routing Path?

Destination Network(for Entertainment)

Low Rate VHF• Reliable• Low Latency

4

Aviation Specific Issues• Safety of Life / Safety of Flight

– Time-Critical command and control for Air Traffic Control • Fast convergence time is essential!

• New radio link technologies are “uncertified” for Air Traffic Control / Air Operations Communications (ATC/AOC)

• Regulatory requirements force network design • Three independent network domains

– (required for regulatory, QoS, & security)– Passenger & In-Flight-Entertainment– Airline Operations– Air Traffic Control

• Service providers may be authorized to carry one, two, or all services.

• ATC will be a “closed network”• Multiple security and authentication architectures

5

Airplane Communications

Aircraft ControlDomain


Airline InformationServices Domain


PassengerInfo. and EntertainServices

Domain


Domain

Passenger-ownedDevices


Air-GroundNetwork Interface



Control the AircraftControl the Aircraft Operate the AircraftOperate the Aircraft Inform/Entertain the PassengersInform/Entertain the Passengers

CLOSED DomainCLOSED Domain PRIVATE DomainPRIVATE Domain PUBLIC DomainPUBLIC Domain

Airport Network(e.g., Gatelink)

Passenger-accessed3rd Party Providers


Airline-Approved3rd Party Providers


AirlineAirline

Air Traffic ServiceProviders


Air-GroundBroadband Network(e.g., INMARSAT)

Air-GroundDatalink Services(e.g., ACARS)

VHF / HF /SATCOM

WirelessLAN

SATCOM/Cellular

Aircraft






Domain


Domain






Control the AircraftControl the Aircraft Operate the AircraftOperate the Aircraft Inform/Entertain the PassengersInform/Entertain the Passengers

CLOSED DomainCLOSED Domain PRIVATE DomainPRIVATE Domain PUBLIC DomainPUBLIC Domain

Airport Network(e.g., Gatelink)





AirlineAirline



Air-GroundBroadband Network(e.g., INMARSAT)

Air-GroundDatalink Services(e.g., ACARS)

VHF / HF /SATCOM

WirelessLAN

SATCOM/Cellular

Aircraft

6

In-Air Communication

• Multiple networks with varying criteria for utilizing different links– Aircraft Control Domain– Airline Information Services Domain– Passenger Information and Entertainment Services

Domain

• Often multiple links will be active to the same domain simultaneously.

• May need to have connectivity to 10 or more ISPs depending on what airports one flies into– Need to autonomously connect to service providers– Each airport controls the ISP contracts

7

ISO Aeronautics Telecommunication Network (ATN) Island Routing Domain Confederation

ATN TRD ATN TRD

ATN Backbone RDC

ATN TRDATN ERD

ATN ERD

ATN Island RDCMobile RD

Mobile RDMobile RD

AnotherATN Island

ERD – End Routing DomainRD – Routing DomainRDC – Routing Domain ConfederationTRD – Transit Routing Domain

OSI IDRP Routing• Controlled topology to ensure rapid route prorogation

Routing Protocols requires ownership/coordination of infrastructure

• Injecting routes • Not deployed due to cost

8

BGP/OSPF for Air Traffic ControlE-BGP requires configuration with each Autonomous Systems.

This is a scalability problem.

Mobile-1

BGP

Mobile-2

BGP

Mobile-N

BGP

BGP/OSPF

BGP/OSPF

BGP/OSPF

BGP/OSPF

OSPF

AREA 1

OSPF

AREA N

OSPF

AREA 0

Air Ground

If you don’t own the infrastructure, you

probably will not be allowed to inject routes!

This may work for ATC, but not for AOC or Passenger Services(AOC is a closed network and will not propagate routes to the world)

9

Multiplexing at the Radio

MUXNEMO-1

HANEMO-1 Satellite

MUXNEMO-2

HANEMO-2 WiFi

MUXNEMO-3

HANEMO-3 VHF

ATCATC

AOCAOC

PassengerPassenger

If one requires a separate nemo router for each domain, then,

failure to Multiplex requires a radio for each interface!

10

Antenna Systems

Note, this picture does not show:• Satellite links• Passenger service links• Gate links (WiFi)• Gate links (umbilical cord)

11

SATCOM AERO-1

SATCOM AERO-HH

VHF Voice/DAT

A

HF Voice/DAT

A

GateLink

INMARSAT Swift 64

High-Rate Satellite

WiFi Max

Cellular

Future Links

Mobile Router

Operations LAN

(Avionics)

Communication and Display

Passenger Services

Air Traffic Managemen

t LAN

Sensor Controller (Optional Display)

NEM0-1 NEMO-2 NEMO-3

Mobile Network

1

Mobile Network

2

Mobile Network

3

Multiplexing at the Router

12

Global HAHA for NEMO

PrimaryHome Agent

SecondaryHome Agent

Secondary Home Agentprovides pseudo route optimizationwhich is useful over long distances

X

Beware of VPN tunnels.

If security is not considered up front, it may negate route optimization!

VPN Endpoint

VPN Endpoint

13

Global HaHa• Draft allows for

– Distribute HAs at IP layer• HA to HA communications at layer 3 to get rid of home link in

configurations where it is not needed

– MIP proxy for local mobility management• to allow a mobile router to bind locally as it is roaming far away

from any of its own home agents

– Pseudo route optimization in the infrastructure

• No Security• Concerns

– How is routing accomplished to get to appropriate HA?– How many home agents will aviation need?– How fast can one switch to a new home agent?

14

Monami6 for Aeronautics

15

Multiple Links to Aircraft

• Failover for safety-of-life critical control traffic

• Separation of governmental control, airline corporate, and passenger network traffic– Differing priorities on same link– Differing link forwarding selection according to

policy

16

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-DATAHome Agent

Policy-Based Routing, All Links Active

Mobile Router

17

High speed link

int2

int3

Routing Policy

Routing Policy

int1Low latency link

Reliable linkATC

ATCATC

ATCAOC

AOC

P-DATA

P-DATA

P-DATAHome Agent

Policy-Based Routing, Critical Link Active

Mobile Router

18

High speed link

int2

int3

Routing Policy

Routing Policy

Home Agentint1

Low latency link

Reliable link

ATC

ATC

ATC

AOC

AOCAOC

P-DATA

P-DATA

P-DATA

P-DATA

P-DATAP-DATA

Policy-Based Routing, Passengers Link Active

Mobile Router

19

Multiple Care-of Addresses

• Some governments provide VHF/UHF air-to-ground network infrastructure

• Multiple commercial service providers for satellite and other links

• Removes potential single-point-of-failure for safety-of-life traffic

Multiple HAs

20

Within Monami6 ...• Assume an aircraft has a NEMO MR with X links

and care-of addresses, and Y geographically distributed home agents – X*Y bidirectional tunnels

– But only a few active at one time

• At MR, downlink tunnel selection (CoA and HA pair) based on policy for traffic class of each packet

• At HA, uplink tunnel selection (CoA) based on policy

• Different security mechanisms for each tunnel based on policy

21

Desires

• Multiple CoA option works for NEMO– GOOD based on draft-ietf-monami6-

multiplecoa-00

• Support use of flow binding option for NEMO HA-MR tunnel selection– draft-soliman-monami6-flow-binding-02 is

currently worded very mobile-node (not NEMO) centric, although seems to work well for NEMO too

22

Recommendations / Desires

23

Recommendations / Desires• Need Route Optimization for Large Mobile

Platforms that move over large geographical areas.– Global HAHA is a potential – Other proposals also should be considered

• Including work being done in IRTF MOBOPTS

• It is highly desirable to have multiple NEMOs in a single router (multi-domained nemos)– What are the security implications of this?

• Need to examine Security Architecture relative to mobility mechanisms– If we are not careful, security may undo route

optimization.– Ensure the IKEv2 and revised IPsec architecture are

considered

24

Recommendations / Desires

• Aspects of MANET Autoconfiguration may be applicable to traditional routing for large mobile systems regarding the air/ground interface addressing.

• MONAMI6 currently appears to be handling the needs of large mobile platforms.

• It would be advantageous if the filtering mechanisms and policy-base routing for monami6 worked with a hybrid nemo/mip/traditional routing configurations.

25

Non-IETF (?) Issues or Not?

• Automated access to networks – particularly access to radio systems (Internet Docking for Mobile Networks)

• Implementation solutions are a combination of architecture, protocol and policy. Is it appropriate to have an “Informational document” for large mobile platforms?

26

Mobile Platform Internet (MPI)

• Web Page:– http://www.multicasttech.com/mpi/

• To Join to the mailing list, E-mail to: – [email protected]

Documents

1 Multi-Domained, Multi-Homed Mobile Networks Mobile Platform Internet (MPI) mailing