Locator/ID Separation Protocol (LISP) Map-Versioning
RFC 6834
Document | Type | RFC - Experimental (January 2013; No errata) | |
---|---|---|---|
Authors | Luigi Iannone , Damien Saucez , Olivier Bonaventure | ||
Last updated | 2015-10-14 | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6834 (Experimental) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Jari Arkko | ||
IESG note | Terry Manderson (terry.manderson@icann.org) is the document shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) L. Iannone Request for Comments: 6834 Telecom ParisTech Category: Experimental D. Saucez ISSN: 2070-1721 INRIA Sophia Antipolis O. Bonaventure Universite catholique de Louvain January 2013 Locator/ID Separation Protocol (LISP) Map-Versioning 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 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 the mechanism. Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6834. Iannone, et al. Experimental [Page 1] RFC 6834 LISP Map-Versioning January 2013 Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................3 2. Requirements Notation ...........................................4 3. Definitions of Terms ............................................4 4. EID-to-RLOC Map-Version Number ..................................4 4.1. The Null Map-Version .......................................5 5. Dealing with Map-Version Numbers ................................6 5.1. Handling Destination Map-Version Number ....................7 5.2. Handling Source Map-Version Number .........................9 6. LISP Header and Map-Version Numbers ............................10 7. Map Record and Map-Version .....................................11 8. Benefits and Case Studies for Map-Versioning ...................12 8.1. Map-Versioning and Unidirectional Traffic .................12 8.2. Map-Versioning and Interworking ...........................12 8.2.1. Map-Versioning and Proxy-ITRs ......................13 8.2.2. Map-Versioning and LISP-NAT ........................13 8.2.3. Map-Versioning and Proxy-ETRs ......................14 8.3. RLOC Shutdown/Withdraw ....................................14 8.4. Map-Version for Lightweight LISP Implementation ...........15 9. Incremental Deployment and Implementation Status ...............15 10. Security Considerations .......................................16 10.1. Map-Versioning against Traffic Disruption ................16 10.2. Map-Versioning against Reachability Information DoS ......17 11. Open Issues and Considerations ................................17 11.1. Lack of Synchronization among ETRs .......................17 12. Acknowledgments ...............................................19 13. References ....................................................19Show full document text