A Decent LISP Mapping System (LISP-Decent)
draft-farinacci-lisp-decent-04
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-09-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
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 C. Cantrell
Expires: March 6, 2020 Nexus
September 3, 2019
A Decent LISP Mapping System (LISP-Decent)
draft-farinacci-lisp-decent-04
Abstract
This draft describes how the LISP mapping system designed to be
distributed for scale can also be decentralized for management and
trust.
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 https://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 March 6, 2020.
Copyright Notice
Copyright (c) 2019 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
(https://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.
Farinacci & Cantrell Expires March 6, 2020 [Page 1]
Internet-Draft A Decent LISP Mapping System (LISP-Decent) September 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Push-Based Mapping System . . . . . . . . . . . . . . . . . . 5
4.1. Components of a Pushed-Based LISP-Decent xTR . . . . . . 5
4.2. No LISP Protocol Changes . . . . . . . . . . . . . . . . 6
4.3. Configuration and Authentication . . . . . . . . . . . . 7
4.4. Core Seed-Group . . . . . . . . . . . . . . . . . . . . . 7
5. Pull-Based Mapping System . . . . . . . . . . . . . . . . . . 9
5.1. Components of a Pulled-Based LISP-Decent xTR . . . . . . 9
5.2. Deployment Example . . . . . . . . . . . . . . . . . . . 10
5.3. Management Considerations . . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 13
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 14
B.1. Changes to draft-farinacci-lisp-decent-04 . . . . . . . . 14
B.2. Changes to draft-farinacci-lisp-decent-03 . . . . . . . . 14
B.3. Changes to draft-farinacci-lisp-decent-02 . . . . . . . . 14
B.4. Changes to draft-farinacci-lisp-decent-01 . . . . . . . . 14
B.5. Changes to draft-farinacci-lisp-decent-00 . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
The LISP architecture and protocols [RFC6830] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which is intended to provide overlay network functionality.
To map from EID to a set or RLOCs, a control-plane mapping system are
used [RFC6836] [RFC8111]. These mapping systems are distributed in
nature in their deployment for scalability but are centrally managed
by a third- party entity, namely a Mapping System Provider (MSP).
The entities that use the mapping system, such as data-plane xTRs,
depend on and trust the MSP. They do not participate in the mapping
system other than to register and retrieve information to/from the
mapping system [RFC6833].
This document introduces a Decentralized Mapping System (DMS) so the
xTRs can participate in the mapping system as well as use it. They
can trust each other rather than rely on third-party infrastructure.
Show full document text