LISP: A NOVEL APPROACH TOWARDS AN FCI MULTILINK SERVICE Wolfgang Kampichler, Manfred Lindner, Bernhard Haindl, Dieter Eier, Bernhard Gronau
32nd DASC, Syracuse, NY, 10/2013 2013-10-09
KAMPICHLER Wolfgang
Outline LISP Base Ideas LISP Basic Elements and Examples FCI and Multilink Concept Mobility in Aeronautics (LISP use case) Summary
Page: 2 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
LISP Base Ideas Locator / Identifier Separation Protocol Open Standard – Currently experimental RFCs and IETF drafts only – RFCs 6830 - 6836 – Driven mainly by Cisco
Network based solution – Available already in Cisco IOS and NX-OS
Original driven by routing scalability issues – In case of multi-homing to Internet service providers (ISPs) the PI (provider independent) addressing and PA (provider assigned) addressing consumes BGP table space
Page: 3 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
LISP Base Ideas (continued) Separation of identity and location of an IP device / IP service – Remark: IP address covers both. Change of location means change of IP address and hence change of identity.
LISP mapping system – Consists of mapping server(s) and resolver(s)
LISP border routers – Separate EID (endsystem identifier) address domain from RLOC (routing locater) address domain
Dynamic unidirectional encapsulation – Performed by LISP border routers
Dynamic based caching – Triggered by data traffic between LISP sites
Page: 4 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
LISP Basic Elements LISP Mapping System (Mapping Server / Mapping Resolver)
LISP Border Routers
MS/MR-2
xTR
IP WAN (e.g. ISPs)
172.16.1.1
10.1.0.0/16
172.99.2.1
172.99.1.1
xTR
LISP Border Routers
172.16.2.1
RLOC Address Space (e.g. Internet Addresses)
172.17.1.1
172.17.2.1
xTR
xTR EID Address Space LISP Site-1
ITR … ETR … xTR … RLOC … EID …
Ingress Tunnel Router (performing LISP encapsulation) Egress Tunnel Router (performing LISP decapsulation) ITR plus ETR Routing Locator Endsystem Identifier
Page: 5 of 20 290kampi.pptx
10.2.0.0/16
MS/MR-1
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
EID Address Space LISP Site-2
LISP Map-Registration Site Registration MS/MR
LISP MS / MR t1
EID
RLOC
10.1.0.0/16
172.16.1.1
10.1.0.0/16
172.17.1.1
10.2.0.0/16
172.16.2.1 t3
172.99.1.1
ETR
t2 t4
10.1.0.0/16
172.16.1.1
IP WAN (ISPs) 172.17.1.1
172.16.2.1
RLOC Address Space
10.2.0.0/16
ETR
ETR EID Address Space LISP Site-2
EID Address Space LISP Site-1
LISP control message (well known UDP port 4342) Page: 6 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
LISP Map-Request Site Registration MS/MR Mapping-Cache / ITR
RLOC
TTL
10.2.0.0/16
172.16.2.1
20 h
t5
LISP MS / MR
t0
RLOC
10.1.0.0/16
172.16.1.1
10.1.0.0/16
172.17.1.1
10.2.0.0/16
172.16.2.1
t1
10.1.1.1 -> 10.2.2.2
10.1.0.0/16
172.16.1.1
Mapping Database ETR
t3
EID
t4
IP WAN (ISPs)
172.16.2.1
RLOC Address Space
EID Address Space LISP Site-1
tx … means time X LISP control message (well known UDP port 4342) IP datagram Page: 7 of 20
290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
172.16.2.1
ETR
Map Reply 10.2.0.0 -> 172.16.2.1
172.17.1.1
RLOC
10.2.0.0/16
172.99.1.1
ITR
t2
10.2.0.0/16
EID
EID
EID Address Space LISP Site-2
LISP Dynamic Encapsulation Mapping-Cache / ITR
RLOC
TTL
10.2.0.0/16
172.16.2.1
20 h
t7
t6 172.16.1.1->172.16.2.1
10.1.1.1 -> 10.2.2.2
10.1.1.1 -> 10.2.2.2 plus IP Payload
10.1.1.1 -> 10.2.2.2
LISP Dynamic Unidirectional Tunnel
ITR 10.1.0.0/16
t8
172.16.1.1
IP WAN (ISPs) 172.17.1.1
ETR 172.16.2.1
RLOC Address Space
EID Address Space LISP Site-2
EID Address Space LISP Site-1
LISP data message (well known UDP port 4341) IP datagram Page: 8 of 20 290kampi.pptx
10.2.0.0/16
EID
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
LISP Encapsulation (Data Message)
Source : CiscoLive2013 presentation: “´TECIPM-3191” Page: 9 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
LISP Scope Service provider independency – separation of addressing and routing – address family agnostic
Inherent multi-homing and mobility support – high availability – seamless communication – fast business continuity in case of disaster
Simplicity of configuration – fast deployment – needs less skills for operation and maintenance
Base protection in the transport system – inherent IP VPN functionality
Enhanced protection by usage of LISP&GETVPN – message integrity – encryption (optional) Page: 10 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
Future Communication Technologies Investigations in AP17 led to three proposals for new air/ground data link communications system: – L-band Digital Aeronautical Communication System (LDACS) as a future ground based communication system – a future satellite based communication system (SATCOM) – Aeronautical Mobile Airport Communication System (AeroMACS) as a future specific system for the surface communications in airports with high density traffic
LDACS – a ground-based system using line of sight communications a/g communication in particular for en-route and TMA communications
SATCOM – well suited to cover large oceanic and remote airspaces (ORP)
AeroMACS – is intended to support on-the-ground communication exchanges, particularly at airports (APT domain) Page: 11 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
Data Link Technologies
Page: 12 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
Multilink Concept Future link technologies, or a combination, are considered to provide adequate QoS for future communication services Most operational flight domains will provide more than one data link technology FCI has the objective to provide a robust and highly available data link connectivity The Multilink concept – builds upon the existence of at least two independent a/g data links and – addresses the selection of most appropriate data link for a given service
Security, multi-homing and vertical handover are current technological gaps that need to be addressed
Page: 13 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
Technical Challenges Ongoing research projects like SANDRA or SESAR 15.2.4 are introducing candidate technologies the fill some of the technology gaps Common for these projects is that so far no single technology has potential to solve mobility, security and multi-homing challenges LISP has the capability to provide – a transparent multi-homing solution that – allows load balancing among different data link technologies (based on QoS), – supports network mobility paired with a maintainable security solution and – does not require different technologies like mobile IP, NEMO and IPsec
Page: 14 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
FCI Use Cases FCI comprises of heterogeneous systems – short-range, long-range terrestrial and satellite access technologies
To increase FCI efficiency a means to handover between technologies is requisite – current radio access networks are separated allowing limited or almost no interaction
Multi-homing in a FCI requires interaction and exchange of link qualities – for instance the appropriate data link is determined by radio parameters received via an airborne radio
The following FCI use case assumes LDACS, AeroMACS and SATCOM as data link technologies that are interconnecting mobile (airborne) fixed (ground based) LISP sites
Page: 15 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
Mobility in FCI
1 EID
MS-MR
RLOC
PRIO
10.1.0.0/16
172.16.2.1
10.1.0.0/16
172.17.2.1
10.3.3.0/28
172.18.1.1
1
10.3.3.0/28
172.19.1.1
2
172.99.2.1
Airplane with LISP router
Site Registration MS-MR
10.3.3.0/28
xTR
EID LISP Site-1
RLOC Address Space
Application 1
LDACS
172.18.1.1 Application 2
ANSP Area
SATCOM
xTR1
172.16.2.1
10.1.0.0/16
EID Mobile Site-X
172.17.2.1 xTR2
172.19.1.1
Mapping Database ETR1/2 EID
Mapping Database EID Mobile Site-X EID
RLOC
PRIO
Interface
10.3.3.0/28
172.18.1.1
1
LDACS up
10.3.3.0/28
172.19.1.1
2
SATCOM up Page: 16 of 20
290kampi.pptx
RLOC
10.1.0.0/16
172.16.2.1
10.1.0.0/16
172.17.2.1
Mapping-Cache ITR1/2
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
EID
RLOC
10.3.3.0/28
172.18.1.1
TTL 1h
Mobility in FCI
2 EID
MS-MR
Airplane with LISP router
172.16.2.1
10.1.0.0/16
172.17.2.1
10.3.3.0/28
172.17.1.1
1
10.3.3.0/28
172.18.1.1
1
10.3.3.0/28
172.19.1.1
1
Site Registration MS-MR EID LISP Site-1
RLOC Address Space
LDACS
10.3.3.0/28
172.18.1.1
172.16.2.1
Application 2
ANSP Area 172.19.1.1 172.19.1.1
Mapping Database EID Mobile Site-X RLOC
PRIO
xTR1
172.17.2.1
SATCOM
Application 3
Interface
10.3.3.0/28
172.17.1.1
1
AeroMACS up
10.3.3.0/28
172.18.1.1
1
LDACS up
10.3.3.0/28
172.19.1.1
1
SATCOM up Page: 17 of 20
290kampi.pptx
10.1.0.0/16
Application 1
xTR
EID
PRIO
10.1.0.0/16
EID Mobile Site-X
AeroMACS
172.17.1.1
172.99.2.1
RLOC
xTR2
Load balancing of incoming traffic. Outgoing traffic engineering based on application type Mapping-Cache ITR1/2
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
EID
RLOC
TTL
10.3.3.0/28
172.18.1.1
1h
10.3.3.0/28
172.17.1.1
1h
Mobility in FCI
3 EID
MS-MR
172.17.1.1
AeroMACS
Application 1
10.3.3.0/28
172.16.2.1
10.1.0.0/16
172.17.2.1
10.3.3.0/28
172.18.1.1
1
10.3.3.0/28
172.17.1.1
2
EID LISP Site-1
RLOC Address Space
LDACS
172.18.1.1 Application 2
172.19.1.1 Application 3
10.1.0.0/16
Site Registration MS-MR
EID Mobile Site-X xTR
172.16.2.1
ANSP Area
xTR1
172.17.2.1
SATCOM
xTR2
172.19.1.1
Mapping Database EID Mobile Site-X EID
RLOC
PRIO
Solicited move without break to LDACS again Interface
10.3.3.0/28
172.17.1.1
2
AeroMACS up
10.3.3.0/28
172.18.1.1
1
LDACS up
10.3.3.0/28
172.19.1.1
1
SATCOM up
Mapping-Cache ITR1/2
e.g. detecting AeroMACS radio signal strength below threshold and change PRIO to 2 Page: 18 of 20 290kampi.pptx
PRIO
10.1.0.0/16
Airplane with LISP router
172.99.2.1
RLOC
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
EID
RLOC
10.3.3.0/28
172.18.1.1
TTL 1h
Summary LISP provides a clear demarcation point between user sites and the provider network for routing and security Multi-homing and mobility in ATM are an inherent functionality of LISP supporting multi-link technologies from day-one LISP technology and associated concepts can be easily deployed to support seamless a/g data link communication make-before-brake LISP fast failover in case of a lost link requires tuning of COTS mechanisms (initially implemented for non-critical communication) Separation into different (security) domains via LISP allows using a single communication infrastructure for different stakeholders Finally, instead of deploying different technologies in the FCI, LISP combines various mechanisms into a single technology easing configuration and maintenance cost reduction Page: 19 of 20 290kampi.pptx
Presentation Date: 2013-10-09 Author: KAMPICHLER Wolfgang
THANK YOU!
[email protected]
