SNA and DNA are proprietary computer networking architectures developed by IBM and Digital Equipment Corporation (DEC) respectively. SNA defines communication protocols and message formats for data exchange on IBM mainframe networks, while DNA supports both DEC proprietary protocols as well as standards-based protocols for interconnecting DEC systems. Both architectures define multiple layers of networking similar to the OSI model, with SNA having 7 layers and DNA defining protocols that operate at different layers like the data link, network, and transport layers.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
1K views11 pages
Sna Dna
SNA and DNA are proprietary computer networking architectures developed by IBM and Digital Equipment Corporation (DEC) respectively. SNA defines communication protocols and message formats for data exchange on IBM mainframe networks, while DNA supports both DEC proprietary protocols as well as standards-based protocols for interconnecting DEC systems. Both architectures define multiple layers of networking similar to the OSI model, with SNA having 7 layers and DNA defining protocols that operate at different layers like the data link, network, and transport layers.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11
SNA and DNA
System Network Architecture (SNA)
• SNA is a computer networking architecture developed by
IBM to provide a network structure for IBM mainframe, midrange, and personal computer systems. • SNA defines a set of proprietary communication protocols and message formats for the exchange and management of data on IBM host networks.
SNA is IBM’s proprietary networking architecture, developed in the mid 1970s. SNA describes general characteristics of computer hardware and software required for interconnection. Layer 1 Physical Control This deals with electrical, mechanical, and procedural characteristics of the media and interfaces to the physical media, and is similar to the OSI physical layer. Layer 2 Data Link Control Similar to the data link layer, SDLC is defined here to allow for communication. Layer 3 Path Control Similar to the network layer, flow control and routing are defined and function here. Layer 4 Transmission Control Similar to the transport layer, the transmission control layer provides a connection service from end to end that is reliable. Layer 5 Data Flow Control Request and response processing is done here (similar to the session layer). Layer 6 Presentation Services Resource sharing and data translation algorithms are performed here. Layer 7 Transaction Services Application services are provided through programs (similar to the application layer). Digital Network Architecture (DNA)
• DNA supports Digital Equipment Corporation
(DEC) proprietary protocols and standards- based protocols. • Products using DNA are referred to as DECnet products. DNA Protocols • Ethernet version 2 Uses CSMA/CD, coax cable, and is based on the 3 Mbps Xerox Research Ethernet protocol. Ethernet 2 frames are slightly different from the Ethernet IEEE/ISO frame format. • High-Level Data Link Control (HDLC) HDLC supports synchronous and asynchronous communication. It is a data link layer protocol and defines both the format of the data frames and the commands needed to establish frame transfer. • Digital Data Communications Message Protocol (DDCMP) Operates under asynchronous and synchronous communication and can be used in full- or half- duplex communication. • Connectionless Network Service (CLNS) Supported at the network layer, CLNS supports connection-oriented and connectionless network services. DNA Phase V (current version) uses CLNS. • Connection-Oriented Network Service (CONS) Functions at the network layer, but for CLNS is more often used.
• Connection Oriented Transport Protocol Specification ISO 8073. Used to provide reliable connections at the transport layer.
• Network Services Protocol (NSP) Provides a connection-oriented, flow-controlled service through subchannels.
• Session Control Responsible for providing an interface between applications and transport layer protocols. Provides the following proprietary functions: -> Address/name resolution -> Protocol stack selection -> Transport connection management -> Connection identifier addressing • FTAM and Data Access Protocol (DAP) ISO 8571. May be implemented differently by every vendor who writes FTAM applications. Used as a protocol for file services. DAP’s big difference compared to other protocols is its ability to access indexed files.
• Session Protocol Specification ISO 8327. Provides a negotiated connection establishment and release and half-duplex data transfer. This protocol can use more than one transport layer connection for each session. Tokens are used so a session’s dialog can be reset to any synchronization point.
• Abstract Notation Syntax One ISO 8824 (ASN.1) with ISO 8825 Basic Encoding Rules (BER). ASN.1 performs character code translation; BER defines rules for translating to and from ASN.1.
• Network Virtual Terminal Service (NVTS) Allows data to be translated to from local format to a network format before they are transmitted to the host. • Message Handling System (MHS) MAILbus Product Family and X.400. Provides specifications for DECnet message services. These are not protocols. MAILbus is a proprietary E-mail service developed by DEC. X.400 relates to how messages are stored and forwarded between different devices on an internetwork.
• Naming Service and X.500 Directory A portion of DNA that performs address/name resolution. X.500 is a directory service recommendation.