L3VPN automatical interconnection for VPN4DC
draft-jin-l3vpn-vpn4dc-interconnect-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ning So , Bhumip Khasnabish , Bo Wu | ||
| Last updated | 2012-04-26 (Latest revision 2011-10-24) | ||
| 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
VPN4DC provides VPN oriented datacenter service to customer through L3VPN which is consisted of (private) L3VPN in datacenter and network provider's L3VPN over wide geographical area. If we considering the two L3VPN in two different AS, [RFC4364] providers three options to achieve L3VPN inter-AS connection. Both option A and B could be used to connect L3VPN in VPN4DC. This draft discusses a novel method for implementing option A, to automatically configure the VRF interface in order to interconnect the two segments of the end-to-end L3VPN. This L3VPN interconnection automation mechanism is expected to significantly reduce the VPN oriented inter-connection/service provisioning time.
Authors
Ning So
Bhumip Khasnabish
Bo Wu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)