This is the talk for the European Workshop on Software Defined Networks. It describes the implementation of OpenFlow 1.0 on a Gigabit Ethernet Passive Optical Network. The work describes a generic approach that should work on a number of different access technologies to make them OpenFlow ready. In specific, the work give details on what would be necessary to port the approach used to a new access device.
Software Defined Networking
Software defined networking
This talk describes my work in making an access device (Gigabit Ethernet Passive Optical Network) OpenFlow enabled. This is done via a proxy which uses VLAN tagging. The software is public source and available https://github.com/richardclegg/xcpd. This software should be adaptable to work with any access device of similar specification.
This paper reflects on experience gained from implementing OpenFlow on an access device. The architecture used involves a box at the front of the device for tagging traffic and using those tags to make the device present as a single large OpenFlow switch distributed in space. The system has been implemented and tested using OFtest.
Code is at https://github.com/richardclegg/xcpd
Presentation to International Workshop for Trends in Future Communications, Campinas, Brazil http://futurenets.cpqd.com.br/
This presentation talks about UCL's work on Software defined networking (specifically OpenFlow) and, in particular, adding OpenFlow capabilities to GEPON (Gigabit Ethernet Passive Optical Networking) devices.
This paper is a development of the earlier ideas in PREFLEX -- http://www.richardclegg.org/node/18
In this case the focus is resilience within a data centre. In particular resilience at the network layer. If several paths are available to a destination the system known as INFLEX can support fail over between paths seamlessly using OpenFlow. In this case the system is tested using Openvswitch.
This paper describes Information Centric Networks over Software Defined Networks. Applications are
Traffic engineering in ICN
Content based firewall
Network wide cache management
Per-flow granularity not sufficient for content based routing. Some routing can be done based on content length. Meta-data is extracted from ICN interest and data packets. This can be via
Network layer extraction of content length – classified into mouse/ elephant.