5-2TCP/IP Network Requirements
TCP/IP
The TCP/IP acronym stands for Transport Control Protocol/Internet Protocol. These protocols are implemented in the protocol stack as shown in Figure 5-1 on page 1. This protocol is commonly used in conjunction with ethernet networks. The TCP/IP address, also known as the IP address, is used to uniquely identify each ethernet device on a network. This address is of the form:
nnn.nnn.nnn.nnn
where nnn is a number from 0 to 255 (i.e., 47.246.0.71). This address is normally assigned by the LAN administrator in order to prevent address conflicts between ethernet devices. For more information please see Mark A. Miller, Internetworking: A Guide to Network Communications, MT&T Books, 1991.
LAN requirements
The definition of a Local Area Network (LAN) is a network supporting peer-to-peer communication over distances of tens of meters to several kilometers.
The LAN requirements for the INM Broadband are:
•Connectivity to the INM workstation
•Ethernet connections between the INM Broadband and the X Terminals
•Router or bridge access to remote OPC modules through a WAN
•Ethernet connection between local OPCs and INM Broadband
Routers are usually stand-alone devices which provide the capability to interface to many different types of networks, as well as to determine the optimal path to the destination. Routers are commonly used to bridge remote LANs through a WAN and can provide access to X.25, T1, frame relay, and other types of network. The router for the INM Broadband must be capable of supporting a minimum bandwidth of 56 Kbit/s for a setup consisting of the INM Broadband and two X Terminals. The routers for the OPC modules must have a minimum bandwidth of 56 Kbit/s to support 6 user sessions each. The routers should be able to support both TCP/IP and OSI protocols for future applications.
X.25
The X.25 protocol standard defines the interface to a Packet Data Network (PDN), or more specifically, it defines the Data Terminal Equipment (DTE) and Data Communications Equipment (DCE) interfaces between a synchronous packet-mode host and a PDN. The X.25 protocol suite does not, however, define the internal architecture of the PDN nor does it define the PDN’s operation. An X.25 data packet network is normally used in a wide area
