draft-ietf-lisp-6834bis-00.txt   draft-ietf-lisp-6834bis-01.txt 
Network Working Group L. Iannone Network Working Group L. Iannone
Internet-Draft Telecom ParisTech Internet-Draft Telecom ParisTech
Obsoletes: 6834 (if approved) D. Saucez Obsoletes: 6834 (if approved) D. Saucez
Intended status: Standards Track INRIA Sophia Antipolis Intended status: Standards Track INRIA Sophia Antipolis
Expires: January 3, 2019 O. Bonaventure Expires: March 9, 2019 O. Bonaventure
Universite catholique de Louvain Universite catholique de Louvain
July 2, 2018 September 5, 2018
Locator/ID Separation Protocol (LISP) Map-Versioning Locator/ID Separation Protocol (LISP) Map-Versioning
draft-ietf-lisp-6834bis-00 draft-ietf-lisp-6834bis-01
Abstract Abstract
This document describes the LISP (Locator/ID Separation Protocol) This document describes the LISP (Locator/ID Separation Protocol)
Map-Versioning mechanism, which provides in-packet information about Map-Versioning mechanism, which provides in-packet information about
Endpoint ID to Routing Locator (EID-to-RLOC) mappings used to Endpoint ID to Routing Locator (EID-to-RLOC) mappings used to
encapsulate LISP data packets. The proposed approach is based on encapsulate LISP data packets. The proposed approach is based on
associating a version number to EID-to-RLOC mappings and the associating a version number to EID-to-RLOC mappings and the
transport of such a version number in the LISP-specific header of transport of such a version number in the LISP-specific header of
LISP-encapsulated packets. LISP Map-Versioning is particularly LISP-encapsulated packets. LISP Map-Versioning is particularly
useful to inform communicating Ingress Tunnel Routers (ITRs) and useful to inform communicating Ingress Tunnel Routers (ITRs) and
Egress Tunnel Routers (ETRs) about modifications of the mappings used Egress Tunnel Routers (ETRs) about modifications of the mappings used
to encapsulate packets. The mechanism is optional and transparent to to encapsulate packets. The mechanism is optional and transparent to
implementations not supporting this feature, since in the LISP- implementations not supporting this feature, since in the LISP-
specific header and in the Map Records, bits used for Map-Versioning 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 can be safely ignored by ITRs and ETRs that do not support or do not
want to use the mechanism. want to use the mechanism.
This document obsoletes [RFC6834], which is the inital experimental This document obsoletes RFC 6834 "Locator/ID Separation Protocl
specifications of the mechanims updated by this document. (LISP) Map-Versionin", which is the initial experimental
specifications of the mechanisms updated by this document.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 9, 2019.
This Internet-Draft will expire on January 3, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 30 skipping to change at page 2, line 31
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4
3. Definitions of Terms . . . . . . . . . . . . . . . . . . . . 4 3. Definitions of Terms . . . . . . . . . . . . . . . . . . . . 4
4. EID-to-RLOC Map-Version Number . . . . . . . . . . . . . . . 4 4. EID-to-RLOC Map-Version Number . . . . . . . . . . . . . . . 4
4.1. The Null Map-Version . . . . . . . . . . . . . . . . . . 5 4.1. The Null Map-Version . . . . . . . . . . . . . . . . . . 5
5. Dealing with Map-Version Numbers . . . . . . . . . . . . . . 6 5. Dealing with Map-Version Numbers . . . . . . . . . . . . . . 6
5.1. Handling Destination Map-Version Number . . . . . . . . . 7 5.1. Handling Destination Map-Version Number . . . . . . . . . 7
5.2. Handling Source Map-Version Number . . . . . . . . . . . 9 5.2. Handling Source Map-Version Number . . . . . . . . . . . 9
6. LISP Header and Map-Version Numbers . . . . . . . . . . . . . 9 6. LISP Header and Map-Version Numbers . . . . . . . . . . . . . 10
7. LISP Generic Protocol Encapsulation (GPE) Header and Map- 7. LISP Generic Protocol Encapsulation (GPE) Header and Map-
Version Numbers . . . . . . . . . . . . . . . . . . . . . . . 10 Version Numbers . . . . . . . . . . . . . . . . . . . . . . . 10
8. Map Record and Map-Version . . . . . . . . . . . . . . . . . 11 8. Map Record and Map-Version . . . . . . . . . . . . . . . . . 11
9. Benefits and Case Studies for Map-Versioning . . . . . . . . 12 9. Benefits and Case Studies for Map-Versioning . . . . . . . . 12
9.1. Map-Versioning and Unidirectional Traffic . . . . . . . . 12 9.1. Map-Versioning and Unidirectional Traffic . . . . . . . . 12
9.2. Map-Versioning and Interworking . . . . . . . . . . . . . 13 9.2. Map-Versioning and Interworking . . . . . . . . . . . . . 13
9.2.1. Map-Versioning and Proxy-ITRs . . . . . . . . . . . . 13 9.2.1. Map-Versioning and Proxy-ITRs . . . . . . . . . . . . 13
9.2.2. Map-Versioning and LISP-NAT . . . . . . . . . . . . . 14 9.2.2. Map-Versioning and LISP-NAT . . . . . . . . . . . . . 14
9.2.3. Map-Versioning and Proxy-ETRs . . . . . . . . . . . . 14 9.2.3. Map-Versioning and Proxy-ETRs . . . . . . . . . . . . 14
9.3. RLOC Shutdown/Withdraw . . . . . . . . . . . . . . . . . 14 9.3. RLOC Shutdown/Withdraw . . . . . . . . . . . . . . . . . 14
9.4. Map-Version Additional Use Cases . . . . . . . . . . . . 15 9.4. Map-Version Additional Use Cases . . . . . . . . . . . . 15
10. Security Considerations . . . . . . . . . . . . . . . . . . . 15 10. Security Considerations . . . . . . . . . . . . . . . . . . . 15
10.1. Map-Versioning against Traffic Disruption . . . . . . . 16 10.1. Map-Versioning against Traffic Disruption . . . . . . . 16
10.2. Map-Versioning against Reachability Information DoS . . 16 10.2. Map-Versioning against Reachability Information DoS . . 16
11. Considerations . . . . . . . . . . . . . . . . . . . . . . . 17 11. Considerations . . . . . . . . . . . . . . . . . . . . . . . 17
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18
13.1. Normative References . . . . . . . . . . . . . . . . . . 18 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
13.2. Informative References . . . . . . . . . . . . . . . . . 19 14.1. Normative References . . . . . . . . . . . . . . . . . . 18
14.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
This document describes the Map-Versioning mechanism used to provide This document describes the Map-Versioning mechanism used to provide
information on changes in the EID-to-RLOC (Endpoint ID to Routing information on changes in the EID-to-RLOC (Endpoint ID to Routing
Locator) mappings used in the LISP (Locator/ID Separation Protocol Locator) mappings used in the LISP (Locator/ID Separation Protocol
[I-D.ietf-lisp-rfc6830bis][I-D.ietf-lisp-rfc6833bis]) context to [I-D.ietf-lisp-rfc6830bis][I-D.ietf-lisp-rfc6833bis]) context to
perform packet encapsulation. The mechanism is totally transparent perform packet encapsulation. The mechanism is totally transparent
to xTRs (Ingress and Egress Tunnel Routers) not supporting or not to xTRs (Ingress and Egress Tunnel Routers) not supporting or not
using such functionality. using such functionality.
This document obsoletes [RFC6834], which is the inital experimental This document obsoletes [RFC6834], which is the initial experimental
specifications of the mechanims updated by this document. specifications of the mechanisms updated by this document.
The basic mechanism is to associate a Map-Version number to each LISP The basic mechanism is to associate a Map-Version number to each LISP
EID-to-RLOC mapping and transport such a version number in the LISP- EID-to-RLOC mapping and transport such a version number in the LISP-
specific header. When a mapping changes, a new version number is specific header. When a mapping changes, a new version number is
assigned to the updated mapping. A change in an EID-to-RLOC mapping assigned to the updated mapping. A change in an EID-to-RLOC mapping
can be a change in the RLOCs set, by adding or removing one or more can be a change in the RLOCs set, by adding or removing one or more
RLOCs, but it can also be a change in the priority or weight of one RLOCs, but it can also be a change in the priority or weight of one
or more RLOCs. or more RLOCs.
When Map-Versioning is used, LISP-encapsulated data packets contain When Map-Versioning is used, LISP-encapsulated data packets contain
skipping to change at page 4, line 14 skipping to change at page 4, line 16
Cache the latest mapping for the source EID (in the case of Cache the latest mapping for the source EID (in the case of
bidirectional traffic). If this is not the case, a Map-Request can bidirectional traffic). If this is not the case, a Map-Request can
be sent. be sent.
Considerations about the deployment of LISP Map-Versioning for Considerations about the deployment of LISP Map-Versioning for
Internet traffic are discussed in Section 11. Internet traffic are discussed in Section 11.
2. Requirements Notation 2. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Definitions of Terms 3. Definitions of Terms
This document uses terms already defined in the main LISP This document uses terms already defined in the main LISP
specification (, [I-D.ietf-lisp-rfc6830bis] specification (, [I-D.ietf-lisp-rfc6830bis]
[I-D.ietf-lisp-rfc6833bis]). Here, we define the terms that are [I-D.ietf-lisp-rfc6833bis]). Here, we define the terms that are
specific to the Map-Versioning mechanism. Throughout the whole specific to the Map-Versioning mechanism. Throughout the whole
document, Big Endian bit ordering is used. document, Big Endian bit ordering is used.
Map-Version number: An unsigned 12-bit integer is assigned to an Map-Version number: An unsigned 12-bit integer is assigned to an
skipping to change at page 18, line 23 skipping to change at page 18, line 23
Status Bits it will start sending Map-Requests to confirm each change Status Bits it will start sending Map-Requests to confirm each change
in reachability. in reachability.
So far, LISP does not provide any specific synchronization mechanism So far, LISP does not provide any specific synchronization mechanism
but assumes that synchronization is provided by configuring the but assumes that synchronization is provided by configuring the
different xTRs consistently. The same applies for Map-Versioning. different xTRs consistently. The same applies for Map-Versioning.
If in the future any synchronization mechanism is provided, Map- If in the future any synchronization mechanism is provided, Map-
Versioning will take advantage of it automatically, since it is Versioning will take advantage of it automatically, since it is
included in the Record format, as described in Section 8. included in the Record format, as described in Section 8.
12. Acknowledgments 12. IANA Considerations
This document includes no request to IANA.
13. Acknowledgments
This work benefited support from NewNet@Paris, Cisco's Chair This work benefited support from NewNet@Paris, Cisco's Chair
"Networks for the Future" at Telecom ParisTech "Networks for the Future" at Telecom ParisTech
(http://newnet.telecom-paristech.fr). Any opinions, findings or (http://newnet.telecom-paristech.fr). Any opinions, findings or
recommendations expressed in this material are those of the author(s) recommendations expressed in this material are those of the author(s)
and do not necessarily reflect the views of partners of the Chair. and do not necessarily reflect the views of partners of the Chair.
13. References 14. References
13.1. Normative References 14.1. Normative References
[I-D.ietf-lisp-gpe] [I-D.ietf-lisp-gpe]
Maino, F., Lemon, J., Agarwal, P., Lewis, D., and M. Maino, F., Lemon, J., Agarwal, P., Lewis, D., and M.
Smith, "LISP Generic Protocol Extension", draft-ietf-lisp- Smith, "LISP Generic Protocol Extension", draft-ietf-lisp-
gpe-03 (work in progress), April 2018. gpe-05 (work in progress), August 2018.
[I-D.ietf-lisp-rfc6830bis] [I-D.ietf-lisp-rfc6830bis]
Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A.
Cabellos-Aparicio, "The Locator/ID Separation Protocol Cabellos-Aparicio, "The Locator/ID Separation Protocol
(LISP)", draft-ietf-lisp-rfc6830bis-12 (work in progress), (LISP)", draft-ietf-lisp-rfc6830bis-16 (work in progress),
March 2018. August 2018.
[I-D.ietf-lisp-rfc6833bis] [I-D.ietf-lisp-rfc6833bis]
Fuller, V., Farinacci, D., and A. Cabellos-Aparicio, Fuller, V., Farinacci, D., and A. Cabellos-Aparicio,
"Locator/ID Separation Protocol (LISP) Control-Plane", "Locator/ID Separation Protocol (LISP) Control-Plane",
draft-ietf-lisp-rfc6833bis-10 (work in progress), March draft-ietf-lisp-rfc6833bis-13 (work in progress), August
2018. 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
13.2. Informative References [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
14.2. Informative References
[RFC6832] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller, [RFC6832] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller,
"Interworking between Locator/ID Separation Protocol "Interworking between Locator/ID Separation Protocol
(LISP) and Non-LISP Sites", RFC 6832, (LISP) and Non-LISP Sites", RFC 6832,
DOI 10.17487/RFC6832, January 2013, DOI 10.17487/RFC6832, January 2013,
<https://www.rfc-editor.org/info/rfc6832>. <https://www.rfc-editor.org/info/rfc6832>.
[RFC6834] Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID [RFC6834] Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID
Separation Protocol (LISP) Map-Versioning", RFC 6834, Separation Protocol (LISP) Map-Versioning", RFC 6834,
DOI 10.17487/RFC6834, January 2013, DOI 10.17487/RFC6834, January 2013,
 End of changes. 16 change blocks. 
24 lines changed or deleted 36 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/