As per Relevance of the word available, we have this rfc below:
Network Working Group V.
Request for Comments: 1169
K.
August 1990
Explaining the Role of
1. Status of this
This informational RFC represents the official view of the
Activities Board (IAB), after coordination with the
Networking Council (FNC). This RFC does not specify a standard
Distribution of this memo is unlimited
Table of
1. Status of this Memo........................................... 1
2. Abstract...................................................... 2
3. Introduction.................................................. 2
4. Acknowledgements.............................................. 3
5. GOSIP Background.............................................. 3
6. Understanding GOSIP........................................... 4
6.1. Applicability............................................... 4
6.1.1. Procurement Vs. Transition................................ 5
6.1.2. Small Network Add-on Vs. Major Upgrade.................... 5
6.1.3. OSI Incompleteness........................................ 5
6.2. Exclusivity................................................. 5
6.3. Implementation.............................................. 6
6.4. Waivers..................................................... 6
6.5. Enforcement................................................. 7
7. Role of the IETF in Support of OSI............................ 7
8. Role of the Internet Infrastructure Agencies
Support of OSI................................................ 7
9. Role of the Internet Using Agencies in
Application of OSI............................................ 7
10. Summary...................................................... 8
11. References................................................... 9
12. Appendix -- To Obtain GOSIP Documents........................ 9
12.1 GOSIP....................................................... 9
12.1.1 GOSIP Version 1........................................... 9
12.1.2 GOSIP Version 2........................................... 10
12.2 NIST Workshop for Implementors of OSI Documents............. 11
12.2.1 SIA, Version 1............................................ 11
12.2.2 SIA, Version 2............................................ 12
12.2.3 WIA (August, 1989)........................................ 13
Cerf & Mills [Page 1]
RFC 1169 Explaining the Role of GOSIP August 1990
12.3 GOSIP Users' Guide.......................................... 13
12.4 Addresses/Telephone Numbers................................. 14
13. Security Considerations...................................... 15
14. Authors' Addresses........................................... 15
2.
The Federal Networking Council (FNC), the Internet Activities
(IAB), and the Internet Engineering Task Force (IETF) have a
commitment to responsible integration of OSI based upon sound
planning. This implies that OSI will be added to the
without sacrificing services now available to existing
users, and that a multi-protocol environment will exist in
Internet for a prolonged period. Planning is underway within
Internet community to enable integration of OSI, coexistence of
with TCP/IP, and interoperability between OSI and TCP/IP
The U.S. Government OSI Profile (GOSIP) is a necessary tool
planning OSI integration. However, as the August 1990
date for GOSIP compliance approaches, concern remains as to how
should be applied to near-term network planning
The intent of this statement is to help explain the role
applicability of the GOSIP document, as well as to emphasize
government's commitment to an integrated interoperable
environment based on responsible planning
3.
The Federal Agencies, represented in the Federal Networking
(FNC), as well as the Internet community represented by the
Activities Board (IAB), and the Internet Engineering Task
(IETF) are fully committed to integrating OSI into the Internet,
it is recognized that OSI is an international standard
protocol suite. The FNC, IAB, and IETF are taking sound
steps to integrate OSI in a fashion and on a schedule that
current levels of service to users of the existing
networks that are a part of the Internet. The large
installed base of TCP/IP protocol users, the limited deployment
commercial OSI products, and the incomplete development of
standards for routing, network management, and directory
combine to make an immediate, total transition to a pure
environment in the Internet unrealistic
In what follows, we present a brief overview of GOSIP and we
some of the often confusing points about the intent, applicability
and implementation of GOSIP. We also describe the role of the
regarding the integration of OSI into the Internet. Further,
Cerf & Mills [Page 2]
RFC 1169 Explaining the Role of GOSIP August 1990
discuss the role of Federal Agencies in this process
4.
Special thanks are due to Rebecca Nitzan of Sterling and Phill
of CNRI for developing several draft versions of this RFC
5. GOSIP
The Government OSI Profile (GOSIP), published as Federal
Processing Standard (FIPS) 146, issued by the National Institute
Standards and Technology (NIST), specifies the details of an
configuration for use in the Government so that interoperable
products can be procured from commercial vendors. GOSIP is
because OSI standards allow many potential options and choices,
of which are incompatible. GOSIP is based on refinements of
standards. The refinements are agreed to by commercial
and potential users through a series of OSI Implementors
(OIW) hosted by NIST four times every year since 1983. As
becomes more widely deployed, GOSIP compliance will
increasingly important
GOSIP was written by an inter-agency group and continues to
under the guidance of the GOSIP Advanced Requirements Group.
IETF is represented on the GOSIP Advanced Requirements Group, as
Federal Government Agencies, including the FNC agencies
The GOSIP FIPS consists of
1. An announcement adopting GOSIP as a Federal standard.
announcement section of the FIPS covers topics such as
objectives of GOSIP, its applicability,
requirements, and waiver procedures
2. The technical specification of GOSIP products to be procured
The technical specification section of GOSIP describes
details of a subset of OSI protocols. Products
GOSIP are in development by or available from many
vendors
3. Appendices describing the plans for including
functionality into future versions of the GOSIP
specification
The first version of GOSIP was published in August 1988 following
long comment period beginning as early as January 1987. GOSIP
adopted as FIPS 146 in February 1989 and will become a
procurement requirement in August 1990 [1]. A second version
Cerf & Mills [Page 3]
RFC 1169 Explaining the Role of GOSIP August 1990
GOSIP will become a FIPS in 1990 and will then become a
procurement requirement 18 months later [2]. Along with the
version of GOSIP, NIST will issue errata associated with
Version 1.0.
There is an additional publication called the GOSIP Users'
which provides an expanded explanation of GOSIP including tutorials
interpretation, integration planning advice, and information
registration [3]. The GOSIP Users' Guide will be updated and re
released in coordination with each version of GOSIP.
regarding how to obtain GOSIP and related documents is included
the Appendix to this RFC
6. Understanding
There is a common misunderstanding that GOSIP mandates an immediate
total transition to the use of OSI protocols in August 1990.
factors contribute to this misunderstanding including the
nature of the FIPS applicability and implementation sections,
press synopses trying to explain a complex subject in simple terms
and hearsay. The FIPS language will be improved in GOSIP
2.0. Additionally, more detailed treatment is given to these
in the GOSIP Users' Guide. Below is a summary of the issues
6.1.
The motivation behind the creation of the U.S. GOSIP document is
achieve, in the long term, a common, vendor neutral,
computer communication capability throughout the U.S. Government
Agreement on a common configuration of OSI protocols (GOSIP)
purposes of procurement is intended to aid this objective
Beginning in August, 1990, federal agencies procuring
network products and services must require that those products
services comply with OSI, where feasible, as specified in
Version 1.0. This will insure that all government-procured
products and services meet the same OSI Protocol profile
If the application for which network services or products
procured can be supported through GOSIP Version 1.0-
facilities, then it is required that compliant products or
be procured
Cerf & Mills [Page 4]
RFC 1169 Explaining the Role of GOSIP August 1990
6.1.1. Procurement Vs.
FIPS 146 is a procurement specification. The FIPS mandates
acquisition of OSI products when agencies require the
supplied by the OSI features specified in GOSIP. GOSIP does
mandate an immediate, total transition to OSI in August 1990.
6.1.2. Small Network Add-on Vs. Major
GOSIP applies most readily to procurement of new networks and
upgrades to existing networks. "Major upgrade" does not
mean adding components to an existing non-GOSIP network.
example, if an agency has an existing network and needs to
several compatible devices, there is no mandate to retrofit
into the entire existing network
6.1.3. OSI
Many of the OSI protocols are still in the process of
standardized. The GOSIP 1.0 and 2.0 versions address
configurations of fully-standardized OSI protocols. As new
standards emerge (e.g., for directory services, network
and dynamic routing), the GOSIP documents will be revised
incorporate agreed profiles/configurations. Each GOSIP
contains appendices describing the status of OSI
standardization and plans for incorporating new functionality
subsequent GOSIP versions
6.2.
GOSIP is not exclusive. When an agency implements GOSIP,
protocols may be procured and used in the same network. This non
exclusive arrangement will remain for the indefinite future
several reasons
1. Agencies, with existing networks, that are planning an
integration will require support for existing protocols
protocol converters during the integration period
2. Non-GOSIP protocols may provide some enhanced feature
improved performance that an agency may find beneficial
GOSIP is meant to provide for Government-wide interoperability
but is not meant to do so at the expense of other requirements
3. GOSIP does not meet every networking requirement of
agency. In fact, given the pace of technological change
computing and communications, no single protocol suite
likely to meet every networking requirement
Cerf & Mills [Page 5]
RFC 1169 Explaining the Role of GOSIP August 1990
6.3.
Each agency is responsible for planning the integration of OSI
agency networks. Many factors must be considered, including, but
limited to
o the installed network
o requirements for functionality not yet present in
o availability of
o future plans for networks in support of agency
o requirements for agency and government wide
o planned additions to OSI functionality in future versions
GOSIP
NIST recommends a three step approach to implement the provisions
GOSIP
1. develop a clear and definitive policy regarding use of
within an
2. develop an appropriate set of plans to implement the
3. update and act on the plans as agency networks are
and upgraded
Agency management has the responsibility to determine
of GOSIP to particular procurements and to evaluate and grant or
waivers from GOSIP when GOSIP would otherwise apply. For
details on these issues see the GOSIP Users' Guide
6.4.
Waivers may be granted from the mandated provisions of GOSIP
adherence to GOSIP would prevent an agency from accomplishing
mission or when an agency would suffer adverse financial effects
are not offset by Government-wide savings. Authority to grant
waivers is delegated to the heads of agencies
Developing a waiver process should be part of an agency'
implementation planning. No waiver is needed if GOSIP does
apply. Procedures are outlined in the FIPS and further discussed
the GOSIP Users' Guide
Cerf & Mills [Page 6]
RFC 1169 Explaining the Role of GOSIP August 1990
6.5.
NIST does not have an enforcement responsibility with respect
GOSIP. Any enforcement that occurs will result from the
process of planning, acquiring, and implementing networks
government agencies
7. Role of the IETF in Support of
Within the Internet community the IETF, working under the
of the IAB, plays a key role in planning for integration of OSI
the Internet. The IETF will define the technical
necessary to accommodate OSI in the Internet and to
coexistence and interoperability between OSI and TCP/IP
during the indeterminate period of multi-protocol operation.
activities include, but are not limited to, drafting
RFCs, creating input to GOSIP, the GOSIP Users' Guide, and the
Implementors Workshop (OIW). The IETF may also recommend to the
experiments to be undertaken to further the integration of OSI
the Internet. One of the eight areas of work for the IETF
dedicated to OSI integration. A representative of the IETF is
official member of the GOSIP Advanced Requirements Group
8. Role of the Internet Infrastructure Agencies in Support of
Certain of the FNC agencies have a role in providing a
part of the communications infrastructure for the Internet, that is
links, backbone routers, management facilities, and
services. For example, the National Science Foundation (NSF),
National Aeronautics and Space Administration (NASA), the
of Energy (DOE) and the Defense Advanced Research Projects
(DARPA) have such a role. These agencies must provide for
infrastructure services such as routing of ISO 8473 packets in
NSFnet backbone, provision of application level gateways
interoperability between TCP/IP and OSI applications, and
of OSI directory services
9. Role of the Internet Using Agencies in the Application of
The FNC agencies using Internet services also have a necessary
in the integration of OSI. The FNC agencies must identify
requirements and participate in the IETF and GOSIP groups to
that their needs can be met. The FNC agencies should also plan
implement OSI within their networks in accordance with the
of their technical and management plans, taking cognizance of
plans for and progress toward implementation of key OSI elements
the Internet Infrastructure. Each FNC agency should develop
agency policy on the adoption and use of GOSIP and should
Cerf & Mills [Page 7]
RFC 1169 Explaining the Role of GOSIP August 1990
planning for incorporation of GOSIP-compliant products into
networks
10.
The FNC, the IAB, and the IETF have a firm commitment to
integration of OSI protocols into the Internet based upon
network planning. A multi-protocol environment will exist in
Internet for a considerable period of time. As OSI products grow
number and capability and as more OSI standards are completed,
role of GOSIP will grow in importance
To summarize
o FIPS 146 (GOSIP) is a specification of which OSI protocols
to be procured for U.S. Government use. GOSIP does
mandate, or even explicitly address, the issue of
transition
o As a procurement specification, GOSIP does not apply to
installed equipment. It applies to new network procurements
major upgrades to existing networks. "Major upgrade" does
necessarily apply to increasing the number of components
current functionality in existing non-GOSIP networks
o When GOSIP does apply, it is not exclusionary. That is,
protocol families can also be procured and used
o When GOSIP does apply, waivers are allowed in consideration
specific agency requirements. When GOSIP does not apply,
waiver is necessary
o Agencies have the responsibility 1) for agency-wide
for GOSIP compliance in their network procurements, 2)
developing their own waiver process, and 3) for
the applicability of GOSIP to any specific procurement
Cerf & Mills [Page 8]
RFC 1169 Explaining the Role of GOSIP August 1990
11.
[1] "U.S. Government Open Systems Interconnection Profile", U.S
Federal Information Processing Standards Publication 146,
1, August 1988.
[2] "U.S. Government Open Systems Interconnection Profile", U.S
Federal Information Processing Standards Publication 146-1,
Version 2, April 1989.
[3] Boland, T., "Government Open Systems Interconnection
Users' Guide", NIST Special Publication 500-163, August 1989.
12. Appendix -- To Obtain GOSIP
Below is the information needed to obtain the U.S. GOSIP and NIST/
Implementors Workshop (OIW) documents. All prices are in U.S
dollars and represent the most up-to-date information available
this time; for further pricing information and ordering details
contact the seller (all addresses and telephone numbers are to
found at the end).
12.1
12.1.1 GOSIP Version 1.
GOSIP Version 1 (Federal Information Processing Standard 146)
published in August 1988. It becomes mandatory in applicable
procurements in August 1990.
NIST POINT OF CONTACT: Jerry
HARDCOPY
Order Number: FIPS PUB 146
Price: $17.00 (paper); $8.00 (microfiche
Cerf & Mills [Page 9]
RFC 1169 Explaining the Role of GOSIP August 1990
ON-LINE
1. The federal register announcement (FIPS 146) as well as GOSIP
available through anonymous ftp from nic.ddn.mil (192.67.67.20) as
o gosip-fedreg.txt (ascii
o gosip-fips-draft.txt (ascii
o gosip-v1.txt (ascii
2. Through anonymous ftp or FTAM (ISODE 5.0, user: ftam
realstore=unix) from osi3.ncsl.nist.gov (129.6.48.100) as
o pub/gosip/gosip_v1_fedreg.txt (ascii
o pub/gosip/fips146_draft.txt (ascii
o pub/gosip/gosip_v1.txt (ascii
o pub/gosip/gosip_v1.txt.Z (compressed
12.1.2 GOSIP Version 2.
GOSIP Version 2 is currently a draft. It has undergone public
and comment. Comments will be addressed by the GOSIP
Requirements Committee in May, 1990. Final text is expected to
available in August, 1990.
NIST POINT OF CONTACT: Jerry
HARDCOPY
NIST Standards Processing Coordinator (ADP
ON-LINE
1. Available through anonymous ftp or FTAM (ISODE 5.0, user: ftam
realstore=unix) from osi3.ncsl.nist.gov (129.6.48.100) as
o pub/gosip/gosip_v2_draft.txt (ascii
o pub/gosip/gosip_v2_draft.txt.Z (compressed
o pub/gosip/gosip_v2_draft.ps (postscript
o pub/gosip/gosip_v2_draft.ps.Z (compressed
Cerf & Mills [Page 10]
RFC 1169 Explaining the Role of GOSIP August 1990
2. Available through anonymous ftp from nic.ddn.mil (192.67.67.20)
as
o gosip-v2-draft.
12.2 NIST Workshop for Implementors of OSI
The output of the NIST Workshop for Implementors of OSI (OIW) is
pair of aligned documents, one representing Stable
Agreements (SIA), the other containing Working
Agreements (WIA) that have not yet gone into the stable document
Material is in either one or the other of these documents, but
both, and the documents have the same index structure
The SIA is reproduced in its entirety at the beginning of
calendar year, with an incremented version number. Replacement
sets are distributed subsequently three times during each year (
each Workshop), reflecting edits to the stable material.
replacement pages constitute the next edition of that year's version
The WIA is reproduced in its entirety after each Workshop (held
March, June, September and December). OIW attendees
receive the WIA. OIW meeting dates in 1990 are: March 12-16;
18-22; September 10-14; and December 10-14.
NIST POINTS OF CONTACT
1. Tim Boland/management
Chairman,
2. Brenda Gray/administrative
OIW
12.2.1 SIA, Version 1.
SIA, Version 1, Edition 1 (Dec, 1987) The SIA, V1E1 is published
NIST Special Publication 500-150. It is the appropriate version
edition of the SIA for GOSIP Version 1 (FIPS 146).
HARDCOPY
1. U.S. Government Printing
GPO Stock Number: 003-02838-0
Price: $20.00
Cerf & Mills [Page 11]
RFC 1169 Explaining the Role of GOSIP August 1990
2.
Order Number: PB 88-168331
Price: $31.00 (paper); $8.00 (microfiche
SIA, Version 1, Edition 3 (August, 1988) The SIA, V1E3 is
published as NBS Special Publication 500-150 (note the different
Stock Number when ordering).
HARDCOPY
U.S. Government Printing
GPO Stock Number: 003-003-02838-0
Price: $12.00 (paper
ON-LINE
1. Available through anonymous ftp or FTAM (ISODE 5.0, user: ftam
realstore=unix) from from osi3.ncsl.nist.gov (129.6.48.100) as
o pub/gosip/nist_osiws_sia_v1e3.txt (ascii
o pub/gosip/nist_osiws_sia_v1e3.txt.Z (compressed
2. Available through anonymous ftp from nic.ddn.mil (192.67.67.20)
as
o nbsosi-argrements.
12.2.2 SIA, Version 2.
SIA, Version 2, Edition 1 (Dec, 1988) The SIA, V2E1 is published
NBS Special Publication 500-162.
HARDCOPY
1. U.S. Government Printing
GPO Stock Number: 003-003-02921-1
Price: $26.00
2. IEEE Computer
ISBN 0-8186-9022-4
Book No. 2022
Price: $75.00 (casebound
(a subscription service is available from IEEE
3.
Order Number: PB 89193312
Price: $53.00 (paper); $8.00 (microfiche
Cerf & Mills [Page 12]
RFC 1169 Explaining the Role of GOSIP August 1990
SIA, Version 2, Editions 2-4 These are available as hardcopy
NIST staff, subject to staff availability. Contact
Brenda Gray/administrative
OIW
SIA, Version 3, Edition 1 (Dec, 1989) The SIA V3E1 is expected to
available in the first half of 1990. It may be ordered from the
Computer Society and the U.S. GPO. Future editions of Version 3
expected to be available from NTIS, and possibly GPO and the
Computer Society
12.2.3 WIA (August, 1989).
The August, 1989 WIA, published as a NIST Interagency Report (IR-89-
4140) is the most recent copy of the WIA that is available to order
The December, 1989 WIA document is available from NTIS and the
Computer Society. The August, 1989 WIA (NIST IR-89-4140)
available in hardcopy from
Order Number: PB 89235931/
Price: $36.95 (paper); $6.95 (microfiche
12.3 GOSIP Users'
This publication assists federal agencies in planning for
procuring OSI. It provides tutorial information on OSI protocols
well as information on OSI registration, GOSIP technical evaluation
and GOSIP transition strategies
HARDCOPY
Order Number: PB 90-111212
Price: $23 (paper); $8 (microfiche
Cerf & Mills [Page 13]
RFC 1169 Explaining the Role of GOSIP August 1990
12.4 Addresses/Telephone
NIST
Tim Boland/management
Chairman,
Technology, B217
Gaithersburg, MD 20899
(301) 975-3608
boland@ecf.ncsl.nist.
Brenda Gray/administrative
OIW
Technology, B217
Gaithersburg, MD 20899
(301) 975-3664
Jerry
Technology, B217
Gaithersburg, MD 20899
(301) 975-3631
mulvenna@ecf.ncsl.nist.
OTHER SOURCES OF
National Technical Information Service (NTIS
U.S. Department of
5285 Port Royal
Springfield, VA 22161
(703)487-4650
IEEE Computer
Order
10662 Los Vaqueros
Los Alamitos, CA 90720
1-800-272-6657
U.S. Government Printing
Washington, DC 20402
(202) 783-3238
Standards Processing Coordinator (ADP
National Institute of Standards and
Technology Building, Room B-64
Gaithersburg, MD 20899
(301) 975-2816
Cerf & Mills [Page 14]
RFC 1169 Explaining the Role of GOSIP August 1990
13. Security
Security issues are not discussed in this memo
14. Authors'
Vinton G.
Chairman,
Corporation for National Research
1895 Preston White Drive, Suite 100
Reston, VA 22091
Phone: (703) 620-8990
EMail: vcerf@nri.reston.va.
Kevin L.
National Institute of Standards and
Building 225, Room B217
Gaithersburg, MD 20899
Phone: (301) 975-3618
EMail: MILLS@ECF.NCSL.NIST.
Cerf & Mills [Page 15]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
