1 / 30

LISP update

LISP update. RIPE-59 Lisbon, October 2009 Vince Fuller (for the rest of the LISP crew: Noel Chiappa, Dino Farinacci, Darrel Lewis, Dave Meyer, Andrew Partan, and John Zwiebel). http://www.vaf.net/prezos/lisp-ripe59.ppt. Agenda. Problem Statement – good news & bad news

glain
Download Presentation

LISP update

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. LISP update RIPE-59 Lisbon, October 2009 Vince Fuller (for the rest of the LISP crew: Noel Chiappa, Dino Farinacci, Darrel Lewis, Dave Meyer, Andrew Partan, and John Zwiebel) http://www.vaf.net/prezos/lisp-ripe59.ppt

  2. Agenda • Problem Statement – good news & bad news • Brief review of LISP and LISP+ALT • LISP-MS map server/map resolver – an easier way to access the mapping database • LISP-MN mobility • What’s happening in the IETF? • Implementation & Deployment Status • Spec References • Q & A RIPE-59 Lisbon, October 2009

  3. Review: Problem Statement • What provoked this? • Stimulated by problem statement effort at the Amsterdam IAB Routing Workshop on October 2006 • RFC 4984 • More info on problem statement: • http://www.vaf.net/~vaf/apricot-plenary.pdf • First and foremost - scale the Internet • Growth trends in global routing system state RIPE-59 Lisbon, October 2009

  4. Internet Routing State RIPE-59 Lisbon, October 2009

  5. Good news & bad news + Recent analysis work by Geoff Huston suggests that stability (update & withdrawal rate) may be improving http://www.potaroo.net/presentations/2009-05-06-bgp2008.pdf - Trend is still “up & to the right” - Multi-homing is still hard + LISP makes it easier and adds functionality - Long-term trends are unclear RIPE-59 Lisbon, October 2009

  6. Review: What is LISP? • Locator/ID Separation Protocol • EIDs for hosts, topological RLOCs for “core” • Separate numbering allows routing to scale • Ground rules for LISP • Network-based solution • No changes to hosts whatsoever • No new addressing changes to site devices • Minimal configuration file changes • Imperative to be incrementally deployable • Address family agnostic RIPE-59 Lisbon, October 2009

  7. 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 Unicast 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 RIPE-59 Lisbon, October 2009

  8. Review: What is LISP+ALT? • Mechanism for an ITR to find the ETR for an EID • Advertise EID-prefixes in BGP on an alternate topology of GRE tunnels • An ALT Device is: • An xTR configured with GRE tunnels • A Map-Server (new) • A Map-Resolver (new) • A pure ALT-only router for aggregating other ALT peering connections • An ALT-only device can be off-the-shelf gear: • Router hardware, commodity Linux host, etc. • Just needs to run BGP and GRE RIPE-59 Lisbon, October 2009

  9. 11.0.0.1 -> 240.1.1.1 11.0.0.1 -> 240.1.1.1 <- 240.1.1.0/24 < - 240.1.0.0/16 <- 240.1.2.0/24 240.0.0.1 -> 240.1.1.1 ITR ITR ETR ETR ETR 11.0.0.1 -> 1.1.1.1 ? ? ? ? 1.1.1.1 -> 11.0.0.1 240.0.0.1 -> 240.1.1.1 ALT-rtr ALT-rtr ALT-rtr ALT-rtr ALT-rtr ALT-rtr Using ALT to find an ETR Original way: extend ALT to xTRs for policy control EID-prefix 240.1.1.0/24 EID-prefix 240.0.0.0/24 1.1.1.1 11.0.0.1 EID-prefix 240.1.2.0/24 2.2.2.2 12.0.0.1 Legend: EIDs -> Green Locators -> Red GRE Tunnel Physical link Map-Request Map-Reply 3.3.3.3 ALT EID-prefix 240.2.1.0/24 RIPE-59 Lisbon, October 2009

  10. New: LISP Map Server • ETRs register site EID-prefixes with Map-Servers • Securely with pair-wise trust model (no PKI needed) • Policy can be applied on Map-Servers before EID-prefix accepted into mapping service • ETR is still authoritative for its database mappings • Map-Servers advertise EID-prefixes in to the ALT on behalf of their client ETRs • ITRs send encapsulated Map-Requests to Map-Resolvers instead of connecting to ALT • Map-Server/Map-Resolver functionality may be in existing ALT router (most likely) or separate box • draft-ietf-lisp-ms-03.txt RIPE-59 Lisbon, October 2009

  11. 2.0.0.2 -> 1.1.1.1 11.0.0.1 -> 240.1.1.1 11.0.0.1 -> 240.1.1.1 11.0.0.1 -> 1.0.0.1 11.0.0.1 -> 240.1.1.1 ? 240.0.0.1 -> 240.1.1.1 ITR ITR ETR ETR ETR 11.0.0.1 -> 1.1.1.1 ? ? ? 1.1.1.1 -> 11.0.0.1 240.0.0.1 -> 240.1.1.1 ALT-rtr ALT-rtr ALT-rtr ALT-rtr ALT-rtr (MS) ALT-rtr (MR) Encapsulated Data Packet Using LISP-MS to attach xTRs Easy way: xTR uses Map-Server/Map-Resolver EID-prefix 240.1.1.0/24 EID-prefix 240.0.0.0/24 1.1.1.1 11.0.0.1 2.0.0.2 1.0.0.1 EID-prefix 240.1.2.0/24 2.2.2.2 12.0.0.1 Legend: EIDs -> Green Locators -> Red GRE Tunnel Physical link Map-Request Map-Reply 3.3.3.3 ALT EID-prefix 240.2.1.0/24

  12. S D LISP-MS Detailed Example EID Topology PI EID-prefix 1.0.0.0/8 ITR 11.0.0.1 Provider A 11.0.0.0/8 Provider X 12.0.0.0/8 Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link 12.0.0.1 ETR PI EID-prefix 2.0.0.0/8 RIPE-59 Lisbon, October 2009

  13. Map-Resolver, Map-Server and ALT Infrastructure LISP-ALT LISP-ALT LISP-ALT LISP-ALT Map-Server S D Map-Resolver PI EID-prefix 1.0.0.0/8 ITR 11.0.0.1 Provider A 11.0.0.0/8 65.1.1.1 Provider X 12.0.0.0/8 66.2.2.2 12.0.0.1 Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link ETR PI EID-prefix 2.0.0.0/8 RIPE-59 Lisbon, October 2009

  14. LISP Map-Register LISP-ALT LISP-ALT LISP-ALT LISP-ALT Map-Server S D 12.0.0.1 -> 66.2.2.2 Map-Resolver (3) (2) (4) 2.0.0.0/8 2.0.0.0/8 2.0.0.0/8 (1) [1] Map-Server Registration PI EID-prefix 1.0.0.0/8 ITR 11.0.0.1 65.1.1.1 Provider A 11.0.0.0/8 Provider X 12.0.0.0/8 66.2.2.2 12.0.0.1 Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link ETR PI EID-prefix 2.0.0.0/8 RIPE-59 Lisbon, October 2009

  15. LISP-ALT LISP-ALT LISP-ALT LISP-ALT Map-Request UDP 4342 Map-Request UDP 4342 LISP Packet UDP 4342 LISP Packet UDP 4342 Map-Server Map-Request UDP 4342 D S 11.0.0.1-> 2.0.0.1 11.0.0.1-> 2.0.0.1 11.0.0.1-> 2.0.0.1 66.2.2.2-> 12.0.0.1 11.0.0.1-> 65.1.1.1 Map-Resolver 1.0.0.1 -> 2.0.0.1 ? ? ? ? ? [2] Data request Triggers Map-Request PI EID-prefix 1.0.0.0/8 ITR 11.0.0.1 How do I get to 2.0.0.1? (1) (5) 65.1.1.1 Provider A 11.0.0.0/8 (4) (2) (3) Provider X 12.0.0.0/8 66.2.2.2 12.0.0.1 Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link ETR PI EID-prefix 2.0.0.0/8 RIPE-59 Lisbon, October 2009

  16. LISP-ALT LISP-ALT LISP-ALT LISP-ALT Map-Request UDP 4342 Map-Request UDP 4342 LISP Packet UDP 4342 LISP Packet UDP 4342 Map-Reply UDP 4342 Map-Server Map-Request UDP 4342 S D 11.0.0.1-> 2.0.0.1 1.0.0.1-> 2.0.0.1 11.0.0.1-> 2.0.0.1 12.0.0.1 -> 11.0.0.1 66.2.2.2-> 12.0.0.1 11.0.0.1-> 65.1.1.1 Map-Resolver 1.0.0.1 -> 2.0.0.1 ? ? ? ? ? [3] Map-Request Evokes Map-Reply PI EID-prefix 1.0.0.0/8 ITR 11.0.0.1 How do I get to 2.0.0.1? (5) (1) 65.1.1.1 Provider A 11.0.0.0/8 (4) (2) (3) Provider X 12.0.0.0/8 66.2.2.2 12.0.0.1 Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link ETR (6) PI EID-prefix 2.0.0.0/8 RIPE-59 Lisbon, October 2009

  17. LISP-ALT LISP-ALT LISP-ALT LISP-ALT Map-Request UDP 4342 Map-Request UDP 4342 LISP Packet UDP 4342 LISP Packet UDP 4342 Map-Reply UDP 4342 Map-Server Map-Request UDP 4342 D S 11.0.0.1-> 2.0.0.1 1.0.0.1-> 2.0.0.1 11.0.0.1-> 2.0.0.1 12.0.0.1 -> 11.0.0.1 66.2.2.2-> 12.0.0.1 11.0.0.1-> 65.1.1.1 Map-Resolver 1.0.0.1 -> 2.0.0.1 Map-Cache Entry EID-prefix: 2.0.0.0/8 Locator-set: 12.0.0.2, priority: 1, weight: 100 (D1) ? ? ? ? ? [4] Map-Cache Populated, data packets can flow PI EID-prefix 1.0.0.0/8 ITR 11.0.0.1 How do I get to 2.0.0.1? (1) (5) 65.1.1.1 Provider A 11.0.0.0/8 (4) (2) Policy Controlled by destination site (3) Provider X 12.0.0.0/8 66.2.2.2 12.0.0.1 Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link ETR (6) PI EID-prefix 2.0.0.0/8 RIPE-59 Lisbon, October 2009

  18. New: LISP Mobile Node Simple host ITR/ETR implementation for mobile node MN registers with “home” Map-Server for assigned EID Map-Server will “proxy” answer Map-Requssts MN uses Map-Resolver at its current location (roaming) MN encapsulates all traffic using LISP Use of Map-Server/Map-Resolver service interface Enables scalable roaming with same LISP infrastructure used for multi-homing and route scaling Map-Request flows to “home” Map-Server User data flows to RLOCs, so no “stretch” latency Map cache management slightly different for MN Shorter TTLs, use of Solicit Map Requests, etc. See: draft-meyer-lisp-mn-00.txt (future WG document) RIPE-59 Lisbon, October 2009 Slide 18

  19. Roaming - Control Plane LISP-ALT LISP-ALT LISP-ALT LISP-ALT Map-Server Map-Resolver Map-Resolver Map-Resolver EID: 153.16.1.1 3.3.3.3 -> 65.1.1.1 LISP Map-Register 153.16.1.1 -> (3.3.3.3, 4.4.4.4) MN1 MN2 EID: 153.16.2.1 EID: 153.16.3.1 153.16.1.0./24 65.1.1.1 MN3 Legend: EIDs -> Green, RLOCs -> Red 3G network -> 3.0.0.0/8 4G network -> 4.0.0.0/8 BGP-over-GRE Map-Register BGP update (1) No matter where MN3 roams, MN1 and MN2 can find it’s locator by using the database mapping system. (2) Only the Map-Server will store 153.16.1.1/32 state with the latest set of RLOCs. (3) Data always travels on shortest path to and from MN. RIPE-59 Lisbon, October 2009 Slide 19

  20. Roaming - Data Plane 1.0.0.1 -> 5.5.5.5 1.0.0.1 -> 4.4.4.4 S MN roams, stays multi-homed and TCP connection does not reset 4.4.4.4 Map-Cache entry: EID-prefix: 153.16.1.1/32 RLOC-set: 4.4.4.4, priority: 1, weight: 50 3.3.3.3, priority: 1, weight: 50 10.0.0.1 -> 153.16.1.1 10.0.0.1 -> 153.16.1.1 10.0.0.1 -> 153.16.1.1 5.5.5.5 Map-Cache entry: EID-prefix: 153.16.1.1/32 RLOC-set: 4.4.4.4, priority: 2, weight: 100 5.5.5.5, priority: 1, weight: 100 S1 S2 EID: 153.16.1.1 ITR Provider A 1.0.0.0/8 3G Provider 3.0.0.0/8 3.3.3.3 1.0.0.1 ITR LISP EID-prefix 10.0.0.0/8 EID: 153.16.1.1 2.0.0.1 4G Provider 4.0.0.0/8 Provider B 2.0.0.0/8 4.4.4.4 DNS entry: mn.abc.com A153.16.1.1 WiFi Provider 5.0.0.0/8 Legend: EIDs -> Green, Locators -> Red RIPE-59 Lisbon, October 2009 Slide 20

  21. Review: LISP/IETF timeline • Created over dinner at IAB RAWS (Oct ’06) • Lunch discussions at San Diego IETF (Nov ’06) • RRG in Prague (March ’07) • RRG and “lunch BOF” in Vancouver (Dec ’07) • Tutorial and start of “LISP test center” • RRG in Philadelphia (March ’08) • IETF (grow, rtgarea, idr) in Dublin (July ’08) • EXPLISP BOF “process experiment” • IETF (grow) in Minneapolis (Nov ’08) • IETF BOF in San Francisco (March ’09) RIPE-59 Lisbon, October 2009

  22. LISP in the IETF now • Much deliberation on RRG list, etc. • LISP BOF in San Francisco (March ’09) • First WG meeting in Stockholm (July ’09) • Darrel Lewis & Sam Hartman co-chairs • Core LISP documents are now WG I-D’s • Adoption of LISP-MN is still pending • Discussion on WG list: lisp@ietf.org RIPE-59 Lisbon, October 2009

  23. Prototype Implementation • Cisco NXOS, on NX7000 and Titanium • Underlying Linux code base • Includes LISP, ALT, Interworking, and Map-Server/Map-Resolver functionality • “lig” diagnostic tool • Software switching only • Supports LISP for both IPv4 and IPv6 • ITR, ETR, and PTR • LISP-NAT for IPv4 only RIPE-59 Lisbon, October 2009

  24. Other Coding Efforts • IOS implementation under-way • Loc/ID split functionality • Considering IOS-XR implementation • TE-ITR/TE-ETR functionality • OpenLISP implementation for FreeBSD; available and for a while and being updated • For testing the specs • Considering native Linux implementation (and recently learned of preliminary work on one) • Any other efforts? RIPE-59 Lisbon, October 2009

  25. LISP Deployment • LISP Pilot Network Operational • Incrementally deployed during the last 2 years • 30+ sites across 7 countries • US, UK, BE, JP, UY, AU, DE • Uses the NX-OS Titanium Platform • IOS and OpenLISP platforms to be added • EID-Prefixes used • 153.16.0.0/16 and 2610:00d0::/32 • GRE tunnels out of 240.0.0.0/4, 32-bit ASNs • RLOCs used • Current site attachment points to the Internet RIPE-59 Lisbon, October 2009

  26. RIPE-59 Lisbon, October 2009

  27. LISP Deployment • LISP Interworking Deployed • Have LISP 1-to-1 address translation working • http://www.translate.lisp4.net • Proxy Tunnel Router (PTR) • IPv4 PTRs: • Andrew, ISC, and UY • IPv6 PTRs: • Dave (UofO), ISC, and UY • http://www.lisp6.net reachable through IPv6 PTR • http://www.ptr.lisp4.net reachable through IPv4 PTR RIPE-59 Lisbon, October 2009

  28. Open Policy for LISP • It’s been almost 3 years since the IAB Routing & Addressing Workshop • 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 designers, implementors, testers, and researchers • As always, please let us know if you are interested RIPE-59 Lisbon, October 2009

  29. Internet Drafts draft-ietf-lisp-05.txt draft-ietf-lisp-multicast-02.txt draft-ietf-lisp-alt-01.txt draft-ietf-lisp-ms-03.txt draft-ietf-lisp-interworking-00.txt draft-meyer-lisp-eid-block-01.txt draft-meyer-loc-id-implications-01.txt draft-meyer-lisp-mobility-00.txt draft-farinacci-lisp-lig-00.txt draft-mathy-lisp-dht-00.txt draft-iannone-openlisp-implementation-02.txt draft-brim-lisp-analysis-00.txt draft-meyer-lisp-cons-04.txt draft-lear-lisp-nerd-04.txt draft-curran-lisp-emacs-00.txt RIPE-59 Lisbon, October 2009

  30. References • Public mailing list: lisp@ietf.org • Core LISP team: lispers@cisco.com • More info at: http://www.lisp4.net http://www.lisp6.net RIPE-59 Lisbon, October 2009

More Related