Presentation is loading. Please wait.

Presentation is loading. Please wait.

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.

Published by Modified over 8 years ago

Similar presentations

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

1 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 John Zwiebel) LISP update

2 LISP UpdateNANOG-46 Philadelphia, May 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 What’s happening in the IETF? Implementation & Deployment Status Spec References Q & A

3 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 3 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 UpdateNANOG-46 Philadelphia, May 2009Slide 4 Internet Routing State

5 LISP UpdateNANOG-46 Philadelphia, May 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 UpdateNANOG-46 Philadelphia, May 2009Slide 6 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 UpdateNANOG-46 Philadelphia, May 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 UpdateNANOG-46 Philadelphia, May 2009Slide 8 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 –A Map-Resolver –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 UpdateNANOG-46 Philadelphia, May 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 Hard way: extend ALT to xTRs for policy control

10 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 10 LISP-MS: ALT an easier way 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

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 UpdateNANOG-46 Philadelphia, May 2009Slide 12 Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link Map-Request path ETR Map-Resolver LISP-ALT 2.2.2.2 ITR 65.1.1.1 1.1.1.1 -> 240.1.1.1 Map-Request UDP 4342 1.1.1.1 -> 240.1.1.1 Map-Request UDP 4342 1.1.1.1 -> 65.1.1.1 LISP Packet UDP 4341 66.2.2.2 Map-Server 1.1.1.1 -> 240.1.1.1 Map-Request UDP 4342 66.2.2.2 -> 2.2.2.2 LISP Packet UDP 4341 1.1.1.1 240.1.0.0/16 (1) (2) (3) (4) (6) (5) 2.2.2.2 -> 1.1.1.1 Map-Reply UDP 4342 Transit Example in detail

13 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 13 How Map-Server Registration Works ETR Map-Resolver LISP-ALT 2.2.2.2 ITR 65.1.1.1 66.2.2.2 Map-Server 1.1.1.1 240.1.1.0/24 Transit Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link Map-Register BGP update (1) 2.2.2.2 -> 66.2.2.2 LISP Map-Register (in AH) (2) 240.1.1.0/24 240.1.0.0/16 (3)

14 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 14 Interoperates with LISP-ALT Sites ETR LISP-ALT 2.2.2.2 ITR 65.1.1.1 66.2.2.2 1.1.1.1 ETR ITR ETR LISP-ALT Legend: BGP-over-GRE GRE only Physical link Map-Server Site Map-Server user site Map-Server user site LISP-ALT site LISP-ALT site Low OpEx GRE-only site Low OpEx GRE-only site Map-Resolver Map-Server Map-Resolver Map-Server

15 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 15 Mapping Database Infrastructure xTRs MS/MRs ALT Legend: LISP Sites -> green 1st layer access infrastructure -> blue 2nd layer core infrastructure -> red

16 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 16 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)

17 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 17 LISP in the IETF now Much deliberation on RRG list, etc. LISP BOF in San Francisco (March ’09) New WG at Stockholm (July ’09) –Darrel Lewis & Sam Hartman co-chairs –Core LISP documents are now WG I-D’s

18 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 18 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

19 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 19 Other Coding Efforts IOS implementation under-way –Loc/ID split functionality Considering IOS-XR implementation –TE-ITR/TE-ETR functionality OpenLISP implementation been available for FreeBSD a while and being updated –For testing the specs Considering native Linux implementation (and recently learned of preliminary work on one) Any other efforts?

20 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 20 LISP Deployment LISP Pilot Network Operational –Deployed for nearly 2 years –~32 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

21 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 21

22 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 22 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

23 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 23 Open Policy for LISP It’s been >2 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

24 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 24 Internet Drafts draft-ietf-lisp-01.txt draft-ietf-lisp-multicast-01.txt draft-ietf-lisp-alt-01.txt draft-ietf-lisp-ms-01.txt draft-ietf-lisp-interworking-00.txt draft-meyer-lisp-eid-block-01.txt draft-meyer-loc-id-implications-01.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

25 LISP UpdateNANOG-46 Philadelphia, May 2009Slide 25 References Public mailing list: lisp@ietf.org Core LISP team: lisp-dddvaz@external.cisco.com More info at: http://www.lisp4.net http://www.lisp6.net

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

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.
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.
1 IPv6 and IPv4 Interoperation and Transition Tony Hain co-chair IETF ngtrans WG

1 IPv6 and IPv4 Interoperation and Transition Tony Hain co-chair IETF ngtrans WG
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.
Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.

Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.
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.
1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.

1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.
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.
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.
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.

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.
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.
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
An ID/locator split architecture for future networks Ved P. Kafle, Hideki Otsuki, and Masugi Inoue, National Institute of Information and Communications.

An ID/locator split architecture for future networks Ved P. Kafle, Hideki Otsuki, and Masugi Inoue, National Institute of Information and Communications.

Similar presentations

Ads by Google