Hi Folks, This draft describes vanilla and partial option-B solution for inter-as connection between NVO3 and MPLS/IP VPN network. Centralized NVE-NVA archetecture is used. Compared with option-A solution, this solution has more scalability. Appreciate more comments and suggestions.
Thanks, weiguo ________________________________________ From: [email protected] [[email protected]] Sent: Thursday, March 05, 2015 9:59 To: Lucy yong; Shahram Davari; Andrew Qu; Luyuan Fang; Haoweiguo; Lucy yong; Luyuan Fang; Osama Zia; Robert Raszuk; Osama Zia; Shahram Davari; Andrew Qu; Robert Raszuk; Haoweiguo Subject: New Version Notification for draft-hao-nvo3-inter-as-vpn-00.txt A new version of I-D, draft-hao-nvo3-inter-as-vpn-00.txt has been successfully submitted by Weiguo Hao and posted to the IETF repository. Name: draft-hao-nvo3-inter-as-vpn Revision: 00 Title: Inter-AS Option B between NVO3 and BGP/MPLS IP VPN network through centralized architecture Document date: 2015-03-05 Group: Individual Submission Pages: 14 URL: http://www.ietf.org/internet-drafts/draft-hao-nvo3-inter-as-vpn-00.txt Status: https://datatracker.ietf.org/doc/draft-hao-nvo3-inter-as-vpn/ Htmlized: http://tools.ietf.org/html/draft-hao-nvo3-inter-as-vpn-00 Abstract: This draft describes the solution of vanilla inter-as option-B connection between NVO3 network and MPLS/IP VPN network through centralized NVE-NVA architecture. The ASBR located in NVO3 network is called ASBR-d, NVO3 tunnel and MPLS tunnel stitching should be performed on the ASBR-d. No distributed BGP VPN protocol (RFC4364) is running between NVEs and ASBR-d in NVO3 network, NVEs and ASBR-d are controlled by centralized NVA. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
