Integration of LISP and LISP-MN in INET - Semantic Scholar

Institute of Computer Science Chair of Communication Networks Prof. Dr.-Ing. P. Tran-Gia

Integration of LISP and LISP-MN in INET

Dominik Klein, Matthias Hartmann (University of Wuerzburg, Germany)

Michael Höfling, Michael Menth (University of Tuebingen, Germany)

Motivation  Current naming and addressing architecture is facing scalability problems 450k

Active BGP entries (FIB)

400k

IPv4 FIB entries from 01.01.1989 – 19.03.2012

350k 300k 250k 200k 150k 100k 50k 0 89

95

00

05

10

12

Date

 Overload of IP address semantics with identification & routing information  Possible solution  Locator identifier split  Example: Locator/ID Separation Protocol (LISP) by CISCO Integration of LISP and LISP-MN in INET Dominik Klein

2

Outline  Introduction  Locator/identifier split

 LISP background  Basic LISP architecture  Overview of LISP extensions  LISP simulation model  Implemented nodes and messages  Evaluation  Detailed analysis of handover delay  Summary and future work Integration of LISP and LISP-MN in INET Dominik Klein

3

Introduction – Locator/Identifier Split Mapping system

Data packets Mapping update Provider X

B?

B

RLOC Y X Provider Z A Provider Y Data

B

RLOC X Y

 Idea  Address space divided into identifiers and routing locators  Mapping system provides ID-to-Loc information  Network layer entities, e.g. gateways, add source and destination Locs to outgoing packets after mapping lookup

Integration of LISP and LISP-MN in INET Dominik Klein

4

Locator/ID Separation Protocol (LISP)  Separates local naming and addressing from global routing  EIDs: locally routable and identifier on global scope  RLOCs: globally routable IP addresses of LISP gateways  LISP gateways add RLOCs to IP packets after mapping lookup  Mapping service provides EID-to-RLOC information

Internet

LISP domain

MS LISP gateway RLOC B

LISP gateway RLOC A

SN EID 1

Src:

Dest:

OH: IH: EID 1

LISP domain

Src:

Dest:

SN EID 2

Src:

Dest:

EID 1

EID 2

RLOC A RLOC B EID 2 DATA

EID 1

EID 2 DATA

Integration of LISP and LISP-MN in INET Dominik Klein

DATA 5

LISP Interworking: Outgoing Flow  Idea: send LISP packets without outer header  Problem: upstream provider drops packets due to uRPF

 Solution: tunnel packets to proxy ETR (PETR)

LISP domain

Dest:

OH: IH: EID 1

Internet

Non-LISP domain

LISP gateway RLOC A

SN EID 1

Src:

PETR RLOC E

Src:

Non-LISP node 11.3.2.5

Dest:

Src:

Dest:

EID 1

11.3.2.5

RLOC A RLOC E 11.3.2.5 DATA

EID 1

11.3.2.5 DATA

Integration of LISP and LISP-MN in INET Dominik Klein

DATA 6

LISP Interworking: Incoming Flow  Observation: non-LISP nodes use EIDs as destination address  Problem: EIDs are not globally routable

 Solution: proxy ITRs announces highly aggregated EID-prefix

Src:

MS

?

LISP gateway RLOC A

SN EID 1

Dest:

OH: IH: 11.3.2.5 EID 1 DATA

Non-LISP domain

Internet

LISP domain

Non-LISP node 11.3.2.5

PITR RLOC I

Src:

Dest:

RLOC I

RLOC A

11.3.2.5

EID 1

Src:

Dest:

11.3.2.5

EID 1

DATA Integration of LISP and LISP-MN in INET Dominik Klein

DATA 7

LISP Mobile Node (MN)  MN acts as whole LISP domain  Implements LISP gateway functionality  EID used for identification and not for forwarding anymore  Care-of-address used for forwarding within local domain  MN registers care-of-address as RLOC at mapping service

Internet

Non-LISP domain

LISP domain

MS LISP gateway RLOC B

MN EID 1 17.87.7.2

Src:

Dest:

SN EID 2

Src:

Dest:

EID 2

EID 1

OH: RLOC B 17.87.7.2 IH: EID 2

EID 1 DATA Integration of LISP and LISP-MN in INET Dominik Klein

DATA 8

LISP NAT Traversal

MN EID 1 10.0.0.1

MS

Internet

Non-LISP domain NAT 17.87.7.2

NTR RLOC N

Traffic for MN

 NAT traversal router (NTR) acts as anchor and relay  NTR collocated with PETR  MN registers at an NTR  NTR adds own RLOC to mapping service  Tunnel between MN and NTR used to bypass NAT Integration of LISP and LISP-MN in INET Dominik Klein

