1 / 16

Separating Location from Identification

Separating Location from Identification. Dino Farinacci March 3, 2008. 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

laurien
Download Presentation

Separating Location from Identification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  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 CRC AAM Workshop

  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 CRC AAM Workshop

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

  5. Host Stack: supplies IDs Host Stack: supplies IDs Router: rewrites RLOCs from existing address Router: supplies RLOCs by adding new header Map-n-Encap vs Address-Rewrite Map-n-Encap Address-Rewrite GSE LISP CRC AAM Workshop

  6. CRC AAM Workshop

  7. ( ) LISP ( ) UDP ( ) IP ( ) LISP ( ) UDP ( ) IP LISP - the language LISP - the protocol ( ) (: - )) CRC AAM Workshop

  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: CRC AAM Workshop

  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! CRC AAM Workshop

  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 CRC AAM Workshop

  11. S D 11.0.0.1 -> 12.0.0.2 11.0.0.1 -> 12.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 1.0.0.1 -> 2.0.0.2 1.0.0.1 -> 2.0.0.2 1.0.0.1 -> 2.0.0.2 S1 S2 D1 D2 Policy controlled by destination site Packet Forwarding PI EID-prefix 1.0.0.0/8 PI EID-prefix 2.0.0.0/8 ETR ITR Provider A 10.0.0.0/8 Provider X 12.0.0.0/8 12.0.0.2 10.0.0.1 ITR ETR 11.0.0.1 13.0.0.2 Provider B 11.0.0.0/8 Provider Y 13.0.0.0/8 DNS entry: D.abc.com A2.0.0.2 Legend: EIDs -> Green Locators -> Red CRC AAM Workshop

  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 CRC AAM Workshop

  13. Lower OpEx for Sites and Providers Improve site multi-homing Improve provider traffic engineering Reduce size of core routing tables End Site Benefit Easier Transition to IPv6 Change provider without address change BGP R1 R2 What Features do I get? Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 Site with PI Addresses CRC AAM Workshop

  14. Before LISP After LISP 10^4 routes 10^7 routes What Fixes do I get? A 16-bit value! CRC AAM Workshop

  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 CRC AAM Workshop

  16. References lisp-interest@lists.civil-tongue.net CRC AAM Workshop

More Related