Separating Location from Identification Dino Farinacci March 3, 2008.

Separating Location from Separating Location from IdentificationIdentification

Dino FarinacciMarch 3, 2008

Loc/ID SeparationLoc/ID Separation CRC AAM WorkshopCRC AAM Workshop Slide Slide 22

AgendaAgenda• Why separate Location from ID?

– Another way to scale routing• We have a proposal called LISP

– Provides Features for the architecture– Provides Fixes for the current architecture– Increments to the architecture (doesn’t change it)– With one incremental solution

• Problem Statement discussed while describing the Solution Statement

• References


Why Separate Location from ID?Why Separate Location from ID?• Level of Indirection allows us to:

– Keep either ID or Location fixed while changing the other

– Create separate namespaces which can have different allocation properties

• By keeping IDs fixed– Assign fixed addresses that never change to

hosts and routers at a site• You can change Locators

– Now the sites can change providers– Now the hosts can move


Separating (or adding) an AddressSeparating (or adding) an Address Let’s define how and what is separating out location

and identification from the existing IP address semantic

Locator ID

2001:0102:0304:0506:1111:2222:3333:4444IPv6:

209.131.36.158IPv4:

Locator

.10.0.0.1

ID

ID & Location

ID & Location

If PI, get new locatorIf PA, get new ID


Map-n-Encap vs Address-Map-n-Encap vs Address-RewriteRewrite

Host Stack:supplies IDs

LISP

Router:supplies RLOCsby adding newheader

Map-n-Encap Address-Rewrite

Host Stack:supplies IDs

Router:rewrites RLOCsfrom existingaddress

GSE


( )LISP( )UDP( )IP( )LISP( )UDP( )IP ( )

LISP - the language

LISP - the protocol

(: - ))


LISP - the protocolLISP - the protocol• First the authors:

– Scott Brim, Dino Farinacci, Vince Fuller, Eliot Lear, Darrel Lewis, Dave Meyer, Dave Oran

– Noel Chiappa, John Curran, Jason Schiller• Many others:


Open Policy for LISPOpen Policy for LISP• It’s been 1 1/2 years since the IAB RAWS

– Some of us committed to working in the IETF and IRTF in an open environment

• This is not a Cisco only effort– We have approached and recruited others– There are no patents (cisco has no IPR on this)– All documents are Internet Drafts

• We need and seek new designers, implementors, and testers

• We need research analysis• We want this to be an open effort!


What is LISP?What is LISP?• Locator/ID Separation Protocol• Ground rules:

– Network-based solution– No changes to hosts whatsoever– No new addressing changes to site devices– Very few configuration file changes– Imperative to be incrementally deployable– Address family agnostic


Packet ForwardingPacket Forwarding

Provider A10.0.0.0/8

Provider B11.0.0.0/8

S

ITR

DITR

ETR

ETR

Provider Y13.0.0.0/8

Provider X12.0.0.0/8S1

S2

D1

D2

PI EID-prefix 1.0.0.0/8 PI EID-prefix 2.0.0.0/8

DNS entry:D.abc.com A 2.0.0.2 EID-prefix: 2.0.0.0/8

Locator-set: 12.0.0.2, priority: 1, weight: 50 (D1) 13.0.0.2, priority: 1, weight: 50 (D2)

MappingEntry

1.0.0.1 -> 2.0.0.2

1.0.0.1 -> 2.0.0.211.0.0.1 -> 12.0.0.2

Legend: EIDs -> Green Locators -> Red

1.0.0.1 -> 2.0.0.211.0.0.1 -> 12.0.0.2

1.0.0.1 -> 2.0.0.2

12.0.0.2

13.0.0.2

10.0.0.1

11.0.0.1

Policy controlledby destination site


LISP ResearchLISP Research• We are building a scalable mapping database

infrastructure– Scale - tinkering with (state * rate)– Ubiquity - tinkering with packet delay/loss tradeoffs– Secure - tinkering with simple security mechanisms

• Push? Pull? Hybrid?– LISP-ALT, LISP-CONS, LISP-NERD, LISP-EMACs– Maybe LISP-DHT

• Interworking – How LISP sites talk to non-LISP sites– Mandatory and high development priority


Provider A10.0.0.0/8

Provider B11.0.0.0/8

R1 R2BGP

End Site Benefit(1) Easier Transition to IPv6(2) Change provider without address change

Lower OpEx for Sites and Providers(1) Improve site multi-homing(2) Improve provider traffic engineering(3) Reduce size of core routing tables

What Features do I get?What Features do I get?

Site withPI Addresses


What Fixes do I get?What Fixes do I get?

10^7 routes

Before LISP

10^4 routesAfter LISP

A 16-bit value!


ReferencesReferencesdraft-farinacci-lisp-06.txtdraft-fuller-lisp-alt-02.txtdraft-lewis-lisp-interworking-00.txt

draft-meyer-lisp-cons-03.txtdraft-lear-lisp-nerd-03.txtdraft-curran-lisp-emacs-00.txt


[email protected]

Separating Location from Identification Dino Farinacci March 3, 2008.

Documents

Transcript of Separating Location from Identification Dino Farinacci March 3, 2008.