Requirements for Extending BGP/MPLS VPNs to End-Systems

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Maria Napierala  , Luyuan Fang 
Last updated 2014-04-24 (latest revision 2013-10-21)
Replaced by draft-ietf-l3vpn-end-system-requirements
Stream (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The proven scalability and extensibility beyond the original design purposes of the BGP/MPLS IP VPNs (IP VPN) technology [RFC4364] has made it an attractive candidate for Data Center (DC)/Cloud virtualization. This document provides the requirements for extending IP VPN (in original or modified versions) into the end-systems/end- devices, such as a server in a DCs/Cloud. Physical separation of the control and the forwarding planes; virtualizing the network functions of the IP VPN network elements, such as a PE, are the key differences compared with the classic IP VPN solutions.


Maria Napierala
Luyuan Fang (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)