LISP Predictive RLOCs
draft-farinacci-lisp-predictive-rlocs-01

Document Type Active Internet-Draft (individual)
Last updated 2016-11-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       D. Farinacci
Internet-Draft                                               lispers.net
Intended status: Experimental                          P. Pillay-Esnault
Expires: May 17, 2017                                Huawei Technologies
                                                       November 13, 2016

                         LISP Predictive RLOCs
                draft-farinacci-lisp-predictive-rlocs-01

Abstract

   This specification will describe a method to achieve near-zero packet
   loss when an EID is roaming quickly across RLOCs.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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 May 17, 2017.

Copyright Notice

   Copyright (c) 2016 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

Farinacci & Pillay-EsnaultExpires May 17, 2017                  [Page 1]
Internet-Draft            LISP Predictive RLOCs            November 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Design Details  . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  RLE Encoding  . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Packet Delivery Optimizations . . . . . . . . . . . . . .   6
     4.3.  Trading Off Replication Cost  . . . . . . . . . . . . . .   7
   5.  Directional Paths with Intersections  . . . . . . . . . . . .   8
   6.  Multicast Considerations  . . . . . . . . . . . . . . . . . .   9
   7.  Multiple Address-Family Considerations  . . . . . . . . . . .  10
   8.  Scaling Considerations  . . . . . . . . . . . . . . . . . . .  10
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     11.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  12
   Appendix B.  Document Change Log  . . . . . . . . . . . . . . . .  13
     B.1.  Changes to draft-farinacci-lisp-predictive-rlocs-01.txt .  13
     B.2.  Changes to draft-farinacci-lisp-predictive-rlocs-00.txt .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The LISP architecture [RFC6830] specifies two namespaces, End-Point
   IDs (EIDs) and Routing Locators (RLOCs).  An EID identifies a node in
   the network and the RLOC indicates the EID's topological location.
   When an node roams in the network, its EID remains fixed and
   unchanged but the RLOCs associated with it change to reflect its new
   topological attachment point.  This specification will focus EIDs and
   RLOCs residing in separate nodes.  An EID is assigned to a host node
   that roams while the RLOCs are assigned to network nodes that stay
   stationary and are part of the network topology.  For example, a set
   of devices on an aircraft are assigned EIDs, and base stations on the
   ground attached to the Internet infrastructure are configured as LISP
Show full document text