About inter-as option-B solution between NVO3 network and EVPN network

[Haoweiguo <[e-mail]>]

Hi Ali,

I think the inter-as option-B solution in our draft is different from current EVPN inter-as solution. The procedures are described as follows:



Assuming ASBR in NVO3 network is called ASBR-d, ASBR in EVPN network is called ASBR-w.



Control plane process:

1. From DC to WAN side:

MPLS VPN Label is allocated on ASBR-d per ESI per VN, the usage of the VN has no change from traditional NVO3 network,the VN has global significance; For single-homed scenario, it is allocated per NVE per VN. Incoming forwarding table is generated on ASBR-d. ASBR-d advertises the MAC/IP advertisement route with new allocated MPLS VPN Label to peer ASBR-w.



2.From WAN to DC side:

VN ID is allocated per MPLS VPN Label, the VN ID has local significance on ASBR-d.  Outgoing forwarding table is generated on ASBR-d. ASBR-d advertises the MAC/IP advertisement route with new VN ID to local NVE.



Data plane process:

1.From DC to WAN side:

When a NVE receives traffic from local TS, the NVE performs MAC lookup in local VN, then it sends the traffic to ASBR-d using NVO3 encapsulation, VN ID is the new allocated VN ID on ASBR-d, It can only have local significance on ASBR-d. ASBR-d performs NVO3 decapsulation, switch VN ID to MPLS VPN Label, then performs MPLS encapsulation and sends to peer ASBR-w.



2. From WAN to DC side:

When ASBR-d receives traffic from peer ASBR-w, ASBR-d switches MPLS VPN Label to local NVE+ VN ID and sends it to local NVE using NVO3 encapsulation. The VN ID in the NVO3 header has global significance on all NVEs.



In option-B solution, only VN ID and MPLS VPN Label switching is supported on ASBR-d, ASBR-d doesn't need to perform MAC look up, ASBR-d has more scalability.

Thanks

weiguo