<i>Stored Program Controlled Network</i>: Overview

Horing, S.; Menard, J. Z.; Staehler, R. E.; Yokelson, B. J.

doi:10.1002/j.1538-7305.1982.tb04362.x

Cited by 9 publications

(3 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…2 In this paper, we use the term "RCP" to refer to both the architecture as a whole and to the specific instance of RCP within a routing domain. 3 RCP more closely resembles the Network Control Point (NCP), introduced in the telephone network in the early 1980s to simplify network management and support the rapid introduction of new features (e.g., enhanced 1-800 service) [24,27]. RCP's deployment path is as interesting as the envisioned end state.…”

Section: Introductionmentioning

confidence: 98%

The case for separating routing from routers

Feamster¹,

Balakrishnan²,

Rexford

et al. 2004

Proceedings of the ACM SIGCOMM Workshop on Future Directions in Network Architecture

217

149

View full text Add to dashboard Cite

Over the past decade, the complexity of the Internet's routing infrastructure has increased dramatically. This complexity and the problems it causes stem not just from various new demands made of the routing infrastructure, but also from fundamental limitations in the ability of today's distributed infrastructure to scalably cope with new requirements.The limitations in today's routing system arise in large part from the fully distributed path-selection computation that the IP routers in an autonomous system (AS) must perform. To overcome this weakness, interdomain routing should be separated from today's IP routers, which should simply forward packets (for the most part). Instead, a separate Routing Control Platform (RCP) should select routes on behalf of the IP routers in each AS and exchange reachability information with other domains.Our position is that an approach like RCP is a good way of coping with complexity while being responsive to new demands and can lead to a routing system that is substantially easier to manage than today. We present a design overview of RCP based on three architectural principles-path computation based on a consistent view of network state, controlled interactions between routing protocol layers, and expressive specification of routing policies-and discuss the architectural strengths and weaknesses of our proposal.

show abstract

Section: Introductionmentioning

confidence: 98%

The case for separating routing from routers

Feamster¹,

Balakrishnan²,

Rexford

et al. 2004

Proceedings of the ACM SIGCOMM Workshop on Future Directions in Network Architecture

217

149

View full text Add to dashboard Cite

show abstract

“…While this architectural shift has gained significant attention from both the academic and network industry, the concept of separating control and data plane functionality has been around for much longer. In the 1980s, central network control [1] was explored followed by active networks in the 1990s [2] to introduce programmability into the network. During this time, the driving application for the central/programmable network was missing.…”

Section: Introductionmentioning

confidence: 99%

A Survey of Security in Software Defined Networks

Scott-Hayward

Natarajan²,

Sezer

2016

IEEE Commun. Surv. Tutorials

413

213

View full text Add to dashboard Cite

The proposition of increased innovation in network applications and reduced cost for network operators has won over the networking world to the vision of Software-Defined Networking (SDN). With the excitement of holistic visibility across the network and the ability to program network devices, developers have rushed to present a range of new SDN-compliant hardware, software and services. However, amidst this frenzy of activity, one key element has only recently entered the debate: Network Security. In this article, security in SDN is surveyed presenting both the research community and industry advances in this area. The challenges to securing the network from the persistent attacker are discussed and the holistic approach to the security architecture that is required for SDN is described. Future research directions that will be key to providing network security in SDN are identified.

show abstract

“…Since the 1980s the centralized architectural network control system has been very robust [20]. As developers push the limits of what is possible, the capabilities of the interconnected networks that form the Internet increases.…”

Section: The Trend Of Computer Networkingmentioning

confidence: 99%

Dealing With Well-Formed and Malformed Packets, Associated With Point of Failure That Cause Network Security Breach

2020

View full text Add to dashboard Cite

It is quite challenging to understand the weakest single points of failure in a network because it is the point where an entire network system can be taken down. The paths leading to a point of failure, and the status of packets that causes network security breaches were examined by Intent-Based Networking approach in this study. Two algorithms are proposed, utilizing single-path and multipath in transmission flow. Every path is potentially weak and a point of failure for which a network security can be breached. Two sets of rules, namely, "vulnerability rules policies" with "rules formulation" from the regions of connection recognized by Euler's theorem were outlined. The intent is to use these sets of rules in finding the point of failure the packet status that is leading to possible security breaches within network connections. The frequencies of the packets that are liable to create security breaches and the paths where they originate are analyzed. Well-formed packet originating from the least likely weak point of failure is associated the network security breach than malformed packets. This study has contributed to revealing that network security breaches are influenced by the paths with least likely point of failure from well-formed packets.

show abstract

Stored Program Controlled Network: Overview

Cited by 9 publications

References 0 publications

The case for separating routing from routers

The case for separating routing from routers

A Survey of Security in Software Defined Networks

Dealing With Well-Formed and Malformed Packets, Associated With Point of Failure That Cause Network Security Breach

Contact Info

Product

Resources

About