1. Separating Location from Identification Dino Farinacci March 3, 2008

2. Loc/ID SeparationCRC AAM WorkshopSlide 2 Agenda 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

3. Loc/ID SeparationCRC AAM WorkshopSlide 3 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

4. Loc/ID SeparationCRC AAM WorkshopSlide 4 Separating (or adding) an Address Let’s define how and what is separating out location and identification from the existing IP address semantic LocatorID 2001:0102:0304:0506:1111:2222:3333:4444IPv6: 209.131.36.158IPv4: Locator.10.0.0.1 ID ID & Location If PI, get new locator If PA, get new ID

5. Loc/ID SeparationCRC AAM WorkshopSlide 5 Map-n-Encap vs Address-Rewrite Host Stack: supplies IDs LISP Router: supplies RLOCs by adding new header Map-n-EncapAddress-Rewrite Host Stack: supplies IDs Router: rewrites RLOCs from existing address GSE

6. Loc/ID SeparationCRC AAM WorkshopSlide 6

7. Loc/ID SeparationCRC AAM WorkshopSlide 7 ( ) LISP ( ) UDP ( ) IP ( ) LISP ( ) UDP ( ) IP ( ) LISP - the language LISP - the protocol (: - ))

8. Loc/ID SeparationCRC AAM WorkshopSlide 8 LISP - 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:

9. Loc/ID SeparationCRC AAM WorkshopSlide 9 Open 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!

10. Loc/ID SeparationCRC AAM WorkshopSlide 10 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

11. Loc/ID SeparationCRC AAM WorkshopSlide 11 Packet Forwarding Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 S ITR D ETR Provider Y 13.0.0.0/8 Provider X 12.0.0.0/8 S1 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) Mapping Entry 1.0.0.1 -> 2.0.0.2 11.0.0.1 -> 12.0.0.2 Legend: EIDs -> Green Locators -> Red 1.0.0.1 -> 2.0.0.2 11.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 controlled by destination site

12. Loc/ID SeparationCRC AAM WorkshopSlide 12 LISP 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

13. Loc/ID SeparationCRC AAM WorkshopSlide 13 Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 R1R2 BGP 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? Site with PI Addresses

14. Loc/ID SeparationCRC AAM WorkshopSlide 14 What Fixes do I get? 10^7 routes Before LISP 10^4 routes After LISP A 16-bit value!

15. Loc/ID SeparationCRC AAM WorkshopSlide 15 References draft-farinacci-lisp-06.txt draft-fuller-lisp-alt-02.txt draft-lewis-lisp-interworking-00.txt draft-meyer-lisp-cons-03.txt draft-lear-lisp-nerd-03.txt draft-curran-lisp-emacs-00.txt

16. Loc/ID SeparationCRC AAM WorkshopSlide 16 References lisp-interest@lists.civil-tongue.net