Re: [Paper] B4: Experience with a Globally-Deployed Software Defined
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
Unpossible. I heard that no one really uses sdn for anything.
:)
T
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 On Sat, Aug 17, 2013 at 4:32 PM, Avi Freedman <freedman@freedman.net> wrote:
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
Unpossible. I heard that no one really uses sdn for anything.
:)
T
On Sat, Aug 17, 2013 at 2:32 PM, Avi Freedman <freedman@freedman.net> wrote:
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.
Avi
-- -JH
Hacker will love SDN ... :) Bye, bye dumb and resilient network ... .as On 8/17/13 8:02 PM, Jimmy Hess wrote:
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.
On 8/17/2013 7:14 PM, Arturo Servin wrote:
Hacker will love SDN ...
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. On Sat, Aug 17, 2013 at 4:29 PM, Jeff Kell <jeff-kell@utc.edu> wrote:
On 8/17/2013 7:14 PM, Arturo Servin wrote:
Hacker will love SDN ...
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
-- "Subvert the paradigm." - C.K. Prahlad
Well, you just made my point. Just change "cold" for "cyber". /as On 8/17/13 9:26 PM, Jayram Déshpandé wrote:
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.
On Sat, Aug 17, 2013 at 4:29 PM, Jeff Kell <jeff-kell@utc.edu> wrote:
On 8/17/2013 7:14 PM, Arturo Servin wrote:
Hacker will love SDN ...
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
participants (6)
-
Arturo Servin -
freedman＠freedman.net -
Jayram Déshpandé -
Jeff Kell -
jim deleskie -
Jimmy Hess