One way to provide more flexibility for computer networks is through software defined networks (SDN). This paradigm supports network applications, whose behavior is defined by the controllers. However, management applications SDN is a solution under explored, such applications are scattered in various repositories codes on-line, or are still embedded in the factory switches. This article proposes a model of organization and distribution of applications, called SDNrepo, may specify and model all the way that applications must do to reach the end user, in this case the controllers.

This paper describes the experience of RNP, the Brazilian research and education network, in creating a large scale research facility for experimentation on Future Internet as a member of the FIBRE (Future Internet testbeds experimentation between BRazil and Europe) project. Its main goal is to create common space between Brazil and EU for Future Internet experimental research into network infrastructure and distributed applications, by building and operating a federated EU-Brazil Future Internet experimental facility. The FIBRE testbed is currently composed by a federation of 13 local testbeds (a.k.a. experimental islands), located in different R&E organizations. The FIBRE infrastructure combines heterogeneous physical resources and different technologies, including OpenFlow, wireless and optical communications. We also present the architecture of FIBRE, which allows users to access the testbed through an integrated interface for either experimental or control planes, and provides a common access to the different underlying Control and Monitoring Frameworks (CMFs) for Future Internet experimentation

The Future Internet approach requires new solutions to support novel usage scenarios driven by the technological evolution and the new service demands. However, this paradigm shift requires deeper changes in the existing systems, which makes Internet providers reluctant in deploying the full transformation required for the Future Internet. The Entity Title Architecture (ETArch) is a holistic clean-slate Future Internet system embedding new services for these scenarios leveraging the Software Defined Networking (SDN) concept materialized by the OpenFlow. However, legacy ETArch deploys a fully per-flow approach to provision the same transport model for all sessions (equivalent to the Internet best-effort), while suffering with performance drawbacks and lacking Quality of Service (QoS) control. To that, we evolved ETArch with SMART (Support of Mobile Sessions with High Transport Network Resource Demand) QoS control approach, which coordinates admission control and dynamic control of super-dimensioned resources to accommodate multimedia sessions with QoS-guaranteed over time, while keeping scalability/performance and users with full Quality of Experience (QoE). The SMART-enabled ETArch system evaluation was carried out using a real Testbed of the OFELIA Brazilian Island, confirming its benefits in both data and control planes over the legacy ETArch.

Software Defined Networking (SDN) has emerged as a new paradigm that highly increase the network management flexibility through simple but powerful abstractions. The key idea is decoupling the control plane, which makes the forward decisions, from the data plane, which effectively makes the forward. However, the OpenFlow, the main SDN enabler, is designed mainly by wired networks characteristics. As consequence, Wireless Mesh Networks (WMNs) is not suitable for operating as control plane and many wireless networks features are neglected in the OpenFlow, e.g.: power control and network ID. In addition, there are few effort research to extend SDN to wireless networks and these existing works focus on very specific issues of this integration. In this paper, we propose an architecture to extent the OpenFlow functionalities in order to proper deal with wireless networks, including an approach for transporting the control plane over wireless multihop networks. The extensions include new rules, actions, and commands, which bring the network management flexibility to the wireless context. We validated our proposal by implementing and testing some extensions in a small real world testbed. As a proof of concept, we illustrate the OpenFlow capability of isolation between research and production traffics in a wireless backhaul.

. On the context of OpenFlow networks, the FlowVisor has emerged as a tool to enable the network virtualization, creating an environment for running multiple concurrent and independent experiments. However, this solution still has some limitations, such as the definition of mechanisms to allocate resources to different virtual networks. Although newer versions of the tool allow the queue assignment network slice, to provide resource control among them, device configurations are on the dependency of external tools. Therefore, this article aims to propose a solution to extend the FlowVisor functionality, creating a structure to allow traffic control configuration parameters in the network device, to ensure resource isolation and interference mitigation between the different virtual networks.

Packet scheduling is essential to properly support applications on Software-Defined Networking (SDN) model. However, on OpenFlow/SDN, QoS is only performed with bandwidth guarantees and by a well-known FIFO scheduling. Facing this limitation, this paper presents the QoSFlow proposal, which controls multiple packet schedulers of Linux kernel and improve the flexibility of QoS control. The paper assesses QoSFlow performance, by analysing response time of packet scheduler operations running on datapath level, maximum bandwidth capacity, hardware resource utilization rate, bandwidth isolation and QoE. Our outcomes show an increase more than 48% on PSNR value of QoE by using SFQ scheduling.

The increase in complexity of computer networks and their services have boosted the development of standardizations, models, and solutions for network management over the years. Lately, the Distributed Management Task Force (DMTF) defined the Common Information Model (CIM) for describing computational entities and businesses on the Internet. This paper proposes an extension of the CIM for Software-Defined Networking (SDN) by adding new elements (Controllers, Apps, Slices and others) to improve the system management performance. Furthermore, we define a metamodel to help the process of creating and understanding the proposed model. The proposal was validated by creating a script that generates the FlowVisor configuration file using the network model as input and using Object Constraint Language (OCL) to find inconsistencies in the network.

