Internetworking
From Wikipedia, the free encyclopedia
Internetworking involves connecting two or more distinct computer networks or network segments together to form an internetwork (often shortened to internet), using devices which operate at layer 3 (Network layer) of the OSI Basic Reference Model (such as routers or layer 3 switches) to connect them together to allow traffic to flow back and forth between them.[1] The layer 3 routing devices guide traffic on the correct path (among several different ones usually available) across the complete internetwork to their destination.
Note: Routers were originally called gateways, but that term was discarded in this context, due to confusion with functionally different devices using the same name.
The connecting together of networks with bridges is sometimes incorrectly termed "internetworking", but the resulting system mimics a single subnetwork, and no internetworking protocol (such as IP) is required to traverse it. However, a single computer network may be converted into an internetwork by dividing the network into segments and then adding routers or other layer 3 devices between the segments [1].
The original term for an internetwork was catenet. Internetworking started as a way to connect disparate types of networking technology, but it became widespread through the developing need to connect two or more local area networks via some sort of wide area network. The definition now includes the connection of other types of computer networks such as personal area networks.
The most notable example of internetworking in practice is the Internet, a network of networks running different low-level protocols, unified by an internetworking protocol, the Internet Protocol (IP).
IP only provides an unreliable packet service across an internet. To transfer data reliably, applications must utilize a Transport layer protocol, such as TCP, which provides a reliable stream (These terms do not mean that IP is actually unreliable but instead that it sends packets without contacting and establishing a connection with the destination router beforehand. The opposite applies for reliable). Since TCP is the most widely used transport protocol, people commonly refer to TCP and IP together, as "TCP/IP". Some applications occasionally use a simpler transport protocol (called UDP) for tasks which do not require absolutely reliable delivery of data, such as video streaming.[2]
Contents |
[edit] History of Internetworking
The first networks were time-sharing networks that used mainframes and attached terminals. Such environments were implemented by both IBM's Systems Network Architecture (SNA) and Digital's network architecture.
Local-area networks (LANs) evolved around the PC revolution. LANs enabled multiple users in a relatively small geographical area to exchange files and messages, as well as access shared resources such as file servers and printers.
Wide-area networks (WANs) interconnect LANs with geographically dispersed users to create connectivity. Some of the technologies used for connecting LANs include T1, T3, ATM, ISDN, ADSL, Frame Relay, radio links, and others. New methods of connecting dispersed LANs are appearing everyday.
Today, high-speed LANs and switched internetworks are becoming widely used, largely because they operate at very high speeds and support such high-bandwidth applications as multimedia and videoconferencing.
Internetworking evolved as a solution to three key problems: isolated LANs, duplication of resources, and a lack of network management. Isolated LANs made electronic communication between different offices or departments impossible. Duplication of resources meant that the same hardware and software had to be supplied to each office or department, as did separate support staff. This lack of network management meant that no centralized method of managing and troubleshooting networks existed.[2]
[edit] Internetworking challenges
Implementing a functional internetwork is no simple task. Many challenges must be faced, especially in the areas of connectivity, reliability, network management, and flexibility. Each area is key in establishing an efficient and effective internetwork.
The challenge when connecting various systems is to support communication among disparate technologies. Different sites, for example, may use different types of media operating at varying speeds, or may even include different types of systems that need to communicate.
Because companies rely heavily on data communication, internetworks must provide a certain level of reliability. This is an unpredictable world, so many large internetworks include redundancy to allow for communication even when problems occur.
Furthermore, network management must provide centralized support and troubleshooting capabilities in an internetwork. Configuration, security, performance, and other issues must be adequately addressed for the internetwork to function smoothly. Security within an internetwork is essential. Many people think of network security from the perspective of protecting the private network from outside attacks. However, it is just as important to protect the network from internal attacks, especially because most security breaches come from inside. Networks must also be secured so that the internal network cannot be used as a tool to attack other external sites.
Early in the year 2000, many major web sites were the victims of distributed denial of service (DDOS) attacks. These attacks were possible because a great number of private networks currently connected with the Internet were not properly secured. These private networks were used as tools for the attackers.
Because nothing in this world is stagnant, internetworks must be flexible enough to change with new demands.[2]
[edit] Open System Interconnection Reference Model
The Open System Interconnection (OSI) reference model describes how information from a software application in one computer moves through a network medium to a software application in another computer. The OSI reference model is a conceptual model composed of seven layers, each specifying particular network functions. The model was developed by the International Organization for Standardization (ISO) in 1984, and it is now considered the primary architectural model for intercomputer communications. The OSI model divides the tasks involved with moving information between networked computers into seven smaller, more manageable task groups. A task or group of tasks is then assigned to each of the seven OSI layers. Each layer is reasonably self-contained so that the tasks assigned to each layer can be implemented independently. This enables the solutions offered by one layer to be updated without adversely affecting the other layers. The following list details the seven layers of the Open System Interconnection (OSI) reference model:
•Layer 7—Application
•Layer 6—Presentation
•Layer 5—Session
•Layer 4—Transport
•Layer 3—Network
•Layer 2—Data link
•Layer 1—Physical
[edit] See also
[edit] References
- ^ a b Groth, David; Toby Skandier (2005). 'Network+ Study Guide, Fourth Edition'. Sybex, Inc.. ISBN 0-7821-4406-3.
- ^ a b c Teare, Diane (July 1999). 'Designing Cisco Networks'. Indianapolis: Cisco Press.
[edit] External links
- E-book (pdf format) - Deals with the foundations of major internetworking architectures (chapters 4 to 9).
