Locator/ID Separation Protocol (LISP) Map-Versioning
draft-iannone-6834bis-00

Document Type Active Internet-Draft (lisp WG)
Last updated 2018-05-21 (latest revision 2018-05-20)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         L. Iannone
Internet-Draft                                         Telecom ParisTech
Intended status: Standards Track                               D. Saucez
Expires: November 18, 2018                        INRIA Sophia Antipolis
                                                          O. Bonaventure
                                        Universite catholique de Louvain
                                                            May 17, 2018

          Locator/ID Separation Protocol (LISP) Map-Versioning
                      draft-iannone-6834bis-00.txt

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 18, 2018.

Iannone, et al.         Expires November 18, 2018               [Page 1]
Internet-Draft             LISP Map-Versioning                  May 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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 . . . . . . . . . . . . .   9
   7.  LISP Generic Protocol Encapsulation (GPE) Header and Map-
       Version Numbers . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Map Record and Map-Version  . . . . . . . . . . . . . . . . .  11
   9.  Benefits and Case Studies for Map-Versioning  . . . . . . . .  12
     9.1.  Map-Versioning and Unidirectional Traffic . . . . . . . .  12
     9.2.  Map-Versioning and Interworking . . . . . . . . . . . . .  13
       9.2.1.  Map-Versioning and Proxy-ITRs . . . . . . . . . . . .  13
       9.2.2.  Map-Versioning and LISP-NAT . . . . . . . . . . . . .  14
       9.2.3.  Map-Versioning and Proxy-ETRs . . . . . . . . . . . .  14
     9.3.  RLOC Shutdown/Withdraw  . . . . . . . . . . . . . . . . .  14
     9.4.  Map-Version Additional Use Cases  . . . . . . . . . . . .  15
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  15
     10.1.  Map-Versioning against Traffic Disruption  . . . . . . .  16
     10.2.  Map-Versioning against Reachability Information DoS  . .  16
   11. Considerations  . . . . . . . . . . . . . . . . . . . . . . .  17
   12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
Show full document text