> From: Nick Hilliard <n...@foobar.org> > Sent: Thursday, April 30, 2020 7:14 PM > > adamv0...@netconsultings.com wrote on 30/04/2020 13:14: > > Never understood this VXLAN nonsense in DC universe (not the comics), > > in SP space this was a solved problem and is a well-trodden path since > > ever -PWs, > > everything has its use. PWs have major problems loadbalancing over multiple > links. > Yes back in the days, but one can use flow labels now,
> Also the complexity of mpls + associated control plane is a drawback in > situations. > Well if you compare EVPN VXLAN -there's not that much of a difference compared to EVPN MPLS, oh and with VPN labels you get micro-segmentation for free and not as an afterthought. > Sometimes vxlan provides the required functionality. Why use a > more complicated protocol when a simpler one is a 100% match for your > requirements? > Futureproofing. DC-folks# This STP sucks, let's MC-LAG/VSS everything, ok that sucks let's do TRILL et, al., that sucked let's do VXLAN, wait, how do we do CP-based mac learning? Let's do EVPN VXLAN, Oh has anyone reserved VXLAN header field that can be used for micro-segmentation? Tumbleweed ... SP-folks# no way we'll have STP to core, let's sue VPLS, that sucked let's use EVPN/PBB-EVPN...... adam _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