Currently, there is a philosophical problem that arises between the real need for current support to OpenFlow and legacy network infrastructure. Among them, the legacy networking has not been compatible with OpenFlow network, and for that, it needs to be replaced or a few cases upgraded, as a consequence there are additional spending with new equipment OpenFlow-based. This paper introduces a proposal of hybrid SDN solution based on OpenFlow protocol and called of LegacyFlow, which is able to control Legacy equipment (non-OpenFlow) through OpenFlow protocol 1.0. Results show that it is possible used the LegacyFlow together with OpenFlow switches keeping a good performance time with OpenFlow application.

The OpenFlow technology enables the creation of a programmable layer over the control-plane of a network, in this way dictating the data-plane forwarding behaviour through the use of applications plugged to a network controller. Dynamic Circuit Network is an architecture that permits the scheduling of network resources on virtual circuits, such as bandwidth, over multiple domains with heterogeneous technologies. Recently, researches were conducted in order to integrate both technologies so that dynamic circuits can be dynamically provisioned over OpenFlow domains. The objective of this work is to propose an architecture that enables such provision, maintaining the QoS requisites of a DCN architecture.

The Future Internet will arise from the convergence of new network concepts and combine technologies, services, media and content. It will offer flexibility and diversity with scalable content and services that are accessible through a wide range of interfaces and devices. However, the biggest challenge now is how to enable and test the proposed approaches so that they can be validated without sacrificing the current production infrastructure. The OpenFlow protocol allows production networking environments such as campus networks, metropolitan networks or R&D networks, to be used as experimental infrastructure hosting, future Internet architectures, software and protocols, in parallel with the production traffic. During rollout, there is a practical problem that arises with Legacy networks that do not support OpenFlow and need to be replaced/upgraded or refined by means of costly network re-engineering. This paper proposes a new OpenFlow architecture with new components, capable of managing Legacynon-OpenFlow elements by offering a new solution that facilitates the management of Legacy technologies and allows them to be employed in FI experimentation environment and increase the number of experiment with the Legacy Network Environment using OpenFlow control.

Nos últimos anos houve expressivo esforço em prol de soluções de mobilidade para redes sem fio tradicionais, tais como redes de celulares e IEEE 802.11. Outro tipo de rede sem fio que vem se destacando mais recentemente são as redes de múltiplos saltos. Porém a questão da mobilidade neste tipo de rede não é uma simples extensão das redes sem fio tradicionais. Assim, são necessárias soluções específicas de mobilidade que atendam os requisitos dessas novas redes. Visando este objetivo, o presente trabalho propõe uma adaptação ao DHCP, voltado para redes sem fio de múltiplos saltos. A proposta agrega inteligência ao agente DHCP relay, tornando-o capaz de acelerar o processo de configuração de endereço IP aos clientes móveis durante o handoff.

Os tradicionais sistemas de prevenção de intrusão (Intrusion Prevention Systems–IPS) possuem limitações em sua atuação. Quando operam no modo ativo, não possuem uma ampla cobertura na rede, e quando capturam tráfego espelhado, só bloqueiam o tráfego malicioso se atuarem em conjunto com equipamentos de rede do mesmo fabricante ou solução. Neste contexto, propomos neste artigo o IPSFlow, um framework de IPS para Redes Definidas por Software (Software Defined Networks-SDN) que, através do protocolo Openflow, possibilita a criação de um IPS com ampla cobertura na rede, permitindo a captura seletiva e o bloqueio automatizado de tráfego malicioso o mais próximo de sua origem, através da combinação dos resultados de diferentes técnicas de análise de tráfego.

The OpenFlow protocol allows production networking environments such as campus networks, metropolitan networks or R&D networks, to be used as experimental infrastructure hosting, future internet architectures, softwares and protocols, in isolation to the production traffic. During rollout, one practical problem arises with legacy switches that do not support the OpenFlow protocol and need to be replaced/upgraded or worked around by means of costly network re-engineering. This poster proposes a new OpenFlow datapath, which is able to interact with non OpenFlow legacy equipment, creating a new approach to hybrid OpenFlow networks.

A Internet é um enorme sucesso mundial e vem mudando a forma como interagimos, trabalhamos e nos divertimos. Boa parte deste sucesso se deve à grande flexibilidade da tecnologia IP. Apesar de todo o sucesso da Internet, a tecnologia básica IP é a causa das suas próprias limitações que se tornam cada vez mais evidentes. Um dos principais objetivos da atividade conhecida como Internet do Futuro (IF) é a formulação e avaliação de arquiteturas alternativas para substituir o protocolo IP. Nesse contexto, duas abordagens estão sendo discutidas e investigadas: a primeira denominada limpa (Clean Slate), que visa substituir a arquitetura atual por uma nova totalmente reconstruída, e a outra chamada evolucionária (Evolutionary) que pretende evoluir a arquitetura atual sem perder a compatibilidade com a anterior.