Requirements for Extending BGP/MPLS VPNs to End-Systems
draft-ietf-bess-end-system-requirements-00
| Document | Type |
Expired Internet-Draft
(bess WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Maria Napierala , Luyuan Fang | ||
| Last updated | 2018-04-11 (Latest revision 2014-11-11) | ||
| Replaces | draft-ietf-l3vpn-end-system-requirements | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Reviews |
RTGDIR Early review
by Ross Callon
Has nits
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Parked WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 proven scalability and extensibility of the BGP/MPLS IP VPNs (IP VPN) technology has made it an attractive candidate for data center/cloud virtualization. Virtualized end-system environment imposes additional requirements to MPLS/BGP VPN technology. This document provides the requirements for extending IP VPN technology (in original or modified versions) into the end-systems/hosts, such as a server in a data center.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)