Locator/Identifier Separation Protocol

Last updated
The LISP Logo Lisp-logo.jpg
The LISP Logo

Locator/ID Separation Protocol (LISP) ( RFC   6830) is a "map-and-encapsulate" protocol which is developed by the Internet Engineering Task Force LISP Working Group. [1] 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. [2]

Contents

Historical origin

The Internet Architecture Board's October 2006 Routing and Addressing Workshop [3] 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". [4]

Current Internet Protocol Architecture

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

LISP

There are several advantages to decoupling Location and Identifier, and to LISP specifically. [5]

A recent discussion of several LISP use cases may be found in [6]

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.

Terminology

The LISP mapping system

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. [10] [11] 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), [12] but this has now been replaced by a DNS-like indexing system called DDT inspired from LISP-TREE. [13] 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.

Implementations

LISP beta network

A testbed has been developed to gain real-life experience with LISP. Participants include Google, Facebook, NTT, Level3, InTouch N.V. and the Internet Systems Consortium. [23] As of January 2014, around 600 companies, universities, and individual contributors from 34 countries are involved. The geographical distribution of participating routers, and the prefixes they are responsible for, could be observed on the LISPmon project website (updated daily). The multi-company, LISP-community initiative LISP4.net/LISP6.net published relevant information about this beta network on http://www.lisp4.net/ and http://www.lisp6.net/. Since March 2020 the LISP Beta Network is not maintained anymore and the mentioned websites have since been cybersquatted.

LISP-Lab consortium research network

The LISP-Lab project, [24] coordinated by UPMC/LIP6, aims at building a LISP network experimentation platform exclusively built using open source LISP nodes (OpenLISP) acting as ITR/ETR tunnelling routers, MS/MR mapping servers/resolvers, DDT root and Proxy ITR/ETR. Partners include two academic institutions (UPMC, TPT), two Cloud Networking SME (Alphalink, NSS), two network operators (Renater, Orange), two SMEs on Access/Edge Networking (Border 6, Ucopia) and one Internet eXchange Point (Rezopole). [25] The platform should be opened to external partners on 2014/2015 and is already interconnected to the LISP Beta Network with an OpenLISP DDT root. [26]

Future use of LISP

ICAO is considering Ground-Based LISP as a candidate technology for the next-generation Aeronautical Telecommunications Network (ATN). [27] The solution is under further development in part of the SESAR (Single European Sky ATM Research) FCI activities.

Other approaches

Several proposals for separating the two functions and allowing the Internet to scale better have been proposed, for instance GSE/8+8 as network based solution and SHIM6, HIP and ILNP as host based solutions.

See also

Related Research Articles

<span class="mw-page-title-main">IPv4</span> Fourth version of the Internet Protocol

Internet Protocol version 4 (IPv4) is the first version of the Internet Protocol (IP) as a standalone specification. It is one of the core protocols of standards-based internetworking methods in the Internet and other packet-switched networks. IPv4 was the first version deployed for production on SATNET in 1982 and on the ARPANET in January 1983. It is still used to route most Internet traffic today, even with the ongoing deployment of Internet Protocol version 6 (IPv6), its successor.

<span class="mw-page-title-main">IPv6</span> Version 6 of the Internet Protocol

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion, and was intended to replace IPv4. In December 1998, IPv6 became a Draft Standard for the IETF, which subsequently ratified it as an Internet Standard on 14 July 2017.

The Internet Protocol (IP) is the network layer communications protocol in the Internet protocol suite for relaying datagrams across network boundaries. Its routing function enables internetworking, and essentially establishes the Internet.

In computer networking, the User Datagram Protocol (UDP) is one of the core communication protocols of the Internet protocol suite used to send messages to other hosts on an Internet Protocol (IP) network. Within an IP network, UDP does not require prior communication to set up communication channels or data paths.

In computing, Internet Protocol Security (IPsec) is a secure network protocol suite that authenticates and encrypts packets of data to provide secure encrypted communication between two computers over an Internet Protocol network. It is used in virtual private networks (VPNs).

<span class="mw-page-title-main">Network address translation</span> Technique for making connections between IP address spaces

Network address translation (NAT) is a method of mapping an IP address space into another by modifying network address information in the IP header of packets while they are in transit across a traffic routing device. The technique was initially used to bypass the need to assign a new address to every host when a network was moved, or when the upstream Internet service provider was replaced but could not route the network's address space. It has become a popular and essential tool in conserving global address space in the face of IPv4 address exhaustion. One Internet-routable IP address of a NAT gateway can be used for an entire private network.

<span class="mw-page-title-main">Subnet</span> Logical subdivision of an IP network

A subnetwork, or subnet, is a logical subdivision of an IP network. The practice of dividing a network into two or more networks is called subnetting.

Generic routing encapsulation (GRE) is a tunneling protocol developed by Cisco Systems that can encapsulate a wide variety of network layer protocols inside virtual point-to-point links or point-to-multipoint links over an Internet Protocol network.

Multihoming is the practice of connecting a host or a computer network to more than one network. This can be done in order to increase reliability or performance.

Mobile IP is an Internet Engineering Task Force (IETF) standard communications protocol that is designed to allow mobile device users to move from one network to another while maintaining a permanent IP address. Mobile IP for IPv4 is described in IETF RFC 5944, and extensions are defined in IETF RFC 4721. Mobile IPv6, the IP mobility implementation for the next generation of the Internet Protocol, IPv6, is described in RFC 6275.

In computer networking, Teredo is a Microsoft transition technology that gives full IPv6 connectivity for IPv6-capable hosts that are on the IPv4 Internet but have no native connection to an IPv6 network. Unlike similar protocols such as 6to4, it can perform its function even from behind network address translation (NAT) devices such as home routers.

The Neighbor Discovery Protocol (NDP), or simply Neighbor Discovery (ND), is a protocol of the Internet protocol suite used with Internet Protocol Version 6 (IPv6). It operates at the internet layer of the Internet model, and is responsible for gathering various information required for network communication, including the configuration of local connections and the domain name servers and gateways.

Anything In Anything (AYIYA) is a computer networking protocol for managing IP tunneling protocols in use between separated Internet Protocol networks. It is most often used to provide IPv6 transit over an IPv4 network link when network address translation masquerades a private network with a single IP address that may change frequently because of DHCP provisioning by Internet service providers.

IPFC stands for Internet Protocol over Fibre Channel. It governs a set of standards created in January 2006 for address resolution (ARP) and transmitting IPv4 and IPv6 network packets over a Fibre Channel (FC) network. IPFC makes up part of the FC-4 protocol-mapping layer of a Fibre Channel system.

6LoWPAN was a working group of the Internet Engineering Task Force (IETF). It was created with the intention of applying the Internet Protocol (IP) even to the smallest devices, enabling low-power devices with limited processing capabilities to participate in the Internet of Things.

The Site Multihoming by IPv6 Intermediation (SHIM6) protocol is an Internet Layer defined in RFC 5533.

An IPv6 transition mechanism is a technology that facilitates the transitioning of the Internet from the Internet Protocol version 4 (IPv4) infrastructure in use since 1983 to the successor addressing and routing system of Internet Protocol Version 6 (IPv6). As IPv4 and IPv6 networks are not directly interoperable, transition technologies are designed to permit hosts on either network type to communicate with any other host.

A unique local address (ULA) is an Internet Protocol version 6 (IPv6) address in the address range fc00::/7. These addresses are non-globally reachable. For this reason, ULAs are somewhat analogous to IPv4 private network addressing, but with significant differences. Unique local addresses may be used freely, without centralized registration, inside a single site or organization or spanning a limited number of sites or organizations.

<span class="mw-page-title-main">IPv6 address</span> Label to identify a network interface of a computer or other network node

An Internet Protocol version 6 address is a numeric label that is used to identify and locate a network interface of a computer or a network node participating in a computer network using IPv6. IP addresses are included in the packet header to indicate the source and the destination of each packet. The IP address of the destination is used to make decisions about routing IP packets to other networks.

IPv4 Residual Deployment (4rd) is an IPv6 transition mechanism for Internet service providers for deployment of Internet Protocol version 6 (IPv6), while maintaining IPv4 service to customers. The protocol and sample applications are specified in RFC 7600.

