No, people never use *flow controllers* for anything.
People have been doing SDN since before Google was around.
OK, so it was horrible expect scripts but it worked.
Avi
At iMCI (pre-Worldcom) we had scripts that would build all our ATM VC's
for a 400node mesh, would take all night to run 
-jim
No, people never use *flow controllers* for anything.
People have been doing SDN since before Google was around.
OK, so it was horrible expect scripts but it worked.
Not really.
Automatic reconfiguration of routers is not what a software-defined network
is.
It is one of the things (but not all of the things) that SDN provides.
A software defined network is one where the forwarding behavior can be
completely defined
in software running outside of the devices that perform the forwarding.
You can write expect scripts all day; but you cannot turn your basic switch
into a Load balancer or stateful firewall with one.
or decide in real time exactly which destination Ethernet ports a packet
coming in a certain port is going to touch, without having structured
VLANs and static MAC tables on the switches ahead of time.
Changing device configurations with expect scripts is a limited tiny subset
of what SDN is.
Hacker will love SDN ...
Bye, bye dumb and resilient network ...
.as
Yes. Traditional SDN is big, flat layer-2 network with global
mac-address resolution, and a big fat Java applet managing the adjacency
tables.
What could *possibly* go wrong?
Jeff
SDN is not a new concept at all.
Infact since ARPANET days, the notion of centralized control plane had a
lot of traction. But with Cold war around, It made more sense to push the
control plane intelligence into individual decision points (routers ,
switches , et . al. ). Considering the possibility of the commies taking
down some part of the early Internet, the remaining partitioned network
could still survive as the rest of the decision points could converge and
act as independent network snippets.
-Jay.
Well, you just made my point.
Just change "cold" for "cyber".
/as