Presentation is loading. Please wait.

Presentation is loading. Please wait.

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.

Published by Modified over 9 years ago

Similar presentations

Presentation on theme: "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."— Presentation transcript:

1 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) LISP update http://www.vaf.net/prezos/lisp-ripe59.ppt

2 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

3 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

4 LISP UpdateRIPE-59 Lisbon, October 2009Slide 4 Internet Routing State

5 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

6 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

7 LISP UpdateRIPE-59 Lisbon, October 2009Slide 7 Unicast 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

8 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

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

10 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

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

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

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

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

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

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

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

18 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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)

19 LISP UpdateRIPE-59 Lisbon, October 2009Slide 19 Roaming - Control Plane Map-Resolver LISP-ALT Map-Server Map-Resolver EID: 153.16.2.1 EID: 153.16.3.1 3.3.3.3 -> 65.1.1.1 LISP Map-Register 153.16.1.1 -> (3.3.3.3, 4.4.4.4) 153.16.1.0./24 EID: 153.16.1.1 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 65.1.1.1 (1) No matter where MN3 roams, MN1 and MN2 can find it’s locator by using the database mapping system. MN1 MN2 (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. MN3

20 LISP UpdateRIPE-59 Lisbon, October 2009Slide 20 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 DNS entry: mn.abc.com A 153.16.1.1 Roaming - Data Plane Provider A 1.0.0.0/8 Provider B 2.0.0.0/8 S ITR 4G Provider 4.0.0.0/8 S1 S2 LISP EID-prefix 10.0.0.0/8 Legend: EIDs -> Green, Locators -> Red 1.0.0.1 2.0.0.1 EID: 153.16.1.1 3.3.3.3 4.4.4.4 WiFi Provider 5.0.0.0/8 EID: 153.16.1.1 4.4.4.4 5.5.5.5 MN roams, stays multi-homed and TCP connection does not reset 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 10.0.0.1 -> 153.16.1.1 1.0.0.1 -> 4.4.4.410.0.0.1 -> 153.16.1.1 3G Provider 3.0.0.0/8 10.0.0.1 -> 153.16.1.1 1.0.0.1 -> 5.5.5.5

21 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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)

22 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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.orglisp@ietf.org

23 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

24 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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?

25 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

26 LISP UpdateRIPE-59 Lisbon, October 2009Slide 26

27 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

28 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

29 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

30 LISP UpdateRIPE-59 Lisbon, October 2009Slide 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

Download ppt "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."

Similar presentations

LISP Mobile Node LISP Mobile Node draft-meyer-lisp-mn-00.txt Dino Farinacci, Vince Fuller, Darrel Lewis and David Meyer IETF StockholmHiroshima LISP Working.

LISP Mobile Node LISP Mobile Node draft-meyer-lisp-mn-00.txt Dino Farinacci, Vince Fuller, Darrel Lewis and David Meyer IETF StockholmHiroshima LISP Working.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 1 © 2010 Cisco and/or its affiliates. All rights reserved. LISP Mobility.

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 1 © 2010 Cisco and/or its affiliates. All rights reserved. LISP Mobility.
Logically Centralized Control Class 2. Types of Networks ISP Networks – Entity only owns the switches – Throughput: 100GB-10TB – Heterogeneous devices:

Logically Centralized Control Class 2. Types of Networks ISP Networks – Entity only owns the switches – Throughput: 100GB-10TB – Heterogeneous devices:
Why do current IP semantics cause scaling issues? −Today, “addressing follows topology,” which limits route aggregation compactness −Overloaded IP address.

Why do current IP semantics cause scaling issues? −Today, “addressing follows topology,” which limits route aggregation compactness −Overloaded IP address.
IPv4 - IPv6 Integration and Coexistence Strategies Warakorn Sae-Tang Network Specialist Professional Service Department A Subsidiary.

IPv4 - IPv6 Integration and Coexistence Strategies Warakorn Sae-Tang Network Specialist Professional Service Department A Subsidiary.
Project by: Palak Baid (pb2358) Gaurav Pandey (gip2103) Guided by: Jong Yul Kim.

