Locator/ID Separation Protocol (LISP) Map-Versioning
draft-ietf-lisp-6834bis-06

The information below is for an old version of the document
Document Type Expired Internet-Draft (lisp WG)
Authors Luigi Iannone  , Damien Saucez  , Olivier Bonaventure 
Last updated 2020-08-16 (latest revision 2020-02-13)
Replaces draft-iannone-6834bis
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
pdf htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Document shepherd Padma Pillay-Esnault
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Padma Pillay-Esnault <padma.ietf@gmail.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-lisp-6834bis-06.txt

Abstract

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 optional and 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 or do not want to use the mechanism. This document obsoletes RFC 6834 "Locator/ID Separation Protocol (LISP) Map-Versioning", which is the initial experimental specifications of the mechanisms updated by this document.

Authors

Luigi Iannone (ggx@gigix.net)
Damien Saucez (damien.saucez@gmail.com)
Olivier Bonaventure (Olivier.Bonaventure@uclouvain.be)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)