Locator/Identifier Separation Protocol

LISP
Locator/ID Separation Protocol
Status	Published
Organization	Internet Engineering Task Force
Website	RFC 9300

Locator/ID Separation Protocol (LISP) is a "map-and-encapsulate" protocol which is developed by the Internet Engineering Task Force LISP Working Group.¹ The basic idea behind the separation is that the Internet architecture combines two functions, routing locators (where a client is attached to the network) and identifiers (who the client is) in one number space: the IP address. LISP supports the separation of the IPv4 and IPv6 address space following a network-based map-and-encapsulate scheme (RFC 1955). In LISP, both identifiers and locators can be IP addresses or arbitrary elements like a set of GPS coordinates or a MAC address.²

The protocol is currently an IETF Proposed Standard, specified in RFC 9300.

The Internet Architecture Board's October 2006 Routing and Addressing Workshop ³ renewed interest in the design of a scalable routing and addressing architecture for the Internet. Key issues driving this renewed interest include concerns about the scalability of the routing system and the impending exhaustion of IPv4 address space. Since the IAB workshop, several proposals have emerged that attempted to address the concerns expressed at the workshop. All of these proposals are based on a common concept: the separation of Locator and Identifier in the numbering of Internet devices, often termed the "Loc/ID split".⁴

The current namespace architecture used by the Internet Protocol uses IP addresses for two separate functions:

• as an end-point identifier to uniquely identify a network interface within its local network addressing context
• as a locator for routing purposes, to identify where a network interface is located within a larger routing context

There are several advantages to decoupling Location and Identifier, and to LISP specifically.⁵

• Improved routing scalability
• BGP-free multihoming in active-active configuration
• Address family traversal: IPv4 over IPv4, IPv4 over IPv6, IPv6 over IPv6, IPv6 over IPv4
• Inbound traffic engineering
• Mobility
• Simple deployability
• No host changes are needed
• Customer driven VPN provisioning replacing MPLS-VPN
• Network virtualization
• Customer operated encrypted VPN based on LISP/GETVPN replacing IPsec scalability problems
• High availability for seamless communication sessions through (constraint-based) multihoming

A recent discussion of several LISP use cases may be found in ⁶

IETF has an active workgroup establishing standards for LISP. As of 2016, the LISP specifications are on the experimental track. The LISP workgroup started to move the core specifications onto the standards track in 2017 - as of June 2021 three revisions (for RFC 6830, RFC 6833, and 8113) are ready for publication as RFCs, but they await completion of work on a revision of RFC 6834 and the LISP Security Framework.

• Routing Locator (RLOC): A RLOC is an IPv4 or IPv6 address of an egress tunnel router (ETR). A RLOC is the output of an EID-to-RLOC mapping lookup.
• Endpoint ID (EID): An EID is an IPv4 or IPv6 address used in the source and destination address fields of the first (most inner) LISP header of a packet.
• Egress Tunnel Router (ETR): An ETR is a device that is the tunnel endpoint; it accepts an IP packet where the destination address in the "outer" IP header is one of its own RLOCs. ETR functionality does not have to be limited to a router device; server host can be the endpoint of a LISP tunnel as well.
• Ingress Tunnel Router (ITR): An ITR is a device that is the tunnel start point; it receives IP packets from site end-systems on one side and sends LISP-encapsulated IP packets, across the Internet to an ETR, on the other side.
• Proxy ETR (PETR): A LISP PETR implements ETR functions on behalf of non-LISP sites. A PETR is typically used when a LISP site needs to send traffic to non-LISP sites but the LISP site is connected through a service provider that does not accept nonroutable EIDs as packet sources.
• Proxy ITR (PITR): A PITR is used for inter-networking between Non-LISP and LISP sites, a PITR acts like an ITR but does so on behalf of non-LISP sites which send packets to destinations at LISP sites.⁷
• xTR: A xTR refers to a device which functions both as an ITR and an ETR (which is typical), when the direction of data flow is not part of the context description.⁸
• Re-encapsulating Tunnel Router (RTR): An RTR is used for connecting LISP-to-LISP communications within environments where direct connectivity is not supported. Examples include: 1) joining LISP sites connected to "disjointed locator spaces"—for example a LISP site with IPv4-only RLOC connectivity and a LISP site with IPv6-only RLOC connectivity; and 2) creating a data plane 'anchor point' by a LISP-speaking device behind a NAT box to send and receive traffic through the NAT device.⁹

In the Locator/Identifier Separation Protocol the network elements (routers) are responsible for looking up the mapping between end-point-identifiers (EID) and route locators (RLOC) and this process is invisible to the Internet end-hosts.¹⁰¹¹ The mappings are stored in a distributed database called the mapping system, which responds to the lookup queries. The LISP beta network initially used a BGP-based mapping system called LISP ALternative Topology (LISP+ALT),¹² but this has now been replaced by a DNS-like indexing system called DDT inspired from LISP-TREE.¹³ The protocol design made it easy to plug in a new mapping system, when a different design proved to have benefits. Some proposals have already emerged and have been compared.

• Cisco has released public IOS, IOS XR, IOS XE and NX-OS images which support LISP.
• A team of researchers from the Université catholique de Louvain and T-Labs/TU Berlin have written a FreeBSD implementation called OpenLISP.¹⁴
• The LIP6 lab of UPMC, France, has implemented a fully featured control-plane (MS/MR, DDT, xTR) for OpenLISP ¹⁵¹⁶
• Historically, LISPmob was an open source implementation of LISP for Linux, OpenWRT and Android maintained at Polytechnic University of Catalonia. It could act as xTR or LISP Mobile Node.¹⁷ Recently, this implementation has been further developed into a full open source LISP router called the "Open Overlay Router" or OOR.
• AVM added LISP support in firmware for their FRITZ!Box devices starting from FRITZ!OS version 6.00.
• LANCOM Systems supports LISP in the router operating system
• HPE supports LISP in their Comware 7 platform based routers (under the marketing name FlexNetwork MSR and VSR). This platform is developed by H3C Technologies and sold in China under their own logo.
• OpenDaylight supports LISP flow mappings.
• ONOS develops a distributed LISP control plane as an SDN application.¹⁸¹⁹
• Lispers.net provides an open source, feature complete implementation of LISP.²⁰
• fd.io also supports LISP by the Overlay Network Engine (ONE).²¹
• A simple LISP Mapping System implementation is also available in Java.²²