Network Programmability With ForCES

Abstract

Network programmability has re-emerged as top item of the networking research agenda as Software Defined Networking (SDN) gained wide acceptance simultaneously in vendor product line plans and operator expectations for future deployments. One of the key ingredients for the successful deployment of SDN technologies are standardized models, mechanisms, and protocols for the separation of the control and forwarding planes. The Internet Engineering Task Force (IETF) standardization effort on Forwarding and Control Element Separation (ForCES) has published a set of standards track documents which specify in detail a comprehensive architectural framework and the respective standard protocols which can be employed to implement the separation of these two planes in a flexible, scalable and vendor-agnostic yet fully interoperable manner. The IETF standards on ForCES define how to achieve said separation through a complete and modular system model of the forwarding plane elements. In the ForCES model every network element is composed of numerous logically separate and well-defined functional entities that cooperate to provide the desired overall functionality, such as a routing or IP switching. The elegance of the model lies in the fact that a ForCES-based implementation of a network element is indistinguishable from a traditional ("closed-box") network element and therefore can be deployed in the field without any need for migration to a new architecture. Conversely, ForCES allows for rapid prototyping and agile deployment of new architectures as emphasis is placed on software-defined functionality and full programmability. The difference of ForCES from other SDN approaches that depend on logically centralized controllers and the deployment of solely simple or "dumb" switches is that ForCES standards provide a complete toolbox to design, implement, and interoperate ForCES-based network elements with both previously deployed infrastructures as well as in experimental or early-deployment phase endeavors. An example of the former is the implementation of 3GPP-standardized network elements such as a packet gateway (PGW). Examples of the latter include the use of ForCES for network function virtualization (NFV) proves-ofconcepts. This paper surveys the programmable networks and SDN area and provides a comprehensive tutorial on ForCES by summarizing numerous standards documents and thus making the technology easily understood by the wider research community. We present the design goals, choices and tradeoffs for this standardized approach for network programmability and provide a thorough primer on the ForCES model and protocol. The article also surveys recent independent interoperable implementations that showcase the full spectrum of ForCES applications in the era of NFV and SDN.

A Review of Industry 4.0 Manufacturing Process Security Risks

“…IT personnel can thus progressively introduce OpenFlow-based technologies into existing industrial information networks, and can assess and become familiar with this new technology with minimal impact on the underlying processes. Other technologies such as forwarding and control element separation [50], open virtual switch database [51] and protocol oblivious forwarding [52] are also examples of SDN technologies that are currently being researched and developed.…”

A Proof-of-Concept Demonstration of Isolated and Encrypted Service Function Chains

“…With respect to interconnected control planes, we have earlier showed [6] that there are two orchestration methods across multiple service provider domains. (1) A top-down approach by utilising a hierarchy of orchestration planes [19] or control planes [20] or (2) by using an east-west control plane approach such as SDNi [21] or BGP [22]. Both interconnection methods try to overcome the problem of multiple forwarding standards and multiple types of network controllers.…”

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

“…Tarnaras et al [17] and Haleplidis et al [18] they propose through SDN an alternative of programmable networks based on the separation of the planes of control and forwarding. Providing a dynamic and optimized way, capable of dealing with network traffic in constant growth.…”