Internet Protocols (TCP/IP)
The Internet protocol suite (also commonly called the TCP/IP protocol suite) was originally developed by the United States Department of Defense (DoD) to provide robust service on large internetworks that incorporate a variety of computer types. In recent years, the Internet protocols constitute the most popular network protocols currently in use.
One reason for the popularity of TCP/IP is that no one vendor owns it, unlike the IPX/SPX, DNA, SNA, AppleTalk protocol suites, all of which are controlled by specific companies. TCP/IP evolved in response to input from a wide variety of industry sources. Consequently, TCP/IP is the most open of the protocol suites and is supported by the widest variety of vendors. Virtually every brand of computing equipment now supports TCP/IP. Much of the popularity of the TCP/IP protocols comes from their early availability on Unix. The protocols were built into the Berkeley Standard Distribution (BSD) Unix implementation. Since then, TCP/IP has achieved universal acceptance in the Unix community and is a standard feature on all versions of Unix.
One huge advantage of TCP/IP is that TCP/IP is required for communication over the Internet. One disadvantage is that the size of the protocol stack makes TCP/IP difficult to implement on some older machines. (Present-day PC models should have no problem running TCP/IP.) TCP/IP has traditionally been considered slower than other protocol stacks, but again, the power of the newer machines overcomes much of this difficulty. A large number of protocols are associated with TCP/IP.
Internet Protocol (IP)
The Internet Protocol (IP) is a connectionless protocol that provides datagram service, and IP packets are most commonly referred to as IP datagrams. IP is a packet-switching protocol that performs addressing and route selection. An IP header is appended to packets, which are transmitted as frames by lower-level protocols. IP routes packets through internetworks by utilizing dynamic routing tables that are referenced at each hop. Routing determinations are made by consulting logical and physical network device information, as provided by the Address Resolution Protocol (ARP). IP performs packet disassembly and reassembly as required by packet size limitations defined for the Data Link and Physical layers being implemented. IP also performs error checking on the header data using a checksum, although data from upper layers is not error-checked
Internet Protocol (IP)
Internet Control Message Protocol (ICMP)
Routing Information Protocol (RIP)
Open Shortest Path First (OSPF)
Transmission Control Protocol (TCP)
User Datagram Protocol (UDP)
Address Resolution Protocol (ARP)
Domain Name System (DNS)
File Transfer Protocol (FTP)
Simple Mail Transfer Protocol (SMTP)
Remote Terminal Emulation (TELNET)
Network File System (NFS)
BOOTP
Exterior Gateway Protocol (EGP)
Enhanced Interior Gateway Routing Protoco (EIGRP)
Routing Information Protocol II (RIP II)
NetBEUI
This protocol was first introduced by IBM in 1985. NetBEUI is a small and efficient protocol designed for use on a departmental LAN of 20 to 200 workstations. The original design assumed broader connectivity services could be added as the network grew by including gateways.
NetBEUI is a transport protocol that serves as an extension to Microsoft’s Network Basic Input/Output System (NetBIOS).Microsoft has supported the NetBEUI protocol in all of its networking products since Microsoft's first networking product, MS-Net, was introduced in the mid-1980s. Because NetBEUI was developed for an earlier generation of DOS-based PCs, it is small, easy to implement, and fast. It has powerful flow control and tuning parameters and has robust error detection.
Since NetBEUI was built for small, isolated LANs, however, it is non-routable, making it somewhat out of place in today’s diverse and interconnected networking environment.
Fortunately, the NDIS standard enables NetBEUI to coexist with other routable protocols. For instance, you could use NetBEUI for fast, efficient communications on the LAN segment and use TCP/ IP for transmissions that require routing
NetBIOS
NetBIOS is the Network Basic Input/Output System a high-level interface used by applications to communicate with NetBIOS-compliant transports such as NetBEUI. The network redirector, , is an example of a NetBIOS application.
The NetBIOS interface is responsible for establishing logical names on the network, establishing connections (called sessions) between two logical names on the network, and supporting reliable data transfer between computers that have established a session.
This Session-layer interface was developed by Sytek, Inc., for IBM's broadband computer network. At that time, NetBIOS was included on a ROM chip on the network adapter card. Sytek also developed a NetBIOS for IBM's token-ring network, this time implemented as a device driver. Several other vendors have since produced versions of this interface.
NetBIOS uses a unique logical name to identify a workstation for handling communications between nodes. A NetBIOS name is a unique alphanumeric name consisting of one to 15 characters (no other workstation on the network may have the same name as another computer or workgroup).
Communication between networked computers can also be in the form of a conversation. To carry on two-way communication between computers, NetBIOS establishes a logical connection, or session, between them. Once a logical connection is established, computers can then exchange data in the form of NetBIOS requests or in the form of a Server Message Block (SMBs).
AppleTalk
AppleTalk is the computing architecture developed by Apple Computer for the Macintosh family of personal computers. Although AppleTalk originally supported only Apple’s proprietary Local-Talk cabling system, the suite has been expanded to incorporate both Ethernet and Token Ring Physical layers. AppleTalk originally supported networks of limited scope. The AppleTalk Phase 2 specification issued in 1989, however, extended the scope of AppleTalk to enterprise networks. The Phase 2 specification also enabled AppleTalk to coexist on networks with other protocol suites.
The LocalTalk, EtherTalk, and TokenTalk Link Access Protocols (LLAP, ELAP, and TLAP) integrate AppleTalk upper-layer protocols with the LocalTalk, Ethernet, and Token Ring environments.
Datagram Deliver Protocol (DDP)
AppleTalk Transaction Protocol (ATP)
AppleTalk File Protocol (AFP)
Link Access Protocols (LAP)
AppleTalk Update-Based Routing Protocol (AURP)
Name Binding Protocol (NBP)
Printer Access Protocol (PAP)
Zone Information Protocol (ZIP)
Routing Table Maintenance Protocol (RTMP)
AppleShare is a client/server system for Macintosh. AppleShare provides three primary application services:
The AppleShare File Server uses AFP to enable users to store and access files on the network. It logs in users and associates them with network volumes and directories.
The AppleShare Print Server uses NBP and PAP to support network printing. NBP provides name and address information that enables PAP to connect to printers. The Apple-Share Print Server performs print spooling and manages printing on networked printers.
The AppleShare PC enables PCs running MS-DOS to access AppleShare services by running an AppleShare PC program.
Datagram Deliver Protocol (DDP)
Apple’s Datagram Deliver Protocol (DDP) is a Network layer protocol that provides connectionless service between two sockets. A socket is the AppleTalk term for a service address. A combination of a device address, network address, and socket uniquely identifies each process. DDP performs network routing and consults routing tables maintained by Routing Table Maintenance Protocol (RTMP) to determine routing. Packet delivery is performed by the data link protocol operating on a given destination network.
AppleTalk Transaction Protocol (ATP)
The AppleTalk Transaction Protocol (ATP) is a connectionless Transport layer protocol. Reliable service is provided through a system of acknowledgments and retransmissions. Retransmissions are initiated automatically if an acknowledgment is not received within a specified time interval. ATP reliability is based on transactions. A transaction consists of a request followed by a reply. ATP is responsible for segment development and performs fragmentation and reassembly of packets that exceed the specifications for lower-layer protocols. Packets include sequence numbers that enable message reassembly and retransmission of lost packets. Only damaged or lost packets are retransmitted.
AppleTalk File Protocol (AFP)
The AppleTalk File Protocol (AFP) provides file services and is responsible for translating local file service requests into formats required for network file services. AFP directly translates command syntax and enables applications to perform file format translations. AFP is responsible for file system security and verifies and encrypts logon names and passwords during connection setup.
Link Access Protocol (LAP)
LAP works at the Data Link Layer, receiving packets of information and converting them into the proper signals for your network board.
Three LAPs are
LLAP (LocalTalk* LAP). Allows the LocalTalk hardware built into Macintosh computers to communicate on LocalTalk networks.
ELAP (Ethernet LAP). Allows a Macintosh computer with an installed Ethernet board to communicate with devices on AppleTalk networks.
TLAP (Token Ring LAP). Allows devices using IBM* token ring technology to communicate with devices on AppleTalk networks.
ELAP and TLAP use AppleTalk Address Resolution Protocol (AARP) to translate AppleTalk node addresses into addresses that can be used on Ethernet or token ring devices.
AppleTalk Update-Based Routing Protocol (AURP)
AURP operates like RTMP, but sends updates only when a change occurs on the network.
The principal features of AURP are
AppleTalk tunneling in TCP/IP. Enables two AppleTalk networks to be connected through a TCP/IP network.
Update-based routing through tunnels. Reduces the amount of bandwidth by sending updates to peer routers only when network routing information changes, rather than sending periodic broadcasts of the routing table.
Name Binding Protocol (NBP)
Each network process or device has a name that corresponds to network and node addresses. AppleTalk uses an NBP to conceal those addresses from users.
The NBP converts the name of a network object provided by a user (like a printer) into a network address that the Link Access Protocol can locate.
Printer Access Protocol (PAP)
When a network node prints to a network printer, the PAP uses NBP to prepare a path to the requested printer
Zone Information Protocol (ZIP)
In a large internetwork, all AppleTalk nodes are divided into groups, called zones, for ease of locating an object.
The NBP uses ZIP to assist in finding the correct network and node addresses from a Zone List.
Routing Table Maintenance Protocol (RTMP)
RTMP is the routing protocol used by AppleTalk. It is very similar to RIP. When many small networks are connected, a router connects them together in an internetwork. The router maintains the addresses of all networks connected to the internetwork.
Information about other networks is stored in routing tables. Routers update routing tables by using the RTMP to communicate with each other.
