Rare project developers

[mc36 <>]

hi,
i was further thinking about my previous idea about stacking/backplane 
capability, and i already spotted some missing parts...
most importantly, multicast would be completely broken if we followed that 
slim {swid;brid;vrfid;}... moreover the lack of
diversity, as you already mentioned polka as the protocol... and, as per 
original plan, one had to run an igp... so for now,
i stepped back and here is the current idea, a generalized freerouter 
stacking methodology:
- one will configure the backplane ports on the individual switches with mpls 
and an igp...
- one will configure the bgp with the proper afis: vpnv4, vpnv6 and evpn...
- and there will be a new server called stacking...
and this is where the magic will happen:
so under the stacking server, one will export various parts of the freerouter 
configuration, for now, let's talk about ports...
these parts will be locked on the executing switch, but the config changes 
will happen on a remote freerouter running the
counterpart of the stacking server... all the config changes done on the 
controller, will be propagated to the target router...
in this way, we even can add an openvswitch based box to the fabric, not just 
the p4lang based ones...
much like cisco probably do in their aci stuff, which is basically a 
super-nxos seeing all the leafs' configs in one place...
any idea?
br,
cs


On 5/6/22 01:27, Moises R. N. Ribeiro wrote:
[..]