Design and Development of the Reactive BGP peering in Software-Defined Routing Exchanges

The Software-Defined Networking (SDN) is considered to be an improved solution for applying flexible control and operation recently in the network. Its characteristics include centralized management, global view, as well as fast adjustment and adaptation. Many experimental and research networks have already migrated to the SDN-enabled architecture. As the global network continues to grow in a fast pace, how to use SDN to improve the networking fields becomes a popular topic in research. One of the interesting topics is to enable routing exchanges among the SDN-enabled network and production networks. However, considering that many production networks are still operated on legacy architecture, the enabled SDN routing functionalities have to support hybrid mode in operation. In this paper, we propose a routing exchange mechanism by enabling reactive BGP peering actions among the SDN and legacy network components. The results of experiments show that our SDN controller is able to mask as an Autonomous System (AS) to exchange routing information with other BGP routers

Design and Implementation of Monitoring Schemes for Software-Defined Routing over a Federated Multi-domain SDN Testbed

Emerging Software-Defined Networking (SDN) paradigm has been widely affecting most networking fields. However, the real-world SDN application for inter-domain routing management is still limited since the routing exchange among wide-area networks is quite complicate due to the extreme scale of global Internet connectivity. Several SDN-leveraged routing ideas are being proposed to improve the routing exchange among wide-area networks. Thus, in this paper, an on-going experience for experimenting and validating the inter-domain routing proposals over OF@TEIN federated testbed in Asia is shared. By focusing on the design and implementation of monitoring deployment for visibility support, we try to identify practical key points and provide improved monitoring for validating the performance and anomaly of the exchange. Other design considerations are also discussed together with possible future research directions

Internet Evolution:Critical Issues

The Internet has been gradually evolving since its inception. In this paper, we highlight the important factors that have driven this evolution, and describe how the Internet is still struggling with several critical issues that need to be solved to meet predicted requirements of future applications. We discuss possible approaches and solutions, bearing in mind the considerable inertia of the Internet’s key architectural features

On the importance of Internet eXchange Points for today's Internet ecosystem

Internet eXchange Points (IXPs) are generally considered to be the successors of the four Network Access Points that were mandated as part of the decommissioning of the NSFNET in 1994/95 to facilitate the transition from the NSFNET to the "public Internet" as we know it today. While this popular view does not tell the whole story behind the early beginnings of IXPs, what is true is that since around 1994, the number of operational IXPs worldwide has grown to more than 300 (as of May 2013), with the largest IXPs handling daily traffic volumes comparable to those carried by the largest Tier-1 ISPs, but IXPs have never really attracted any attention from the networking research community. At first glance, this lack of interest seems understandable as IXPs have apparently little to do with current "hot" topic areas such as data centers and cloud services or software defined networking (SDN) and mobile communication. However, we argue in this article that, in fact, IXPs are all about data centers and cloud services and even SDN and mobile communication and should be of great interest to networking researchers interested in understanding the current and future Internet ecosystem. To this end, we survey the existing but largely unknown sources of publicly available information about IXPs to describe their basic technical and operational aspects and highlight the critical differences among the various IXPs in the different regions of the world, especially in Europe and North America. More importantly, we illustrate the important role that IXPs play in today's Internet ecosystem and discuss how IXP-driven innovation in Europe is shaping and redefining the Internet marketplace, not only in Europe but increasingly so around the world.Comment: 10 pages, keywords: Internet Exchange Point, Internet Architecture, Peering, Content Deliver

Evaluación comparativa del rendimiento de controladores SDN de código abierto

Software-defined Networking (SDN) constitutes a new era in the development of internetworking. The SDN paradigm splits the data plane from the control plane. It uses controller equipment, which is responsible for centrally managing several network devices simultaneously. This study analyzes three open-source controllers for SDN based on the OpenFlow protocol. Specifically, the performance of FloodLight, OpenDayLight (ODL), and Ryu controllers is evaluated in terms of latency, throughput, and scalability. In doing so, the Cbench tool is used in an emulated environment with Mininet. The results show that the Ryu controller presents the lowest performance in all the evaluated parameters; ODL provides lower latency and FloodLight higher throughput. Regarding scalability, we conclude that Floodlight can be used in small networks, whereas ODL can be used in dense networks. Furthermore, we evaluate their main characteristics, which must be considered for their choice prior to implementation and deployment.Las redes definidas por software (SDN) constituyen una nueva era en el diseño de la interconexión de redes. El paradigma SDN separa el plano de datos del plano de control. Para esto utiliza un equipo controlador, que se encarga de gestionar de forma centralizada varios dispositivos de red al mismo tiempo. Este estudio analiza tres controladores SDN de código abierto basados en el protocol OpenFlow. Específicamente, el rendimiento de los controladores FloodLight, OpenDayLight (ODL) y Ryu son evaluados en términos de latencia, throughput y escalabilidad. Para ello se utilizó la herramienta Cbench en un entorno emulado con Mininet. Los resultados muestran que el controlador presenta un menor rendimiento en todos los parámetros evaluados; ODL tiene una menor latencia y Floodlight un mayor throughput. En lo que tiene que ver a escalabilidad, se concluye que Floodlight es recomendable para redes pequeñas y ODL para redes densas. Además, evaluamos sus principales características, las cuales deben ser tomadas en cuenta para su elección antes de su implementación y despliegue