Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 9302

Locator/ID Separation Protocol (LISP) Map-Versioning,October 2022

File formats:

icon for HTMLicon for text fileicon for v3pdficon for XML
Also available:XML file for editing
 
Status:
PROPOSED STANDARD
Obsoletes:
RFC 6834
Authors:
L. Iannone
D. Saucez
O. Bonaventure
Stream:
IETF
Source:
lisp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9302

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9302


Abstract

This document describes the Locator/ID Separation Protocol (LISP)Map-Versioning mechanism, which provides in-packet information aboutEndpoint-ID-to-Routing-Locator (EID-to-RLOC) mappings used toencapsulate LISP data packets. This approach is based on associatinga version number to EID-to-RLOC mappings and transporting such aversion number in the LISP-specific header of LISP-encapsulatedpackets. LISP Map-Versioning is particularly useful to informcommunicating Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers(ETRs) about modifications of the mappings used to encapsulatepackets. The mechanism is optional and transparent toimplementations not supporting this feature, since in theLISP-specific header and in the Map Records, bits used forMap-Versioning can be safely ignored by ITRs and ETRs that do notsupport or do not want to use the mechanism.

This document obsoletes RFC 6834, which is the initial experimentalspecifications of the mechanisms updated by this document.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp