LISP Map-Versioning
draft-ietf-lisp-map-versioning-08

The information below is for an old version of the document
Document Type Active Internet-Draft (lisp WG)
Last updated 2012-02-14 (latest revision 2012-01-19)
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Has enough positions to pass.
Responsible AD Jari Arkko
IESG note Terry Manderson (terry.manderson@icann.org) is the document shepherd.
Send notices to lisp-chairs@tools.ietf.org, draft-ietf-lisp-map-versioning@tools.ietf.org
Network Working Group                                         L. Iannone
Internet-Draft                           Telekom Innovation Laboratories
Intended status: Experimental                                  D. Saucez
Expires: August 17, 2012                          INRIA Sophia Antipolis
                                                          O. Bonaventure
                                        Universite catholique de Louvain
                                                       February 14, 2012

                          LISP Map-Versioning
                 draft-ietf-lisp-map-versioning-08.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 transport
   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 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 http://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 August 17, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the

Iannone, et al.          Expires August 17, 2012                [Page 1]
Internet-Draft             LISP Map-Versioning             February 2012

   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 . . . . . . . . . 11
     8.1.  Map-Versioning and unidirectional traffic  . . . . . . . . 12
     8.2.  Map-Versioning and interworking  . . . . . . . . . . . . . 12
       8.2.1.  Map-Versioning and Proxy-ITRs  . . . . . . . . . . . . 12
       8.2.2.  Map-Versioning and LISP-NAT  . . . . . . . . . . . . . 13
       8.2.3.  Map-Versioning and Proxy-ETRs  . . . . . . . . . . . . 13
     8.3.  RLOC shutdown/withdraw . . . . . . . . . . . . . . . . . . 14
     8.4.  Map-Version for lightweight LISP implementation  . . . . . 14
   9.  Incremental deployment and implementation status . . . . . . . 15
   10. Security Considerations  . . . . . . . . . . . . . . . . . . . 15
     10.1. Map-Versioning against traffic disruption  . . . . . . . . 15
     10.2. Map-Versioning against reachability information DoS  . . . 16
   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 17
   12. Open Issues and Considerations . . . . . . . . . . . . . . . . 17
Show full document text