lisp tech talk - part 3 deployed network and use-cases dino farinacci, dave meyer, darrel lewis,...

LISP Tech Talk - Part 3LISP Tech Talk - Part 3Deployed Network and Use-CasesDeployed Network and Use-Cases

Dino Farinacci, Dave Meyer, Darrel Lewis, Vince Fuller, Gregg SchudelFebruary 24, 2010

LISP - Part 3LISP - Part 3 LISP Google Tech TalkLISP Google Tech Talk Slide Slide 22

3-Part Series Tech Talk3-Part Series Tech Talk

• LISP Part 1– Problem Statement, Architecture, and Protocol

Design

• LISP Part 2– Mapping Database Infrastructure and

Interworking

• LISP Part 3– Deployed Network and Use-Cases


AgendaAgenda• Summary of LISP Tech Talks Part 1 & Part 2• Describe LISP Test Network• Describe Network Debugging Tools• Pro-Bono Use-Case• Enterprise Use-Cases (2)• Service Provider Use-Case• Data Center Use-Cases (3)• LISP Mobile-Node Use-Case• References


Summary of Part 1Summary of Part 1


Summary of Part 2Summary of Part 2


Goals for LISP NetworkGoals for LISP Network• Experiments

– Course Adjust Protocol Architecture

• Test Multiple Implementations• Prove ALT Topology maps to EID Address

Allocation Delegations• Emulate MSP Business Models• Protocol Learning Tool for Users• Test bed for building Management Tools


When People Learn of LISP . . . When People Learn of LISP . . .

• What do customers say?– “I would like to make my enterprise core network

simpler, I can do that by removing routes”– “I can allow client machines to roam and I can

track them since EIDs never change”– “I can use either global or private addressing and

not have to change them, I own my addresses, I have control”

– “I would like to multi-home and use private addresses but it is so hard to do with NATs, I can do that now with LISP”


When People Learn of LISP . . .When People Learn of LISP . . .

• What do customers say?– “I think I can use LISP on my PE routers and

use BGP next-hops as my locators, my core can stay lean without MPLS”

– “If I can modify LISP priority/weights I can use LISP for load-balancing traffic to servers”

– “I can get IPv6 at my remote offices without upgrading my core network”

– “I care about leaving a robust and scalable Internet when I retire, I want to be Internet Green”


Pro-Bono Use-CasePro-Bono Use-Case

• Pull your prefix from the core– The Internet Core– The Enterprise Core– People want to be Internet Green

• Use less resources in core• Use less power in core• The core is cheaper to operate

• Greener to deploy PI-based IPv6– Since IPv6 EID-prefixes stay out of core


Enterprise Use-Case 1:Enterprise Use-Case 1:Low-Opex Multi-HomingLow-Opex Multi-Homing

Provider A10.0.0.0/8

Provider B11.0.0.0/8

S1 S2

10.0

.0.1

11.0

.0.1

1.0.0.0/8

• Active/active multi-homing– Low-Opex switchover (no BGP)

• More efficient bandwidth use by site– Use all the bandwidth you pay for

• New link revenue for ISP– At the benefit of keeping site’s routes

out of their resources• Decoupling addressing from ISP

– Site has flexibility to change providers

– Raises the bar for ISPs, better for consumer sites


Enterprise Use-Case 2:Enterprise Use-Case 2:Dynamic and Roaming Dynamic and Roaming

VPNsVPNsSan Francisco

Los Angeles

Boston

New York

1.1.0.0/16Engineering


Dallas

65.0.0.0/8

65.1.1.165.1.2.2

10.1.0.0/16Marketing

10.2.0.0/16Marketing

65.2.1

.1

65.2.2

.2

Marketing is using private addresses

65.3.1

.1

Enterprise Core65.

3.2.2

65.4.1.1

65.4.2.2

1.2.0.0/16 -> (65.4.1.1, 65.4.2.2)

65.5.1.1 65.5.2.2

(65.5.1.1, 65.5.2.2)

Engineering is using global PI addresses

Core is using global PA addresses


An engineering site moves

Dynamic creation of a site is done by simply registering EID-to-RLOC mappingto the Mapping Database System


Service Provider Use-Case:Service Provider Use-Case:Multiple Address Family Multiple Address Family

SupportSupport• The Internet core is not dual-stack, deal with it

IPv6-only Site

Dual Stack

IPv6-only Site

Dual Stack

2610:d0:1::/48 65.1.1.165.1.2.2

65.2.1

.1

65.2.2

.2

65.3.1

.1IPv4 Internet Core

65.3.2

.2

65.4.1.1

65.4.2.2

LISP Site LISP Site

2610:d0:2::/48

LISP Site

240.1.0.0/162610:d0:1::/48

Non-LISP Site

65.4.0.0/162001:1:2::/48

2001:1:2::1:1

2001:1:2::2:2

Dual-Stack ISP

PxTRPxTRPxTRPxTR

IPv6 path IPv4 path

dino-unix.lisp6.net ipv6.google.comTCP-over-IPv6 Connection


Service Provider Use-Case:Service Provider Use-Case:Multiple Address Family Multiple Address Family

SupportSupport• A possible cable company

