The Locator/ID Separation Protocol (LISP)
draft-ietf-lisp-rfc6830bis-26
| Document | Type | Active Internet-Draft (lisp WG) | |
|---|---|---|---|
| Last updated | 2018-11-04 | ||
| Replaces | draft-farinacci-lisp-rfc6830bis | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Luigi Iannone | ||
| Shepherd write-up | Show (last changed 2018-07-25) | ||
| IESG | IESG state | IESG Evaluation - Defer::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Has 3 DISCUSSes. Needs 2 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Deborah Brungard | ||
| Send notices to | Luigi Iannone <ggx@gigix.net> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | None | ||
Network Working Group D. Farinacci
Internet-Draft V. Fuller
Obsoletes: 6830 (if approved) D. Meyer
Intended status: Standards Track D. Lewis
Expires: May 8, 2019 Cisco Systems
A. Cabellos (Ed.)
UPC/BarcelonaTech
November 4, 2018
The Locator/ID Separation Protocol (LISP)
draft-ietf-lisp-rfc6830bis-26
Abstract
This document describes the Data-Plane protocol for the Locator/ID
Separation Protocol (LISP). LISP defines two namespaces, End-point
Identifiers (EIDs) that identify end-hosts and Routing Locators
(RLOCs) that identify network attachment points. With this, LISP
effectively separates control from data, and allows routers to create
overlay networks. LISP-capable routers exchange encapsulated packets
according to EID-to-RLOC mappings stored in a local Map-Cache.
LISP requires no change to either host protocol stacks or to underlay
routers and offers Traffic Engineering, multihoming and mobility,
among other features.
This document obsoletes RFC 6830.
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 May 8, 2019.
Farinacci, et al. Expires May 8, 2019 [Page 1]
Internet-Draft LISP November 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 . . . . . . . . . . . . . . . . . . . . 4
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 5
4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. Packet Flow Sequence . . . . . . . . . . . . . . . . . . 11
5. LISP Encapsulation Details . . . . . . . . . . . . . . . . . 13
5.1. LISP IPv4-in-IPv4 Header Format . . . . . . . . . . . . . 13
5.2. LISP IPv6-in-IPv6 Header Format . . . . . . . . . . . . . 14
5.3. Tunnel Header Field Descriptions . . . . . . . . . . . . 15
6. LISP EID-to-RLOC Map-Cache . . . . . . . . . . . . . . . . . 20
7. Dealing with Large Encapsulated Packets . . . . . . . . . . . 20
7.1. A Stateless Solution to MTU Handling . . . . . . . . . . 21
7.2. A Stateful Solution to MTU Handling . . . . . . . . . . . 22
8. Using Virtualization and Segmentation with LISP . . . . . . . 22
9. Routing Locator Selection . . . . . . . . . . . . . . . . . . 23
10. Routing Locator Reachability . . . . . . . . . . . . . . . . 25
10.1. Echo Nonce Algorithm . . . . . . . . . . . . . . . . . . 26
11. EID Reachability within a LISP Site . . . . . . . . . . . . . 27
12. Routing Locator Hashing . . . . . . . . . . . . . . . . . . . 28
13. Changing the Contents of EID-to-RLOC Mappings . . . . . . . . 29
13.1. Database Map-Versioning . . . . . . . . . . . . . . . . 30
14. Multicast Considerations . . . . . . . . . . . . . . . . . . 31
15. Router Performance Considerations . . . . . . . . . . . . . . 31
16. Security Considerations . . . . . . . . . . . . . . . . . . . 32
17. Network Management Considerations . . . . . . . . . . . . . . 33
18. Changes since RFC 6830 . . . . . . . . . . . . . . . . . . . 33
19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
Show full document text