New Productsrec overy of received signals, and interfacingthe communications channel to any processorand memory used to implement higher-levelprotocol functions. Implementations of thislayer encompass hardware interface devicesand device drivers in operating systems, aswell as communic ations hardware suc h asmodems, transceivers, and the physical channelsthemselves.Protocols for the physical layer are rudimentary,emphasizing the specification of electricalinterfacing parameters. No special physical layerspecifications have been developed for DNA.Instead, it relies on industry standards for thephysical layer, thereby ensuring that DECnetproducts can operate over available communicationstechnologies and infrastructures. Physicallayer standards supported by DNA for wide areanetworks include the EIA RS-232C and RS-423specifications, and the CCITT V.24 and X.25Level 1 specific ations. Physical layer standardssupported by the DNA architecture forLANs include two baseband implementationsof ThinWire Ethernet, the original18 and thethinwire2 3 specifications, and a broadband24implementation.Future Directions fo r the DNAArchitectureFor ten years, DNA has evolved in four maindimensions: network applications, communicationstechnologies, network size and scale, anddiversity of supported computer systems. Thisability to evolve independentl y along fourdimensions has proven to be one of the principalbenefits of the architecture. It is reasonable toassume that evolution along these lines will continue.Local area and wide area communicationstechnologies continue to evolve, typically resul ting in higher communications data rates. Newapplications for computer networks and newapplications protocols will also continue toevolve. The DNA architecture will continue toaccommodate these trends.The 16-bit node addresses used by DNA PhaseIV currently limit the size of DECnet networks. ·<strong>Digital</strong>'s own internal DECnet network is nearingthe limits of this address space; over 10, 000nodes are currently registered. Clearly, the architecturemust be extended to support morenodes. From our experience with this network,there are two separate reasons why networkscontinue to grow rapidly. First, the availability oflow-cost computer systems allows individuals toown network nodes rather than sharing a singletimesharing system. Second, certain applications,such as network mail, need to operateacross whole organizations. This breadth makes asingle company-wide network, rather than separateindependent networks, highly desirable.Indeed, there is even a need for networks thatspan multiple organizations, adding further tothe problems of sc ale, complicating networkmanagement requirements, and creating newproblems of network security. DNA will have toevolve to adapt to much larger and more diversenetworks.As computer networks have beco me larger,users have developed increasing requirementsfor networks that interconnect computer systemsfrom multiple vendors. The International StandardsOrganization (ISO) has been developingstandards for such networks through their OpenSystems Interconnection program (OSI) . The OSlreference model defines a network architecturesimilar in many respec ts to that of DNA. 25 Mostmajor computer vendors, ncluding <strong>Digital</strong>, haveannounced their support tor OSI and are beginningto deliver OSI network products. <strong>Digital</strong> hasannounced its strategy to incorporate OSI protocolsinto its networking products, integratingthem into the DNA arc hitecture. Future versionsof the DNA arc hitec ture will correspondto a mixture of standardized and proprietaryprotocols.References1. DECnet <strong>Digital</strong> Ne twork Architecture(Phase IV) General Description (Bedford:<strong>Digital</strong> Equipment Corporation,Order No. AA-149A-TC, 1982) .2. DECnet <strong>Digital</strong> Network Architecture(Phase IV) Network Management FunctionalSp ecification (Bedford: <strong>Digital</strong>Equipment Corporation, Order No.AA-X437A-TK, 1983).3. DECnet <strong>Digital</strong> Network Architecture(Phase IV) Maintenance Op erationsFu nctional Specification (Bedford: <strong>Digital</strong>Equipment Corporation, Order No.AA-X436A-TK, 1983).4. N. La Pelle, M. Seger, and M. Sylor, "TheEvolution of Network Management Products," <strong>Digital</strong> <strong>Technical</strong> journal (<strong>September</strong>1986, this issue): 117-128.<strong>Digital</strong> TecbnicalJournalNo. 3 <strong>September</strong> 198623
A <strong>Digital</strong> Network Architecture Overview5. DECnet <strong>Digital</strong> Network ArchitectureData Access Protocol (DAP) FunctionalSpecification (Bedford: <strong>Digital</strong> EquipmentCorporation, Order No. AA-K177A-TK,1983).6. J. Morency, D. Porter, R. Pitkin, and D.Oran , ''The DECnetjSNA GatewayProduct - A Case Study in Cross VendorNetworking,'' <strong>Digital</strong> <strong>Technical</strong> jo urnal(<strong>September</strong> 1986, this issue) : 35-53.7. P. Beck and J. Krycka, "The DECnet-VAXProduct -An Integrated Approach to Networking,"<strong>Digital</strong> <strong>Technical</strong> journal (<strong>September</strong>1986, this issue) : 88-99.8. DEC net <strong>Digital</strong> Network Architecture SessionControl Layer Functional Specification(Bedford: <strong>Digital</strong> Equipment Corporation,Order No. AA-K 182A-TK, 1980) .9. DECnet <strong>Digital</strong> Network Architecture(Phase IV) NSP Functional Specification(Bedford: <strong>Digital</strong> Equipment Corporation,Order No. AA-X439A-TK, 1983) .10. C. Sunshine and Y. Dalal, "ConnectionManagement in Transport Protocols,"Computer Networks , vol . 2 (December1978): 454-473.11. W. Lai, "Protocol Traps in Computer Networks-A Catalog,'' IEEE Tra nsactionson Communication , vol . COM-30, no. 6oune 1982): 1434-1449.12. DECnet <strong>Digital</strong> Network Architecture(Phase IV) Routing Layer FunctionalSpecification (Bedford: <strong>Digital</strong> EquipmentCorporation, Order No. AA-X43 5A-TK,1983).13. L. Pouzin, "Presentation and Major DesignAspects of the Cyclades Computer Net-.work," Th ird IEEEjA CM Data CommunicationSymposium (November 1973):80-87.14. R. Jain and W. Hawe, "Performance Analysisand Modeling of <strong>Digital</strong>'s NetworkingArchitecture," <strong>Digital</strong> <strong>Technical</strong> journal(<strong>September</strong> 1986, this issue) : 25-34.15. DECnet <strong>Digital</strong> Network Architecture<strong>Digital</strong> Data Communications MessageProtocol (DDCMP) Functional Specification,Version 4. 1. 0 (Bedford: <strong>Digital</strong>16.17.18.19.20.21.22.23.24.25.Equipment Corporation, Order No.AA-K175A-TK, 1984) .CCITT Recommendation X. 25, CCITTYellow Book , vol. VIII.2 (Geneva: lnternationalTelecommunications Union, 1981).Standard ISO 8208 fo r Information ProcessingSystems, "X.25 Packet Level Protocolfor Data Terminal Equipment," InternationalStandards Organization ( 198 5) .The Ethernet: A Local Area Network, DataLink Layer and Physical Layer Specifications,Version 2. 0 (<strong>Digital</strong> Equipment Corporation,Intel Corporation, and XeroxCorporation, Order No. AA-K759B-TK,1982).IEEE Project 802 Local Area NetworkStandards , "IEEE Standard 802.3CSMA/CD Access Method and PhysicalLayer Specifications," Approved IEEE Standard802.3-1985, ISO/DIS 8802/3 Ouly1983).J. Schoch and J. Hupp, "Measured Performanceof an Ethernet Local Area Network,''Communications of the ACM, vol . 23,no. 12 (December 1980) : 711-721.F. Tobagi and B. Hunt, "Performance Analysisof Carrier Sense Multiple Access withCollision Detection," Computer Networks, vol . 4, no. 5 (October/November1980): 245-259.W. Hawe, M. Kempf, and A. Kirby, "TheExtended Local Area Network Architectureand LANBridge 100," <strong>Digital</strong> <strong>Technical</strong>jo urnal (<strong>September</strong> 1986, this issue) :54-72.IEEE Project 802 Local Area Networks ,"Medium Attachment Unit and BasebandMedium Specifications, 1 OBASE2," IEEEP802.3/83j0.21E, Section 10.IEEE Project 802 Local Area Networks ,"Broadband Medium Attachment Unit andBroadband Medium Specifications," IEEEwP802.3j84j0.46B, Section 11.Standard ISC 7498 for Information ProcessingSystems , "Open International StandardsOrganization ( 1982).24. <strong>Digital</strong> <strong>Technical</strong> JournalNo. 3 <strong>September</strong> 1986