Lisp support
draft-ietf-lisp-01.txt
draft-ietf-lisp-alt-01.txt ( draft-ietf-lisp-interworking-00.txt
draft-ietf-lisp-ms-01.txt
draft-farinacci-lisp-lig-00.txt
Support LISP for both IPv4 and IPv6
ITR, ETR and PTR (proxy tunnel router) ( LISP-NAT for IPv4 only
ALT-router, MAP-Resolver and Map-Server
Code Effort
IOS implementation - Loc/ID split functionality
IOX implementation - TE-ITR / TR-ETR functionality
LISP Deployment
LISP-ALT Infrastructure
GRE tunnels numbered out of 240.0.0.0/4
LISP-ALT uses 32-bit AS numbers, format is 32656.X (AS not notation)
EID-prefixes BGP advertised from "lisp" VRF
RLOCs in default VRF
Mapping Database Design
ALT - hybrid push/pull
push EID-prefixes using BGP on alternate topology of GRE tunnels
pull mappings
Service Interface for the Mapping Database
ETRs register site RID-prefixes with MAP-Servers
ETRs (at the site) are authoritative for their own database mappings
When ALT is used, Map-Servers advertise EID-prefixes
What is LISP-ALT ?
Advertise EID-prefixes in BGP on an alternate topolofy of GRE
An ALT Device is:
xTRs configured with GRE tunnels
Map-Servers
Map-Resolvers
Pure ALT-only router for aggregating other ALT peering connections
An ALT-only device can be off-the-shelf gear:
Rouer hardwre
Linux host
Just needs to run BGP and GRE
Mapping Entry
EID-prefix / Locator-set
Two Basic Techniques
LISP Network Address Translation (LISP-NAT)
Proxy Tunnel Routers (PTRs)
LISP Data-Plane
Encapsulation and router placement
Locator reachability
Data-triggered mapping service (Map-request, Map-Reply, Map-Register)
LISP Control-Plane
Definition for "mapping cache" and "mapping database"
mapping database - stored in all ETRs of each LISP site
mapping cache - entries obtained and stored in ITRs for the sites sending packets to
Modular scalable mapping service
ALT
Map-Servers and Map-Resolvers
User tools for querying the mapping database
PI address - Private IP address (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16)
PA address - Public address