OIT STANDARDS
Document Type:
Collection:
Document Number (FOIA) /ESDN (CREST):
CIA-RDP88G01332R000800960003-6
Release Decision:
RIPPUB
Original Classification:
U
Document Page Count:
21
Document Creation Date:
December 27, 2016
Document Release Date:
November 21, 2012
Sequence Number:
3
Case Number:
Publication Date:
December 24, 1986
Content Type:
MEMO
File:
Attachment | Size |
---|---|
![]() | 1.1 MB |
Body:
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
ROUTING ANDTRANSMITTAL SUP Date I 212
TO: symbol,
1Whies
43 ?
ii 04'6,
Deb
1.9611
L=6,611. room number,
ANINY/Post) ,
L AbDA
2, TYD A
Vf?t
..... 4
30ratg
&
4.
I.
Action
File
dilate ant Return
Approval
For Clearance
Per Conversation
As Requested
, For Correction
Pfilimfe lie*
Circulate
For Your Infoemation
See Me
;eminent
Investigate
Signature
Coordination
Justify
?
Tkese s-i-K4Aret.r Ard. s-1-7,4ei,e..d.r AP
rertie"i a -1 tr.iUJ' re. ../.0%*4 ovP l't 'yr&
61.-v 1C A v.k ilk; o-h. . AU art
NI Art ,n s?ret frfl. .
?.1.1%4Yli
DO NOT use this form as a RECORD of approvals, concurrences, disposals,
clearances, and similar actions
FROM: (Name, ore. symbol. Avow/Post)
Room No.?Didg.
Phone No.
1041-102 OPTIONAL FORM 41 (Rev. 7-76)
hA
,U.S.GP 0..1983 -421-529/320 nut fill C.1% i01-11.20$
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
TRANSMITTAL SLIP
YO: DDA
ROOM NO.
7D24
BUILDING
Has.
REMARKS:
FROM:
D/OIT
ROOM NO.
2D00
BUILDING
Hqs .
EXTENSION
FORM NO. ?
1 FEB 56 241
REPLACES FORM 36-8
WHICH MAY BE USED.
(47)
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
MEMORANDUM FOR: Executive Director
VIA:. Deputy Director for Administration
FROM: Edward J. Maloney
Director of Information Technology
SUBJECT: OIT Standards
OIT 1053-86
24 DEC 1986
f16
1. Attached are OIT Statements of Direction for Network Architecture and
Terminal and Workstation Protocol, and OIT Standards for Document Interchange
Format, Electronic Mail Interchange, 3270 Protocol for Terminals and
Workstations and Database Management System Data Language.
2. These Statements of Direction and Standards have received unanimous
approval from the Customer/Standards Committee. I would like to thank the
members of the committee, whose assistance and patience in the coordination of
multiple drafts were invaluable.
3. I have personally reviewed all of these Statements of Direction and
Standards, and I believe that their adoption will increase the effectiveness
of Agency computing by improving our ability to share information through
interconnected Agency computing systems and to utilize vendor-developed
solutions to our problems. Therefore, I adopt them as OIT Statements of
Direction and OIT Standards.
4. These Statements of Direction and Standards will be formally
published and we will prepare a Headquarters Notice announcing their
availability by early February 1987. In addition, we will brief ADP Control
Officers and coordinate with the Office of Logistics to develop language
suitable for inclusion in Agency Requests for Proposal and resulting
contracts. We will also provide consulting and assistance to our customer,
contractor, and vendor communities to ensure an understanding of and
compliance with the Standards.
Attachments:
As Stated
Edward J. Maloney
-
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
UNCLASSIFIED
OIT Statement of Direction
Network Architecture
it
10/27/86
t. Summary
1.1 This is the OIT statement of direction for network architecture,
covering the overall architecture of connections of computer systems,
workstations and terminals with OIT mainframe computer systems. The
direction is System Network Architecture (SNA), an IBM-defined network
architecture.
1.2 It is OIT's ultimate intent to adopt the Open Systems Interconnect
(OSI) network architecture, an international standard, although OIT's
current plan is to implement SNA, as explained in this Statement. The
reasons for the adoption of SNA as the present direction, and the status
of OSI and OIT's plans for OSI, are presented here.
1.3 The need for this statement of direction is discussed, applicable
candidates are reviewed, and the selected approach is presented.
Intentions regarding the applicability of this direction and planned OIT
standards and implementation responsibility are given.
2. Need for this Statement of Direction
2.1 OIT is presently defining strategic interfaces dealing with OIT
computer systems. However, those interfaces cannot be defined
independently; choices of one interface can affect the choices that can
be made for another interface. There are presently two candidate
network architectures, the Open System Interconnect (OSI) model defined
by the Comite Consultatif Internationale Telegraphique et Telephonique
(CCITT), and SNA as defined by IBM.
2.2 The choices of interfaces such as form of document, mail systems,
workstation and terminal connection must all be made within a single
network architecture. Thus, there is a need to select a network
architecture.
2.3 OIT presently does not employ a single network architecture; rather,
selections of communications methods are based on the specific
requirements for each situation. However, the present experience
indicates a need for a set of integrated network software. The network
control features that become available with the adoption of a single
network architecture are one benefit of such an approach; another
benefit is the ability to make wider use of standard software products.
The interoperability of OIT systems with other networks will also be
improved by the use of a single OIT network architecture.
2.4 The adoption of a network architecture direction will provide a
framework for the planning of OIT systems, as well as enable the
selection of an integrated, functionally complete set of products based
on that architecture.
1
?MOTACCTVT011
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
UNCLASSIFIED
OIT Statement of Direction
Network Architecture
2.5 OIT customers and vendors also need a clear statement of OIT's
long-term direction with respect to network architectures, so that they
can make appropriate plans for their systems that will interface with
dIT systems.
3. Candidate Standards
3.1 The leading candidate is SNA from IBM. SNA is completely supported
throughout IBM's product line. Because of IBM's market position, many
vendors other than IBM have developed SNA interfaces. There are-elso a
growing number of "bridge" products, developed specifically to permit
non-IBM products to interface to SNA networks. Thus, SNA is a network
architecture that has become a de facto industry standard.
3.2 The OSI approach has the advantage of being defined by an
established, vendor-independent standards organization. There is
considerable activity to complete the definition of the OSI architecture
and develop OSI products. There is also a clear tendency among
Government organizations to adopt the OSI architecture. However, at
this time the OSI model as defined has a large number of open areas, and
there is not complete set of products implementing the OSI model
available to run with OIT's IBM mainframe computer systems.
3.3 Although the OSI and SNA choices present a clear dichotomy at this
time, it is not expected that the differences between the two approaches
will continue to be as great as they are today. There are industry
trends toward the convergence of the OSI and SNA network architectures,
as well as bridge products to connect the two network types. There is
also some movement on IBM's part toward OSI support. Thus, the
selection of SNA as a single network architecture at this time is
expected to facilitate the later adoption of the OSI network model, by
providing a consistent base for the transition.
4. Direction
4.1 SNA is OIT's direction. Although SNA is an architecture developed
by a single vendor rather than a standard promulgated by an official
standards body, its adoption will not increase our reliance on IBM as a
supplier. In fact, because of its wide vendor acceptance, its adoption
will tend to increase our ability to integrate a multi-vendor computer
environment.
4.2 OIT intends to change its direction to OSI when mature, fully
functional OSI products become available as industry mainstream
products. There is no way to estimate how quickly that change in
direction will occur, however, or how the transition to OSI will be
accomplished.
4.3 For further information about SNA and OSI, see the references.
5. Applicability
2
iMMARRIPM
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
UNCLASSIFIED
OIT Statement of Direction
Network Architecture
it
5.1 OIT's intention is to define a set of strategic interfaces within
the SNA architecture, .such as electronic mail interchange, document
fbrmat, terminal and workstation connectivity. As these interfaces are
defined and implemented, all connections between computer systems,
workstations and terminals and OIT mainframe computer systems will be
required to conform to interface standards within SNA.
5.2 This statement of direction is provided so that OIT customers and
vendors can understand OIT's future direction, and make appropriate
plans for future systems that interface with OIT systems.
6. Implementation
6.1 OIT will develop a set of standards for strategic interfaces within
the SNA architecture.
6.2 SNA includes a very large product set; OIT will select products from
that set to provide network services. Not all products that are
compatible with SNA will necessarily be supported by OIT.
6.3 OIT will continue to monitor the progress of the OSI architecture.
7. References
7.1 Systems Network Architecture Reference Summary, IBM Corporation,
Technical Publication GA27-3136.
7.2 Systems Network Architecture Technical Overview, IBM Corporation,
Technical Publication GC30-3073.
3
UNCLASSIFIED
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
UNCLASSIFIED
OIT Standard
Electronic Mail Interchange
it
10/6/86
1% Summary
1.1.This is the OIT Standard for protocols and data streams used for
electronic sail interchange between OIT mainframe computer systems and
other computer systems and between OIT mainframe computer systems and
workstations. The standard for transfers between OIT mainframe computer
systems and other computer systems is IBM's System Network Architecture
Distribution Services (SNADS); the standard for transfer between OIT
mainframe computer systems and workstations is IBM's Document
Interchange Architecture (DIA).
1.2 This standard covers the protocols used to exchange electronic mail.
1.3 The need for this standard is discussed, applicable potential
standards are reviewed, and the standard is presented. The
applicability, effective date and implementation of the standard are
specified. References are provided.
2. Need for this Standard
2.1 This standard is needed because of the adoption of workstations
instead of terminals and because of the present and planned use of
departmental-level computers with mail systems.
2.2 Workstation computer systems are increasingly being used in place of
terminals within the Agency. Workstations offer the potential of using
computing capability on the user's desk to offer an efficient,
user-friendly interface to a mail system, as well as shifting part of
the workload from OIT mainframes to the workstation. However, an
interface is required that permits the interchange of mail between
cooperating programs in the mainframe and workstation.
2.3 The Agency has operational and planned computer systems that include
electronic mail systems. Among these are Wang networks employed
throughout the DDS&T and DDO, the Improved NPIC System now under
development and the FBIS AFS System. In each case, these computer
systems provide electronic mail services to their users, but these mail
systems cannot exchange mail with each other. Electronic mail is
becoming increasingly important for an ever-wider group of
administrative and other services, as well as an important
communications method for Agency personnel. The need for Agency-wide
access to electronic mail service is apparent. The adoption of a
standard for the protocols and data streams that are employed for the
exchange of electronic sail between Agency computer systems will enable
mail interfaces to be developed that interconnect these computer
systems.
2.4 Using the IBM approach, the workstation-to-mail system interface and
the mail system-to-mail system interface are performed by products
meeting different specifications. The workstation-to-mail system
1
TTMFITAOOTVTOrk
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
UNCLASSIFIED
OIT Standard
Electronic Mail Interchange
it
interface allows a single user to log on, pick up and send mail, and log
off. That interface can be used as a mail system-to-mail system
interface, but it would be cumbersome, since one mail system would have
tb log on, pretending to be each of its users, ask for mail, and log
off. A more appropriate mail system-to-mail system interface allows one
mail system to log on and pick up all mail for all of its users in a
single operation.
3. Candidate Standards
3.1 There are several candidate standards. IBM's System Network
Architecture includes SNADS, a mail system-to-mail system interface, and
DIA, a user-to-mail system interface. The set of international
standards developed by the CCITT includes a standard for electronic
mail, X.400.
3.2 X.400 cannot be used with IBM mainframe systems at this time because
it assumes end-to-end X.25 transport services, that are not available
for IBM mainframes. In addition, it is not mature enough for adoption
as a standard at this time. There are still several areas that are in
active consideration for modification, and products based on X.400 are
not widely available.
3.3 The SNA standards for electronic mail interchange, DIA and SNADS,
are specified and have been implemented successfully. They have also
been accepted by a variety of vendors of computer systems, so that DIA
and SNADS are becoming de facto industry standards. These standards are
supported by IBM on MVS and VM, by Digital Equipment Corporation
minicomputers, Data General minicomputers, Wang systems and other
vendors. No other standard for exchange of electronic mail is supported
by such a large number of vendors.
it Standard
4.1 SNADS is the standard for electronic mail interchange between mail
systems, and DIA is the selected standard for mail interchange between a
mail system and a workstation.
4.2 Although SNADS and DIA are product architectures from a single
vendor, rather than a standard promulgated by an official standards
organization, their adoption will not increase our reliance on IBM as a
supplier. In fact, because of their wide vendor acceptance, this
standard will improve our ability to integrate a multi-vendor office
systems environment.
5. Test Standard
5.1 The current version of the IBM product DISOSS is the test standard
for compliance with this standard.
6. Applicability of the Standard
6.1 This standard is applicable to all electronic mail transfers between
2
HtirLARRIFTWI
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
UNCLASSIFIED
OIT Standard
Electronic Mail Interchange
OIT mainframe computer systems and workstations and computer systems.
All such transfers will take place using the protocols and data streams
of SNADS and DIA.
6.2 This standard restricts the acquisition of computer systems that
will exchange electronic mail with OIT mainframe computer systems to
those that implement SNADS. Every computer system that is acquired that
is to make electronic mail exchanges with OIT mainframe computer systems
must conform to this standard.
6.3 Existing connections that do not comply with this standard are
exempt from compliance until major upgrades are made. When a major
upgrade is made to any connection that is exempt from this standard,
that connection must be brought into compliance.
6.4 New connections with OIT systems for exchange of electronic mail
will not be made unless the connecting systems conform to this standard.
7. Effective Date
7.1 This standard is effective immediately.
8. Implementation
8.1 Before any electronic mail system is connected to OIT mainframe
computer systems, the sponsoring component must provide a demonstration
of compliance with this standard.
8.2 OIT will establish appropriate validation criteria and provide a
point of contact for demonstrating product compliance with this
standard.
8.3 OIT will furnish programs to interface with connecting computer
systems according to SNADS and DIA protocols and data streams as
required.
9. References
9.1 Document Interchange Architecture: Concepts and Structures, IBM
Publication # SC23-0759.
9.2 SNADS Format and Protocol Reference, IBM Publication #SC30-3112.
9.3 Distributed Office Support System/370, Version 3.2: Architecture
Reference for Document Interchange Units and SNADS Interchange Units.
3
UNCLASSIFIED
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
?????
UNCLASSIFIED
OIT Standard
Document Interchange Format
12/19/86
11. Summary
1.1. This is the OIT Standard for the form of a document exchanged
between QIT mainframe computer systems and other computer systems. The
standard is Document Content Architecture (DCA), as defined by IBM.
This standard covers documents that consist of text only.
1.2 The need for this standard is discussed, applicable potential
standards are reviewed, and the recommended standard is presented. The
applicability of the standard and OIT implementation responsibility are
given.
2. Need.for a Document Format Standard
2.1 Using Agency word processing systems, there are today a number of
different methods that can be employed to produce a document. These
include HBWP, AIM, Wang word processors (several types), NBI word
processors, personal computers (principally IBM) using a variety of
commercial word processing programs, and soon IBM 3270/AT's running PC
word processing programs.
2.2 With these different methods of document composition, in some cases
a document produced using one method cannot be edited with another. In
other cases, a document produced using one word processor must be
transformed into a text file before being edited by another, resulting
in the loss of formatting information. This problem will become more
severe when personal computer word processors are used; without a
standard form of document, it may be impossible for a Delta Data user to
edit a document produced on a 3270/AT running OIT-sanctioned word
processing software.
2.3 The adoption of a standard document format, and the implementation
of programs to transform documents from all present document preparation
systems into that standard form and back, will allow for document
interchange among all OIT-sanctioned word processing methods (note,
however, that some loss of formatting controls following a
transformation will occur). In addition, through the implementation of
programs to print documents in DCA format, documents produced on any
OIT-supported word processor will be printable on any OIT-supported
printer.
3. Candidate Standards
3.1 The leading candidate standard is Document Content Architecture
(DCA) from IBM. Because of IBM's support for this standard throughout
their product line, and because DCA is the first widely applicable
document standard that has been completely implemented, it is rapidly
becoming a de facto industry standard.
3.2 DCA is supported by a variety of microcomputer and workstation word
1
TTUrTAOCTVTOT
Declassified in Part - Sanitized Copy Approved for Release 2012/11/21: CIA-RDP88G01332R000800960003-6
Declassified in Part- Sanitized Copy Approved forRelease2012/11/21 : CIA-RDP88G01332R000800960003-6
UNCLASSIFIED
OIT Standard .?
Document Interchange Format
processing programs, including Multimate, Microsoft Word and Alia. DCA
Is also supported by several minicomputer systems from the leading
office systems vendors,. including DEC and Data General. Many software
ind minicomputer suppliers who do not already support DCA are announcing
their intention to support it.
3.3 A competing alternative, in use at the Agency for some time, is
Waterloo Script. Waterloo Script is used by VM installations for VM
word processing and document exchange. Present OIT systems support the
creation, ?