Software:Nox (platform): Difference between revisions

From HandWiki
(import)
 
No edit summary
 
Line 1: Line 1:
<!-- Please do not remove or change this AfD message until the discussion has been closed. -->
{{Article for deletion/dated|page=Nox (platform)|timestamp=20240704193043|year=2024|month=July|day=4|substed=yes|help=off}}
<!-- Once discussion is closed, please place on talk page: {{Old AfD multi|page=Nox (platform)|date=4 July 2024|result='''keep'''}} -->
<!-- End of AfD message, feel free to edit beyond this point -->
{{multiple issues|
{{third-party|date=May 2015}}
}}
'''NOX''' is a piece of the [[Software-defined networking|software-defined networking]] (SDN) ecosystem. Specifically, it's a platform for building network control applications.
'''NOX''' is a piece of the [[Software-defined networking|software-defined networking]] (SDN) ecosystem. Specifically, it's a platform for building network control applications.



Latest revision as of 18:28, 10 July 2024

NOX is a piece of the software-defined networking (SDN) ecosystem. Specifically, it's a platform for building network control applications.

The first SDN technology to get real name recognition was OpenFlow, and NOX was initially developed at Nicira Networks side by side with OpenFlow — NOX was the first OpenFlow controller. Nicira donated NOX to the research community in 2008, and since then, it has been the basis for many and various research projects in the early exploration of the SDN space.

NOX offers C++ OpenFlow 1.0 API for developers and supports fast, asynchronous IO operations. Primarily intended for use on Linux distributions, NOX includes several sample components such as topology discovery, learning switch and network-wide switch functionalities. These components assist developers in building and managing software-defined networks.

Further reading

  • Gude, Natasha; Koponen, Teemu; Pettit, Justin; Pfaff, Ben; Casado, Martín; McKeown, Nick; Shenker, Scott (2008). "NOX: towards an operating system for networks". ACM SIGCOMM Computer Communication Review 38 (3): 105–110. doi:10.1145/1384609.1384625. 

External links