References

  1. ↑ "Locator/ID Separation Protocol (lisp) Working Group".
  2. ↑ Farinacci, Dino; Meyer, David; Snijders, Job (9 July 2012). "LISP Canonical Address Format (LCAF)". Ietf Datatracker.
  3. ↑ "RFC4984 - Report from the IAB Workshop on Routing and Addressing" . Retrieved 2010-10-28.
  4. ↑ Lewis, Darrel (26 January 2009). "IETF I-D Architectural Implications of Locator/ID Separation". Ietf Datatracker.
  5. ↑ "IETF I-D draft-brim-lisp-analysis". Ietf Datatracker. 10 March 2008. Retrieved 2010-10-28.
  6. ↑ Saucez, Damien ; Iannone, Luigi ; Bonaventure, Olivier ; Farinacci, Dino, Designing a Deployable Future Internet: the Locator/Identifier Separation Protocol (LISP) case IEEE Internet Computing, December 2012.
  7. ↑ Lewis, Darrel; Meyer, David; Farinacci, Dino; Fuller, Vince (January 2013). "Interworking LISP with IPv4 and IPv6". Ietf Datatracker.
  8. ↑ Lewis, Darrel; Meyer, David; Farinacci, Dino; Fuller, Vince (January 2013). "Interworking LISP with IPv4 and IPv6". Ietf Datatracker.
  9. ↑ Ermagan, Vina; Farinacci, Dino; Lewis, Darrel; Skriver, Jesper; Maino, Fabio; White, Chris (27 September 2012). "NAT traversal for LISP". IETF.
  10. ↑ IPJ article about LISP
  11. ↑ Scaling the Internet with LISP Archived 2010-03-15 at the Wayback Machine tutorial
  12. ↑ Fuller, Vince; Farinacci, Dino; Meyer, David; Lewis, Darrel (January 2013). "LISP Alternative Topology (LISP+ALT)". Ietf Datatracker.
  13. ↑ Jakab, Lorand; Cabellos-Aparicio, Albert; Coras, Florin; Saucez, Damien; Bonaventure, Olivier (2010). "LISP-TREE: A DNS Hierarchy to Support the LISP Mapping System". IEEE Journal on Selected Areas in Communications. 28 (8): 1332–1343. CiteSeerX   10.1.1.716.8421 . doi:10.1109/JSAC.2010.101011. S2CID   16828730.
  14. ↑ Iannone, Luigi; Saucez, Damien; Bonaventure, Olivier (March 2011). "Implementing the Locator/ID Separation Protocol: Design and Experience". Computer Networks. 55 (4): 948–958. CiteSeerX   10.1.1.648.3739 . doi:10.1016/j.comnet.2010.12.017.
  15. ↑ Open LISP control-plane project: https://github.com/lip6-lisp/control-plane
  16. ↑ Research activities on LISP at LIP6: http://www.lisp.ipv6.lip6.fr (webserver hosted behind the LISP Beta Network)
  17. ↑ "IETF I-D draft-meyer-lisp-mn". Ietf Datatracker. Retrieved 2011-09-13.
  18. ↑ "ONOS-LISP-Management-Plane". GitHub . 14 January 2019.
  19. ↑ "Onos/Protocols/Lisp at master · opennetworkinglab/Onos". GitHub .
  20. ↑ "Farinacci/Lispers.net". GitHub . 10 November 2021.
  21. ↑ "Project Proposals/Overlay Network Engine - fd.io".
  22. ↑ "JLisp/Jlisp". GitHub . 28 January 2019.
  23. ↑ "LISP Site Status" . Retrieved 2010-10-28.
  24. ↑ LISP-Lab project website: http://www.lisp-lab.org Archived 2019-05-08 at the Wayback Machine
  25. ↑ More information on Archived 2019-05-08 at the Wayback Machine .
  26. ↑ DDT root website
  27. ↑ Haindl, Bernhard; Lindner, Manfred; Rahman, Reshad; Portoles-Comeras, Marc; Moreno, Victor; Maino, Fabio (30 October 2017). "Ground-Based LISP for the Aeronautical Telecommunications Network". IETF. Retrieved 2018-03-06.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.