Search RFCs

RFC Editor

File formats:

Status:

EXPERIMENTAL

Authors:

D. Lewis
D. Meyer
D. Farinacci
V. Fuller

Stream:

IETF

Source:

lisp (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6832

Discuss this RFC: Send questions or comments to the mailing listlisp@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6832

Abstract

This document describes techniques for allowing sites running theLocator/ID Separation Protocol (LISP) to interoperate with Internetsites that may be using either IPv4, IPv6, or both but that are notrunning LISP. A fundamental property of LISP-speaking sites is thatthey use Endpoint Identifiers (EIDs), rather than traditional IPaddresses, in the source and destination fields of all traffic theyemit or receive. While EIDs are syntactically identical to IPv4 orIPv6 addresses, normally routes to them are not carried in the globalrouting system, so an interoperability mechanism is needed for non-LISP-speaking sites to exchange traffic with LISP-speaking sites.This document introduces three such mechanisms. The first uses a newnetwork element, the LISP Proxy Ingress Tunnel Router (Proxy-ITR), toact as an intermediate LISP Ingress Tunnel Router (ITR) for non-LISP-speaking hosts. Second, this document adds Network AddressTranslation (NAT) functionality to LISP ITRs and LISP Egress TunnelRouters (ETRs) to substitute routable IP addresses for non-routableEIDs. Finally, this document introduces the Proxy Egress TunnelRouter (Proxy-ETR) to handle cases where a LISP ITR cannot sendpackets to non-LISP sites without encapsulation. This document defines an Experimental Protocol for the Internet community.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.