Locator/ID Separation Protocol (LISP) Impact
RFC 7834
Document | Type | RFC - Informational (April 2016; No errata) | |
---|---|---|---|
Authors | Damien Saucez , Luigi Iannone , Albert Cabellos-Aparicio , Florin Coras | ||
Last updated | 2016-04-29 | ||
Replaces | draft-saucez-lisp-impact | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Wassim Haddad | ||
Shepherd write-up | Show (last changed 2015-07-19) | ||
IESG | IESG state | RFC 7834 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Deborah Brungard | ||
Send notices to | draft-ietf-lisp-impact.all@ietf.org | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) D. Saucez Request for Comments: 7834 INRIA Category: Informational L. Iannone ISSN: 2070-1721 Telecom ParisTech A. Cabellos F. Coras Technical University of Catalonia April 2016 Locator/ID Separation Protocol (LISP) Impact Abstract The Locator/ID Separation Protocol (LISP) aims to improve the Internet routing scalability properties by leveraging three principles: address role separation, encapsulation, and mapping. In this document, based on implementation work, deployment experiences, and theoretical studies, we discuss the impact that the deployment of LISP can have on both the routing infrastructure and the end user. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. 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/rfc7834. Saucez, et al. Informational [Page 1] RFC 7834 LISP Impact April 2016 Copyright Notice Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 2. LISP in a Nutshell . . . . . . . . . . . . . . . . . . . . . 4 3. LISP for Scaling the Internet Routing Architecture . . . . . 5 4. Beyond Scaling the Internet Routing Architecture . . . . . . 6 4.1. Traffic Engineering . . . . . . . . . . . . . . . . . . . 8 4.2. LISP for IPv6 Co-existence . . . . . . . . . . . . . . . 8 4.3. Inter-domain Multicast . . . . . . . . . . . . . . . . . 9 5. Impact of LISP on Operations and Business Models . . . . . . 10 5.1. Impact on Non-LISP Traffic and Sites . . . . . . . . . . 10 5.2. Impact on LISP Traffic and Sites . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . 13 7.2. Informative References . . . . . . . . . . . . . . . . . 14 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Saucez, et al. Informational [Page 2] RFC 7834 LISP Impact April 2016 1. Introduction The Locator/ID Separation Protocol (LISP) relies on three principles to improve the scalability properties of Internet routing: address role separation, encapsulation, and mapping. When invented, LISP was targeted at solving the Internet routing scaling problem [RFC4984]. There have now been years of implementations and experiments examining the impact and open questions of using LISP to improve inter-domain routing scalability. Experience has shown that because LISP utilizes mapping and encapsulation technologies, it can be deployed and used for purposes that go beyond routing scalability. For example, LISP provides a mean for a LISP site to precisely control its inter-domain outgoing and incoming traffic, with the possibility to apply different policies to different domains exchanging traffic with it. LISP can also be used to ease the transition from IPv4 to IPv6 as it allows the transport of IPv4 over IPv6 or IPv6 over IPv4. Furthermore, LISP also supports inter-domainShow full document text