2.

3 The Importance Of Network Protocols

Networking protocol suites:a. Transmission Control Protocol/Internet Protocol (TCP/IP) b. Internetwork Packet Exchange/ Sequenced Packet Exchange (IPX/SPX) c. NetBIOS and NetBEUI d. AppleTalk

TCP/IP
The Internet Protocol Suite is the set of communications protocols used for the Internet and other similar networks.

It is commonly also known as TCP/IP, named from two of the most important protocols in it: the Transmission Control Protocol (TCP) and the Internet Protocol (IP), which were the first two networking protocols defined in this standard.
Modern IP networking represents a synthesis of several developments that began to evolve in the 1960s and 1970s, namely the Internet and local area networks, which emerged during the 1980s, together with the advent of the World Wide Web(www) in the early 1990s.

TCP/IP (2)
The Internet Protocol Suite, like many protocol suites, is constructed as a set of layers.

Each layer solves a set of problems involving the transmission of data.

The TCP/IP model consists of four layers (RFC 1122). From lowest to highest, these are the Link Layer, the Internet Layer, the Transport Layer, and the Application Layer.

IPX/SPX (1)
IPX/SPX stands for Internetwork Packet Exchange/Sequenced Packet Exchange. IPX and SPX are networking protocols used primarily on networks using the Novell NetWare operating systems. IPX and SPX are derived from Xerox Network Systems' IDP and SPP protocols, respectively. IPX is a network layer protocol (layer 3 of the OSI Model), while SPX is a transport layer protocol (layer 4 of the OSI Model). The SPX layer sits on top of the IPX layer and provides connection-oriented services between two nodes on the network.

IPX/SPX (2)
SPX is used primarily by client/server applications. IPX and SPX both provide connection services similar to TCP/IP, with the IPX protocol having similarities to IP, and SPX having similarities to TCP. IPX/SPX was primarily designed for local area networks (LANs), and is a very efficient protocol for this purpose (typically its performance exceeds that of TCP/IP on a LAN). TCP/IP has, however, become the de facto standard protocol.

IPX/SPX (3)
This is in part due to its superior performance over wide area networks and the Internet (which uses TCP/IP exclusively), and also because TCP/IP is a more mature protocol, designed specifically with this purpose in mind.

NetBIOS & NetBEUI (1)

NetBIOS is an acronym for Network Basic Input/Output System. It provides services related to the session layer of the OSI model allowing applications on separate computers to communicate over a local area network. NetBIOS is not a networking protocol.

NetBIOS & NetBEUI (2)

Older operating systems ran NetBIOS over IEEE 802.2 and IPX/SPX using the NetBIOS Frames (NBF) and NetBIOS over IPX/SPX (NBX) protocols, respectively. In modern networks, NetBIOS normally runs over TCP/IP via the NetBIOS over TCP/IP (NBT) protocol. This result in each computer in the network having both a NetBIOS name and an IP address corresponding to a (possibly different) host name.

NetBIOS & NetBEUI (3)

NetBIOS provides three distinct services: 1. Name service for name registration and resolution. 2. Session service for connection-oriented communication. 3. Datagram distribution service for connectionless communication.

Apple Talk
AppleTalk is a proprietary suite of protocols developed by Apple Inc. for networking computers.

It was included in the original Macintosh released in 1984, and is now unsupported with the release of Mac OS X v10.6 in 2009 in favor of TCP/IP networking.
AppleTalk's Datagram Delivery Protocol corresponds closely to the Network layer of the Open Systems Interconnection (OSI) communication model.

Apple Talk (2)

An AppleTalk address was a 4-byte quantity. This consisted of a two-byte network number, a one-byte node number, and a one-byte socket number.

Of these, only the network number required any configuration, being obtained from a router.
Each node dynamically chose its own node number, according to a protocol (originally the LocalTalk Link Access Protocol LLAP and later the AppleTalk Address Resolution Protocol, AARP)[2] which handled contention between different nodes accidentally choosing the same number

Apple Talk (3)

For socket numbers, a few well-known numbers were reserved for special purposes specific to the AppleTalk protocol itself. Apart from these, all application-level protocols were expected to use dynamically-assigned socket numbers at both the client and server.

Apple TalkCont

Protocol