![]() OpenFlow will be examined in detail in Chapter 5. It is also possible that the controller will program wildcard rules that will govern many flows at once. Typically the controller will update the switch with new flow entries as new packet patterns are received, so that the switch can deal with them locally. If no match is found, the switch forwards the packet to the controller for instructions on how to deal with the packet. Depending on the match criteria, this evaluation would begin with the layer two header, and then potentially continue to the layer three and even layer four headers in some cases. The switch evaluates the header(s) of incoming packets and finds a matching flow, then performs the associated action. The controller populates the switch with flow table entries. The following list describes the basic operation of an OpenFlow solution: Indeed, while the term SDN was in use in the research community as early as 2009, SDN did not begin to make a big impact in the broader networking industry until 2011. In reality, the term SDN did not come into use until a year after OpenFlow made its appearance on the scene in 2008, but the existence and adoption of OpenFlow by research communities and networking vendors marked a sea change in networking, one that we are still witnessing even now. Just as the previous sections presented standards and proposals which were precursors to SDN, seeing SDN through a gestation period, then the arrival of OpenFlow is the point at which SDN was actually born. OpenFlow is a protocol specification that describes the communication between OpenFlow switches and an OpenFlow controller. Timothy Culver, in Software Defined Networks (Second Edition), 2017 3.4.1 The Birth of OpenFlow Many network vendors have implemented OpenFlow in their products. The OpenFlow specification encouraged vendors to implement and enable OpenFlow in their switching products for deployment in college campus networks. ![]() Indeed, though the term SDN was in use in the research community as early as 2009, SDN did not begin to make a big impact in the broader networking industry until 2011.įor reasons identified in the previous chapter, OpenFlow was developed and designed to allow researchers to experiment and innovate with new protocols in everyday networks. Just as the previous sections presented standards and proposals that were precursors to SDN, seeing SDN through a gestation period, the arrival of OpenFlow is the point at which SDN was actually born. ![]() Paul Goransson, Chuck Black, in Software Defined Networks, 2014 3.3.1 The Birth of OpenFlow ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |