Design and Implementation of ForCES Protocol

Ramirez, Pedro Luis Gonzalez; Lloret, Jaime; Cordero, Susan Martínez; Arboleda, Luís Carlos

doi:10.5296/npa.v9i1-2.10943

Cited by 2 publications

(2 citation statements)

References 12 publications

(23 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The proposed definitions covered basic Internet protocol version 4 (IPv4) packet processing functionality, while the definitions of advanced elements required to support QoS functionality or firewall functionality were beyond the scope of the above-mentioned paper. The design and implementation of the ForCES protocol are presented in [36]. The introduced implementation enables the creation of new LFB test topologies within the network element structure, which makes it a useful tool in the research of the ForCES data plane.…”

Section: Data Plane Architecturesmentioning

confidence: 99%

A Survey on Data Plane Flexibility and Programmability in Software-Defined Networking

et al. 2019

View full text Add to dashboard Cite

Software-defined networking (SDN) attracts the attention of the research community in recent years, as evidenced by a large number of survey and review papers. The architecture of SDN clearly recognizes three planes: application, control, and data plane. The application plane executes network applications; control plane regulates the rules for the entire network based on the requests generated by network applications; and based on the set rules, the controller configures the switches in the data plane. The role of the switch in the data plane is to simply forward packets based on the instructions given by the controller. By analyzing SDN-related research papers, it is observed that research, from the very beginning, is insufficiently focused on the data plane. Therefore, this paper gives a comprehensive overview of the data plane survey with particular emphasis on the problem of programmability and flexibility. The first part of the survey is dedicated to the evaluation of actual data plane architectures through several definitions and aspects of data plane flexibility and programmability. Then, an overview of SDN-related research was presented with the aim of identifying key factors influencing the gradual deviation from the original data plane architectures given with ForCES and OpenFlow specifications, which we called the data plane evolution. By establishing a correlation between the treated problem and the problem-solving approaches, the limitations of ForCES and OpenFlow data plane architectures were identified. Based on identified limitations, a generalization of approaches to addressing the problem of data plane flexibility and programmability is made. By examining generalized approaches, open issues have been identified, establishing the grounds for future research directions proposal.

show abstract

Section: Data Plane Architecturesmentioning

confidence: 99%

A Survey on Data Plane Flexibility and Programmability in Software-Defined Networking

et al. 2019

View full text Add to dashboard Cite

show abstract

“…This paper shows the operation of a prototype of the CE entity in a real environment of a simple data network, making use of the ForCES protocol [7], [8]. This allows to check the functioning of the ForCES Architecture in the conditions established by the specifications defined and created by the Internet Engineering Task Force (IETF) through the work group Forwarding and Control Element Separation (ForCES).…”

mentioning

confidence: 99%

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

Ramirez

Cordero

Lloret

et al. 2018

NPA

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Design and Implementation of ForCES Protocol

Cited by 2 publications

References 12 publications

A Survey on Data Plane Flexibility and Programmability in Software-Defined Networking

A Survey on Data Plane Flexibility and Programmability in Software-Defined Networking

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

Contact Info

Product

Resources

About