IP-VPN Data Center Problem Statement and Requirements
draft-fang-vpn4dc-problem-statement-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Maria Napierala , Luyuan Fang , Dennis Cai | ||
| Last updated | 2012-12-14 (Latest revision 2012-06-12) | ||
| 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
Network Service Providers commonly use BGP/MPLS VPNs [RFC 4364] as the control plane for virtual networks. This technology has proven to scale to a large number of VPNs and attachment points, and it is well suited for Data Center connectivity, especially when supporting all IP applications. The Data Center environment presents new challenges and imposes additional requirements to IP VPN technologies, including multi- tenancy support, high scalability, VM mobility, security, and orchestration. This document describes the problems and defines the new requirements.
Authors
Maria Napierala
Luyuan Fang
Dennis Cai
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)