LISP: An Architectural Solution to Multi-homing, Traffic ...LISP Designers: Dave Meyer, Vince...
Transcript of LISP: An Architectural Solution to Multi-homing, Traffic ...LISP Designers: Dave Meyer, Vince...
Dave Meyer & Dino Farinacci
LISP Designers:Dave Meyer, Vince Fuller, Darrel Lewis, Andrew Partan,John Zwiebel, Scott Brim, Noel Chiappa & Dino Farinacci
LISP:LISP: An Architectural Solution toAn Architectural Solution toMultiMulti--homing, homing, Traffic Engineering, andTraffic Engineering, and
Internet Route ScalingInternet Route Scaling
QuickTime™ and a decompressor
are needed to see this picture.
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 22
AgendaAgenda• Problem Statement• Architectural Concepts
– Separating Identity and Location– Map-n-Encap to Implement Level of Indirection
• Unicast & Multicast Data Plane Operation• Mapping Database Mechanism
– LISP-ALT• Locator Reachability• Interworking LISP Sites and Legacy Sites• Deployment Status
– Present Prototype Implementation– Present World-Wide LISP Pilot Network
• Q&A
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 33
Problem StatementProblem 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
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 44
Scaling Internet RoutingScaling Internet Routing StateState
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 55
Routing Table Size ProblemRouting Table Size Problem
10^7 routes
Before LISP - all this state in red circle
After LISP -this amount in red circle
A 16-bit number!
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 66
Growth in MultiGrowth in Multi--HomingHoming
Provider A10.0.0.0/8
Provider B11.0.0.0/8
S
(1) Improve site multi-homing
R1 R2
a) Can control egress with IGP routingb) Hard to control ingress without more specific
route injectionc) Desire to be low OpEx multi-homed (avoid
complex protocols, no outsourcing)
(2) Improve ISP multi-hominga) Same problem for providers, can control
egress but not ingress, more specific routingonly tool to circumvent BGP path selection
BGP
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 77
Growth in MultiGrowth in Multi--HomingHoming
Provider A10.0.0.0/8
Provider B11.0.0.0/8
S
R1 R2
(3) Decouple site addressing from providera) Avoid renumbering when site changes providersb) Site host and router addressing decoupled
from core topology
(4) Add new addressing domainsa) From possibly separate allocation entities
(5) Do 1) through 4) and reduce the sizeof the core routing tables
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 88
Separating (or adding) an AddressSeparating (or adding) an AddressChanging the semantics of the IP address
Locator ID
Locator
.10.0.0.1
ID
2001:0102:0304:0506:1111:2222:3333:4444IPv6:
ID & Location
209.131.36.158IPv4:
ID & Location
If PI, get new locatorIf PA, get new ID
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 99
Why the Separation?Why the Separation?• 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
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1010
Some Brief DefinitionsSome Brief Definitions• IDs or EIDs
– End-site addresses for hosts and routers at the site– They go in DNS records– Generally not globally routed on underlying infrastructure – New namespace
• RLOCs or Locators– Infrastructure addresses for LISP routers and ISP routers– Hosts do not know about them– They are globally routed and aggregated along the Internet
connectivity topology– Existing namespace
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1111
Provider A10.0.0.0/8
Provider B11.0.0.0/8
S
Multi-Level Addressing
EIDs are inside of sites
RLOCs used in the core
R2R1
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1212
What is LISP?What is LISP?
• Locator/ID Separation Protocol• Ground rules for LISP
– 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
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1313
WhatWhat is LISP?is LISP?
“Jack-Up” or “Map-n-Encap”
Host Stack:supplies IDs
Router:supplies RLOCsby adding newheader
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1414
draftdraft--farinaccifarinacci--lisplisp--11.txt11.txt0 1 2 30 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ |Version| IHL |Type of Service| Total Length |/ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+/ | Identification |Flags| Fragment Offset |/ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
OH | Time to Live | Protocol = 17 | Header Checksum |\ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\ | Source Routing Locator |\ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\ | Destination Routing Locator |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ | Source Port | Dest Port (4341) | UDP +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ | UDP length | UDP Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ | � Locator Reach Bits |LISP +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ | Nonce |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ |Version| IHL |Type of Service| Total Length |/ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+/ | Identification |Flags| Fragment Offset |/ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IH | Time to Live | Protocol | Header Checksum |\ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\ | Source EID |\ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\ | Destination EID |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1515
LISP for IPv6LISP for IPv6 TransitionTransition
LISP Header
IPv4 Header
IPv4 Header
IPv4 Payload
LISP Header
IPv6 Header
IPv6 Header
IPv6 Payload
Legend:EIDs -> GreenLocators -> Red
LISP Header
IPv4 Header
IPv6 Header
IPv6 Payload
LISP Header
IPv6 Header
IPv4 Header
IPv4 Payload
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1616
What is LISP?What is LISP?• Data plane
– Design for encapsulation and tunnel router placement
– Design for locator reachability– Data-triggered mapping service
• Control plane– Design for a scalable mapping service– Examples are: CONS, NERD, ALT, EMACS
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1717
LISP Network ElementsLISP Network Elements
• Ingress Tunnel Router (ITR)– Finds EID to RLOC mapping– Encapsulates to Locators at source site
• Egress Tunnel Router (ETR)– Owns EID to RLOC mapping– Decapsulates at destination site
• xTR– Term used when not referring to directionality– Basically a LISP router
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1818
Unicast Unicast Packet ForwardingPacket Forwarding
Provider A10.0.0.0/8
Provider B11.0.0.0/8
S
ITR
DITR
ETR
ETR
Provider Y13.0.0.0/8
Provider X12.0.0.0/8S1
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)
MappingEntry
1.0.0.1 -> 2.0.0.2
1.0.0.1 -> 2.0.0.2
11.0.0.1 -> 12.0.0.2
Legend:EIDs -> GreenLocators -> 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 controlledby destination site
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 1919
Multicast Packet ForwardingMulticast Packet Forwarding
• Keep EID state out of core network• No head-end replication at source site• Packets only go to receiver sites• No changes to hosts, site routers, core routers• Use existing protocols• Support PIM SSM, don’t preclude ASM & Bidir• Have separate unicast and multicast policies
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2020
Multicast Packet ForwardingMulticast Packet Forwarding• Group addresses have neither ID or Location semantics
– G is topologically opaque - can be used everywhere• (S-EID, G)
– S-EID is source host– G is group address receivers join to– State resides in source and receiver sites
• (S-RLOC, G)– S-RLOC is ITR on multicast tree– G is group address receivers join to– State resides in core
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2121
Multicast Packet ForwardingMulticast Packet Forwarding
Provider A10.0.0.0/8
Provider B11.0.0.0/8
S
ITR
DITR
ETR
ETR
Provider Y13.0.0.0/8
Provider X12.0.0.0/8S1
S2
D1
D2
12.0.0.2
13.0.0.2
10.0.0.1
11.0.0.1
R11
R1R2
R12 ETR R21 ETRR22ETR ETR
R3
11.0
.0.11
13.0.0.1213.0.0.21
13.0.0.22(S-EID,G)
PIM JP
(S-EID,G)PIM JP
(S-EID,G)PIM JP
(S2-RLOC,G)PIM JP
(S-EID,G)PIM JP
1.0.0.1
(S2-RLOC,G)PIM JP
Legend:EIDs -> GreenLocators -> Red
site or corePIM routerregular PIM JPunicast PIM JP
(S-EID,G)PIM JP
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2222
Multicast Packet ForwardingMulticast Packet Forwarding
Provider A10.0.0.0/8
Provider B11.0.0.0/8
S
ITR
DITR
ETR
ETR
Provider Y13.0.0.0/8
Provider X12.0.0.0/8S1
S2
D1
D2
12.0.0.2
13.0.0.2
10.0.0.1
11.0.0.1
R11
R1R2
R12 ETR R21 ETRR22ETR
R3
11.0
.0.11
13.0.0.1213.0.0.21
13.0.0.221.0.0.1
1.0.0.1 -> G
1.0.0.1 -> G
11.0.0.1 -> G
1.0.0.1 -> G 1.0.0.1 -> G
ETR
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2323
When the When the xTR xTR has no Mappinghas no Mapping• Need a scalable EID to Locator mapping
lookup mechanism• Network based solutions
– Have query/reply latency– Can have packet loss characteristics– Or, have a full table like BGP does
• How does one design a scalable Mapping Service?
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2424
• You need a “map” before you can “encap”• We have designed several mapping database
protocols– CONS, NERD, EMACS, ALT– Tradeoff push versus pull benefit/cost– Needs to be scalable to 1010 entries
• ALT has the most promise– We are deploying ALT
Mapping Database DesignsMapping Database Designs
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2525
What is LISP+ALT?• EID namespace is used at the site• RLOC namespace is used in the Internet core• Mappings need to be authoritative and reside
at site ETRs• Advertise EID-prefixes in BGP on an
alternate topology of GRE tunnels• ITRs get mappings by routing Map-Requests
on ALT topology• ETRs respond with Map-Replies
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2626
How LISP+ALT Works
Legend:EIDs -> GreenLocators -> RedGRE TunnelLow OpexPhysical link Data PacketMap-RequestMap-Reply
ETR
ETR
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
240.0.0.1 -> 240.1.1.1EID-prefix 240.0.0.0/24
1.1.1.1 -> 11.0.0.1240.0.0.1 -> 240.1.1.1
11.0.0.1 -> 1.1.1.1
ALT-rtr
ALT-rtr
ALT-rtr
ALT-rtr
ALT-rtr
ALT-rtr
12.0.0.1
11.0.0.1
?
240.0.0.1 -> 240.1.1.1
11.0.0.1 -> 240.1.1.1
? 240.0.0.1 -> 240.1.1.1
11.0.0.1 -> 240.1.1.1
?<- 240.1.1.0/24
<- 240.1.2.0/24
< - 240.1.0.0/16?
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2727
Locator Locator ReachabilityReachability
Provider A10.0.0.0/8
Provider B11.0.0.0/8
S
ITR
D
ITR
ETR
ETR
Provider Y13.0.0.0/8
Provider X12.0.0.0/8S1
S2
D1
D2
PI EID-prefix 2.0.0.0/8
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)
MappingEntryLegend:
EIDs -> GreenLocators -> Red
12.0.0.2
13.0.0.2
10.0.0.1
11.0.0.1
-> ordinal 0-> ordinal 1
loc-reach-bits:0x0000 0003
S
SD
D
0003
0003D1 D2
D1 D2
7654 3210b’xxxx xxxx’
0002
D2 D2
D2 D2
X X X
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2828
LISP LISP InterworkingInterworking
• LISP will not be widely deployed day-1• Need a way for LISP-capable sites to
communicate with rest of Internet• Two basic Techniques
– LISP Network Address Translators (LISP-NAT)– Proxy Tunnel Routers (PTRs)
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 2929
LISP LISP InterworkingInterworking• These combinations must be supported
– Non-LISP site to non-LISP site• Today’s Internet
– LISP site to LISP site• Encapsulation over IPv4 makes this work• IPv4-over-IPv4 or IPv6-over-IPv4
– LISP-R site to non-LISP site• When LISP site has PI or PA routable addresses
– LISP-NR site to non-LISP site• When LISP site has PI or PA non-routable addresses
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3030
Interworking Interworking using LISPusing LISP--NATNAT
Legend:LISP Sites -> Green (and EIDs)non-LISP Sites -> Red (and RLOCs)
xTR
R-prefix 65.1.0.0/16
R-prefix 65.2.0.0/16
R-prefix 65.3.0.0/16
65.0.0.0/12
Encapsulate
65.3.3.3 -> 66.3.3.31.3.3.3 -> 65.3.3.3
65.3.3.3 -> 1.3.3.3
Forward66.0.0.0/12
Forward
Local/Uncoordinated Solution
1.1.1.1 -> 1.2.2.2
66.1.1.1 -> 66.2.2.2
NR-prefix 1.2.0.0/16
NR-prefix 1.1.0.0/16
NR-prefix 1.3.0.0/16
66.1.1.1
66.2.2.2
66.3.3.3
66.3.3.3 -> 65.3.3.3
Translate
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3131
R-prefix 65.1.0.0/16
R-prefix 65.2.0.0/16
R-prefix 65.3.0.0/16
65.0.0.0/1266.0.0.0/12
Infrastructure SolutionLegend:
LISP Sites -> Green (and EIDs)non-LISP Sites -> Red (and RLOCs)
xTR
NR-prefix 1.2.0.0/16
NR-prefix 1.1.0.0/16
NR-prefix 1.3.0.0/16
66.1.1.1
66.2.2.2
Interworking Interworking using using PTRsPTRs
66.3.3.3
65.9.2.1
PTRPTRBGP Advertise:
1.0.0.0/8
PTRPTRBGP Advertise:
1.0.0.0/8PTRPTR
BGP Advertise:1.0.0.0/8
65.9.3.1
65.9.1.1
65.1.1.1 -> 1.1.1.1
(1)
1.1.1.1 -> 65.1.1.1
Forward Natively
(3)
Encapsulate
65.1.1.1 -> 1.1.1.1
65.9.1.1 -> 66.1.1.1
(2)
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3232
Prototype Implementation Prototype Implementation • cisco has a LISP prototype implementation• Supports:
draft-farinacci-lisp-11.txtdraft-fuller-lisp-alt-03.txtdraft-lewis-lisp-interworking-02.txt
• Software switching only• Supports LISP for both IPv4 and IPv6
– ITR, ETR, and PTR– LISP-NAT for IPv4 only
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3333
Platform and OSPlatform and OS• NX-OS runs on Linux• Used as a research platform• Can run on Nexus 7K/5K & Service Blades
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3434
Implementation ScheduleImplementation Schedule• Started implementation at Prague IETF
– March 2007• Implementation put on pilot network
– July 2007• Since then released over 90 release builds
– Releases occur on demand with new features and bug fixes concurrently
• We have phased testing– Unit/System Test done in development– Alpha test done on pilot network by Dave/Darrel/Vince/John/Andrew– Beta test done on pilot network by volunteers
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3535
Other Coding EffortsOther 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• Any other efforts?
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3636
LISP DeploymentLISP Deployment
• LISP Pilot Network Operational– Deployed for nearly 2 years– ~24 sites across 5 countries
• US, UK, BE, JP, UY– 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– RLOCs used
• Current site attachment points to the Internet
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3737
LISP DeploymentLISP Deployment
• LISP-ALT Infrastructure Built– GRE tunnels numbered out of 240.0.0.0/4– LISP-ALT uses 32-bit AS numbers
• Format is 32656.x (ASDot notation) – EID-prefixes BGP advertised from ‘lisp’ VRF– RLOCs in default VRF
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3838
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 3939
Naming &Naming & AddressingAddressing
• Domain name lisp4.net– Contains hosts and routers from IPv4
EID space• Domain name lisp6.net
– Contains hosts and routers from IPv6 EID space
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 4040
NamingNaming & Addressing& Addressing
• IPv4 EID Assignments from 153.16.0.0/16– North America 153.16.0.0/20
• /22 for regions in the US– Europe 153.16.32.0/20– Asia 153.16.64.0/20
• /21 for regions in Asia– Africa 153.16.96.0/20– Latin America 153.16.128.0/20– Reserved 153.16.{160,192,224}.0/20
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 4141
Naming & AddressingNaming & Addressing
• IPv6 EID Assignments from 2610:00d0::/32– 2610:00d0:x000::/36
•x is continent– 2610:00d0:xy00::/40
•y is region in continent x– 2610:00d0:xy00::/48
• Sites allocate out of /48
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 4242
LISP DeploymentLISP 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
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 4343
Other Uses for LISPOther Uses for LISP• SLBs in Data Centers
– ETRs directly connected to servers– ITRs at Data Center edge
• A/V Mobile Truck Roll– Avoid renumber at each event
• BGP-free Core– Intra-AS avoiding storing external routes– RLOCs are PE routers
• Building topological hierarchy with flat addressing– MAC addressing in L2 networks
• MAC address mobility for “extended subnets”• In an environment of shortage address supply
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 4444
OpenOpen Policy for LISPPolicy for LISP• It’s been >2 years since the IAB Routing &
Addressing WS– 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!
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 4545
Internet DraftsInternet Draftsdraft-farinacci-lisp-11.txtdraft-farinacci-lisp-multicast-01.txtdraft-fuller-lisp-alt-03.txtdraft-lewis-lisp-interworking-02.txtdraft-meyer-lisp-eid-block-01.txtdraft-meyer-loc-id-implications-01.txt
draft-mathy-lisp-dht-00.txtdraft-iannone-openlisp-implementation-02.txtdraft-brim-lisp-analysis-00.txt
draft-meyer-lisp-cons-04.txtdraft-lear-lisp-nerd-04.txtdraft-curran-lisp-emacs-00.txt
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 4646
ReferencesReferences
• Public mailing list:[email protected]
• More info at:http://www.lisp4.net
http://www.lisp6.net
LISP ArchitectureLISP Architecture Nanog Nanog 45 45 -- Jan 2009Jan 2009 Slide Slide 4747