ObsoletedEXPERIMENTALIETF stream

RFC 6834: Locator/ID Separation Protocol (LISP) Map-Versioning

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9302.

Current version: RFC 9302Locator/ID Separation Protocol (LISP) Map-Versioning

In plain English — editorial summary, not part of the RFC

This document describes the LISP (Locator/ID Separation Protocol) Map-Versioning mechanism, which provides in-packet information about Endpoint ID to Routing Locator (EID-to-RLOC) mappings used to encapsulate LISP data packets. The proposed approach is based on associating a version number to EID-to-RLOC mappings and the transport of such a version number in the LISP-specific header of LISP-encapsulated packets. LISP Map-Versioning is particularly useful to inform communicating Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers (ETRs) about modifications of the mappings used to encapsulate packets. The mechanism is transparent to implementations not supporting this feature, since in the LISP- specific header and in the Map Records, bits used for Map-Versioning can be safely ignored by ITRs and ETRs that do not support the mechanism. This document defines an Experimental Protocol for the Internet community.

Document record

Document ID
RFC6834
Published
January 2013
Authors
L. Iannone; D. Saucez; O. Bonaventure
Status
EXPERIMENTAL
Stream
IETF
Area
rtg
Pages
21
Also known as
Obsoleted by:
RFC 9302

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6834-locator-id-separation-protocol-lisp-map-versioning