Using LISP for Secure Hybrid Cloud Extension
draft-freitasbellagamba-lisp-hybrid-cloud-use-case-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Santiago Freitas , Patrice Bellagamba , Yves Hertoghs | ||
Last updated | 2014-08-25 (Latest revision 2014-02-21) | ||
Replaces | draft-freitas-bellagamba-lisp-hybrid-cloud-usecase | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The purpose of this draft is to document how the Locator/Identifier Separation Protocol (LISP) can be used to enable a secure layer 3-based Hybrid Cloud, which is a composition of two or more distinct cloud infrastructures that remain unique entities, but are bound together to enable data and application portability. It describes how LISP, in combination with IPsec, can be implemented on a virtualized router that is deployed on a public cloud and on the enterprise Data Center to enable cloud bursting, workload migration, rapid provision of new applications in the cloud and disaster recovery use cases. This draft covers how LISP allows virtual machines (VMs) to be moved to the cloud without requiring changes to the VMs IP and/or MAC-address.
Authors
Santiago Freitas
Patrice Bellagamba
Yves Hertoghs
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)