Network Working Group D. Lewis
Internet-Draft G. Schudel
Intended status: Experimental Cisco Systems, Inc.
Expires: August 18, 2014 February 14, 2014
LISP Virtual Private Networks (VPNs)
draft-lewis-lisp-vpns-00.txt
Abstract
This document describes the use of the Locator/ID Separation Protocol
(LISP) to create Virtual Private Networks (VPNs). LISP is used to
provide segmentation in both the LISP data plane and control plane.
These IP based VPNs can be created over the top of the Internet or
other VPN protocols, and can be implemented by Enterprise or Service
Provider type networks. The goal of these VPNs is to leverage the
characteristics of LISP - routing scalability, simply expressed
Ingress site TE Policy, IP Address Family traversal, and mobility, in
ways that provide value to network operators.
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 http://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 August 18, 2014.
Copyright Notice
Copyright (c) 2014 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
Lewis & Schudel Expires August 18, 2014 [Page 1]Internet-Draft LISP Virtual Private Networks (VPNs) February 2014
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. Virtualizing LISP . . . . . . . . . . . . . . . . . . . . . . 4
3.1. The LISP IID in the Data Plane . . . . . . . . . . . . . 4
3.2. The LISP IID in the Control Plane . . . . . . . . . . . . 4
3.3. Locator Network Segmentation . . . . . . . . . . . . . . 4
4. LISP VPN Network Elements . . . . . . . . . . . . . . . . . . 5
5. Types of LISP VPNs . . . . . . . . . . . . . . . . . . . . . 5
6. Enterprise VPNs . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Internet based Enterprise LISP VPN Example . . . . . . . 6
6.2. MPLS-VPN based Enterprise LISP VPN Example . . . . . . . 6
7. Service Provider LISP VPNs . . . . . . . . . . . . . . . . . 6
7.1. MPLS VPNs and LISP CE based VPNs, from the SP perspective 6
7.2. Service Provider Internet based LISP VPN Example . . . . 7
7.3. Service Provider MPLS-VPN based LISP VPN Example . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8.1. LISP VPNs and IPSec . . . . . . . . . . . . . . . . . . . 8
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
Network virtualization create multiple, logically separated
topologies across one common physical infrastructure. Virtual
Routing and Forwarding (VRF) containers are used to create multiple
instances of Layer 3 routing tables virtualization (segmentation) at
the device level. Data Plane Forwarding VRF table separation is
maintained across network paths using either single-hop path
segmentation (hop-by-hop) such as 802.1q VLANs or VPI/VCI PW.
Traditional multi-hop mechanisms include MPLS and GRE tunnels.