RFC 9302 on Locator/ID Separation Protocol (LISP) Map-Versioning
rfc-editor@rfc-editor.org Thu, 20 October 2022 21:08 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D1FC185B29 for <ietf-announce@ietfa.amsl.com>; Thu, 20 Oct 2022 14:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level:
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNvoP-nP4uar for <ietf-announce@ietfa.amsl.com>; Thu, 20 Oct 2022 14:08:39 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8D97C1522D4 for <ietf-announce@ietf.org>; Thu, 20 Oct 2022 14:07:46 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id AEBE315D30D; Thu, 20 Oct 2022 14:07:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9302 on Locator/ID Separation Protocol (LISP) Map-Versioning
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20221020210746.AEBE315D30D@rfcpa.amsl.com>
Date: Thu, 20 Oct 2022 14:07:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/kkE1hlpLmh7V_DTZI1ADpX2mt0o>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2022 21:08:40 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9302
Title: Locator/ID Separation Protocol (LISP) Map-Versioning
Author: L. Iannone,
D. Saucez,
O. Bonaventure
Status: Standards Track
Stream: IETF
Date: October 2022
Mailbox: luigi.iannone@huawei.com,
damien.saucez@inria.fr,
Olivier.Bonaventure@uclouvain.be
Pages: 15
Obsoletes: RFC 6834
I-D Tag: draft-ietf-lisp-6834bis-14.txt
URL: https://www.rfc-editor.org/info/rfc9302
DOI: 10.17487/RFC9302
This document describes the Locator/ID Separation Protocol (LISP)
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 transporting 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, which is the initial experimental
specifications of the mechanisms updated by this document.
This document is a product of the Locator/ID Separation Protocol Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC