OpenFlow Compatible Key-Based Routing Protocol: Adapting SDN Networks to Content/Service-Centric Paradigm

Cruz, Adrian Flores de la; Manzanares‐López, Pilar; Muñoz‐Gea, Juan Pedro; Malgosa‐Sanahuja, Josemaría

doi:10.1007/s10922-018-9482-z

Cited by 3 publications

(7 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Primarily, when different purposes require the same content, this identifier scheme supports an efficient routing forward action in delay and information collision. Besides, the paper [109] proposed an OpenFlow compatible key-based routing (OFC-KBR) solution to enable content-based networks to be deployed on the current networks. In this scheme, end hosts are identified by virtual identifiers, which were used for network communications.…”

Section: Sdn Over Icnmentioning

confidence: 99%

Survey on the scheme evaluation, opportunities and challenges of software defined‐information centric network

Ai,

Zhang,

Zhang

et al. 2023

IET Communications

View full text Add to dashboard Cite

As a promising architecture of next‐generation network, software defined‐information centric network (SD‐ICN) inherits the advantages of software defined network (SDN) and information‐centric network (ICN) to enable flexible and fast content retrieval, especially in the current era of artificial intelligence. However, the existing researches mainly focus on a single respective in this field, which motivates in comprehensively providing a forward‐looking guidance and development direction for scholars and engineers. To this end, the latest developments of SD‐ICN is presented. First, the widely‐accepted concepts and impacts on traditional networks are introduced. Second, the shortcomings of SDN and ICN over conventional networks are respectively analyzed to illustrate the necessity of SD‐ICN. Third, based on extensive analysis and deep deliberation, a methodical taxonomy for existing combination studies is proposed. They are divided into SDN over ICN, ICN over SDN, and mutual immersive pattern. Fourth, the performances of three integration categories are compared and the limitations of related works are highlighted. Fifth, the maturity index from six development indicators are evaluated. Further, the maturity and practicality of these schemes are generalized. Based on the above studies and comparisons, the lessons learned by SDN and ICN developments are concluded. Finally, future research directions and opportunities are discussed for the readers.

show abstract

Section: Sdn Over Icnmentioning

confidence: 99%

Survey on the scheme evaluation, opportunities and challenges of software defined‐information centric network

Ai,

Zhang,

Zhang

et al. 2023

IET Communications

View full text Add to dashboard Cite

show abstract

“…For example, the range [303, 319[= [000100101111, 000100111110] cannot be expressed by one bitmasked value. This fact causes a technical difficulty in OpenFlow-based networks, as it was identified in [4], because OpenFlow specification only enables the use of bitmasks to express ranges of values in the IPv4 source and destination matching fields. To solve this problem in OpenFlow networks, proposed the use of the prefix expansion algorithm [22] was proposed, converting each obtained range into a set of bitmasked equivalent ranges.…”

Section: Key-based Routing Mechanismmentioning

confidence: 99%

“…The prefix extension algorithm was proposed as a useful tool that allows programmers to implement this key-based routing protocol in OpenFlow networks [4]. However, as described before (see the example in Section 4.1), this prefix extension algorithm involves the insertion of a relatively high number of flow table entries in the nodes.…”

Section: Translation Of Ranges Solutionmentioning

confidence: 99%

“…A way to address this drawback, which we called the "translation of ranges solution", was theoretically defined in [4]. However, its implementation was left pending awaiting new versions of the OpenFlow standard that would allow it.…”

Section: Translation Of Ranges Solutionmentioning

confidence: 99%

“…A previous version of P4-KBR called OFC-KBR was defined for OpenFlow-based networks [4]. OFC-KBR (OpenFlow Compatible Key-Based Routing) performance was evaluated in different topologies from real networks, validating the foundations of the solution.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

P4-KBR: A Key-Based Routing System for P4-Programmable Networks

2021

Self Cite

View full text Add to dashboard Cite

Software-defined networking (SDN) architecture has provided well-known advantages in terms of network programmability, initially offering a standard, open, and vendor-agnostic interface (e.g., OpenFlow) to instruct the forwarding behavior of network devices from different vendors. However, in the last few years, data plane programmability has emerged as a promising approach to extend the network management allowing the definition and programming of customized and non-standardized protocols, as well as specific packet processing pipelines. In this paper, we propose an in-network key-based routing protocol called P4-KBR, in which end-points (hosts, contents or services) are identified by virtual identifiers (keys) instead of IP addresses, and where P4 network elements are programmed to be able to route the packets adequately. The proposal was implemented and evaluated using bmv2 P4 switches, verifying how data plane programmability offers a powerful tool to overcome continuing challenges that appear in SDN networks.

show abstract