Network Working Group V. Fuller
Internet-Draft D. Farinacci
Intended status: Experimental cisco Systems
Expires: September 5, 2012 March 4, 2012
LISP Map Server Interface
draft-ietf-lisp-ms-16.txt
Abstract
This draft describes the Maping Service for the Locator Identifier
Separation Protocol (LISP), implemented by two new types of LISP-
speaking devices, the LISP Map Resolver and LISP Map Server, that
provides a simplified "front end" to for one or more Endpoint ID to
Routing Locator mapping databases.
By using this service interface and communicating with Map Resolvers
and Map Servers, LISP Ingress Tunnel Routers and Egress Tunnel
Routers, are not dependent on the details of mapping database
systems, which facilitates experimentation with different database
designs. Since these devices implement the "edge" of the LISP
infrastructure, connect directly to LISP-capable Internet end sites,
and comprise the bulk of LISP-speaking devices, reducing their
implementation and operational complexity should also reduce the
overall cost and effort of deploying LISP.
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 September 5, 2012.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
Fuller & Farinacci Expires September 5, 2012 [Page 1]
Internet-Draft LISP Map Server Interface March 2012
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. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
3. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Interactions With Other LISP Components . . . . . . . . . . . 6
4.1. ITR EID-to-RLOC Mapping Resolution . . . . . . . . . . . . 6
4.2. EID Prefix Configuration and ETR Registration . . . . . . 7
4.3. Map Server Processing . . . . . . . . . . . . . . . . . . 8
4.4. Map Resolver Processing . . . . . . . . . . . . . . . . . 9
4.4.1. Anycast Map Resolver Operation . . . . . . . . . . . . 10
5. Open Issues and Considerations . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
Fuller & Farinacci Expires September 5, 2012 [Page 2]
Internet-Draft LISP Map Server Interface March 2012
1. Introduction
[LISP], the Locator Identifier Separation Protocol, specifies an
architecture and mechanism for replacing the addresses currently used
by IP with two separate name spaces: Endpoint IDs (EIDs), used within
sites, and Routing Locators (RLOCs), used on the transit networks
that make up the Internet infrastructure. To achieve this
separation, LISP defines protocol mechanisms for mapping from EIDs to
RLOCs. In addition, LISP assumes the existence of a database to
datatracker.ietf.org