Design and Implementation of ForCES Protocol

[EN] This paper proposes the design and implementation of the ForCES protocol, specifically FP logical point of the ForCES architecture, which is strictly the communication between the CE (Control Element) and the FE (Forwarding Element). It is a flexible and reprogrammable architecture that is established within the specifications issued and defined by the ForCES working group, and consists of elaboration of a protocol that carries information between both elements. In order to comprobate the correct functioning of the implemented the ForCES protocol, is we provide a network testbed scenario, which consist an application client-server. Each device has equipped with the application which based on Java language, that allows the researcher to be able to compare the typical functionality of a conventional router with a router based in architecture ForCES. It allows taking advantage of the benefits of this architecture to reprogram different and new functionalities.Gonzalez Ramirez, PL.; Lloret, J.; Martínez Cordero, S.; Trujillo Arboleda, LC. (2017). Design and Implementation of ForCES Protocol. Network Protocols and Algorithms. 9(1-2):1-27. https://doi.org/10.5296/npa.v9i1-2.10943S12791-

Design and implementation of a prototype of the entity Control Element (CE) of the Architecture ForCES

[EN] This paper presents the designed an implementation of a prototype with the Forwarding and Control Element Separation (ForCES) Architecture. That is to say, which allows each of the elements to be improved separately and then interconnected through the ForCES protocol, even in remote locations. The Control Element (CE) is the logical entity that is part of the control plane and is responsible for managing Forwarding Elements (FE) of the data plane. The ForCES architecture allows you to see these two elements (the CE and the FE through the ForCES protocol) as a single Network Element (NE), even if they are located in remote sites each. To demonstrate this principle, a network testbed scenario was implemented, based on two Local Area Networks (LAN). The LAN 1, for the CEs and the LAN 2 for the FEs, once communicated through the ForCES protocol, the different LFBs configurations of the ARP, SNMP, RIP protocols were used to demonstrate their operation.Martínez Cordero, S.; Gonzalez Ramirez, PL.; Lloret, J.; Trujillo Arboleda, LC. (2017). Design and implementation of a prototype of the entity Control Element (CE) of the Architecture ForCES. Network Protocols and Algorithms. 9(3-4):1-30. https://doi.org/10.5296/npa.v9i3-4.12433S13093-

Physics-Based Swarm Intelligence for Disaster Relief Communications

This study explores how a swarm of aerial mobile vehicles can provide network connectivity and meet the stringent requirements of public protection and disaster relief operations. In this context, we design a physics-based controlled mobility strategy, which we name the extended Virtual Force Protocol (VFPe), allowing self-propelled nodes, and in particular here unmanned aerial vehicles, to fly autonomously and cooperatively. In this way, ground devices scattered on the operation site may establish communications through the wireless multi-hop communication routes formed by the network of aerial nodes. We further investigate through simulations the behavior of the VFPe protocol, notably focusing on the way node location information is disseminated into the network as well as on the impact of the number of exploration nodes on the overall network performance.Comment: in International Conference on Ad Hoc Networks and Wireless, Jul 2016, Lille, Franc

A Survey on the Contributions of Software-Defined Networking to Traffic Engineering

Since the appearance of OpenFlow back in 2008, software-defined networking (SDN) has gained momentum. Although there are some discrepancies between the standards developing organizations working with SDN about what SDN is and how it is defined, they all outline traffic engineering (TE) as a key application. One of the most common objectives of TE is the congestion minimization, where techniques such as traffic splitting among multiple paths or advanced reservation systems are used. In such a scenario, this manuscript surveys the role of a comprehensive list of SDN protocols in TE solutions, in order to assess how these protocols can benefit TE. The SDN protocols have been categorized using the SDN architecture proposed by the open networking foundation, which differentiates among data-controller plane interfaces, application-controller plane interfaces, and management interfaces, in order to state how the interface type in which they operate influences TE. In addition, the impact of the SDN protocols on TE has been evaluated by comparing them with the path computation element (PCE)-based architecture. The PCE-based architecture has been selected to measure the impact of SDN on TE because it is the most novel TE architecture until the date, and because it already defines a set of metrics to measure the performance of TE solutions. We conclude that using the three types of interfaces simultaneously will result in more powerful and enhanced TE solutions, since they benefit TE in complementary ways.European Commission through the Horizon 2020 Research and Innovation Programme (GN4) under Grant 691567 Spanish Ministry of Economy and Competitiveness under the Secure Deployment of Services Over SDN and NFV-based Networks Project S&NSEC under Grant TEC2013-47960-C4-3-

Advanced Message Routing for Scalable Distributed Simulations

The Joint Forces Command (JFCOM) Experimentation Directorate (J9)'s recent Joint Urban Operations (JUO) experiments have demonstrated the viability of Forces Modeling and Simulation in a distributed environment. The JSAF application suite, combined with the RTI-s communications system, provides the ability to run distributed simulations with sites located across the United States, from Norfolk, Virginia to Maui, Hawaii. Interest-aware routers are essential for communications in the large, distributed environments, and the current RTI-s framework provides such routers connected in a straightforward tree topology. This approach is successful for small to medium sized simulations, but faces a number of significant limitations for very large simulations over high-latency, wide area networks. In particular, traffic is forced through a single site, drastically increasing distances messages must travel to sites not near the top of the tree. Aggregate bandwidth is limited to the bandwidth of the site hosting the top router, and failures in the upper levels of the router tree can result in widespread communications losses throughout the system. To resolve these issues, this work extends the RTI-s software router infrastructure to accommodate more sophisticated, general router topologies, including both the existing tree framework and a new generalization of the fully connected mesh topologies used in the SF Express ModSAF simulations of 100K fully interacting vehicles. The new software router objects incorporate the scalable features of the SF Express design, while optionally using low-level RTI-s objects to perform actual site-to-site communications. The (substantial) limitations of the original mesh router formalism have been eliminated, allowing fully dynamic operations. The mesh topology capabilities allow aggregate bandwidth and site-to-site latencies to match actual network performance. The heavy resource load at the root node can now be distributed across routers at the participating sites

Time4: Time for SDN

With the rise of Software Defined Networks (SDN), there is growing interest in dynamic and centralized traffic engineering, where decisions about forwarding paths are taken dynamically from a network-wide perspective. Frequent path reconfiguration can significantly improve the network performance, but should be handled with care, so as to minimize disruptions that may occur during network updates. In this paper we introduce Time4, an approach that uses accurate time to coordinate network updates. Time4 is a powerful tool in softwarized environments, that can be used for various network update scenarios. Specifically, we characterize a set of update scenarios called flow swaps, for which Time4 is the optimal update approach, yielding less packet loss than existing update approaches. We define the lossless flow allocation problem, and formally show that in environments with frequent path allocation, scenarios that require simultaneous changes at multiple network devices are inevitable. We present the design, implementation, and evaluation of a Time4-enabled OpenFlow prototype. The prototype is publicly available as open source. Our work includes an extension to the OpenFlow protocol that has been adopted by the Open Networking Foundation (ONF), and is now included in OpenFlow 1.5. Our experimental results show the significant advantages of Time4 compared to other network update approaches, and demonstrate an SDN use case that is infeasible without Time4.Comment: This report is an extended version of "Software Defined Networks: It's About Time", which was accepted to IEEE INFOCOM 2016. A preliminary version of this report was published in arXiv in May, 201