Sunday, February 14, 2010

History Of OSI Model

History And Development Of The OSI Model
steven parks
osi history and development
5/22/07

The history of the development of the OSI model is a little-known story. Much of the work on the design of OSI was done by a group at Honeywell Information Systems, headed by Mike Canepa, with Charlie Bachman as the principal technical member. This group was organized within Honeywell, with advanced product planning and with the design and development of prototype systems.In the early and mid '70s, the interest of Canepa's group was mainly on database design and then distributed database design. By the mid-70s, it become clear that to support database machines, distributed access, and the like, a structured distributed communications architecture would be needed. The group studied some of the existing solutions, including IBM's system network architecture (SNA), the work on protocols being done for ARPANET, and some of the concepts of presentation services being developed for standardized database systems. The result of this effort was the development by 1977 of a seven-layer architecture known as the distributed systems architecture (DSA).Bachman and Canepa participated in ANSI meetings and presented their seven-layer model. This model was chosen as the only proposal to be submitted to the ISO subcommittee. When the ISO group met in Washington DC in March of '78, the Honeywell team presented their solution. An agreement was reached at that meeting that this layered architecture would satisfy most requirements of OSI, and had the ability to be expanded later to meet new requirements. A provisional version of the model was published in March of '78. The next version, with some minor adjustments, was published in June of '79 and eventually standardized. The resulting OSI model is essentially the same as the DSA model developed in 1977.

Why a layered model?
>reduces complexity
>standardizes interfaces
>gaurantees interoperablity
>accelerates evolution
>simplfies teaching and learning
PRESENTATION LAYER PROTOCOLS
AFP (Apple Filing Protocol)
ASCII (American Standard Code for Information Interchange)
EBCDIC (Extended Binary Coded Decimal Interchange Code )
ICA (Independent Computing Architecture, the Citrix system core protocol)
LPP (Lightweight Presentation Protocol)
NCP (NetWare Core Protocol)
NDR (Network Data Representation)
XDR (eXternal Data Representation)
X.25 PAD (Packet Assembler/Disassembler Protocol)

APPLICATION LAYER PROTOCOLS

9P, (Plan 9 from Bell Labs distributed file system protocol)
AFP, (Qaisar Javeed)
APPC, (Advanced Program-to-Program Communication)
AMQP, (Advanced Message Queuing Protocol)
BitTorrent
Atom Publishing Protocol
BOOTP, (Bootstrap Protocol)
CFDP, (Coherent File Distribution Protocol)
DDS, (Data Distribution Service)
DHCP, (Dynamic Host Configuration Protocol)
DeviceNet
DNS, (Domain Name System (Service) Protocol)
eDonkey
ENRP, (Endpoint Handlespace Redundancy Protocol)
FastTrack (KaZaa, Grokster, iMesh)
Finger, (User Information Protocol)
Freenet
FTAM, (File Transfer Access and Management)
FTP, (File Transfer Protocol)
Gopher, (Gopher protocol)
HL7, (Health Level Seven)
HTTP, (HyperText Transfer Protocol)
H.323, (Packet-Based Multimedia Communications System)
IMAP, ( IMAP4, Internet Message Access Protocol (version 4) )
IRCP, (Internet Relay Chat Protocol)
Kademlia
LDAP, (Lightweight Directory Access Protocol)
LPD, (Line Printer Daemon Protocol)
MIME (S-MIME), (Multipurpose Internet Mail Extensions and Secure MIME )
Modbus
Netconf
NFS, (Network File System)
NIS, (Network Information Service)
NNTP, (Network News Transfer Protocol)
NTCIP, (National Transportation Communications for Intelligent Transportation System Protocol)
NTP, (Network Time Protocol)
OSCAR, (AOL Instant Messenger Protocol)
PNRP, (Peer Name Resolution Protocol)
POP, POP3, (Post Office Protocol (version 3) )
RDP, (Remote Desktop Protocol)
Rlogin, (Remote Login in UNIX Systems)
RPC, (Remote Procedure Call)
RTP, (Real-time Transport Protocol)
RTPS, (Real Time Publish Subscribe)
RTSP, (Real Time Streaming Protocol)
SAP, (Session Announcement Protocol)
SDP, (Session Description Protocol)
SIP, (Session Initiation Protocol)
SLP, (Service Location Protocol)
SMB, (Server Message Block)
SMTP, (Simple Mail Transfer Protocol)
SNMP, (Simple Network Management Protocol)
SNTP, (Simple Network Time Protocol)
SPTP, (Secure Parallel Transfer Protocol)
SSH, (Secure Shell)
SSMS, (Secure SMS Messaging Protocol)
TCAP, (Transaction Capabilities Application Part)
TDS, (Tabular Data Stream)
TELNET, (Terminal Emulation Protocol of TCP/IP)
TFTP, (Trivial File Transfer Protocol)
TSP, (Time Stamp Protocol)
VTP, (Virtual Terminal Protocol)
Waka, (an HTTP replacement protocol)
Whois (and RWhois), (Remote Directory Access Protocol)
WebDAV
X.400, (Message Handling Service Protocol)
X.500, ( Directory Access Protocol (DAP) )
XMPP, (Extensible Messaging and Presence Protocol)

