LISP Delegated Database Tree
draft-fuller-lisp-ddt-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2011-11-28
Replaced by rfc8111, draft-ietf-lisp-ddt
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                                          V. Fuller
Internet-Draft                                                  D. Lewis
Intended status: Experimental                               D. Farinacci
Expires: May 31, 2012                                      cisco Systems
                                                       November 28, 2011

                      LISP Delegated Database Tree
                      draft-fuller-lisp-ddt-00.txt

Abstract

   This draft describes the LISP Delegated Database Tree (LISP-DDT), a
   hierarchical, distributed database which embodies the delegation of
   authority to provide mappings from LISP Endpoint Identifiers (EIDs)
   to Routing Locators (RLOCs).  It is a statically-defined distribution
   of the EID namespace among a set of LISP-speaking servers, called DDT
   nodes.  Each DDT node is configured with an EID-prefix that it "owns"
   plus information, including the RLOCs for Map Servers or other DDT
   nodes for each defined more-specific EID-prefix of the "owned"
   prefix.

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 31, 2012.

Copyright Notice

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

Fuller, et al.            Expires May 31, 2012                  [Page 1]
Internet-Draft        LISP Delegated Database Tree         November 2011

   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.  Definition of Terms  . . . . . . . . . . . . . . . . . . . . .  5
   3.  EID-prefix tree structure and instance IDs . . . . . . . . . .  7
   4.  Configuring XEID-prefix delegation . . . . . . . . . . . . . .  8
     4.1.  Example DDT node configuration . . . . . . . . . . . . . .  8
     4.2.  The root DDT node  . . . . . . . . . . . . . . . . . . . .  8
   5.  DDT node operation - sending referrals . . . . . . . . . . . . 10
     5.1.  Match of a delegated prefix (or sub-prefix)  . . . . . . . 10
     5.2.  Missing delegation from an authoritative prefix  . . . . . 10
   6.  DDT Map Server operation . . . . . . . . . . . . . . . . . . . 11
   7.  DDT Map Resolver operation . . . . . . . . . . . . . . . . . . 12
     7.1.  Queuing, Sending, and Retransmitting DDT Map-Requests  . . 12
     7.2.  Receiving and following referrals  . . . . . . . . . . . . 12
       7.2.1.  Handling referral errors . . . . . . . . . . . . . . . 13
       7.2.2.  Referral loop detection  . . . . . . . . . . . . . . . 14
   8.  Example message flow . . . . . . . . . . . . . . . . . . . . . 15
     8.1.  ITR sends a Map-Request to a DDT Map Resolver  . . . . . . 15
     8.2.  DDT Map Resolver receives and processes Map-Request  . . . 15
     8.3.  DDT Map Resolver searches referral cache for XEID  . . . . 15
     8.4.  DDT Map Resolver creates and sends DDT Map-Request . . . . 16
     8.5.  DDT node receives and processes DDT Map-Request  . . . . . 16
     8.6.  DDT Map Resolver processes Map-Referral  . . . . . . . . . 16
     8.7.  DDT Map Server receives Map-Request  . . . . . . . . . . . 17
     8.8.  DDT Map Resolver finished  . . . . . . . . . . . . . . . . 17
     8.9.  DDT Map Server receives LISP-SEC-enabled Map-Request . . . 17
     8.10. ETR sends Map-Reply to ITR . . . . . . . . . . . . . . . . 18
   9.  Open Issues and Considerations . . . . . . . . . . . . . . . . 19
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 20
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 21
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Show full document text