Software Defined Networks

Thu Dec 5 17:16:48 UTC 2019

I tell everyone we had SDNs in the 90s.

But we called it “expect scripts”.

:-)

-- 
TTFN,
patrick

> On Dec 4, 2019, at 9:41 PM, Jennifer Rexford <jrex at cs.princeton.edu> wrote:
> 
> SDN is definitely an overloaded and confusing term that is used inconsistently.  Here are a few attempts to explain:
> 
> - “The Road to SDN: An Intellectual History of Programmable Networks” (ACM Queue, December 2013)
>   https://queue.acm.org/detail.cfm?id=2560327 <https://queue.acm.org/detail.cfm?id=2560327>
> 
> - “Abstractions for Software-Defined Networks” (CACM, October 2014)
>    http://www.cs.cornell.edu/~jnfoster/papers/sdn-abstractions.pdf <http://www.cs.cornell.edu/~jnfoster/papers/sdn-abstractions.pdf>
> 
> - “From Ethane to SDN and Beyond” (ACM SIGCOMM CCR, October 2019)
>    https://ccronline.sigcomm.org/wp-content/uploads/2019/10/acmdl19-347.pdf <https://ccronline.sigcomm.org/wp-content/uploads/2019/10/acmdl19-347.pdf>
> 
> — Jen
> 
> 
>> On Dec 4, 2019, at 12:56 PM, Rod Beck <rod.beck at unitedcablecompany.com <mailto:rod.beck at unitedcablecompany.com>> wrote:
>> 
>> Can someone explain what is all the fuss? SDN is like the latest telecom craze but the articles do a poor job of explaining the advantages. I seek concrete examples. 
>> 
>> Regards, 
>> 
>> Roderick. 
>> 
>> 
>> Roderick Beck
>> VP of Business Development
>> United Cable Company
>> www.unitedcablecompany.com <http://www.unitedcablecompany.com/>
>> New York City & Budapest
>> rod.beck at unitedcablecompany.com <mailto:rod.beck at unitedcablecompany.com>
>> 36-70-605-5144
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20191205/ebe42d64/attachment.html>