98:(SDN), manages the OpenFlow standard. ONF defines OpenFlow as the first standard communications interface defined between the control and forwarding layers of an SDN architecture. OpenFlow allows direct access to and manipulation of the forwarding plane of network devices such as switches and routers, both physical and virtual (hypervisor-based). It is the absence of an open interface to the forwarding plane that has led to the characterization of today's networking devices as monolithic, closed, and mainframe-like. A protocol like OpenFlow is needed to move network control out of proprietary network switches and into control software that's open source and locally managed.
67:
forwarded to the controller. The controller can then decide to modify existing flow table rules on one or more switches or to deploy new rules, to prevent a structural flow of traffic between switch and controller. It could even decide to forward the traffic itself, provided that it has told the switch to forward entire packets instead of just their header.
121:
Version 1.1 of the OpenFlow protocol was released on 28 February 2011, and new development of the standard was managed by the ONF. In
December 2011, the ONF board approved OpenFlow version 1.2 and published it in February 2012. The current version of OpenFlow is 1.5.1. However, version 1.6 has been
66:
by the controller and translated into rules and actions with a configurable lifespan, which are then deployed to a switch's flow table, leaving the actual forwarding of matched packets to the switch at wire speed for the duration of those rules. Packets which are unmatched by the switch can be
46:
OpenFlow enables network controllers to determine the path of network packets across a network of switches. The controllers are distinct from the switches. This separation of the control from the forwarding allows for more sophisticated traffic management than is feasible using
51:(ACLs) and routing protocols. Also, OpenFlow allows switches from different vendors — often each with their own proprietary interfaces and scripting languages — to be managed remotely using a single, open protocol. The protocol's inventors consider OpenFlow an enabler of
164:
OpenFlow
Controller, and announced its OpenFlow-based SDN Suite in November of that year, which contains a commercial controller, and virtual switching and tap monitoring applications.
78:(TLS). Controllers should listen on TCP port 6653 for switches that want to set up a connection. Earlier versions of the OpenFlow protocol unofficially used port 6633. Some network
143:
in May 2011 launched a SDN Interoperability Lab in conjunction with the ONF to test how well different vendors' software-defined networking and OpenFlow products work together.
182:
described how the company's internal network had been completely re-designed over the previous two years to run under OpenFlow with substantial efficiency improvement.
925:
62:
switch's packet forwarding tables, by adding, modifying and removing packet matching rules and actions. This way, routing decisions can be made periodically or
133:
announced the availability of an OpenFlow-enabled, fully featured switching solution based on
Marvell's networking control stack and the Prestera family of
612:
82:
implementations use the protocol to manage the network forwarding elements. OpenFlow is mainly used between the switch and controller on a secure channel.
806:
524:
371:
252:
556:
870:
738:
963:
1004:
785:
757:
101:
A number of network switch and router vendors announced intent to support or are shipping supported switches for OpenFlow, including
203:, which is designed to bring OpenFlow-based software-defined networking and network virtualisation to those Microsoft environments.
807:"HP takes giant first step into OpenFlow: HP is announcing its first effort to support OpenFlow standard on its Ethernet switches"
482:
317:
588:
71:
938:
790:
95:
52:
1070:
643:
635:
620:
593:
466:
446:
302:
91:
294:
905:
663:
220:
215:
126:
75:
816:
534:
983:
Natarajan, Sriram; et al. (2013). "A Software defined Cloud-Gateway automation system using OpenFlow".
23:
842:
714:
566:
106:
880:
525:"Brocade Leads OpenFlow Adoption to Accelerate Network Virtualization and Cloud Application Development"
419:
154:
79:
871:"NEC rolls out OpenFlow for Microsoft Hyper-V: NEC virtual switch adds IPv6 support to SDN controller"
461:
161:
658:
194:
48:
1022:
1010:
388:
269:
140:
35:
503:
228:
Programming and
Communication Channel Issues (w.r.t. security) - OpenFlow Deployment Experience
1000:
134:
992:
847:
508:
380:
261:
27:
441:
1034:
487:
1053:
366:
247:
691:
158:
130:
102:
31:
150:
released LINC, an open-source OpenFlow version 1.2 and 1.3 compliant software switch.
1064:
875:
811:
338:
179:
168:
1014:
910:
392:
273:
996:
414:
933:
838:
598:
968:
200:
843:"Going With the Flow: Google's Secret Switch to the Next Wave of Networking"
384:
265:
190:
339:"Onix: A Distributed Control Platform for Large-scale Production Networks"
171:
said it is supporting the standard on 16 of its
Ethernet switch products.
762:
147:
561:
529:
197:
110:
59:
122:
available since
September 2016, but accessible only to ONF's members.
94:(ONF), a user-led organization dedicated to promotion and adoption of
719:
343:
175:
964:"OpenFlow security: Does OpenFlow secure software-defined networks?"
686:
985:
2013 IEEE 2nd
International Conference on Cloud Networking (Cloud
322:
724:
462:"Software-Defined Networking (SDN): The New Norm for Networks"
186:
906:"OpenFlow protocol has a switch authentication vulnerability"
504:"You Can't Have Google's Pluto Switch, But You Can Have This"
318:"Service Name and Transport Protocol Port Number Registry"
758:"Big Switch releases open source controller for OpenFlow"
16:
Computer network protocol for software-defined networking
483:"Alcatel Now Supports OpenFlow, OpenStack on Switches"
786:"Big Switch Emerges with Commercial SDN Portfolio"
367:"OpenFlow: Enabling innovation in campus networks"
248:"OpenFlow: Enabling innovation in campus networks"
900:
898:
153:In February 2012, Big Switch Networks released
70:The OpenFlow protocol is layered on top of the
659:"Marvell Introduces OpenFlow-enabled Switches"
337:Koponen, Teemu; et al. (4 October 2010).
8:
225:Potential single point of attack and failure
58:OpenFlow allows remote administration of a
589:"Open Networking Foundation Press Release"
784:Kerner, Sean Michael (13 November 2012).
442:"Open Networking Foundation: SDN Defined"
372:ACM SIGCOMM Computer Communication Review
365:McKeown, Nick; et al. (April 2008).
253:ACM SIGCOMM Computer Communication Review
246:McKeown, Nick; et al. (April 2008).
557:"FlowEngine:Intelligent Flow Management"
238:
1030:
1020:
687:"OpenFlow – Innovate in Your Network"
7:
715:"SDN Interoperability Lab - InCNTRE"
481:Solomon, Howard (11 December 2013).
926:"OpenFlow Vulnerability Assessment"
415:"TR10: Software-Defined Networking"
295:"OpenFlow Switch Errata v1.0.2-rc1"
565:. 20 February 2016. Archived from
14:
805:Neagle, Colin (2 February 2012).
756:Cole, Bernard (2 February 2012).
413:Greene, Kate (March–April 2009).
74:(TCP) and prescribes the use of
597:. 20 March 2011. Archived from
869:Duffy, Jim (22 January 2013).
523:Radda, Pavel (22 March 2011).
189:unveiled a virtual switch for
1:
997:10.1109/CloudNet.2013.6710582
723:. 5 June 2012. Archived from
72:Transmission Control Protocol
791:Enterprise Networking Planet
502:Metz, Cade (26 March 2013).
96:software-defined networking
53:software-defined networking
1087:
644:Open Networking Foundation
621:Open Networking Foundation
594:Open Networking Foundation
467:Open Networking Foundation
447:Open Networking Foundation
303:Open Networking Foundation
92:Open Networking Foundation
26:that gives access to the
221:Man-in-the middle attack
76:Transport Layer Security
385:10.1145/1355734.1355746
266:10.1145/1355734.1355746
105:, Big Switch Networks,
24:communications protocol
107:Brocade Communications
420:MIT Technology Review
212:Covert communications
991:. pp. 219–226.
739:"Project Floodlight"
162:open-source software
49:access control lists
743:www.openflowhub.org
195:Windows Server 2012
537:on 4 November 2013
167:In February 2012,
155:Project Floodlight
141:Indiana University
38:over the network.
1071:Network protocols
1006:978-1-4799-0568-3
841:(17 April 2012).
636:"OpenFlow v1.5.1"
601:on 26 March 2011.
306:. 4 October 2013.
216:Denial of service
207:Security concerns
185:In January 2013,
135:packet processors
1078:
1057:
1056:
1054:Official website
1039:
1038:
1032:
1028:
1026:
1018:
980:
974:
973:
960:
954:
953:
951:
949:
943:
937:. Archived from
930:
922:
916:
915:
902:
893:
892:
890:
888:
879:. Archived from
866:
860:
859:
857:
855:
835:
829:
828:
826:
824:
815:. Archived from
802:
796:
795:
781:
775:
774:
772:
770:
753:
747:
746:
735:
729:
728:
711:
705:
704:
702:
700:
683:
677:
676:
674:
672:
655:
649:
648:
640:
632:
626:
625:
617:
609:
603:
602:
585:
579:
578:
576:
574:
569:on 16 April 2016
553:
547:
546:
544:
542:
533:. Archived from
520:
514:
513:
499:
493:
492:
478:
472:
471:
458:
452:
451:
450:. 23 March 2013.
438:
432:
431:
429:
427:
410:
404:
403:
401:
399:
362:
356:
355:
353:
351:
334:
328:
327:
314:
308:
307:
299:
291:
285:
284:
282:
280:
243:
28:forwarding plane
1086:
1085:
1081:
1080:
1079:
1077:
1076:
1075:
1061:
1060:
1052:
1051:
1048:
1043:
1042:
1029:
1019:
1007:
982:
981:
977:
962:
961:
957:
947:
945:
944:on 4 March 2016
941:
928:
924:
923:
919:
904:
903:
896:
886:
884:
883:on 3 April 2013
868:
867:
863:
853:
851:
837:
836:
832:
822:
820:
804:
803:
799:
783:
782:
778:
768:
766:
755:
754:
750:
737:
736:
732:
727:on 5 June 2012.
713:
712:
708:
698:
696:
685:
684:
680:
670:
668:
657:
656:
652:
638:
634:
633:
629:
615:
613:"OpenFlow v1.2"
611:
610:
606:
587:
586:
582:
572:
570:
555:
554:
550:
540:
538:
522:
521:
517:
501:
500:
496:
488:IT World Canada
480:
479:
475:
460:
459:
455:
440:
439:
435:
425:
423:
412:
411:
407:
397:
395:
364:
363:
359:
349:
347:
336:
335:
331:
316:
315:
311:
297:
293:
292:
288:
278:
276:
245:
244:
240:
235:
209:
174:In April 2012,
159:Apache-licensed
119:
88:
44:
17:
12:
11:
5:
1084:
1082:
1074:
1073:
1063:
1062:
1059:
1058:
1047:
1046:External links
1044:
1041:
1040:
1005:
975:
955:
917:
894:
861:
830:
819:on 13 May 2013
797:
776:
748:
730:
706:
692:Larch Networks
678:
650:
627:
604:
580:
548:
515:
494:
473:
453:
433:
405:
357:
329:
309:
286:
237:
236:
234:
231:
230:
229:
226:
223:
218:
213:
208:
205:
146:In June 2012,
131:Larch Networks
118:
115:
103:Alcatel-Lucent
87:
84:
43:
40:
32:network switch
15:
13:
10:
9:
6:
4:
3:
2:
1083:
1072:
1069:
1068:
1066:
1055:
1050:
1049:
1045:
1036:
1024:
1016:
1012:
1008:
1002:
998:
994:
990:
986:
979:
976:
971:
970:
965:
959:
956:
940:
936:
935:
927:
921:
918:
913:
912:
907:
901:
899:
895:
882:
878:
877:
876:Network World
872:
865:
862:
850:
849:
844:
840:
834:
831:
818:
814:
813:
812:Network World
808:
801:
798:
793:
792:
787:
780:
777:
765:
764:
759:
752:
749:
744:
740:
734:
731:
726:
722:
721:
716:
710:
707:
694:
693:
688:
682:
679:
667:. 10 May 2011
666:
665:
660:
654:
651:
646:
645:
637:
631:
628:
623:
622:
614:
608:
605:
600:
596:
595:
590:
584:
581:
568:
564:
563:
558:
552:
549:
536:
532:
531:
526:
519:
516:
511:
510:
505:
498:
495:
490:
489:
484:
477:
474:
469:
468:
463:
457:
454:
449:
448:
443:
437:
434:
422:
421:
416:
409:
406:
394:
390:
386:
382:
378:
374:
373:
368:
361:
358:
346:
345:
340:
333:
330:
325:
324:
319:
313:
310:
305:
304:
296:
290:
287:
275:
271:
267:
263:
259:
255:
254:
249:
242:
239:
232:
227:
224:
222:
219:
217:
214:
211:
210:
206:
204:
202:
199:
196:
192:
188:
183:
181:
177:
172:
170:
165:
163:
160:
156:
151:
149:
144:
142:
138:
136:
132:
128:
125:In May 2011,
123:
116:
114:
112:
108:
104:
99:
97:
93:
85:
83:
81:
80:control plane
77:
73:
68:
65:
61:
56:
54:
50:
41:
39:
37:
33:
29:
25:
21:
988:
984:
978:
967:
958:
946:. Retrieved
939:the original
932:
920:
911:The Register
909:
885:. Retrieved
881:the original
874:
864:
852:. Retrieved
846:
839:Levy, Steven
833:
821:. Retrieved
817:the original
810:
800:
789:
779:
767:. Retrieved
761:
751:
742:
733:
725:the original
718:
709:
697:. Retrieved
695:. 6 May 2011
690:
681:
669:. Retrieved
662:
653:
642:
630:
619:
607:
599:the original
592:
583:
571:. Retrieved
567:the original
560:
551:
539:. Retrieved
535:the original
528:
518:
507:
497:
486:
476:
465:
456:
445:
436:
424:. Retrieved
418:
408:
396:. Retrieved
379:(2): 69–74.
376:
370:
360:
348:. Retrieved
342:
332:
321:
312:
301:
289:
277:. Retrieved
260:(2): 69–74.
257:
251:
241:
184:
173:
166:
152:
145:
139:
124:
120:
100:
89:
69:
63:
57:
45:
19:
18:
1031:|work=
934:Indiana.edu
573:11 February
541:29 November
117:Development
42:Description
969:TechTarget
769:2 February
398:2 November
279:2 November
233:References
201:hypervisor
180:Urs Hölzle
1033:ignored (
1023:cite book
426:7 October
350:1 October
191:Microsoft
1065:Category
1015:16248079
887:28 April
854:17 April
823:28 April
763:EE Times
148:Infoblox
20:OpenFlow
948:23 June
699:28 June
671:28 June
664:Marvell
562:Radisys
530:Reuters
393:1153326
274:1153326
198:Hyper-V
127:Marvell
111:Radisys
86:History
60:layer 3
55:(SDN).
1013:
1003:
720:IU.edu
391:
344:USENIX
272:
176:Google
109:, and
64:ad hoc
36:router
1011:S2CID
942:(PDF)
929:(PDF)
848:Wired
639:(PDF)
616:(PDF)
509:Wired
389:S2CID
298:(PDF)
270:S2CID
157:, an
30:of a
22:is a
1035:help
1001:ISBN
950:2014
889:2013
856:2012
825:2013
771:2012
701:2015
673:2015
575:2016
543:2011
428:2011
400:2009
352:2010
323:IANA
281:2009
129:and
90:The
993:doi
987:Net
381:doi
262:doi
193:'s
187:NEC
178:'s
34:or
1067::
1027::
1025:}}
1021:{{
1009:.
999:.
966:.
931:.
908:.
897:^
873:.
845:.
809:.
788:.
760:.
741:.
717:.
689:.
661:.
641:.
618:.
591:.
559:.
527:.
506:.
485:.
464:.
444:.
417:.
387:.
377:38
375:.
369:.
341:.
320:.
300:.
268:.
258:38
256:.
250:.
169:HP
137:.
113:.
1037:)
1017:.
995::
989:)
972:.
952:.
914:.
891:.
858:.
827:.
794:.
773:.
745:.
703:.
675:.
647:.
624:.
577:.
545:.
512:.
491:.
470:.
430:.
402:.
383::
354:.
326:.
283:.
264::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.