Author(s):	Deepa Dhurka
Location	OGGB3
Date	jan Thu 15	Days Raw Files
Start	10:40	First Raw Start	10:32
Duration	0:45:00	Offset	0:07:43
End	11:25	Last Raw End	11:28
Chapters	00:00 0:32:03
Total cuts_time	45 min.

http://lca2015.linux.org.au/schedule/30182/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf OFconnect_An_OpenFlow_Software_Defined_Networking_Library_For_Everyone.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Presented by Deepa Karnad Dhurka with Ramya Bolla Software Defined Network (SDN) architecture has two basic elements in its simplest design - (one) controller and (many) switches. The controller is centralized and has a complete view of the network of switches. It processes control plane decisions/policies and installs forwarding rules in each switch. The switches process traffic by applying these forwarding rules. Any unknown traffic is either sent to the controller for creation of new rules or is dropped - and this too can be programmed by the controller. The switches are connected to the controller in a “hub and spoke” topology. They talk to the controller over IP, using various transport protocols such as UDP, TCP, and TLS. OpenFlow, an SDN protocol has a Channel specification for these devices to communicate. What if all of this communication was handled by a shared library? This would allow the designers of controllers and switches to focus on the data - the topology, the packets, the flows - and the programmability of it all. OFconnect is an open source library created by CodeChix.org that handles network connectivity of controllers and switches. The current support includes IPv4 with TCP transport and has been integrated successfully with a controller (mul). In this talk, I will show the basic design and architecture of the library and how you can build a controller or switch around it. Additionally, I will share how you can contribute to the library by adding a transport protocol and greater OpenFlow protocol awareness. markdown
Comment:	production notes