<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.iannone-6834bis" target="https://datatracker.ietf.org/doc/html/draft-iannone-6834bis-00">
   <front>
      <title>Locator/ID Separation Protocol (LISP) Map-Versioning</title>
      <author initials="L." surname="Iannone" fullname="Luigi Iannone">
         <organization>Telecom ParisTech</organization>
      </author>
      <author initials="D." surname="Saucez" fullname="Damien Saucez">
         <organization>INRIA Sophia Antipolis</organization>
      </author>
      <author initials="O." surname="Bonaventure" fullname="Olivier Bonaventure">
         <organization>Universite catholique de Louvain</organization>
      </author>
      <date month="May" day="20" year="2018" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-iannone-6834bis-00" />
   
</reference>
