/
BGP L3VPN Virtual BGP L3VPN Virtual

BGP L3VPN Virtual - PowerPoint Presentation

lois-ondreau
lois-ondreau . @lois-ondreau
Follow
416 views
Uploaded On 2016-04-12

BGP L3VPN Virtual - PPT Presentation

PE draftfangl3vpnvirtualpe04 Luyuan Fang David Ward Rex Fernando ID: 279569

virtual vpe plane network vpe virtual network plane bgp location vpn control devices wan architecture device systems orchestration controller

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "BGP L3VPN Virtual" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

BGP L3VPN Virtual PE draft-fang-l3vpn-virtual-pe-04

Luyuan Fang David Ward Rex Fernando Maria Napierala Nabil Bitar Dhananjaya Rao

Bruno

Rijsman

Ning

So

Jim

Guichard

Wen Wang

Manuel PaulSlide2

What is this draft about?A solution architecture of virtual PE

Allow physical control plane and data plane separationAllow IP VPN (RFC 4364) to be extended into end-systems/devicesAllow large scale dynamic orchestration supportScope Anywhere, DC and beyondSlide3

Virtual PE DefinitionA virtual PE (vPE): a BGP IP VPN PE software instance which may reside in any network or computing devices.

vPE-F: vPE Forwarding PlanevPE-C: vPE Control PlanevPE-C and vPE-F can be decoupled, they may reside in the same physical device, or most often in different physical devices.Slide4

vPE Architecture and Design Options

Design Options1. vPE-F location1a. End device, such as a server1b. Top of the Rack (ToR)1c. Any other devices/systems, e.g., a Gateway router2. vPE-C location2a. Controller (centralized or distributed)2b. Same location as vPE-F, using mp-bgp for signaling3. Orchestration models3a. Push model: push IP VPN provisioning from NMS or other central control provisioning systems to the IP VPN network elements.3b. Pull model: pull from network elements to network management/AAA based upon data plane or control plane activity. Slide5

WAN Network

GatewayService Network FabricCompute/ Storage/Appliance

vPE Architecture Reference Models (1)

vPE-F in the end device, vPE-C in the controller

5

Application/VM

(CE

)

vPE-F

WAN edge Gateway

Virtual RR (vRR)

MPLS Core

Controller

/OrchestrationSlide6

WAN Network

GatewayService Network FabricCompute/ Storage/Appliance

vPE Architecture Reference Models (2)

vPE in the end device, using MP-BGP for control

6

Application/VM

(CE

)

vPE

WAN edge Gateway

Virtual RR (vRR)

MPLS Core

MP-BGPSlide7

Status and recent commentsDifference form 03 to 04 Editing through out the document

Security text additionComments from WimMake sure to be clear on the scope is beyond DCNeed static routes for virtualized appliances own routing stateRenaming VPE-F location to VPE-F host locationRegarding L2 content, either expand to include bothh l3 and l2 BGP VPN approach, or not to include mentioning of l2Slide8

Next StepsPlease send your comments on the list or talk to usReady to ask the WG to check interest for adopting this work as WG item