– IPv6 core, can’t upgrade residential on IPv4

IPv4-only Residential Site

IPv4-only Server Site

192.168.1.0/24

65.1.1.1

65.4.2.2

IPv6 CableCore Network

LISP Site

LISP Site

1.1.0.0/16

IPv4-only Server Site

Non-LISP Site

65.4.0.0/16

65.4.1.165.1.2.2

65.3.1.1

65.3.2.2

IPv6 path IPv4 path

Dual-Stack Region

PxTRPxTRPxTRPxTR


Data-Center Use-Case 1:Data-Center Use-Case 1:Virtual Machine MobilityVirtual Machine Mobility

S1 S3S2 S4

RLOC A RLOC A’

A’A’AA1.1.1.254/24 1.1.11.254/24

1.1.1.1/24 1.1.11.2/24

2.2.2.254/24 2.2.22.254/24

2.2.2.3/24 2.2.22.4/24

1.1.0.0/16 -> A

2.2.0.0/16 -> A’

L3 Router LISP Router

S1 moves

Register to Map-Server

Reg

iste

r to

Map

-Ser

ver

1.1.1.1/32 -> A’

Registe

r to

Map

-Ser

ver

for m

oved

VM

Data Center


Data-Center Use-Case 2:Data-Center Use-Case 2:Need 256-Wide ECMP?Need 256-Wide ECMP?


Data-Center Use-Case 3:Data-Center Use-Case 3:Load Balance the SLBsLoad Balance the SLBs

Array of Servers

Internet

Data Center

Array of SLBs

L3 Router LISP Router Any brand Server Load Balancer Servers

ETRETR ETRETR ETRETR ETRETR

ITRITRITRITR ITRITR

ITRITR

VIPs are EIDs

VIPs

EIDs -> RLOC-sets


LISP Mobile Node Use-LISP Mobile Node Use-CaseCase

• What if 2 mobile hand-sets could roam and keep a TCP connection established?

• What if 2 mobile hand-sets LISP encapsulated to each other with path stretch of 1?

• What if you could put up server functionality on your mobile hand-set?

• What if your hand-set could use all radios at the same time?


QuickTime™ and a decompressor

are needed to see this picture.

EID-prefix: 2001:xxxx:yyyy::1/128 64.0.0.1


This is a LISP site!

65.0.0.1

Map-Server: 64.1.1.1

wifi

3G

Can set ingress packet policy!

Green x.x.x.x -> EID Red x.x.x.x -> Locator (RLOC)



• Run lightweight variant of LISP on the MN– draft-meyer-lisp-mn-01.txt

• EID can be burned into SIM card– Can be either an IPv4 or probably IPv6 address– Will be yours forever, your ‘network name’

• Your DHCP address is the MN’s RLOC• MN carries Map-Server RLOC while roaming• When you get a new DHCP address:

– Register new RLOC(s) to Map-Server(s)– Update ITR/PITR cachers


LISP-MN: Can it Scale?LISP-MN: Can it Scale?• Leave RLOCs alone, they map to underlying

physical topology– There is absolutely no more specific state in the core for

LISP MNs (or any other LISP site for that matter)

• More-specific state only in Map-Server – Map-Server is control-plane home agent– Map-Server already has covering route so no more

specifics in the ALT

• Only other place for more specific state is in cachers (ITRs and PITRs)– How bad could this be?


Back of the Envelope Back of the Envelope CalculationCalculation

• What if a map-cache entry was 1000 bytes?• 1M entries in an ITR would cost you 1GB

– A Google ITR would be a carrier class ITR, but 1GB isn’t much

• Let’s keep scaling up– Deploy 100 Google ITRs, you’re at 100M MNs– Ah, throw more memory at it, 10GB, you’re at 1B MNs

• 100 ITRs is not unreasonable since good user experience forces shortest exit, so an ITR can hold 10M phones

• Oh, by the way, 1000 bytes per entry is fairly fat!– Can optimize that easily

• This is achievable since granular state is only where you need it and no where else!

Green: tracking EIDs or map-cache entries, Red: RLOC cost, Violet: memory cost


Encouragement by the Following Encouragement by the Following Peer ReviewersPeer Reviewers

• Vint Cerf– Father of the Internet and Google Chief Scientist

• Dave Clark– Luminary Internet Researcher from MIT

• Noel Chiappa– Locator/ID Separation Visionary and creator of NIMROD

• Paul Mockapetris– Inventor of DNS

• Len Bosack– Founder of cisco


LISP Reference MaterialLISP Reference Material• LISP Specs

– draft-ietf-lisp-06.txt– draft-ietf-lisp-multicast-02.txt– draft-ietf-lisp-ms-03.txt– draft-ietf-lisp-alt-02.txt– draft-ietf-lisp-interwork-02.txt– draft-meyer-lisp-mn-01.txt– draft-farinacci-lisp-lig-02.txt

• URLs– http://www.lisp4.net– http://lisp4.cisco.com

lisp tech talk - part 3 deployed network and use-cases dino farinacci, dave meyer, darrel lewis,...

Documents

lisp slide

interworking lisp

lisp priorityweights

lisp google tech talkslide

lisp test network

series tech talk lisp

protocol design lisp

core slide