The Internet was built on a simple assumption: every device has one IP address, and that address describes both who it is and where it is located.
That assumption worked fine when networks were small and stable.
The Scalability Problem
Today, your enterprise hosts thousands of endpoints spread across branches, data centers, and cloud environments.
When a device moves from one site to another, its IP address changes.
Active sessions drop. Applications reconnect. Users notice.At the routing level, the problem is just as serious.

Figure 1 — Global BGP Routing Table Overview
Internet routers carry over 900,000 prefixes in their BGP tables today.
Every new site and every mobile endpoint contributes to that growth.
This is not sustainable at scale.The Root Cause
The root cause is that a single IP address carries two meanings at once:
Identity — who the device is
Location — where the device is attached in the network topology
When those two roles are fused into a single address, mobility becomes painful and routing tables become bloated.
Separating Identity from Location
In Figure 2, each LISP site has two clearly distinct elements.
Your endpoint (PC1 or PC2) carries an Identity.
Your edge router carries a Location.
The RLOC space in the center only knows about locations, not about individual endpoints.

Figure 2 — Identity Location Separation
LISP was designed to separate identity from location by introducing two distinct address spaces.
Answer the question below
Besides location, what is the second role LISP separates into its own address space?
LISP (Locator/ID Separation Protocol), defined in RFC 9300, solves the problem by splitting the IP address space into two separate namespaces.
EID — Endpoint Identifier
The first namespace is the EID (Endpoint Identifier).
An EID is the address assigned to your endpoint: a host, a VM, or an entire subnet.
It represents identity. When your laptop moves from Paris to London, its EID does not change.
Figure 3 — Endpoint Identifier Concept
Answer the question below
In LISP, which identifier names the endpoint itself and stays the same when the host moves?
RLOC — Routing Locator
The second namespace is the RLOC (Routing Locator).
An RLOC is the routable IP address of the edge router at a site.
It represents location. When your laptop moves to London, it is now reachable through the London edge router's RLOC.
Figure 4 — Routing Locator Transport Network
Only RLOCs appear in the global routing table.
EIDs are kept entirely out of the routing table.
This is what reduces routing table size: instead of millions of endpoint routes, the network only needs to know the edge router locations.Answer the question below
Which address type appears in the global routing table in LISP?
The Four LISP Roles
You might be wondering how a router finds the RLOC for a given EID if that information is not in the routing table.
LISP answers this with a dedicated control plane built around four functional roles.ITR and ETR

Figure 5 — LISP Architecture and Roles
ITR (Ingress Tunnel Router) — the router at the source site. It intercepts traffic destined for an EID, resolves the corresponding RLOC, and encapsulates the packet for transport across the underlay.
ETR (Egress Tunnel Router) — the router at the destination site. It receives the encapsulated packet, strips the LISP headers, and delivers the original packet to the local EID.
MS and MR

Figure 6 — Map Server Resolver Roles
Map Server (MS) — the central mapping database. ETRs register their EID-to-RLOC bindings here. It is the authoritative source of truth for endpoint location.
Map Resolver (MR) — the query handler. When an ITR does not know where an EID is located, it sends a Map-Request to the MR. The MR returns the correct RLOC.
In practice, the MS and MR roles are often hosted on the same device, referred to as the MS/MR.
A router that acts as both ITR and ETR is called an xTR. You will see this term frequently in SD-Access documentation.Answer the question below
Which LISP component registers EID-to-RLOC mappings?
Definitions are useful, but let's see how all of this plays out in practice.
LISP operates on two distinct planes.
The control plane handles mapping discovery.
The data plane handles encapsulation and forwarding.

Figure 7 — ETR Mapping Registration Topology
Let's trace what happens from the moment an ETR comes online to the moment a packet reaches its destination.
Step 1 — ETR Registration (Map-Register)
When your site's ETR comes online, it sends a Map-Register message to the Map Server.
This message declares the EID prefix your site owns and the RLOC an ITR should use to reach it.
Map-Register messages are sent periodically to keep the binding fresh.
Figure 8 — ETR Map Register Process
The Map Server stores this binding.
It now knows that to reach your EID prefix, an ITR must encapsulate toward your RLOC.
Figure 9 — EID RLOC Mapping Stored
Step 2 — ITR Lookup (Map-Request)
Your source ITR receives a packet destined for an EID in another site.
It checks its local mapping cache. No entry exists yet.
Figure 10 — ITR Map Cache Lookup
The ITR sends a Map-Request to the Map Resolver, asking where the destination EID is located.

