Locator/ID Separation Protocol (LISP) Control-Plane
draft-ietf-lisp-rfc6833bis-23
- Versions
- 00
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (lisp WG) | |
Authors | Vince Fuller , Dino Farinacci , Albert Cabellos-Aparicio | ||
Last updated | 2018-12-10 | ||
Replaces | draft-farinacci-lisp-rfc6833bis | ||
Stream | Internet Engineering Task Force (IETF) | ||
Formats | pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Luigi Iannone | ||
Shepherd write-up | Show (last changed 2018-07-27) | ||
IESG | IESG state | IESG Evaluation - Defer::AD Followup | |
Consensus Boilerplate | Yes | ||
Telechat date |
Needs a YES. Has enough positions to pass. |
||
Responsible AD | Deborah Brungard | ||
Send notices to | Luigi Iannone <ggx@gigix.net> | ||
IANA | IANA review state | Version Changed - Review Needed |
Network Working Group V. Fuller Internet-Draft D. Farinacci Obsoletes: 6833 (if approved) Cisco Systems Intended status: Standards Track A. Cabellos (Ed.) Expires: June 13, 2019 UPC/BarcelonaTech December 10, 2018 Locator/ID Separation Protocol (LISP) Control-Plane draft-ietf-lisp-rfc6833bis-23 Abstract This document describes the Control-Plane and 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 Control-Plane service interface and communicating with Map-Resolvers and Map-Servers, LISP Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers (ETRs) are not dependent on the details of mapping database systems, which facilitates modularity with different database designs. Since these devices implement the "edge" of the LISP Control-Plane infrastructure, connecting EID addressable nodes of a LISP site, their implementation and operational complexity reduces the overall cost and effort of deploying LISP. This document obsoletes RFC 6830 and 6833. 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 June 13, 2019. Fuller, et al. Expires June 13, 2019 [Page 1] Internet-Draft LISP Control-Plane December 2018 Copyright Notice Copyright (c) 2018 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Scope of Applicability . . . . . . . . . . . . . . . . . 4 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 5 3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 5 4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . 6 5. LISP IPv4 and IPv6 Control-Plane Packet Formats . . . . . . . 8 5.1. LISP Control Packet Type Allocations . . . . . . . . . . 11 5.2. Map-Request Message Format . . . . . . . . . . . . . . . 12 5.3. EID-to-RLOC UDP Map-Request Message . . . . . . . . . . . 15 5.4. Map-Reply Message Format . . . . . . . . . . . . . . . . 17 5.5. EID-to-RLOC UDP Map-Reply Message . . . . . . . . . . . . 21 5.6. Map-Register Message Format . . . . . . . . . . . . . . . 24 5.7. Map-Notify/Map-Notify-Ack Message Format . . . . . . . . 28 5.8. Encapsulated Control Message Format . . . . . . . . . . . 30 6. Changing the Contents of EID-to-RLOC Mappings . . . . . . . . 32 6.1. Solicit-Map-Request (SMR) . . . . . . . . . . . . . . . . 32 7. Routing Locator Reachability . . . . . . . . . . . . . . . . 33 7.1. RLOC-Probing Algorithm . . . . . . . . . . . . . . . . . 35 8. Interactions with Other LISP Components . . . . . . . . . . . 36 8.1. ITR EID-to-RLOC Mapping Resolution . . . . . . . . . . . 36 8.2. EID-Prefix Configuration and ETR Registration . . . . . . 37 8.3. Map-Server Processing . . . . . . . . . . . . . . . . . . 39 8.4. Map-Resolver Processing . . . . . . . . . . . . . . . . . 40 8.4.1. Anycast Operation . . . . . . . . . . . . . . . . . . 40 9. Security Considerations . . . . . . . . . . . . . . . . . . . 41 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 42 11. Changes since RFC 6833 . . . . . . . . . . . . . . . . . . . 43Show full document text