[lisp] Last Call: <draft-ietf-lisp-6834bis-10.txt> (Locator/ID Separation Protocol (LISP) Map-Versioning) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 04 May 2022 20:55 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: Padma Pillay-Esnault <padma.ietf@gmail.com>, aretana.ietf@gmail.com, draft-ietf-lisp-6834bis@ietf.org, lisp-chairs@ietf.org, lisp@ietf.org, padma.ietf@gmail.com
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <165169770276.21983.16421609311411069002@ietfa.amsl.com>
Date: Wed, 04 May 2022 13:55:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/kdStGvd1_JZBJPQ36TIwTdsMuME>
Subject: [lisp] Last Call: <draft-ietf-lisp-6834bis-10.txt> (Locator/ID Separation Protocol (LISP) Map-Versioning) to Proposed Standard

The IESG has received a request from the Locator/ID Separation Protocol WG
(lisp) to consider the following document: - 'Locator/ID Separation Protocol
(LISP) Map-Versioning'
  <draft-ietf-lisp-6834bis-10.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-05-19. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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.  This 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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lisp-6834bis/



No IPR declarations have been submitted directly on this I-D.

[lisp] Last Call: <draft-ietf-lisp-6834bis-10.txt… The IESG