[165084] in North American Network Operators' Group
Re: [Paper] B4: Experience with a Globally-Deployed Software Defined
daemon@ATHENA.MIT.EDU (Jimmy Hess)
Sat Aug 17 19:03:14 2013
In-Reply-To: <20130817193218.023845500008D@freedman.net>
Date: Sat, 17 Aug 2013 18:02:44 -0500
From: Jimmy Hess <mysidia@gmail.com>
To: Avi Freedman <freedman@freedman.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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
