Requirements for Extending BGP/MPLS VPNs to End-Systems
draft-fang-l3vpn-end-system-requirements-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Maria Napierala , Luyuan Fang | ||
| Last updated | 2013-05-09 (Latest revision 2012-11-05) | ||
| Replaced by | draft-ietf-l3vpn-end-system-requirements | ||
| RFC stream | (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
Service Providers commonly use BGP/MPLS VPNs [RFC 4364] as the technology for providing wide-area virtual private network services. This technology has proven to scale to a very large number of VPNs and attachment points, and it is well suited for extending VPN connectivity to end-systems operating in a multi- tenant environments. Virtualized end-system environment imposes additional requirements to MPLS/BGP VPN technology when applied to end-system networking, which are defined in this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)