Hi Co-authors, In today's BESS meeting, i have some comments, pls allow me to reiterate here.
1. EVPN supports mass MAC withdraw when local PE link failure occurs. If EVPN is used for NVO3 network interconnecting, if a local NVE occurs node failure, local DCI PE how to notify remote PEs to flush MAC table in mass mode, because in this case, there maybe many TS's MAC attached to the local NVE, mass MAC withdraw should be supported to provide MAC withdraw efficiecy. 2. For EVPN multi-homing, DF is elected per I-ESI, can you ensure BUM traffic load balancing among multiple PEs? 3. If DC GW and WAN PE are separated device, Option-B solution should be supprted to ensure scalability, Option-A (In your draft, it is called vlan hand-off)has two much scalability limitations. For unicast traffic, the DC GW should support VN ID and MPLS VPN Label switching. VN ID and MPLS VPN Label at WAN PE assign machanism also should be specified. For BUM traffic, the DC GW should stitch the multicast tree within data center and the multicast tree in WAN network. The description is too simple in your draft, in our previous drafts, the option-B solution is described in detail, your reading are welcomed. http://datatracker.ietf.org/doc/draft-hao-l2vpn-inter-nvo3-evpn/ http://ietfreport.isoc.org/idref/draft-hao-l3vpn-inter-nvo3-vpn/ In my today's Option-C presentation, transport layer stitching mechanism is described. Option-B solution should support service layer stitching, the mechansim also should be fully described. Thanks weiguo
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
