No file available
To read the file of this research,
you can request a copy directly from the authors.
SDN Architecture and Southbound APIs for IPv6 Segment Routing Enabled Wide Area Networks
Preprints and early-stage research may not have been peer reviewed yet.
Abstract
The SRv6 architecture (Segment Routing based on IPv6 data plane) is a promising solution to support services like Traffic Engineering, Service Function Chaining and Virtual Private Networks in IPv6 backbones and datacenters. The SRv6 architecture has interesting scalability properties as it reduces the amount of state information that needs to be configured in the nodes to support the network services. In this paper, we describe the advantages of complementing the SRv6 technology with an SDN based approach in backbone networks. We discuss the architecture of a SRv6 enabled network based on Linux nodes. In addition, we present the design and implementation of the Southbound API between the SDN controller and the SRv6 device. We have defined a data-model and four different implementations of the API, respectively based on gRPC, REST, NETCONF and remote Command Line Interface (CLI). Since it is important to support both the development and testing aspects we have realized an Intent based emulation system to build realistic and reproducible experiments. This collection of tools automate most of the configuration aspects relieving the experimenter from a significant effort. Finally, we have realized an evaluation of some performance aspects of our architecture and of the different variants of the Southbound APIs and we have analyzed the effects of the configuration updates in the SRv6 enabled nodes.
... More precisely, we propose an enhanced path computation function and we investigate how the integration of a fully centralized TSN control plane with segment routing can be realized. SDN assisted operations for Segment routing are also discussed in Ventre et al. 8 For enhanced reliability of TSN flows, frame replication and elimination according to 802.1CB can be used. On one hand, frame replication may increase the probability of successful reception; on the other hand it may lead to waste of bandwidth since duplicated flows are traversing the network. ...
... • SRv6 Manager: We consider a Linux-based SRv6-enabled device according to previous works. 8,43 The SRv6 manager is responsible for parsing SRv6 configuration information sent to the NETCONF server. Configuration information encompasses (i) path encapsulation in SRH according to YANG-based SRv6 models, translated into a suitable set of actions that tune the forwarding logic at the access devices (srv6-explicit-path YANG model) and (ii) mapping of segment IDs to functions (srv6-local-sid YANG model). ...
... Configuration information encompasses (i) path encapsulation in SRH according to YANG-based SRv6 models, translated into a suitable set of actions that tune the forwarding logic at the access devices (srv6-explicit-path YANG model) and (ii) mapping of segment IDs to functions (srv6-local-sid YANG model). In this work, both models are based on the ones presented in Ventre et al. 8 Our SRv6 Manager implementation internally relies on the iproute utility in order to apply the SIDs allocation (in all network devices), as well as the routing policy configuration (at the access devices). • TSN manager: It is responsible for parsing GCL configuration sent over the NETCONF interface, based on 802.1Qcw aligned YANG models, and for applying the corresponding set of actions that affect the queuing disc layer of the Linux kernel (TAPRIO). ...
Time‐Sensitive Networks (TSN) aims at providing a solid underpinning for the support of application connectivity demands across a wide spectrum of use cases and operational environments, such as industrial automation and automotive networks. However, handling network updates in TSN entails additional challenges, stemming from the need to perform both flow rerouting and TSN schedule reconfiguration. To address this issue, we propose a software‐defined network (SDN)‐based approach for low‐overhead TSN network updates, exploiting segment routing over IPv6 (SRv6) for path control. To this end, we introduce the concept of TSN subgraphs in order to quickly reschedule the flows traversing the problematic area and propose a TSN‐aware routing heuristic to minimize the convergence time. We further describe the control plane implementation and its integration into Mininet, which empowers us to conduct a wide range of performance tests. Our evaluation results indicate that our approach yields faster recovery and reduces significantly the number of required reconfigurations upon failures, at the expense of a small SRv6 encoding/decoding overhead. We propose a Software‐Defined Network (SDN)‐based approach for low‐overhead TSN network updates, exploiting Segment Routing over IPv6 (SRv6) for path control. Analysis of both control plane and data plane aspects is provided, and implementation experience is reported.
... The controller interacts with the network nodes using an API, which needs to be carefully designed. We decided to extend the SRv6 Southbound API proposed in [30], in order to allow full control of the SRv6 data plane and routing of a Linux node. In [30] the authors had prototyped, validated and compared three different implementations: gRPC, REST, NETCONF. ...
... We decided to extend the SRv6 Southbound API proposed in [30], in order to allow full control of the SRv6 data plane and routing of a Linux node. In [30] the authors had prototyped, validated and compared three different implementations: gRPC, REST, NETCONF. In this work we have adopted the gRPC solution for API implementation. ...
... All the developed software components are available as open source [32]. The local SRv6 Manager defined in [30] is extended for controlling the TWAMP Sender and Reflector that implement the TWAMP protocol for SRv6. The SRv6 Manager provide the Southbound loss monitoring interface that allows the SDN Controller to communicate with the nodes configure, start and stop the measure. ...
Segment Routing over IPv6 (SRv6 in short) is a networking architecture suitable for both IP backbones and datacenters. The research, standardization and implementation of this architecture are actively progressing and SRv6 is already adopted in a number of large scale deployments. Effective solutions for Performance Monitoring (PM) of SRv6 networks are strongly needed and there is a lot of activity in this area. A full blown Performance Monitoring solution needs to include: i) Data Plane (as needed to measure metrics such as packet loss and delay); ii) Control Plane (to send commands to the monitoring entities in the nodes); iii) Management Plane (e.g., to collect the measured metrics). Moreover, Big-Data tools and solutions can be applied inside or
above
the traditional Management Plane boundaries to store and analyze the collected data. In this article we describe SRv6-PM, a solution for Performance Monitoring of SRv6 networks that deals with all the aspects discussed above. SRv6-PM features a cloud-native architecture that supports: i) the ingestion, processing, storage and visualization of PM data using Big-Data tools; ii) the SDN-based control of network routers to drive the performance monitoring operations. In particular, we focus on Loss Monitoring and consider a solution capable of tracking single packet loss events operating in near-real time (e.g., with a time granularity in the order of 10-20 seconds). SRv6-PM is released as open source. We offer a re-usable and extensible platform that can be automatically deployed in different environments, from a single host to multiple servers on private/public clouds and includes a set of Big-Data tools and the SDN control plane. We also provide a reproducible Data Plane environment for PM experiments in SRv6 networks based on the Mininet emulator.
... El intercambio entre el plano de datos y el de control, se realiza por medio de las API hacia el sur (southbound API), con OpenFlow como protocolo estándar. Mediante esta API el controlador puede enviar un conjunto de políticas o configuraciones [47], controlar la programación de todas las operaciones de reenvío, realizar informes de estadísticas y enviar/recibir notificaciones de eventos de los dispositivos del plano de datos. ...
... El controlador administra las tablas de flujo añadiendo, modificando o eliminando las entradas [47]. Esta administración puede ser de manera reactiva (en respuesta de la llegada de un paquete al conmutador) o proactiva (antes de que el paquete llegue al conmutador). ...
The incessant growth and evolution of the Internet highlights the limitations of its architecture and the need for better design. At the same time, new requirements emerged as a result of the development of new applications that made clear to the research community the need to make significant adjustments to the Internet model. In this panorama, ICNs (Information-Centric Networks) and SDNs (Software-Defined Networks) stand out as two of the main proposals for an Internet of the future. The combination of ICN's efficient data delivery and SDN's flexible management framework looks interesting as a solution to today's Internet design problems.
The present work proposes an SD-ICN architecture for the Internet of the future. ICN and SDN technologies are analyzed, as well as some works that show the advantages of their union. From the study of the aforementioned projects, an efficient name-based content delivery mechanism is proposed through centralized management of routing and caching parameters in the network. For the validation of the SD-ICN architecture, a scenario was used for which it was verified that it was possible to implement the proposed architecture.
Key words: Information Centric Networks (ICN), Software Defined Networks (SDN), Internet, Network Architecture, Future Internet Architecture
... Next, in Figure 3, we will illustrate the SFC orchestration based on the SRv6 mechanism in a single domain, which can be extended to multi-domain. The SRv6 architecture is a promising solution to support services like Traffic Engineering and Service Function Chaining [27]. In the SR domain, the different VNFs are hosted by NFV nodes. ...
... This can simplify the SFC deployment scheme and reduce the problem of excessive load on one node, achieving better load balancing. This is shown is Formulas (26) and (27) ...
With the emergence of virtualization technology, Network Function Virtualization (NFV) and Software Defined Networking (SDN) make the network function abstract from the hardware and allow it to be run on virtual machines. These technologies can help to provide more efficient services to users by Service Function Chaining (SFC). The sequence of multiple VNFs required by network operators to perform traffic steering is called SFC. Mapping and deploying SFC on the physical network can enable users to obtain customized services in time. At present, a key problem in deploying SFC is how to reduce network resource consumption and load pressure while ensuring the corresponding services for users. In this paper, we first introduce an NFV architecture for SFC deployment, and illustrate the SFC orchestration process which is based on SRv6 in multi-domain scenario. Then, we propose an effective SFC dynamic orchestration algorithm. First, we use Breadth-First Search algorithm to traverse network and find the shortest path for deploying VNFs. Next, we use the improved Ant Colony Optimization algorithm to generate the optimal deployment scheme. Finally, we conduct a series of experiments to verify the performance of our algorithm. Compared with other deployment algorithms, the results show that our solution effectively optimizes end-to-end delay, bandwidth resource consumption and load balancing.
... Segment routing [11] encodes the transmission path in the packet header, making the transmission path definable. Particularly when it is used with software-defined networking (SDN), the performance of segment routing has been effectively improved [12]. However, the excessive overhead limits the transmission efficiency. ...
Information-Centric Networking (ICN) has revolutionized the manner of content acquisition by shifting the communication mode from host-centric to information-centric. Considering the existing, large amount of IP infrastructure in current networks, the new ICN architecture is proposed to be compatible with existing networks in order to reduce deployment cost. However, due to compatibility with IP networks, ICN data packets must be transmitted through the default path provided by IP routing regulations, which also limits the transmission efficiency and reliability of ICN. In order to address this issue, this paper introduces a multipath transmission method applied in ICN which takes full advantage of the functions and characteristics of ICN and builds multiple end-to-end relay paths by using the ICN routers as relay nodes. We then propose a relay-node-selection algorithm based on path correlation to minimize the impact of overlapping links. Moreover, we comprehensively calculate the path state value by combining the round-trip time and packet loss rate and propose a multipath data-scheduling algorithm based on the path state value. Simulation experiments show that the proposed method can maintain high bandwidth utilization while reducing the number of out-of-order packets.
... In addition, segment routing (SR) has advantages in network structure that can help solve these problems in the SDN. Therefore, many scholars began to explore the possibility of combining the SDN with segment routing [7] . Segment routing is a novel network architecture that has realized further control of SDN in recent years. ...
Segment routing has been a novel architecture for traffic engineering in recent years. However, segment routing brings control overheads, i.e., additional packets headers should be inserted. The overheads can greatly reduce the forwarding efficiency for a large network, when segment headers become too long. To achieve the best of two targets, we propose the intelligent routing scheme for traffic engineering (IRTE), which can achieve load balancing with limited control overheads. To achieve optimal performance, we first formulate the problem as a mapping problem that maps different flows to key diversion points. Second, we prove the problem is nondeterministic polynomial (NP)-hard by reducing it to a k-dense subgraph problem. To solve this problem, we develop an ant colony optimization algorithm as improved ant colony optimization (IACO), which is widely used in network optimization problems. We also design the load balancing algorithm with diversion routing (LBA-DR), and analyze its theoretical performance. Finally, we evaluate the IRTE in different real-world topologies, and the results show that the IRTE outperforms traditional algorithms, e.g., the maximum bandwidth is 24.6% lower than that of traditional algorithms when evaluating on BellCanada topology.
... SDN provides a consolidated view of an organization's whole network, making corporate administration and provisioning more efficient [13]. The centralized control makes controlling easier and more powerful in distributed environments. ...
The Internet of Everything (IoE) connects millions of machines, vehicles, nodes, smoke detectors, watches, glasses, webcams, and other devices to the internet. These entities need the proper guidance and control for expected performance. There is always a need to manage their networks for better performance properly. However, managing all these entities is not easy; it is always a big concern. All types of network architectures are getting enhanced daily, and the traditional network management process becomes more complex, especially rendering the performance during technology and entity modifications. Software-Defined Networking (SDN) is extensively used in all types of networks, especially in future network technologies (IoT, IoV, 6G, AI, etc.) to tackle such types of concerns and issues. However, as with any new phrase or paradigm, no clear description of this technology has emerged yet, which will give a complete understanding of SDN, from basic terminology to its management capabilities. The contribution of this research article is a significant step forward in understanding the basics of SDN. This research article proposes a detailed review of SDN in the form of history, overview, architecture, benefits, services, trends, application, features, and challenges.
... The segment holds identification for instructions such as context, locator, and services. These services can be leveraged through multiprotocol label switching (MPLS) in conjunction with the Internet protocol for listing the segments in the routing extension header [66]. ...
Software-defined networking (SDN) is a networking paradigm to enable dynamic, flexible, and programmatically efficient configuration of networks to revolutionize network control and management via separation of the control plane and data plane. The SDN market has evolved in response to the demands from large data centers toward the aggregation of multiple types of network connections. On the one hand, SDNs have provided solutions for high-demand resources, managing unpredictable data traffic patterns, and rapid network reconfiguration. They are further used to enhance network virtualization and security. On the other hand, SDN is still subject to many traditional network security threats. It also introduces new security vulnerabilities, primarily due to its logically centralized control plane infrastructure and functions. In this paper, we conduct a comprehensive survey on the core functionality of SDN from the perspective of secure communication infrastructure at different scales. A specific focus is put forward to address the challenges in securing SDN-based communications, with efforts taken up to address them. We further categorize the appropriate solutions for specific threats at each layer of SDN infrastructure. Lastly, security implications and future research trends are highlighted to provide insights for future research in the domain.
... However, when the SR network uses IPv6 as its data plane, additional encapsulation will never be used due to that both SRv6-enabled routers and non-SRv6 routers can forward the packet under the same packet header definition. In [23], the authors proposed an architecture for SRv6 network and designed a series of southbound APIs. In this paper, we focus on how to incrementally deploy SRv6-enabled routers into the legacy network from a traffic engineering view, i.e., minimizing the maximum link utilization under the constraint of a limited number of SRv6 routers. ...
Many organizations nowadays have multiple sites at different geographic locations. Typically, transmitting massive data among these sites relies on the interconnection service offered by ISPs. Segment Routing over IPv6 (SRv6) is a new simple and flexible source routing solution which could be leveraged to enhance interconnection services. Compared to traditional technologies, e.g., physical leased lines and MPLS-VPN, SRv6 can easily enable quick-launched interconnection services and significantly benefit from traffic engineering with SRv6-TE. To parse the SRv6 packet headers, however, hardware support and upgrade are needed for the conventional routers of ISP. In this paper, we study the problem of SRv6 incremental deployment to provide a more balanced interconnection service from a traffic engineering view. We formally formulate the problem as an SRID problem with integer programming. After transforming the SRID problem into a graph model, we propose two greedy methods considering short-term and long-term impacts with reinforcement learning, namely GSI and GLI. The experiment results using a public dataset demonstrate that both GSI and GLI can significantly reduce the maximum link utilization, where GLI achieves a saving of 59.1% against the default method.
... The use of APIs allows the configuration and management of the network using open and standard programming languages. Several protocols and programming languages have been defined to establish communications between the control plane and data plane through the southbound interface, such as OpenFlow [10], P4 language [11], NETCONF and gRPC [18]. However the most common protocol used within the Southbound interface is OpenFlow [10]. ...
... The device named router decide to deliver the packet to right machine after matching of Mac with routing table. If the path matched from table then the destination host will receive data otherwise packet will be discarded [26]. The routing table can store a large number of routes. ...
... Also, the Core Controller uses xmlrpc-based API of Open Nebula Edge 5.8 to provide container deployment as a service slice on edge. In the Core Controller, the control plane communicates with Quagga-based routers through South-Bound Interface (SBI), a gRPC-based customized from [37]. NANO uses that interface to install SID as part of the slice configuration in the onboarding process. ...
The traditional business models exploited in networking are changing into industry verticals, which in turn builds new applications with striking and specific requirements. Therefore, the service-oriented, fully programmable, and flexible features that translate to sliced-capable networks are fundamentals in the design, deployment, and orchestration of networks such as 5G and beyond. Also, application consumption experiences are moving towards pervasiveness, and it is necessary to address the established inter-domain constraints uniformly. Leveraged by SDN, Cloud/Edge Computing, and NFV, several state-of-the-art proposals aim to address multi-domain slice deployment. However, they focus on multi-domain control plane efforts, leaving numerous data plane challenges openly. This paper seeks to overcome the multi-domain slice establishing issues through a source routing and BGP-based approach to provide slice abstraction to cope with application requirements. A proof-of-concept called NASOR was implemented and validated using VxFs use-cases. The results showcase its deployment suitability in traditional core networks and enhancement of the end-user experience.
... SRv6 forwarded packets from a new connection through a set of candidate servers until the connection is accepted to a dedicated server. Ventre et al. [12] designed and implemented Southbound API between an SDN controller and the SRv6 device. gRPC, REST, NETCONF, and remote command line interface (CLI) were implemented to analyze performance differences when each protocol is used as Southbound API. ...
... The authors in [114] went further and proposed an SDNbased SR on top of IPv6. Motivated by the centralized control of SDN, they propose an SDN architecture to control IPv6based SR enabled networks. ...
Software-Defined Networking (SDN) is an emerging network architecture that promises to simplify network management, improve network resource utilization, and boost evolution and innovation in traditional networks. SDN allows the abstraction and centralized management of the lower-level network functionalities by decoupling the network logic from the data forwarding devices into a logically centralized distributed controllers. However, this separation introduces new scalability and performance challenges in large-scale networks of dynamic traffic and topology conditions. Many research studies have represented that centralization and maintaining the global network visibility over the distributed SDN controller introduce scalability concern. This paper surveys the state-of-the-art proposed techniques toward minimizing the control to data planes communication overhead and controllers consistency traffic to enhance the OpenFlow-SDN scalability in the context of logically centralized distributed SDN control plane architecture. The survey mainly focuses on four issues including logically centralized visibility, link-state discovery, flow rules placement and controllers’ load balancing. In addition, the paper discusses each issue and present an updated and detailed study of existing solutions and limitations in enhancing the OpenFlow-SDN scalability and performance. Moreover, it outlines the potential challenges that need to be addressed further in obtaining adaptive and scalable OpenFlow-SDN flow control.
Modern networks urge agility, flexibility, and capacity to cope with the growing demand for media content and applications increasingly oriented toward data consumption. The Central Offices (CO) of telecommunication providers, being a vital aggregator of different access networks, such as optical and mobile, need to be prepared to deal with these demands. The Open Broadband-Broadband Access Abstraction (OB-BAA) architecture fits into the initiative to modernize the Information Technology (IT) components of broadband networks, more specifically the COs. This paper discusses the development of a Virtualized Network Function (VNF) in the context of network security to be integrated as a component of an OB-BAA architecture guided by the Software-Defined Network paradigm. More specifically, the authentication and authorization of network equipment within the IEEE 802.1X protocol are applied to Next Generation Passive Optical Networks. The VNF development is based on the Golang language combined with gRPC programmable interfaces for communication between the various elements of the OB-BAA architecture, and then the components were “containerized” and inserted in the Docker and Kubernetes virtualization frameworks of a multinational telecommunications operator. Finally, performance metrics such as computational resource usage (CPU, memory, and network I/O) and execution time of VNF processes were analyzed in usage tests with multiple supplicants and distinct operational modes, to attest to the most promising virtualization scenarios.
Multipath routing conforms to the evolution principle of network development and is a trend of routing architectures. It can not only meet the needs but also enhance the performance and security of a network. However, deploying multipath routing further increases the scale of the forwarding information base (FIB) and the cost of forwarding devices. Therefore, to realize the lightweight deployment of multipath routing with a distributed architecture, this paper takes two-dimensional routing (TD routing) as an example to provide a solution. We propose a distributed storage mechanism of TD routing in combination with SRv6 (TDSR) and the corresponding SRv6 header (SRH) compression (CARD) method. The main methods are as follows: Inspired by a software-defined wide area network (SD-WAN), this paper introduces segment routing (SR) in the data plane, which can disperse TD-FIBs in different ingress nodes. The ingress routers push path information into the stack, and the intermediate routers forward the packets according to the SRH. Second, for the bandwidth waste of the SRH, compression is attempted by comparing the difference between the the shortest path first (SPF) path and the SRv6 path. Only a few hops in the TD path that are different from those in the one-dimensional (OD) path are kept. Finally, we sort out several typical application scenes of multipath routing and discuss several simplification algorithms. The experimental results show that the TDSR can reduce TD entries by 69%, and the average compression rate of CARD can reach 70%. In addition, CARD can be combined with existing methods to improve their effect.
Software defined networking (SDN) has brought a novel networking paradigm for achieving the goal of anonymous communication. In this paper, we propose a strong anonymous communication scheme based on segment routing (STAR), which does not need all forwarding devices to support OpenFlow protocol and is easy to deploy in SDNs. In STAR, by expanding the packet format of segment routing via Sphinx protocol, the required routing information is encrypted and hidden in the packet header to prevent the enemy from associating with the communication parties. Moreover, to avoid the adversary connecting the communication parties based on load information, the trust controller is employed as an auxiliary node to negotiate the symmetric key between the communication parties for encrypting the packet load. The theoretical analysis shows that, when the adversary compromises multiple intermediate nodes, a low correct linking probability and effective attack resistance are obtained, which proves the weak correlation and stronger anonymity of STAR. Besides, evaluation results confirm that, compared with existing anonymous systems, the proposed STAR can ensure stronger anonymity and higher throughput (83.7% for that of no anonymity) by just introducing very small communication latency (microseconds) and resource cost. Especially for the large-volume data in large-scale SDNs, the advantages will be more obvious.
Various types of services in the era of 5G and cloud have a wide range of requirements for IP backbone networks, which brings increasingly big gaps between traditional IP backbone networks and the service requirements since there are very few path calculations and forwarding policies that can be launched on traditional IP networks. This paper proposes a method to calculate explicit paths which are encoded in an SRv6 segment list, the path calculation is based on an SRv6 topology and one or multiple constraints such as latency, packet loss rate, primary and backup protection, etc., and used to establish multiple forwarding planes on an IP backbone network. The authors build a reference test bed and successfully validate that a low-latency and high-reliability slice can be established as expected via the proposed calculation method by leveraging an SDN controller. In addition, the authors also validate that the performance of the protection and failover of the primary and backup paths can reach a sub-second level based on an operational-grade dataset of low-latency SRv6 policy. In summary, the method is feasible for large-scale implementation on IP backbone networks.KeywordsSRv6Forwarding planeLow-latencyHigh-reliabilitySDN
The Segment Routing (SR) architecture is based on source routing. Within an SR enabled network, a list of instructions called segments can be added to the packet headers to influence the forwarding and the processing of the packets. In SRv6 (Segment Routing over IPv6 data plane) the segments are represented with IPv6 addresses, which are 16 bytes long. There are some SRv6 service scenarios that may require to carry a large number of segments in the IPv6 packet headers. Reducing the size of these overheads is useful to minimize the impact on MTU (Maximum Transfer Unit) and to enable SRv6 on legacy hardware devices with limited processing capabilities that could suffer from the long headers. In this paper we present the Micro SID solution for the efficient representation of segment identifiers. The proposed Micro SID solution has been implemented on three different architectures (VPP, Linux, P4) and interoperability tests have been performed. We also analyze the reduction of the header size that can be achieved with Micro SIDs and compare it with other proposals for segment list compression. Our results show that the header size can be reduced up to 75%. Finally, we mention that a fundamental asset of the proposed Micro SID solution is the full compatibility and seamless interoperability with existing SRv6 architecture.
The number of tunnels configured and state kept in IP/MPLS backbones depends on the number of flows and traffic engineering requirements. Segment routing automates tunnel configuration and reduces state in the network, based on the concept of segments: subpaths of the graph. A flow can be defined using only one segment if the route matches the shortest path computed by the IGP, while this number grows with the need for different subpaths. As a consequence, there is a trade-off between traffic engineering and the number of segments used, which translates to header overhead and state in routers. The challenge then is to have flows sharing as many segments as possible. We advance the state of the art with a two-step bi-objective optimization model to reduce the number of configured segments, considering two traffic engineering requirements, load balancing and latency. Our results show that, as we increase the number of flows in the network, the number of configured segments also increases, and then stabilizes regardless of the number of additional flows. Hence, using a real telecommunication network, we show that we can meet traffic engineering requirements with less than 22% of the total number of states as compared to the usual case of IP/MPLS backbones.
The emerging latency-sensitive services such as smart grid and tactile internet require deterministic network performance including deterministic end-to-end latency, latency jitter and bounded packet loss rate. To empower standard Ethernet with such capability, we provide a deterministic forwarding system named DLCC with end-to-end congestion control and queue management available at common hardwares to provide bounded delay over Internet. Meanwhile, DLCC provides a per-hop delay correction scheme to minimize delay variation under dynamic scenarios. Compared with other schemes, DLCC effectively reduces the delay jitter by up to 90% and is able to quickly converge to the required end-to-end delay.
Emerging technologies like IoT (Internet of Things) and wearable devices like Smart Glass, Smart watch, Smart Bracelet and Smart Plaster produce delay sensitive traffic. Cloud computing services are emerging as supportive technologies by providing resources. Most services like IoT require minimum delay which is still an area of research. This paper is an effort towards the minimization of delay in delivering cloud traffic, by geographically localizing the cloud traffic through establishment of Cloud mini data centers. The anticipated architecture suggests a software defined network supported mini data centers connected together. The paper also suggests the use of segment routing for stitching the transport paths between data centers through Software defined Network Controllers.
With the increasing requirements of industrial production efficiency, Industrial Internet has played a very important role in the fourth industrial revolution. However, the current Industrial Internet still has many drawbacks, especially in terms of network systems, such as low network expansion, inconvenient troubleshooting, and low data transmission efficiency. For this motivation, a novel SRv6 Based Multi-domain Integrated Architecture for Industrial Internet (SMA) has been proposed. Multi-layer controllers are deployed in SMA and the SDN controller that generates the transmission path is replaced by SMA nodes, which realizes the high network scalability and efficient data transmission of the Industrial Internet. The faulty node in the SMA can be quickly and accurately identified through the periodic detection actively sent by the controller node in the domain and the passive feedback of the SMA nodes, and the generated SMA Nodes Trusted Set (SNTS) can be usedfor forwarding path generation. A Bellman-Ford algorithm with a hop count constraint based on the Total number of SNTS Nodes (BF-TN) is proposed, which effectively avoids long-path forwarding and improves network resource utilization. Through theoretical analysis, the safety and scalability of SMA have been fully verified. The simulation results of SMA on the experimental platform show that SMA is superior to the existing Industrial Internet network structure in terms of troubleshooting efficiency of faulty nodes, network throughput, and data communication overhead. In the Industrial Internet, when the proportion of SMA nodes reaches 30%, the SMA controller can control nearly 80% of the traffic.
Current IP-based networks support a wide range of delay-sensitive applications such as live video streaming of network gaming. Providing an adequate quality of experience to these applications is of paramount importance for a network provider. The offered services are often regulated by tight Service Level Agreements (SLAs) that needs to be continuously monitored. Since the first step to guarantee a metric is to measure it, delay measurement becomes a fundamental operation for a network provider. In many cases, the operator needs to measure the delay on all network links. We refer to the collection of all link delays as the Link Delay Vector (LDV). Typical solutions to collect the LDV impose a substantial overhead on the network. In this paper, we propose a solution to measure the LDV in real-time with a low-overhead approach. In particular, we inject some flows into the network and infer the LDV based on the delay of those flows. To this end, the monitoring flows and their paths should be selected minimizing the network monitoring overhead. In this respect, the challenging issue is to select a proper combination of flows such that by knowing their delay it is possible to solve a set of linear equations and obtain a unique LDV. This combination of monitoring flows should be optimal according to some criteria and should meet some feasibility constraints. We first propose a mathematical formulation to select the optimal combination of flows, in form of an Integer Linear Programming (ILP) problem. Then we develop a heuristic algorithm to overcome the high computational complexity of existing ILP solvers. As a further step, we propose a meta-heuristic algorithm to solve the above-mentioned equations and infer the LDV. The challenging part of this step is the volatility of link delays. The proposed solution is evaluated over real-world emulated network topologies using the Mininet network emulator. Emulation results show the accuracy of the proposed solution with a negligible networking overhead in a real-time manner.
Segment Routing with IPv6 (SRv6) is a leading Hybrid SDN (HSDN) architecture, as it fully exploits standard IP routing and forwarding both in the control plane and in the data plane. In this paper we design, implement and evaluate a programmable data plane solution for Linux routers called HIKE (HybrId Kernel/eBPF forwarding), integrated in an HSDN/SRv6 architecture. HIKE integrates the conventional Linux kernel packet forwarding with custom designed eBPF/XDP (extended Berkeley Packet Filter/eXtreme Data Path) bypass to speed up performance of SRv6 software routers. Thus, in addition to the hybrid IP/SDN forwarding, we foster an additional hybrid approach inside a Linux forwarding engine combining eBPF/XDP and kernel based forwarding, taking the best from both worlds. Therefore, considering the two different conceptual levels of hybridization, we call our overall solution Hybrid squared or Hˆ2.
We have applied the Hˆ2 solution to Performance Monitoring (PM) in Hybrid SDNs, and we show how our HIKE data plane architecture supports SRv6 networking and Performance Monitoring (in particular Loss Monitoring) allowing a significant increase in performance: our implementation results show a remarkable throughput improvement (5x) with respect to a conventional Linux based solution.
In Software Defined-Content Delivery Networks (SD-CDN), the policies of tenants such as Youtube, Netflix, Office 365, etc. are not the same due to having different 5G traffic requirements for such contents as enhanced Mobile Broadband (eMBB), ultra-reliable low-latency (URLLC) and massive machine-type communication (mMTC). This leads SD-CDN multi-tenant slicing to provide different services with limited network resources, where each tenant can functionally manage their own virtual slice of a physical component according to service level agreements (SLAs). However, they are not permitted to dynamically configure their own components. Therefore, the physical end-to-end configuration of all edge devices causes extra hardware and bandwidth costs. Although software as a service (SaaS) is more preferred to handle cost-efficiency on a switch configuration that increases forwarding throughput (Mbps) with a less number of physical components in SD-CDN, the edge devices can be only served as infrastructure as a service (IaaS) currently. This motivation leads us to serve the
switch as a service
that includes both IaaS and SaaS characteristics. Therefore, we propose an OpenFlow as a service (OFaaS) design where each tenant has flow management and switch configuration permissions on their own virtual slice. In flow management, we define a novel Service Oriented Architecture (SOA) to orchestrate OFaaS driven topology by isolating each tenant from physical complexity. Here, each tenant can dynamically alter QoS on a flow and load balance between a sub-set of contents via OpenFlow protocol. In switch configuration; a novel OFaaS Management Algorithm for a multi-tenant slicing increases the number of tenants served per OpenFlow switch thanks to OFaaS design. It enables an end-to-end configuration via the NETCONF protocol with a novel YANG model of OFaaS. According to performance evaluation; OFaaS has the same forwarding throughput as conventional IaaS based OpenFlow switch for a homogenous content, whereas it has 71% more forwarding throughput (Mbps) and it has 40% more cost-efficient than conventional one for a heterogeneous content with $17 savings per tenant.
Fixed and mobile telecom operators, enterprise network operators and cloud providers strive to face the challenging demands coming from the evolution of IP networks (e.g. huge bandwidth requirements, integration of billions of devices and millions of services in the cloud). Proposed in the early 2010s, Segment Routing (SR) architecture helps face these challenging demands, and it is currently being adopted and deployed. SR architecture is based on the concept of source routing and has interesting scalability properties, as it dramatically reduces the amount of state information to be configured in the core nodes to support complex services. SR architecture was first implemented with the MPLS dataplane and then, quite recently, with the IPv6 dataplane (SRv6). IPv6 SR architecture (SRv6) has been extended from the simple steering of packets across nodes to a general network programming approach, making it very suitable for use cases such as Service Function Chaining and Network Function Virtualization. In this paper we present a tutorial and a comprehensive survey on SR technology, analyzing standardization efforts, patents, research activities and implementation results. We start with an introduction on the motivations for Segment Routing and an overview of its evolution and standardization. Then, we provide a tutorial on Segment Routing technology, with a focus on the novel SRv6 solution. We discuss the standardization efforts and the patents providing details on the most important documents and mentioning other ongoing activities. We then thoroughly analyze research activities according to a taxonomy. We have identified main categories during our analysis of the current state of play: Monitoring, Traffic Engineering, Failure Recovery, Centrally Controlled Architectures, Path Encoding, Network Programming, Performance Evaluation and Miscellaneous. We report the current status of SR deployments in production networks and of SR implementations (including several open source projects). Finally, we report our experience from this survey work and we identify a set of future research directions related to Segment Routing.
Quality of Experience (QoE) reflects end users' overall experience and feeling with network services, but needs support in terms of end-to-end Quality of Service (QoS). Segment routing (SR) as a new routing paradigm can provide good end-to-end QoS guarantee, making traditional multimedia traffic routing more efficient and scalable. In this paper, we address two problems related to the new SR mechanism: enabling fine-grained end-to-end QoS routing under a complex network environment and constructing the multicast routing tree with branch node load balancing. To solve these problems, an Inaccurate information-based QoE-driven Routing algorithm (IQdR) and a Branch-aware Multicast Tree (BaMT) algorithm were proposed. Simulation test results that have compared the performance of our proposed solution against that of other algorithms show that the previous works were outperformed. Additionally, the results also show that our multicast architecture improves the scalability of the network in terms of the number of flows.
The softwarization of networks is enabled by the SDN (Software-Defined Networking), NV (Network Virtualization), and NFV (Network Function Virtualization) paradigms, and offers many advantages for network operators, service providers and datacenter providers. Given the strong interest in both industry and academia in the softwarization of telecommunication networks and cloud computing infrastructures, a series of special section was established in IEEE Transactions on Network and Service Management, which aims at the timely publication of recent innovative research results on management of softwarized networks.
Large-scale data centers are major infrastructures in the big data era. Therefore, a stable and optimized architecture is required for Data Center Networks (DCNs) to provide services to the applications. Many research use SDN (Software Defined Network) based Multipath TCP (MPTCP) implementation to utilize the entire DCN’s performance and achieve good results. However, the deployment cost is high. In SDN-based MPTCP solutions, the flow allocation mechanism leads to a large number of forwarding rules which may lead to storage consumption. Considering the advantages and limitations of the SDN-based MPTCP solution, we aim to reduce the deployment cost due to the use of an extremely expensive storage resource - Ternary Content Addressable Memory (TCAM). We combine MPTCP and Segment Routing (SR) for traffic management to limit the storage requirements. And to the best of our knowledge, we are among the first to use the collaboration of MPTCP and SR in multi-rooted DCN topologies. To explain how MPTCP and SR work together, we use a four-layer DCN architecture for better description, which contains physical topology, SR over the topology, multiple path selection supplied by MPTCP, and traffic scheduling on the selected paths. Finally, we implement the proposed design in a simulated SDN-based DCN environment. The simulation results reveal the great benefits of such a collaborative approach.
The introduction of SDN in large-scale IP provider networks is still an open
issue and different solutions have been suggested so far. In this paper we
propose a hybrid approach that allows the coexistence of traditional IP routing
with SDN based forwarding within the same provider domain. The solution is
called OSHI - Open Source Hybrid IP/SDN networking as we have fully implemented
it combining and extending Open Source software. We discuss the OSHI system
architecture and the design and implementation of advanced services like Pseudo
Wires and Virtual Switches. In addition, we describe a set of Open Source
management tools for the emulation of the proposed solution using either the
Mininet emulator or distributed physical testbeds. We refer to this suite of
tools as Mantoo (Management tools). Mantoo includes an extensible web-based
graphical topology designer, which provides different layered network "views"
(e.g. from physical links to service relationships among nodes). The suite can
validate an input topology, automatically deploy it over a Mininet emulator or
a distributed SDN testbed and allows access to emulated nodes by opening
consoles in the web GUI. Mantoo provides also tools to evaluate the performance
of the deployed nodes.
Traffic Engineering (TE) in IP carrier networks is one of the functions that can benefit from the Software Defined Networking paradigm. However traditional per-flow routing requires a direct interaction between the SDN controller and each node that is involved in the traffic paths. Segment Routing (SR) may simplify the route enforcement delegating all the configuration and per-flow state at the border of the network. In this work we propose an architecture that integrates the SDN paradigm with SR based TE, for which we have provided an open source reference implementation. We have designed and implemented a simple TE/SR heuristic for flow allocation and we show and discuss experimental results.
Software-Defined Networking (SDN) is an emerging paradigm that promises to
change the state of affairs of current networks, by breaking vertical
integration, separating the network's control logic from the underlying routers
and switches, promoting (logical) centralization of network control, and
introducing the ability to program the network. The separation of concerns
introduced between the definition of network policies, their implementation in
switching hardware, and the forwarding of traffic, is key to the desired
flexibility: by breaking the network control problem into tractable pieces, SDN
makes it easier to create and introduce new abstractions in networking,
simplifying network management and facilitating network evolution. Today, SDN
is both a hot research topic and a concept gaining wide acceptance in industry,
which justifies the comprehensive survey presented in this paper. We start by
introducing the motivation for SDN, explain its main concepts and how it
differs from traditional networking. Next, we present the key building blocks
of an SDN infrastructure using a bottom-up, layered approach. We provide an
in-depth analysis of the hardware infrastructure, southbound and northbounds
APIs, network virtualization layers, network operating systems, network
programming languages, and management applications. We also look at cross-layer
problems such as debugging and troubleshooting. In an effort to anticipate the
future evolution of this new paradigm, we discuss the main ongoing research
efforts and challenges of SDN. In particular, we address the design of switches
and control platforms -- with a focus on aspects such as resiliency,
scalability, performance, security and dependability -- as well as new
opportunities for carrier transport networks and cloud providers. Last but not
least, we analyze the position of SDN as a key enabler of a software-defined
environment.
Software Defined Networking (SDN) promises to bring unparalleled flexibility, fine-grained control, configuration simplification and no vendor lock-in. The introduction of SDN in an existing network, however, must be incremental in most cases, for both technical and economical reasons. During the transition, operators have to manage hybrid networks, where SDN and traditional protocols coexist. In this paper, we show that the simultaneous presence of SDN and traditional routing protocols can create forwarding anomalies that ultimately defeat the purpose of deploying SDN. We devise techniques to adapt traffic flows to network dynamics, update routing policies and incrementally deploy SDN in hybrid networks, while avoiding those anomalies. We assess the applicability of our approach by extensive simulations. By adding support for manageability and evolv-ability, our techniques make hybrid networks not only a means for transition but also an interesting design point that can merge advantages of SDN and traditional paradigms.
This whitepaper proposes OpenFlow: a way for researchers to run experimental protocols in the networks they use ev- ery day. OpenFlow is based on an Ethernet switch, with an internal flow-table, and a standardized interface to add and remove flow entries. Our goal is to encourage network- ing vendors to add OpenFlow to their switch products for deployment in college campus backbones and wiring closets. We believe that OpenFlow is a pragmatic compromise: on one hand, it allows researchers to run experiments on hetero- geneous switches in a uniform way at line-rate and with high port-density; while on the other hand, vendors do not need to expose the internal workings of their switches. In addition to allowing researchers to evaluate their ideas in real-world traffic settings, OpenFlow could serve as a useful campus component in proposed large-scale testbeds like GENI. Two buildings at Stanford University will soon run OpenFlow networks, using commercial Ethernet switches and routers. We will work to encourage deployment at other schools; and We encourage you to consider deploying OpenFlow in your university network too.
IPv6 Segment Routing is a major IPv6 extension that provides a modern version of source routing that is currently being developed within the Internet Engineering Task Force (IETF). We propose the first open-source implementation of IPv6 Segment Routing in the Linux kernel. We first describe it in details and explain how it can be used on both endhosts and routers. We then evaluate and compare its performance with plain IPv6 packet forwarding in a lab environment. Our measurements indicate that the performance penalty of inserting IPv6 Segment Routing Headers or encapsulating packets is limited to less than 15%. On the other hand, the optional HMAC security feature of IPv6 Segment Routing is costly in a pure software implementation. Since our implementation has been included in the official Linux 4.10 kernel, we expect that it will be extended by other researchers for new use cases.
In Chapter 1, we presented an overview of networking and looked at the structure and usage of different network protocols such as TCP, UDP, IP, and DNS. In this chapter, we start with network programming using classes from the System.Net namespace.
This document describes the modifications to OSPF to support version 6 of the Internet Protocol (IPv6). The fundamental mechanisms of OSPF (flooding, DR election, area support, SPF calculations, etc.) remain unchanged. However, some changes have been necessary, either due to changes in protocol semantics between IPv4 and IPv6, or simply to handle the increased address size of IPv6.
Source packet routing in networking (SPRING) problem statement and requirements
- S Previdi
S. Previdi et al., "Source Packet Routing in Networking (SPRING)
Problem Statement and Requirements," IETF RFC 7855, May 2016.
Resiliency use cases in source packet routing in networking (SPRING) networks
- C Filsfils
- S Previdi
- B Decraene
- R Shakir
C. Filsfils, S. Previdi, B. Decraene, and R. Shakir, "Resiliency use cases
in source packet routing in networking (SPRING) networks," Internet
Eng. Task Force, Fremont, CA, USA, RFC 8355, Mar. 2018.
Use cases for IPv6 source packet routing in networking (SPRING)
- J Brzozowski
- J Leddy
- C Filsfils
- R Maglione
- M Townsley
J. Brzozowski, J. Leddy, C. Filsfils, R. Maglione, and M. Townsley,
"Use cases for IPv6 source packet routing in networking (SPRING),"
Internet Eng. Task Force, Fremont, CA, USA, RFC 8354, Mar. 2018.
Topology Independent Fast Reroute Using Segment Routing
- A Bashandy
A. Bashandy et al., "Topology Independent Fast Reroute using Segment
Routing," March 2018. [Online]. Available: http://tools.ietf.org/html/
draft-bashandy-rtgwg-segment-routing-ti-lfa
Interconnecting Millions of Endpoints With Segment Routing
- C Filsfils
- S Previdi
- G Dawra
- W Henderickx
- D Cooper
C. Filsfils, S. Previdi, G. Dawra, W. Henderickx, and D. Cooper.
(Mar. 2018). Interconnecting Millions of Endpoints With Segment
Routing. [Online]. Available: https://datatracker.ietf.org/doc/html/draftfilsfils-spring-large-scale-interconnect-09
Use of BGP-4 multiprotocol extensions for IPv6 inter-domain routing
- P Marques
- F Dupont
P. R. Marques et al., "Use of BGP-4 Multiprotocol Extensions for IPv6
Inter-Domain Routing," RFC 2545, Mar. 1999. [Online]. Available:
https://rfc-editor.org/rfc/rfc2545.txt
The open vSwitch database management protocol
- B Pfaff
- B Davie
B. Pfaff et al., "The Open vSwitch Database Management Protocol,"
RFC 7047, Dec. 2013. [Online]. Available: https://rfc-editor.org/rfc/
rfc7047.txt
Internet-Draft draft-smith-opflex-03
- M Smith
M. Smith et al., "OpFlex control protocol," Internet Eng. Task Force,
Fremont, CA, USA, Internet-Draft draft-smith-opflex-03, Apr. 2016.
[Online]. Available: https://datatracker.ietf.org/doc/html/draft-smithopflex-03
Path computation element (PCE) communication protocol (PCEP)
J. Vasseur et al., "Path Computation Element (PCE) Communication
Protocol (PCEP)," RFC 5440, Mar. 2009. [Online]. Available:
https://rfc-editor.org/rfc/rfc5440.txt
Network configuration protocol (NETCONF)
- R Enns
- M Bjorklund
- J Schoenwaelder
- A Bierman
R. Enns, M. Bjorklund, J. Schoenwaelder, and A. Bierman, "Network
configuration protocol (NETCONF)," Internet Eng. Task Force, Fremont,
CA, USA, RFC 6241, Jun. 2011. [Online]. Available: https://rfceditor.org/rfc/rfc6241.txt
A high performance, open-source universal RPC framework
- Grpc
Google. GRPC: A high performance, open-source universal RPC
framework. [Online]. Available: https://grpc.io/
[38] Google. Protocol Buffers. [Online]. Available: https://developers.google.
com/protocol-buffers/
Segment Routing: A comprehensive survey of research activities, standardization efforts and implementation results
- P L Ventre
- Others
P.L. Ventre and others, "Segment Routing: A comprehensive survey of
research activities, standardization efforts and implementation results,"
arXiv preprint arXiv:?, 2018.
Testbeds IntErconnections With L2 Overlays—SRv6 for SFC
- S Salsano
S. Salsano and others. Testbeds IntErconnections with L2 overlays
-SRv6 for SFC. [Online]. Available: https://www.slideshare.net/
stefanosalsano/testbeds-interconnections-with-l2-overlays-srv6-for-sfc
- Onf Stratum Project
ONF. Stratum Project. [Online]. Available: https://stratumproject.org
[47] OpenConfig
Home
Page.
(2018).
Resiliency Use Cases in Source Packet Routing in Networking (SPRING) Networks
- C Filsfils
C. Filsfils et al., "Resiliency Use Cases in Source Packet Routing in
Networking (SPRING) Networks," IETF RFC 8355, March 2018.
Use Cases for IPv6 Source Packet Routing in Networking (SPRING)
- J Brzozowski
J. Brzozowski et al., "Use Cases for IPv6 Source Packet Routing in
Networking (SPRING)," IETF RFC 8354, March 2018.
Interconnecting Millions Of Endpoints With Segment Routing
- C Filsfils
C. Filsfils et al., "Interconnecting Millions Of Endpoints
With
Segment
Routing,"
Mar.
2018,
work
in
Progress. [Online]. Available: https://datatracker.ietf.org/doc/html/
draft-filsfils-spring-large-scale-interconnect-09
Internet Engineering Task Force, Internet-Draft draft-smith-opflex-03
- M Smith
M. Smith et al., "OpFlex Control Protocol," Internet Engineering
Task Force, Internet-Draft draft-smith-opflex-03, Apr. 2016, work
in Progress. [Online]. Available: https://datatracker.ietf.org/doc/html/
draft-smith-opflex-03
Network Configuration Protocol (NETCONF)
- R Enns
R. Enns et al., "Network Configuration Protocol (NETCONF)," RFC
6241, Jun. 2011. [Online]. Available: https://rfc-editor.org/rfc/rfc6241.txt
OpenConfig Home Page
- Onf Stratum
ONF. Stratum project. [Online]. Available: https://stratumproject.org
[47] "OpenConfig Home Page," 2018. [Online]. Available: http://www.
openconfig.net/
he was one of the beneficiary of the scholarship "Orio Carlini" granted by the Italian NREN GARR. His main research interests focus on Software Defined Networking, Network Function Virtualization, Virtualization and IPv6 Segment Routing. He worked as researcher in several projects founded by the EU
- Softfire Project
SoftFire Project. [Online]. Available: https://www.softfire.eu
Pier Luigi Ventre received his PhD in Electronics
Engineering in 2018 from University of Rome "Tor
Vergata". From 2013 to 2015, he was one of the
beneficiary of the scholarship "Orio Carlini" granted
by the Italian NREN GARR. His main research
interests focus on Software Defined Networking,
Network Function Virtualization, Virtualization and
IPv6 Segment Routing. He worked as researcher in
several projects founded by the EU and currently he
is a post-doctoral researcher at CNIT.
He is a PhD candidate in Tarbiat Modares University, Tehran, Iran. Currently, he is spending his sabbatical period in University Rome "Tor Vergata". His main research interests are Network QoS, media streaming over the Internet
- Tajiki Mohammad Mahdi
Mohammad Mahdi Tajiki graduated from Electrical and Computer Engineering School of Tehran
University, Tehran, Iran. He is a PhD candidate in
Tarbiat Modares University, Tehran, Iran. Currently,
he is spending his sabbatical period in University
Rome "Tor Vergata". His main research interests are
Network QoS, media streaming over the Internet,
data center networking, traffic engineering, and software defined networking (SDN).
IPv6 Segment Routing Header (SRH)
Segment Routing Architecture
- C Filsfils
OpFlex control protocol
- M Smith