Thursday, February 4, 2010

About The Apple Talk

APPLE TALK
AppleTalk, a protocol suite developed by Apple Computer in the early 1980s, was developed in conjunction with the Macintosh computer. AppleTalk's purpose was to allow multiple users to share resources, such as files and printers. The devices that supply these resources are called servers, while the devices that make use of these resources (such as a user's Macintosh computer) are referred to as clients. Hence, AppleTalk is one of the early implementations of a distributed client-server networking system. This chapter provides a summary of AppleTalk's network architecture.
AppleTalk was designed with a transparent network interface. That is, the interaction between client computers and network servers requires little interaction from the user. In addition, the actual operations of the AppleTalk protocols are invisible to end users, who see only the result of these operations. Two versions of AppleTalk exist: AppleTalk Phase 1 and AppleTalk Phase 2.


AppleTalk Phase 1, which is the first AppleTalk specification, was developed in the early 1980s strictly for use in local workgroups. Phase 1 therefore has two key limitations: its network segments can contain no more than 127 hosts and 127 servers, and it can support only nonextended networks.

AppleTalk Phase 2, which is the second enhanced AppleTalk implementation, was designed for use in larger internetworks. Phase 2 addresses the key limitations of AppleTalk Phase 1 and features a number of improvements over Phase 1. In particular, Phase 2 allows any combination of 253 hosts or servers on a single AppleTalk network segment and supports both nonextended and extended networks.
AppleTalk Network Components
AppleTalk networks are arranged hierarchically. Four basic components form the basis of an AppleTalk network: sockets, nodes, networks, and zones. Below figure illustrates the hierarchical organization of these components in
an AppleTalk internetwork. Each of these concepts is summarized in the sections that follow.

Figure: The AppleTalk internetwork consists of a hierarchy of components.

Sockets
An AppleTalk socket is a unique, addressable location in an AppleTalk node. It is the logical point at which upper-layer AppleTalk software processes and the network-layer Datagram-Delivery Protocol (DDP) interact. These upper-layer processes are known as socket clients. Socket clients own one or more sockets, which they use to send and receive datagrams. Sockets can be assigned statically or dynamically. Statically assigned sockets are reserved for use by certain protocols or other processes. Dynamically assigned sockets are assigned by DDP to socket clients upon request. An AppleTalk node can contain up to 254 different socket numbers. Figure illustrates the relationship between the sockets in an AppleTalk node and DDP at the network layer.
Figure :
Socket clients use sockets to send and receive datagrams.



Nodes
An AppleTalk node is a device that is connected to an AppleTalk network. This device might be a Macintosh computer, a printer, an IBM PC, a router, or some other similar device. Within each AppleTalk node exist numerous software processes called sockets. As discussed earlier, the function of these sockets is to identify the software processes running in the device. Each node in an AppleTalk network belongs to a single network and a specific zone.

Networks
An AppleTalk network consists of a single logical cable and multiple attached nodes. The logical cable is composed of either a single physical cable or multiple physical cables interconnected by using bridges or routers. AppleTalk networks can be nonextended or extended.