9

Motivation & Background  Motivation  Test and evaluate improvements to mobile node  Proof-of-concept for NAT traversal  Check interoperability of LISP-MN and NAT traversal  Study handover performance of LISP-MN  Implementation background  Extends INET framework with LISP protocol functionality  Based on design ideas of OpenLISP  Implementation according to LISP working group drafts  Several modifications – Integration of DHCP – Extension of wireless model  multihoming support – Integration of basic NAT functionality Integration of LISP and LISP-MN in INET Dominik Klein

10

 Modified IP module  Anchor point for LISP modules  LISP routing module Other applications  Adds and removes LISP header on data plane  Triggers signaling messages TCP UDP  Map resolver module IP  UDP application  Control plane signaling  LISP mapping cache  Stores used mappings Ethernet PPP  Inter-module communication  Done via Notification Board

Integration of LISP and LISP-MN in INET Dominik Klein

MapResolver

MappingCache

NotificationBoard

Overview

LISPRouting Unchanged module Changed module New module

11

Implemented Messages  Message types and message formats implemented according to LISP working group drafts  LISP header added and removed by lisp routing module  Signaling messages sent by map resolver module over UDP  Registration messages  Mapping messages (lookup, probing, …) cMessage

LISPMessage

LISPHeader Signaling

Map-Register

Map-Notify

Map-Request

Map-Reply

Integration of LISP and LISP-MN in INET Dominik Klein

Data

12

Implemented LISP Nodes

Integration of LISP and LISP-MN in INET Dominik Klein

13

LISP (Proxy) Router Module

Stores recently used mappings

Performs LISP signaling (e.g. register, lookup, …)

Used for inter-module communication

Adds/Removes LISP header Triggers LISP signaling

IP module as anchor point for LISP routing module

Integration of LISP and LISP-MN in INET Dominik Klein

14

Implemented LISP Nodes

Integration of LISP and LISP-MN in INET Dominik Klein

15

LISP Mobile Node Module

One DHCP client per interface

Same module as in LISP router Mobile node behavior activated via flag Keeps track of mobile EID

Integration of LISP and LISP-MN in INET Dominik Klein

16

Implemented LISP Nodes

Integration of LISP and LISP-MN in INET Dominik Klein

17

LISP Map Server

Handles registration requests Handles mapping lookups

Database for mapping entries

Integration of LISP and LISP-MN in INET Dominik Klein

18

Implemented LISP Nodes

Integration of LISP and LISP-MN in INET Dominik Klein

19

NAT Traversal Router Database for external IP:port of registered mobile nodes

Database for mapping entries of registered mobile nodes

Extended mapServer module with NTR specific functionality NTR specific forwarding, e.g. (NAT tunneling, packet relay,…) LISP routing module as NTR also acts as PETR

Integration of LISP and LISP-MN in INET Dominik Klein

20

Handover Scenario UDPVideoStreamCli

1

2

3

6

5

4

UDPVideoStreamSvr

UDPVideoStreamSvr

Larger delay: 50ms

Integration of LISP and LISP-MN in INET Dominik Klein

21

Detailed Delay Analysis

Delay in seconds

2

1.5

Beacon lost detection delay Scanning and association delay LISP signaling delay Total handover delay

event 1 event 2 event 3 event 4 event 5 event 6

1

Registration MN updates NTR

Relay next packet 50 ms Cache update

0.5 Passive scanning with one channel and 300 ms maxChannelTime

50 ms Registration

0

Beacon considered lost after 350ms.

LIS P

300 ms

300 ms Cache update

100 ms

100 ms Relaying via NTR

100 ms

nL I NA nL I LIS T-> T S S P ->n P-> P-> ->n ->N LI S L IS NA LI S LI S AT P P T P P NA

Integration of LISP and LISP-MN in INET Dominik Klein

22

Summary  Implementation of LISP model in INET  Based on OpenLISP design idea and working group drafts  Basic LISP architecture with interworking and mapping interface  LISP mobility architecture with own NAT traversal  Handover delay study as working example  Future work  Extension of existing framework with mapping system  Update/upgrade implementation according to the newest drafts  Update implementation to the newest INET version  Own website with documentation, tutorial, paper, …

Integration of LISP and LISP-MN in INET Dominik Klein

23

Thank You for Your Attention no Got question?

Thank audience and leave podium

yes no

Know answer?

Questions?

Pretend that time has run out

yes Answer question

Integration of LISP and LISP-MN in INET Dominik Klein

24