Project by: Palak Baid (pb2358) Gaurav Pandey (gip2103) Guided by: Jong Yul Kim.
Multihoming in IPV6 Habib Naderi Department of Computer Science University of Auckland.

Multihoming in IPV6 Habib Naderi Department of Computer Science University of Auckland.
IETF 72 – July 2008 Vince Fuller, Darrel Lewis, Eliot Lear, Scott Brim, Dave Oran, Noel Chiappa, John Curran, Dino Farinacci, and David Meyer LISP Deployment.

IETF 72 – July 2008 Vince Fuller, Darrel Lewis, Eliot Lear, Scott Brim, Dave Oran, Noel Chiappa, John Curran, Dino Farinacci, and David Meyer LISP Deployment.
Introduction to LISP (not (the (programming ( language))))

Introduction to LISP (not (the (programming ( language))))
LISP-CONS A Mapping Database Service NANOG 41 David Meyer, Dino Farinacci, Vince Fuller, Darrel Lewis, Scott Brim, Noel Chiappa NANOG 41 October, 2007.

LISP-CONS A Mapping Database Service NANOG 41 David Meyer, Dino Farinacci, Vince Fuller, Darrel Lewis, Scott Brim, Noel Chiappa NANOG 41 October, 2007.
Internet Draft Status Internet Draft Status draft-farinacci-lisp-{00-12}.txt Dave Meyer, Vince Fuller, Darrel Lewis, Dino Farinacci IETF San Francisco.

Internet Draft Status Internet Draft Status draft-farinacci-lisp-{00-12}.txt Dave Meyer, Vince Fuller, Darrel Lewis, Dino Farinacci IETF San Francisco.
IPv4 and IPv6 Mobility Support Using MPLS and MP-BGP draft-berzin-malis-mpls-mobility-00 Oleg Berzin, Andy Malis {oleg.berzin,

IPv4 and IPv6 Mobility Support Using MPLS and MP-BGP draft-berzin-malis-mpls-mobility-00 Oleg Berzin, Andy Malis {oleg.berzin,
LISP MIB draft-lisp-mib-05 Vancouver IETF - LISP WG Gregg Schudel, Amit Jain, Victor Moreno July 2012.

LISP MIB draft-lisp-mib-05 Vancouver IETF - LISP WG Gregg Schudel, Amit Jain, Victor Moreno July 2012.
COM555: Mobile Technologies Location-Identifier Separation.

COM555: Mobile Technologies Location-Identifier Separation.
NANOG-46 Philadelphia, June 2009 Vince Fuller & Dave Meyer (for the rest of the LISP crew: Noel Chiappa, Dino Farinacci, Darrel Lewis, Andrew Partan, and.

NANOG-46 Philadelphia, June 2009 Vince Fuller & Dave Meyer (for the rest of the LISP crew: Noel Chiappa, Dino Farinacci, Darrel Lewis, Andrew Partan, and.
LISP, SDN, and OpenDaylight

LISP, SDN, and OpenDaylight
21.11.2013 Petteri Sirén. Content Preface Locator/ID Separation Protocol (LISP) How LISP works Methods how LISP was studied Test cases Result Summary.

Petteri Sirén. Content Preface Locator/ID Separation Protocol (LISP) How LISP works Methods how LISP was studied Test cases Result Summary.
Mobile IP Performance Issues in Practice. Introduction What is Mobile IP? –Mobile IP is a technology that allows a mobile node (MN) to change its point.

Mobile IP Performance Issues in Practice. Introduction What is Mobile IP? –Mobile IP is a technology that allows a "mobile node" (MN) to change its point.
LISP Tech Talk - Part 3 Deployed Network and Use-Cases Dino Farinacci, Dave Meyer, Darrel Lewis, Vince Fuller, Gregg Schudel February 24, 2010.

LISP Tech Talk - Part 3 Deployed Network and Use-Cases Dino Farinacci, Dave Meyer, Darrel Lewis, Vince Fuller, Gregg Schudel February 24, 2010.
LISP Mapping Request Format And related topics Joel M. Halpern

LISP Mapping Request Format And related topics Joel M. Halpern

Similar presentations

Ads by Google