Experiment of Example Solution for VPN4DC
draft-zeng-vpn4dc-example-solution-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Delei Yu , Qing Zeng | ||
| Last updated | 2012-05-03 (Latest revision 2011-10-31) | ||
| 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
More and more service providers proposed VPN4DC requirements. That is how to maintain and manage the host-to-host connectivity through Layer 3 Virtual Private Networks (L3VPNs) between an enterprise legacy VPN site and the virtual datacenter (VDC) in datacenter, including automated provisioning, monitoring, and so on[VPN4DC]. This document provides an example solution by prototyping experiment for VPN4DC auto-provision. This solution is focus on the network side and the DC Edge, the DC inside is out of scope.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)