scispace - formally typeset
Search or ask a question
Book

IP Network Design Guide

TL;DR: This redbook identifies some of the basic design aspects of IP networks and explains how to deal with them when implementing new IP networks or redesigning existing IP networks, and provides three examples for IP network design, depicting a small, medium and large network.
Abstract: This redbook identifies some of the basic design aspects of IP networks and explains how to deal with them when implementing new IP networks or redesigning existing IP networks. This project focuses on internetwork and transport layer issues such as address and name management, routing, network management, security, load balancing and performance, design impacts of the underlying networking hardware, remote access, quality of service, and platform-specific issues. Application design aspects, such as e-mail, gateways, Web integration, etc., are discussed briefly where they influence the design of an IP network. After a general discussion of the aforementioned design areas, this redbook provides three examples for IP network design, depicting a small, medium and large network. You are taken through the steps of the design and the reasoning as to why things are shown one way instead of another. Of course, every network is different and therefore these examples are not intended to generalize. Their main purpose is to illustrate a systematic approach to an IP network design given a specific set of requirements, expectations, technologies and budgets. This redbook will help you design, create or change IP networks implementing the basic logical infrastructures required for a successful operation of such networks. This book does not describe how to deploy corporate applications such as e-mail, e-commerce, Web server or distributed databases, just to name a few.
Citations
More filters
Patent
29 Oct 2007
TL;DR: In this paper, an individual characteristic analysis of a message was performed to determine whether the message is suspicious, determining whether a similar message has been noted previously in the event that the message was determined to be suspicious, classifying the message according to its individual characteristics and its similarity to the noted message.
Abstract: Detecting infectious messages comprises performing an individual characteristic analysis of a message to determine whether the message is suspicious, determining whether a similar message has been noted previously in the event that the message is determined to be suspicious, classifying the message according to its individual characteristics and its similarity to the noted message in the event that a similar message has been noted previously.

18 citations

Journal ArticleDOI
01 Oct 2021
TL;DR: In this article, the authors focus on E-IoT system components, vulnerabilities, solutions, and their security implications, and provide a list of open research problems that need further research.
Abstract: As technology becomes more widely available, millions of users worldwide have installed some form of smart device in their homes or workplaces. These devices are often off-the-shelf commodity systems, such as Google Home or Samsung SmartThings, that are installed by end-users looking to automate a small deployment. In contrast to these “plug-and-play” systems, purpose-built Enterprise Internet-of-Things (E-IoT) systems such as Crestron, Control4, RTI, Savant offer a smart solution for more sophisticated applications (e.g., complete lighting control, A/V management, security). In contrast to commodity systems, E-IoT systems are usually closed source, costly, require certified installers, and are overall more robust for their use cases. Due to this, E-IoT systems are often found in expensive smart homes, government and academic conference rooms, yachts, and smart private offices. However, while there has been plenty of research on the topic of commodity systems, no current study exists that provides a complete picture of E-IoT systems, their components, and relevant threats. As such, lack of knowledge of E-IoT system threats, coupled with the cost of E-IoT systems has led many to assume that E-IoT systems are secure. To address this research gap, raise awareness on E-IoT security, and motivate further research, this work emphasizes E-IoT system components, E-IoT vulnerabilities, solutions, and their security implications. In order to systematically analyze the security of E-IoT systems, we divide E-IoT systems into four layers: E-IoT Devices Layer, Communications Layer, Monitoring and Applications Layer, and Business Layer. We survey attacks and defense mechanisms, considering the E-IoT components at each layer and the associated threats. In addition, we present key observations in state-of-the-art E-IoT security and provide a list of open research problems that need further research.

17 citations

Patent
19 Dec 2014
TL;DR: In this paper, a system and methods for managing forwarded infectious messages are provided, which comprises receiving a message, forwarding the message, determining that the forwarded message is infectious after the message has been forwarded and preventing the infectious forwarded message from spreading.
Abstract: Systems and methods for managing forwarded infectious messages are provided. Managing electronic message comprises receiving a message, forwarding the message, determining that the forwarded message is infectious after the message has been forwarded and preventing the infectious forwarded message from spreading.

12 citations

Patent
29 Oct 2007
TL;DR: In this article, a message is forwarded, the forwarded message is determined to be infectious after the message has been forwarded, and the message is prevented from spreading by preventing the infectious forwarded message from spreading.
Abstract: Managing electronic messages comprises receiving a message, forwarding the message, determining that the forwarded message is infectious after the message has been forwarded and preventing the infectious forwarded message from spreading.

9 citations

Proceedings ArticleDOI
30 Dec 2010
TL;DR: The paper describes multicriteria modular approach to redesign/improvement of a networked system (e.g., sensor/ actuator network, communication network) and uses a numerical illustrative example of a real-world cooperative communication network to describe the suggested redesign approach.
Abstract: The paper describes multicriteria modular approach to redesign/improvement of a networked system (e.g., sensor/ actuator network, communication network). Generally, the approach consists of the following stages: (1) revelation of system bottlenecks, (2) generation of alternative improvement actions for each system bottleneck (i.e., new communication facilities as design alternatives for the upgrade process), (3) multicriteria assessment of the improvement actions, (4) multicriteria ranking of the improvement actions, and (5) forming a generalized improvement plan while taking into account a total resource constraint (multiple choice knapsack problem). A set of requirements/criteria is divided into several groups (criteria clusters: reliability, performance, manageability, etc.). An outranking technique (version of Electre method) is used for multicriteria ranking. A multistage heuristic is used for solving multiple choice knapsack problem. A numerical illustrative example of a real-world cooperative communication network is used to describe the suggested redesign approach. Three redesign schemes are analyzed: (1) a new full system design, (2) a partial system redesign, and (3) a hybrid redesign framework.

7 citations