Figure 11 — Map Request Resolution
The Map Resolver forwards the request to the correct Map Server.
Answer the question below
What message does an ETR send to the Map Server to register its EID prefix?
Step 3 — Map-Reply
The Map Server instructs the destination ETR to send a Map-Reply directly back to the ITR.
The reply contains the RLOC for the destination site and a TTL for the cache entry.
Figure 12 — Map Reply Mapping
Your ITR stores the mapping locally and reuses it for all subsequent packets without querying again.

Figure 13 — ITR Map Cache Installed
Step 4 — Encapsulation and Forwarding
Your ITR now knows the destination RLOC.
It wraps the original IP packet inside a new outer IP/UDP header.
Figure 14 — LISP Packet Encapsulation Flow
Outer source IP — the ITR's RLOC
Outer destination IP — the ETR's RLOC
UDP destination port — 4341 (IANA-assigned LISP data plane port)
The encapsulated packet travels through the underlay using the outer RLOC addresses.
The ETR at the destination strips the outer headers and delivers the original EID-addressed packet to the local host.
The endpoint receives it with no awareness that LISP was involved.Answer the question below
What does the ITR send when its mapping cache has no entry for a destination EID?
Not every site in the world runs LISP.
When a LISP site needs to communicate with a non-LISP site, standard ITR/ETR logic breaks down.
The non-LISP site has no EID registration, no Map Server, and no way to participate in the LISP control plane.LISP solves this with two proxy roles.
PITR and PETR Overview

Figure 15 — PITR PETR Internet Connectivity
On the left, a PITR (Proxy Ingress Tunnel Router) sits at the edge of a non-LISP site.
It acts as the entrance to the LISP domain from outside: it intercepts traffic coming from non-LISP sources and encapsulates it into the LISP fabric.
On the right, a PETR (Proxy Egress Tunnel Router) sits at the edge of another non-LISP site.
It acts as the exit from the LISP domain toward outside: it receives LISP-encapsulated traffic from an ITR and forwards it natively toward the non-LISP destination.
ITR to PETR — Reaching a Non-LISP Destination
Your LISP site needs to reach PC2 at 10.20.1.10, which sits behind a non-LISP site.
Your ITR starts the process it always follows: it sends a Map-Request to the MS/MR, asking where the destination is located.
Figure 16 — Map Request (ITR → MR) in LISP Proxy ETR Process
The mapping system has no EID registered for 10.20.1.10.
It returns a Negative Map-Reply, signaling that this prefix belongs to a non-LISP destination.
Figure 17 — Negative Map Reply from Mapping System
Your ITR now knows it cannot encapsulate directly toward an ETR.
Instead, it redirects the traffic toward the PETR. The packet is encapsulated with the PETR's RLOC as the outer destination. The PETR decapsulates it and forwards it natively to the non-LISP host.

Figure 18 — LISP Encapsulation from ITR to PETR
Answer the question below
Which LISP device receives encapsulated traffic when the destination is a non-LISP site?
PITR to ETR — Non-LISP Source Reaching a LISP Site
Now the reverse scenario. A non-LISP host at 10.10.1.10 wants to reach a LISP EID at 10.20.1.10.
That non-LISP host has no knowledge of the LISP mapping system. It simply sends a standard IP packet.
Figure 19 — PITR Sends Map Request to Locate Destination EID
The PITR intercepts this traffic on behalf of the LISP domain. It sends a Map-Request to the MS/MR to locate the destination EID.
The MS/MR forwards the request to the ETR that owns the EID prefix.The ETR responds with a Map-Reply directly back to the PITR.
The reply contains the EID prefix 10.20.1.0/24 and the RLOC 203.0.113.20 to use for encapsulation.
Figure 20 — Map Reply from ETR with EID-to-RLOC Mapping
It encapsulates the original packet and forwards it toward the ETR using the RLOC from the Map-Reply.
The ETR decapsulates it and delivers the packet to the local EID.
Figure 21 — LISP Encapsulation from PITR to ETR (Data Plane)
The non-LISP host receives a reply as if LISP had never been involved.
Answer the question below
In an SD-Access fabric, which node acts as the LISP Map Server and Map Resolver?