Locator/ID Separation Protocol (LISP) Map-Versioning
draft-iannone-6834bis-00
| Document | Type |
Replaced Internet-Draft
(lisp WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Luigi Iannone , Damien Saucez , Olivier Bonaventure | ||
| Last updated | 2018-06-29 (Latest revision 2018-05-20) | ||
| Replaced by | RFC 9302 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Consensus: Waiting for Write-Up | |
| Document shepherd | Padma Pillay-Esnault | ||
| IESG | IESG state | Replaced by draft-ietf-lisp-6834bis | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | Padma Pillay-Esnault <padma@huawei.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 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.
Authors
Luigi Iannone
Damien Saucez
Olivier Bonaventure
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)