Inter-AS Option C between NVO3 and BGP/MPLS IP VPN network
draft-hao-bess-inter-nvo3-vpn-optionc-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Hao Weiguo , Lucy Yong , Susan Hares | ||
| Last updated | 2015-04-30 (Latest revision 2014-10-27) | ||
| 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
This draft describes inter-as option-C solution between NVO3 network and MPLS/IP VPN network. BGP label routing information is extended to create multi-hop forwarding path between local NVE and remote PE. Also to ensure VPNv4 route exchange correctly between local NVE and remote PE, VN ID space should be partitioned, only the VN IDs of lower 1 Million can be used for interconnection with outer MPLS VPN network using option-C solution, the rest 15 Million VN IDs can only be used for intra DC.
Authors
Hao Weiguo
Lucy Yong
Susan Hares
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)