A Virtual Id Routing Protocol for Future Dynamics Networks and Its Implementation Using the SDN Paradigm

Dumba, Braulio; Mekky, Hesham; Jain, Sourabh; Sun, Guobao; Zhang, Zhi-Li

doi:10.1007/s10922-016-9373-0

Cited by 8 publications

(4 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Thus, for a well‐managed infrastructure (such as a production datacenter), a logically centralized directory service would be favored. For a loosely controlled and frangibly connected environment, for example, in a mobile ad hoc network (MANET) or a dynamic internet overlay network, maintaining a centralized directory service could be either too expensive to maintain the states or too hard to implement due to ownership/membership management problems. For such a challenging network environment, a DHT‐like distributed directory service can help.…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

SEAL2: An SDN‐enabled all‐Layer2 packet forwarding network architecture for multitenant datacenter networks

Yeh

Qiu

Chang

2019

Int J Communication

View full text Add to dashboard Cite

This paper presents the design and development of a new network virtualization scheme to support multitenant datacenter networking (MT-DCN) based on software-defined networking (SDN) technologies. Effective multitenancy supports are essential and challenging for datacenter networking designs. In this study, we propose a new network virtualization architecture framework for efficient packet forwarding in MT-DCN. Traditionally, an internet host uses IP addresses for both host identification and location information, which causes mobile IP problems whenever the host is moved from one IP subnet to another. Unfortunately, virtual machine (VM) mobility is inevitable for cloud computing in datacenters for reasons such as server consolidation and network traffic flow optimization. To solve the problems, we decouple VM identification and location information with two independent values neither by IP addresses. We redefine the semantics of Ethernet MAC address to embed tenant ID information to the MAC address field without violating its original functionality. We also replace traditional Layer2/Layer3 two-stage routing schemes (MAC/IP) with an all-Layer2 packet forwarding mechanism that combines MAC addresses (for VM identification and forwarding in local server groups under an edge switch gateway) and multiprotocol label switching (MPLS) labels (for packet transportation between edge switch gateways across the core label switching network connecting all the edge gateways). To accommodate conventional IP packet architecture in a multitenant environment, SDN (OpenFlow) technology is used to handle all this complex network traffics. We verified the design concepts by a simple system prototype in which all the major system components were implemented. Based on the prototype system, we evaluated packet forwarding efficiency under the proposed network architecture and compared it with conventional IP subnet routing approaches. We also evaluated the incurred packet processing overhead caused by each of the packet routing components.

show abstract

Section: Discussionmentioning

confidence: 99%

“…VIRO presents another Layer2‐based routing protocol for future dynamics networks. It shares many similar design features with SEATTLE.…”

Section: Related Workmentioning

confidence: 99%

SEAL2: An SDN‐enabled all‐Layer2 packet forwarding network architecture for multitenant datacenter networks

Yeh

Qiu

Chang

2019

Int J Communication

View full text Add to dashboard Cite

show abstract

“…VIRO (Virtual Id ROuting) [15] proposed a key-based routing solution in the context of SDN/Openflow networks. The idea behind VIRO is the introduction of a topologyaware, structured virtual id space onto which both physical identifiers (e.g., Ethernet MAC addresses) as well as higher layer addresses/names (e.g., IPv4/IPv6) are mapped.…”

Section: Related Workmentioning

confidence: 99%

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

2021

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

“…By installing multiple paths at a switch, the controller can overflow the small TCAM‐based flow tables at the switch. To avoid this problem, one approach could be to use DHT‐based routing, according to which the routing and forwarding is performed by using logical identifier (LID) instead of IP address . The benefits of DHT‐based routing is that the LID of a node provides multiple paths without computing and installing multiple paths …”

Section: Future Research Directionsmentioning

confidence: 99%

Solutions for adopting software defined network in practice

Shah

Giaccone

Rawat

et al. 2019

Int J Communication

View full text Add to dashboard Cite

Software defined networking (SDN) has emerged as a new network paradigm, which decouples both control and management planes from data plane by implementing control and management at a (logically) centralized node, i.e., the controller. The data plane communicates with controller by using an open programming interface (like Openflow protocol 1 ). The reference SDN architecture is given in Figure 1 and explained as follows.Data plane: The data plane consists of standard switching devices, acting as routers, switches, and access points depending on the how they are programmed. A forwarding table is available in each switching device. When a data packet arrives at the switching device, the latter looks up its forwarding table whether an entry exists for the corresponding flow. If yes, then the data packet is forwarded/dropped as per action specified in the entry. Otherwise, the switching device buffers the data packet and sends a message to the controller to ask for instructions on how to process the packet. The controller sends back a forwarding rule to install in the forwarding table, which programs the action that the switching device must apply for the buffered data packet, and eventually for the future packets belonging to the same flow.Control plane: The controller acts as the "network brain" and is responsible for computing the forwarding behavior for the data packets based on the network topology, the network requirements (e.g., specified throughout access control list (ACL) policies), and the configuration of other network management functions (e.g., load balancing). The controller computes the forwarding decision and installs the corresponding rules in the forwarding tables present in the switching devices.Management plane: The management plane specifies the network applications (like load balancing, firewall, and monitoring) developed by the network operator.Plane interfaces: These planes in SDN interact with each other through standardized interfaces. The basic interfaces are (a) the southbound interface, used for communication between data plane and control plane, and (b) the northbound interface, used for communication between control plane and management plane.The SDN architecture has several advantages over the traditional networks. First, it centralizes the control in the SDN controller allowing a single and coherent view of the network state, simplifying the development of complex network applications and enabling the network administrator to push specific policies across the entire network. Second, the SDN architecture allows to evolve the control plane without changing the switching devices, since their actual behavior is programmed at the controller and can be reprogrammed at wish. Third, in traditional networks, the network administrator has to utilize management systems and/or manually define and implement security policies (e.g., ACL) at several switching devices. Instead, in SDN, security and/or traffic engineering policies can be defined just at the controller, and these will be forced in th...

show abstract

A Virtual Id Routing Protocol for Future Dynamics Networks and Its Implementation Using the SDN Paradigm

Cited by 8 publications

References 19 publications

SEAL2: An SDN‐enabled all‐Layer2 packet forwarding network architecture for multitenant datacenter networks

SEAL2: An SDN‐enabled all‐Layer2 packet forwarding network architecture for multitenant datacenter networks

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

Solutions for adopting software defined network in practice

Contact Info

Product

Resources

About