Skip to content
rule 11 reader
  • about
    • about me
    • mailing list
    • author page
    • rss feeds
  • reading
    • technology books
    • skills books
    • fiction books
    • philosophy & culture books
    • christian books
    • papers
    • worth reading
  • categories
    • career
      • career
      • design skills
      • communication skills
      • education
      • soft skills
      • troubleshooting skills
    • coding
    • complexity
    • culture
    • ddos
    • ipv6
    • other technologies
    • research
    • reviews
    • routing
      • bgp
      • bgp security
      • eigrp
      • is-is
      • ospf
      • mpls
      • other routing
    • security
    • standards
    • worth reading
    • content type
      • long video
      • long audio
      • short video
      • written
    • other
      • governance
      • humor
    • archive
  • the hedge
  • history
  • resources
    • my goodreads
    • my feedly
    • network icons
  • photos

On the ‘net: Looking at Openflow

Openflow is the “father of software defined networks” in the minds of many engineers. To understand Openflow, however, you cannot just look at the protocol itself; rather you must go back to the beginning, in the mists of old networking. It is important to start here: in the “old days,” when I was still taking network cases in the routing protocols team at a major vendor, when we wanted to understand how routing worked, we looked at the code. What is the point? Networking has always been about software control planes. So networks have always been built on software; hence the “software” in software defined networking (SDN) cannot have ever meant “building control planes in software,” because that is the way it has always been done. —ECI

Related

Posted in ON THE NET
← IPv6, DHCP, and Unintended ConsequencesGreen Doors →
© 2023 rule 11 reader | Powered by Beaver Builder
Scroll To Top