Locator/ID Separation Protocol (LISP) Map-Server Interface
RFC 6833
| Document | Type |
RFC - Experimental
(January 2013; No errata)
Was draft-ietf-lisp-ms (lisp WG)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-fuller-lisp-ms | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6833 (Experimental) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Jari Arkko | ||
| IESG note | Joel Halpern (jmh@joelhalpern.com) is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) V. Fuller
Request for Comments: 6833
Category: Experimental D. Farinacci
ISSN: 2070-1721 Cisco Systems
January 2013
Locator/ID Separation Protocol (LISP) Map-Server Interface
Abstract
This document describes the Mapping Service for the Locator/ID
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" 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 document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Engineering
Task Force (IETF). It represents the consensus of the IETF
community. It has received public review and has been approved for
publication by the Internet Engineering Steering Group (IESG). Not
all documents approved by the IESG are a candidate for any level of
Internet Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6833.
Fuller & Farinacci Experimental [Page 1]
RFC 6833 LISP Map-Server Interface January 2013
Copyright Notice
Copyright (c) 2013 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
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. Basic Overview ..................................................4
4. Interactions with Other LISP Components .........................5
4.1. ITR EID-to-RLOC Mapping Resolution .........................5
4.2. EID-Prefix Configuration and ETR Registration ..............6
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 .................................10
6. Security Considerations ........................................11
7. References .....................................................12
7.1. Normative References ......................................12
7.2. Informative References ....................................12
Appendix A. Acknowledgments .......................................13
1. Introduction
The Locator/ID Separation Protocol [RFC6830] 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
store and propagate those mappings globally. Several such databases
have been proposed; among them are the Content distribution Overlay
Network Service for LISP (LISP-CONS) [LISP-CONS], LISP-NERD
(a Not-so-novel EID-to-RLOC Database) [RFC6837], and LISP Alternative
Show full document text