Multi-Domained, Multi-Homed Mobile Networks

1. Multi-Domained, Multi-Homed Mobile Networks To Join to the Mobile Platform Internet (MPI) mailing list, E-mail to: MPI-subscribe@multicasttech.com Terry Davis – Boeing (terry.l.davis@boeing.com) Will Ivancic – NASA Glenn (william.d.ivancic@nasa.gov)

2. Common Sectors • Aviation • Maritime • Trains • Trucking (Shipping) • Automotive • Others ???

3. Low Rate VHF • Reliable • Low Latency Destination Network (for Entertainment) How Do You Select and Implement the Routing Path? • 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 Entertainment Mobile Network Command and Control Operations • High Speed Terrestrial • Not Available when Mobile • High Bandwidth • Low latency • Lower Cost • High Speed LOS Network • Globally Available • High Bandwidth • Low Latency • Lower Security • Moderate Cost Internet Destination Network (for Operations) Destination Network (for Command & Control) How do you decide which path the data should take? How do you cause the network(s) to route the data via this path?

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

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 Mobile RD Mobile RD Another ATN Island ATN Backbone RDC ATN TRD ATN TRD Mobile RD ATN Island RDC ATN TRD ATN ERD • OSI IDRP Routing • Controlled topology to ensure rapid route prorogation • Routing Protocols requires ownership/coordination of infrastructure • Injecting routes • Not deployed due to cost ATN ERD ERD – End Routing Domain RD – Routing Domain RDC – Routing Domain Confederation TRD – Transit Routing Domain

8. OSPF AREA 0 OSPF AREA N OSPF AREA 1 BGP BGP BGP Mobile-2 Mobile-N Mobile-1 BGP/OSPF BGP/OSPF BGP/OSPF BGP/OSPF BGP/OSPF for Air Traffic Control E-BGP requires configuration with each Autonomous Systems. This is a scalability problem. If you don’t own the infrastructure, you probably will not be allowed to inject routes! Air Ground 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. NEMO-1 HA NEMO-2 HA NEMO-3 HA MUX MUX MUX VHF Satellite WiFi Multiplexing at the Radio ATC ATC NEMO-1 AOC AOC NEMO-2 Passenger Passenger NEMO-3 If one requires a separate nemo router for each domain, then, failure to Multiplex requires a radio for each interface!

10. Independent Systems

11. Passenger Services Operations LAN (Avionics) Air Traffic Management LAN SATCOM AERO-1 Multiplexing at the Router Communication and Display SATCOM AERO-HH Mobile Network 1 VHF Voice/DATA Mobile Router HF Voice/DATA Mobile Network 2 NEM0-1 NEMO-2 NEMO-3 INMARSAT Swift 64 High-Rate Satellite Sensor Controller (Optional Display) WiFi Max Mobile Network 3 GateLink Cellular Future Links

12. X VPN Endpoint VPN Endpoint Beware of VPN tunnels. If security is not considered up front, it may negate route optimization!  Secondary Home Agent Global HAHA for NEMO Primary Home Agent Secondary Home Agent provides pseudo route optimization which is useful over long distances

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. Policy-Based Routing, All Links Active P-DATA P-DATA High speed link Mobile Router P-DATA P-DATA AOC Home Agent int1 P-DATA Low latency link ATC AOC AOC ATC int2 P-DATA Reliable link int3 ATC ATC AOC Routing Policy Routing Policy

17. Policy-Based Routing, Critical Link Active P-DATA Mobile Router High speed link P-DATA AOC Home Agent int1 Low latency link ATC AOC ATC int2 P-DATA Reliable link int3 ATC ATC Routing Policy Routing Policy

18. Policy-Based Routing, Passengers Link Active P-DATA High speed link P-DATA Mobile Router P-DATA P-DATA AOC ATC AOC Home Agent int1 P-DATA Low latency link ATC AOC int2 P-DATA Reliable link int3 ATC Routing Policy Routing Policy

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 Mailing List • To Join to the mailing list, E-mail to: • MPI-subscribe@multicasttech.com