Debian Codegraph @

rfc1169.html

raw
1 <pre>Network Working Group V. Cerf
2 Request for Comments: 1169 IAB
3 K. Mills
4 NIST
5 August 1990
6
7
8 <span class="h1">Explaining the Role of GOSIP</span>
9
10 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Status of this Memo</span>
11
12 This informational RFC represents the official view of the Internet
13 Activities Board (IAB), after coordination with the Federal
14 Networking Council (FNC). This RFC does not specify a standard.
15
16 Distribution of this memo is unlimited.
17
18 Table of Contents
19
20 <a href="#section-1">1</a>. Status of this Memo........................................... <a href="#page-1">1</a>
21 <a href="#section-2">2</a>. Abstract...................................................... <a href="#page-2">2</a>
22 <a href="#section-3">3</a>. Introduction.................................................. <a href="#page-2">2</a>
23 <a href="#section-4">4</a>. Acknowledgements.............................................. <a href="#page-3">3</a>
24 <a href="#section-5">5</a>. GOSIP Background.............................................. <a href="#page-3">3</a>
25 <a href="#section-6">6</a>. Understanding GOSIP........................................... <a href="#page-4">4</a>
26 <a href="#section-6.1">6.1</a>. Applicability............................................... <a href="#page-4">4</a>
27 <a href="#section-6.1.1">6.1.1</a>. Procurement Vs. Transition................................ <a href="#page-5">5</a>
28 <a href="#section-6.1.2">6.1.2</a>. Small Network Add-on Vs. Major Upgrade.................... <a href="#page-5">5</a>
29 <a href="#section-6.1.3">6.1.3</a>. OSI Incompleteness........................................ <a href="#page-5">5</a>
30 <a href="#section-6.2">6.2</a>. Exclusivity................................................. <a href="#page-5">5</a>
31 <a href="#section-6.3">6.3</a>. Implementation.............................................. <a href="#page-6">6</a>
32 <a href="#section-6.4">6.4</a>. Waivers..................................................... <a href="#page-6">6</a>
33 <a href="#section-6.5">6.5</a>. Enforcement................................................. <a href="#page-7">7</a>
34 <a href="#section-7">7</a>. Role of the IETF in Support of OSI............................ <a href="#page-7">7</a>
35 8. Role of the Internet Infrastructure Agencies in
36 Support of OSI................................................ <a href="#page-7">7</a>
37 9. Role of the Internet Using Agencies in the
38 Application of OSI............................................ <a href="#page-7">7</a>
39 <a href="#section-10">10</a>. Summary...................................................... <a href="#page-8">8</a>
40 <a href="#section-11">11</a>. References................................................... <a href="#page-9">9</a>
41 <a href="#section-12">12</a>. Appendix -- To Obtain GOSIP Documents........................ <a href="#page-9">9</a>
42 <a href="#section-12.1">12.1</a> GOSIP....................................................... <a href="#page-9">9</a>
43 <a href="#section-12.1.1">12.1.1</a> GOSIP Version 1........................................... <a href="#page-9">9</a>
44 <a href="#section-12.1.2">12.1.2</a> GOSIP Version 2........................................... <a href="#page-10">10</a>
45 <a href="#section-12.2">12.2</a> NIST Workshop for Implementors of OSI Documents............. <a href="#page-11">11</a>
46 <a href="#section-12.2.1">12.2.1</a> SIA, Version 1............................................ <a href="#page-11">11</a>
47 <a href="#section-12.2.2">12.2.2</a> SIA, Version 2............................................ <a href="#page-12">12</a>
48 <a href="#section-12.2.3">12.2.3</a> WIA (August, 1989)........................................ <a href="#page-13">13</a>
49
50
51
52 <span class="grey">Cerf &amp; Mills [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
55
56
57 <a href="#section-12.3">12.3</a> GOSIP Users' Guide.......................................... <a href="#page-13">13</a>
58 <a href="#section-12.4">12.4</a> Addresses/Telephone Numbers................................. <a href="#page-14">14</a>
59 <a href="#section-13">13</a>. Security Considerations...................................... <a href="#page-15">15</a>
60 <a href="#section-14">14</a>. Authors' Addresses........................................... <a href="#page-15">15</a>
61
62 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Abstract</span>
63
64 The Federal Networking Council (FNC), the Internet Activities Board
65 (IAB), and the Internet Engineering Task Force (IETF) have a firm
66 commitment to responsible integration of OSI based upon sound network
67 planning. This implies that OSI will be added to the Internet
68 without sacrificing services now available to existing Internet
69 users, and that a multi-protocol environment will exist in the
70 Internet for a prolonged period. Planning is underway within the
71 Internet community to enable integration of OSI, coexistence of OSI
72 with TCP/IP, and interoperability between OSI and TCP/IP.
73
74 The U.S. Government OSI Profile (GOSIP) is a necessary tool for
75 planning OSI integration. However, as the August 1990 requirement
76 date for GOSIP compliance approaches, concern remains as to how GOSIP
77 should be applied to near-term network planning.
78
79 The intent of this statement is to help explain the role and
80 applicability of the GOSIP document, as well as to emphasize the
81 government's commitment to an integrated interoperable OSI
82 environment based on responsible planning.
83
84 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Introduction</span>
85
86 The Federal Agencies, represented in the Federal Networking Council
87 (FNC), as well as the Internet community represented by the Internet
88 Activities Board (IAB), and the Internet Engineering Task Force
89 (IETF) are fully committed to integrating OSI into the Internet, as
90 it is recognized that OSI is an international standard networking
91 protocol suite. The FNC, IAB, and IETF are taking sound technical
92 steps to integrate OSI in a fashion and on a schedule that assures
93 current levels of service to users of the existing operational
94 networks that are a part of the Internet. The large existing
95 installed base of TCP/IP protocol users, the limited deployment of
96 commercial OSI products, and the incomplete development of OSI
97 standards for routing, network management, and directory services
98 combine to make an immediate, total transition to a pure OSI
99 environment in the Internet unrealistic.
100
101 In what follows, we present a brief overview of GOSIP and we address
102 some of the often confusing points about the intent, applicability,
103 and implementation of GOSIP. We also describe the role of the IETF
104 regarding the integration of OSI into the Internet. Further, we
105
106
107
108 <span class="grey">Cerf &amp; Mills [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
111
112
113 discuss the role of Federal Agencies in this process.
114
115 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgements</span>
116
117 Special thanks are due to Rebecca Nitzan of Sterling and Phill Gross
118 of CNRI for developing several draft versions of this RFC.
119
120 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. GOSIP Background</span>
121
122 The Government OSI Profile (GOSIP), published as Federal Information
123 Processing Standard (FIPS) 146, issued by the National Institute of
124 Standards and Technology (NIST), specifies the details of an OSI
125 configuration for use in the Government so that interoperable OSI
126 products can be procured from commercial vendors. GOSIP is needed
127 because OSI standards allow many potential options and choices, some
128 of which are incompatible. GOSIP is based on refinements of OSI
129 standards. The refinements are agreed to by commercial implementors
130 and potential users through a series of OSI Implementors Workshops
131 (OIW) hosted by NIST four times every year since 1983. As OSI
132 becomes more widely deployed, GOSIP compliance will become
133 increasingly important.
134
135 GOSIP was written by an inter-agency group and continues to evolve
136 under the guidance of the GOSIP Advanced Requirements Group. The
137 IETF is represented on the GOSIP Advanced Requirements Group, as are
138 Federal Government Agencies, including the FNC agencies.
139
140 The GOSIP FIPS consists of:
141
142 1. An announcement adopting GOSIP as a Federal standard. The
143 announcement section of the FIPS covers topics such as the
144 objectives of GOSIP, its applicability, implementation
145 requirements, and waiver procedures.
146
147 2. The technical specification of GOSIP products to be procured.
148 The technical specification section of GOSIP describes the
149 details of a subset of OSI protocols. Products implementing
150 GOSIP are in development by or available from many computer
151 vendors.
152
153 3. Appendices describing the plans for including additional
154 functionality into future versions of the GOSIP technical
155 specification.
156
157 The first version of GOSIP was published in August 1988 following a
158 long comment period beginning as early as January 1987. GOSIP was
159 adopted as FIPS 146 in February 1989 and will become a Federal
160 procurement requirement in August 1990 [<a href="#ref-1" title="&quot;U.S. Government Open Systems Interconnection Profile&quot;">1</a>]. A second version of
161
162
163
164 <span class="grey">Cerf &amp; Mills [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
167
168
169 GOSIP will become a FIPS in 1990 and will then become a Federal
170 procurement requirement 18 months later [<a href="#ref-2" title="&quot;U.S. Government Open Systems Interconnection Profile&quot;">2</a>]. Along with the second
171 version of GOSIP, NIST will issue errata associated with GOSIP
172 Version 1.0.
173
174 There is an additional publication called the GOSIP Users' Guide
175 which provides an expanded explanation of GOSIP including tutorials,
176 interpretation, integration planning advice, and information on
177 registration [<a href="#ref-3" title="&quot;Government Open Systems Interconnection Profile Users' Guide&quot;">3</a>]. The GOSIP Users' Guide will be updated and re-
178 released in coordination with each version of GOSIP. Information
179 regarding how to obtain GOSIP and related documents is included in
180 the Appendix to this RFC.
181
182 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Understanding GOSIP</span>
183
184 There is a common misunderstanding that GOSIP mandates an immediate,
185 total transition to the use of OSI protocols in August 1990. Several
186 factors contribute to this misunderstanding including the summary
187 nature of the FIPS applicability and implementation sections, trade
188 press synopses trying to explain a complex subject in simple terms,
189 and hearsay. The FIPS language will be improved in GOSIP Version
190 2.0. Additionally, more detailed treatment is given to these issues
191 in the GOSIP Users' Guide. Below is a summary of the issues.
192
193 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Applicability</span>
194
195 The motivation behind the creation of the U.S. GOSIP document is to
196 achieve, in the long term, a common, vendor neutral, interoperable
197 computer communication capability throughout the U.S. Government.
198 Agreement on a common configuration of OSI protocols (GOSIP) for
199 purposes of procurement is intended to aid this objective.
200
201 Beginning in August, 1990, federal agencies procuring computer
202 network products and services must require that those products and
203 services comply with OSI, where feasible, as specified in GOSIP
204 Version 1.0. This will insure that all government-procured OSI
205 products and services meet the same OSI Protocol profile.
206
207 If the application for which network services or products are
208 procured can be supported through GOSIP Version 1.0-compliant
209 facilities, then it is required that compliant products or services
210 be procured.
211
212
213
214
215
216
217
218
219
220 <span class="grey">Cerf &amp; Mills [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
223
224
225 <span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. Procurement Vs. Transition</span>
226
227 FIPS 146 is a procurement specification. The FIPS mandates the
228 acquisition of OSI products when agencies require the functionality
229 supplied by the OSI features specified in GOSIP. GOSIP does not
230 mandate an immediate, total transition to OSI in August 1990.
231
232 <span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. Small Network Add-on Vs. Major Upgrade</span>
233
234 GOSIP applies most readily to procurement of new networks and major
235 upgrades to existing networks. "Major upgrade" does not necessarily
236 mean adding components to an existing non-GOSIP network. For
237 example, if an agency has an existing network and needs to add
238 several compatible devices, there is no mandate to retrofit GOSIP
239 into the entire existing network.
240
241 <span class="h4"><a class="selflink" id="section-6.1.3" href="#section-6.1.3">6.1.3</a>. OSI Incompleteness</span>
242
243 Many of the OSI protocols are still in the process of being
244 standardized. The GOSIP 1.0 and 2.0 versions address only
245 configurations of fully-standardized OSI protocols. As new OSI
246 standards emerge (e.g., for directory services, network management
247 and dynamic routing), the GOSIP documents will be revised to
248 incorporate agreed profiles/configurations. Each GOSIP document
249 contains appendices describing the status of OSI protocol
250 standardization and plans for incorporating new functionality into
251 subsequent GOSIP versions.
252
253 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Exclusivity</span>
254
255 GOSIP is not exclusive. When an agency implements GOSIP, other
256 protocols may be procured and used in the same network. This non-
257 exclusive arrangement will remain for the indefinite future for
258 several reasons:
259
260 1. Agencies, with existing networks, that are planning an OSI
261 integration will require support for existing protocols and
262 protocol converters during the integration period.
263
264 2. Non-GOSIP protocols may provide some enhanced feature or
265 improved performance that an agency may find beneficial.
266 GOSIP is meant to provide for Government-wide interoperability,
267 but is not meant to do so at the expense of other requirements.
268
269 3. GOSIP does not meet every networking requirement of every
270 agency. In fact, given the pace of technological change in
271 computing and communications, no single protocol suite is
272 likely to meet every networking requirement.
273
274
275
276 <span class="grey">Cerf &amp; Mills [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
279
280
281 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Implementation</span>
282
283 Each agency is responsible for planning the integration of OSI into
284 agency networks. Many factors must be considered, including, but not
285 limited to:
286
287 o the installed network base
288
289 o requirements for functionality not yet present in GOSIP
290
291 o availability of funds
292
293 o future plans for networks in support of agency missions
294
295 o requirements for agency and government wide interoperability
296
297 o planned additions to OSI functionality in future versions of
298 GOSIP.
299
300 NIST recommends a three step approach to implement the provisions of
301 GOSIP:
302
303 1. develop a clear and definitive policy regarding use of OSI
304 within an agency
305
306 2. develop an appropriate set of plans to implement the policy
307
308 3. update and act on the plans as agency networks are acquired
309 and upgraded.
310
311 Agency management has the responsibility to determine applicability
312 of GOSIP to particular procurements and to evaluate and grant or deny
313 waivers from GOSIP when GOSIP would otherwise apply. For further
314 details on these issues see the GOSIP Users' Guide.
315
316 <span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Waivers</span>
317
318 Waivers may be granted from the mandated provisions of GOSIP when
319 adherence to GOSIP would prevent an agency from accomplishing its
320 mission or when an agency would suffer adverse financial effects that
321 are not offset by Government-wide savings. Authority to grant such
322 waivers is delegated to the heads of agencies.
323
324 Developing a waiver process should be part of an agency's
325 implementation planning. No waiver is needed if GOSIP does not
326 apply. Procedures are outlined in the FIPS and further discussed in
327 the GOSIP Users' Guide.
328
329
330
331
332 <span class="grey">Cerf &amp; Mills [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
335
336
337 <span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Enforcement</span>
338
339 NIST does not have an enforcement responsibility with respect to
340 GOSIP. Any enforcement that occurs will result from the normal
341 process of planning, acquiring, and implementing networks within
342 government agencies.
343
344 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Role of the IETF in Support of OSI</span>
345
346 Within the Internet community the IETF, working under the direction
347 of the IAB, plays a key role in planning for integration of OSI into
348 the Internet. The IETF will define the technical mechanisms
349 necessary to accommodate OSI in the Internet and to permit
350 coexistence and interoperability between OSI and TCP/IP protocols
351 during the indeterminate period of multi-protocol operation. IETF
352 activities include, but are not limited to, drafting appropriate
353 RFCs, creating input to GOSIP, the GOSIP Users' Guide, and the OSI
354 Implementors Workshop (OIW). The IETF may also recommend to the FNC
355 experiments to be undertaken to further the integration of OSI into
356 the Internet. One of the eight areas of work for the IETF is
357 dedicated to OSI integration. A representative of the IETF is an
358 official member of the GOSIP Advanced Requirements Group.
359
360 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Role of the Internet Infrastructure Agencies in Support of OSI</span>
361
362 Certain of the FNC agencies have a role in providing a significant
363 part of the communications infrastructure for the Internet, that is,
364 links, backbone routers, management facilities, and directory
365 services. For example, the National Science Foundation (NSF), the
366 National Aeronautics and Space Administration (NASA), the Department
367 of Energy (DOE) and the Defense Advanced Research Projects Agency
368 (DARPA) have such a role. These agencies must provide for essential
369 infrastructure services such as routing of ISO 8473 packets in the
370 NSFnet backbone, provision of application level gateways enabling
371 interoperability between TCP/IP and OSI applications, and provision
372 of OSI directory services.
373
374 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Role of the Internet Using Agencies in the Application of OSI</span>
375
376 The FNC agencies using Internet services also have a necessary role
377 in the integration of OSI. The FNC agencies must identify their
378 requirements and participate in the IETF and GOSIP groups to ensure
379 that their needs can be met. The FNC agencies should also plan to
380 implement OSI within their networks in accordance with the realities
381 of their technical and management plans, taking cognizance of the
382 plans for and progress toward implementation of key OSI elements in
383 the Internet Infrastructure. Each FNC agency should develop an
384 agency policy on the adoption and use of GOSIP and should initiate
385
386
387
388 <span class="grey">Cerf &amp; Mills [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
391
392
393 planning for incorporation of GOSIP-compliant products into agency
394 networks.
395
396 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Summary</span>
397
398 The FNC, the IAB, and the IETF have a firm commitment to responsible
399 integration of OSI protocols into the Internet based upon sound
400 network planning. A multi-protocol environment will exist in the
401 Internet for a considerable period of time. As OSI products grow in
402 number and capability and as more OSI standards are completed, the
403 role of GOSIP will grow in importance.
404
405 To summarize:
406
407 o FIPS 146 (GOSIP) is a specification of which OSI protocols are
408 to be procured for U.S. Government use. GOSIP does not
409 mandate, or even explicitly address, the issue of protocol
410 transition.
411
412 o As a procurement specification, GOSIP does not apply to existing
413 installed equipment. It applies to new network procurements and
414 major upgrades to existing networks. "Major upgrade" does not
415 necessarily apply to increasing the number of components of
416 current functionality in existing non-GOSIP networks.
417
418 o When GOSIP does apply, it is not exclusionary. That is, other
419 protocol families can also be procured and used.
420
421 o When GOSIP does apply, waivers are allowed in consideration of
422 specific agency requirements. When GOSIP does not apply, no
423 waiver is necessary.
424
425 o Agencies have the responsibility 1) for agency-wide planning
426 for GOSIP compliance in their network procurements, 2) for
427 developing their own waiver process, and 3) for determining
428 the applicability of GOSIP to any specific procurement.
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Cerf &amp; Mills [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
447
448
449 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
450
451 [<a id="ref-1">1</a>] "U.S. Government Open Systems Interconnection Profile", U.S.
452 Federal Information Processing Standards Publication 146, Version
453 1, August 1988.
454
455 [<a id="ref-2">2</a>] "U.S. Government Open Systems Interconnection Profile", U.S.
456 Federal Information Processing Standards Publication 146-1, Draft
457 Version 2, April 1989.
458
459 [<a id="ref-3">3</a>] Boland, T., "Government Open Systems Interconnection Profile
460 Users' Guide", NIST Special Publication 500-163, August 1989.
461
462 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Appendix -- To Obtain GOSIP Documents</span>
463
464 Below is the information needed to obtain the U.S. GOSIP and NIST/OSI
465 Implementors Workshop (OIW) documents. All prices are in U.S.
466 dollars and represent the most up-to-date information available at
467 this time; for further pricing information and ordering details,
468 contact the seller (all addresses and telephone numbers are to be
469 found at the end).
470
471 <span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a> GOSIP</span>
472
473 <span class="h4"><a class="selflink" id="section-12.1.1" href="#section-12.1.1">12.1.1</a> GOSIP Version 1.</span>
474
475 GOSIP Version 1 (Federal Information Processing Standard 146) was
476 published in August 1988. It becomes mandatory in applicable federal
477 procurements in August 1990.
478
479 NIST POINT OF CONTACT: Jerry Mulvenna
480
481 HARDCOPY:
482
483 NTIS
484 Order Number: FIPS PUB 146
485 Price: $17.00 (paper); $8.00 (microfiche)
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Cerf &amp; Mills [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
503
504
505 ON-LINE:
506
507 1. The federal register announcement (FIPS 146) as well as GOSIP are
508 available through anonymous ftp from nic.ddn.mil (192.67.67.20) as:
509
510 o &lt;protocols&gt;gosip-fedreg.txt (ascii)
511
512 o &lt;protocols&gt;gosip-fips-draft.txt (ascii)
513
514 o &lt;protocols&gt;gosip-v1.txt (ascii)
515
516 2. Through anonymous ftp or FTAM (ISODE 5.0, user: ftam,
517 realstore=unix) from osi3.ncsl.nist.gov (129.6.48.100) as:
518
519 o pub/gosip/gosip_v1_fedreg.txt (ascii)
520
521 o pub/gosip/fips146_draft.txt (ascii)
522
523 o pub/gosip/gosip_v1.txt (ascii)
524
525 o pub/gosip/gosip_v1.txt.Z (compressed)
526
527 <span class="h4"><a class="selflink" id="section-12.1.2" href="#section-12.1.2">12.1.2</a> GOSIP Version 2.</span>
528
529 GOSIP Version 2 is currently a draft. It has undergone public review
530 and comment. Comments will be addressed by the GOSIP Advanced
531 Requirements Committee in May, 1990. Final text is expected to be
532 available in August, 1990.
533
534 NIST POINT OF CONTACT: Jerry Mulvenna
535
536 HARDCOPY:
537
538 NIST Standards Processing Coordinator (ADP)
539
540 ON-LINE:
541
542 1. Available through anonymous ftp or FTAM (ISODE 5.0, user: ftam,
543 realstore=unix) from osi3.ncsl.nist.gov (129.6.48.100) as:
544
545 o pub/gosip/gosip_v2_draft.txt (ascii)
546
547 o pub/gosip/gosip_v2_draft.txt.Z (compressed)
548
549 o pub/gosip/gosip_v2_draft.ps (postscript)
550
551 o pub/gosip/gosip_v2_draft.ps.Z (compressed)
552
553
554
555
556 <span class="grey">Cerf &amp; Mills [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
559
560
561 2. Available through anonymous ftp from nic.ddn.mil (192.67.67.20)
562 as:
563
564 o &lt;protocols&gt;gosip-v2-draft.doc
565
566 <span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a> NIST Workshop for Implementors of OSI Documents</span>
567
568 The output of the NIST Workshop for Implementors of OSI (OIW) is a
569 pair of aligned documents, one representing Stable Implementation
570 Agreements (SIA), the other containing Working Implementation
571 Agreements (WIA) that have not yet gone into the stable document.
572 Material is in either one or the other of these documents, but not
573 both, and the documents have the same index structure.
574
575 The SIA is reproduced in its entirety at the beginning of each
576 calendar year, with an incremented version number. Replacement page
577 sets are distributed subsequently three times during each year (after
578 each Workshop), reflecting edits to the stable material. The
579 replacement pages constitute the next edition of that year's version.
580
581 The WIA is reproduced in its entirety after each Workshop (held in
582 March, June, September and December). OIW attendees automatically
583 receive the WIA. OIW meeting dates in 1990 are: March 12-16; June
584 18-22; September 10-14; and December 10-14.
585
586 NIST POINTS OF CONTACT:
587
588 1. Tim Boland/management information
589 Chairman, OIW
590
591 2. Brenda Gray/administrative information
592 OIW Registrar
593
594 <span class="h4"><a class="selflink" id="section-12.2.1" href="#section-12.2.1">12.2.1</a> SIA, Version 1.</span>
595
596 SIA, Version 1, Edition 1 (Dec, 1987) The SIA, V1E1 is published as
597 NIST Special Publication 500-150. It is the appropriate version and
598 edition of the SIA for GOSIP Version 1 (FIPS 146).
599
600 HARDCOPY:
601
602 1. U.S. Government Printing Office
603 GPO Stock Number: 003-02838-0
604 Price: $20.00
605
606
607
608
609
610
611
612 <span class="grey">Cerf &amp; Mills [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
615
616
617 2. NTIS
618 Order Number: PB 88-168331
619 Price: $31.00 (paper); $8.00 (microfiche)
620
621 SIA, Version 1, Edition 3 (August, 1988) The SIA, V1E3 is also
622 published as NBS Special Publication 500-150 (note the different GPO
623 Stock Number when ordering).
624
625 HARDCOPY:
626
627 U.S. Government Printing Office
628 GPO Stock Number: 003-003-02838-0
629 Price: $12.00 (paper)
630
631 ON-LINE:
632
633 1. Available through anonymous ftp or FTAM (ISODE 5.0, user: ftam,
634 realstore=unix) from from osi3.ncsl.nist.gov (129.6.48.100) as:
635
636 o pub/gosip/nist_osiws_sia_v1e3.txt (ascii)
637
638 o pub/gosip/nist_osiws_sia_v1e3.txt.Z (compressed)
639
640 2. Available through anonymous ftp from nic.ddn.mil (192.67.67.20)
641 as:
642
643 o &lt;protocols&gt;nbsosi-argrements.doc
644
645 <span class="h4"><a class="selflink" id="section-12.2.2" href="#section-12.2.2">12.2.2</a> SIA, Version 2.</span>
646
647 SIA, Version 2, Edition 1 (Dec, 1988) The SIA, V2E1 is published as
648 NBS Special Publication 500-162.
649
650 HARDCOPY:
651
652 1. U.S. Government Printing Office
653 GPO Stock Number: 003-003-02921-1
654 Price: $26.00
655
656 2. IEEE Computer Society
657 ISBN 0-8186-9022-4
658 Book No. 2022
659 Price: $75.00 (casebound)
660 (a subscription service is available from IEEE)
661
662 3. NTIS
663 Order Number: PB 89193312
664 Price: $53.00 (paper); $8.00 (microfiche)
665
666
667
668 <span class="grey">Cerf &amp; Mills [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
671
672
673 SIA, Version 2, Editions 2-4 These are available as hardcopy from
674 NIST staff, subject to staff availability. Contact:
675
676 Brenda Gray/administrative information
677 OIW Registrar
678
679 SIA, Version 3, Edition 1 (Dec, 1989) The SIA V3E1 is expected to be
680 available in the first half of 1990. It may be ordered from the IEEE
681 Computer Society and the U.S. GPO. Future editions of Version 3 are
682 expected to be available from NTIS, and possibly GPO and the IEEE
683 Computer Society.
684
685 <span class="h4"><a class="selflink" id="section-12.2.3" href="#section-12.2.3">12.2.3</a> WIA (August, 1989).</span>
686
687 The August, 1989 WIA, published as a NIST Interagency Report (IR-89-
688 4140) is the most recent copy of the WIA that is available to order.
689 The December, 1989 WIA document is available from NTIS and the IEEE
690 Computer Society. The August, 1989 WIA (NIST IR-89-4140) is
691 available in hardcopy from:
692
693 NTIS
694 Order Number: PB 89235931/AS
695 Price: $36.95 (paper); $6.95 (microfiche)
696
697 <span class="h3"><a class="selflink" id="section-12.3" href="#section-12.3">12.3</a> GOSIP Users' Guide</span>
698
699 This publication assists federal agencies in planning for and
700 procuring OSI. It provides tutorial information on OSI protocols as
701 well as information on OSI registration, GOSIP technical evaluation,
702 and GOSIP transition strategies.
703
704 HARDCOPY:
705
706 NTIS
707 Order Number: PB 90-111212
708 Price: $23 (paper); $8 (microfiche)
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Cerf &amp; Mills [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
727
728
729 <span class="h3"><a class="selflink" id="section-12.4" href="#section-12.4">12.4</a> Addresses/Telephone Numbers</span>
730
731 NIST CONTACTS
732
733 Tim Boland/management information
734 Chairman, OIW
735 Technology, B217
736 Gaithersburg, MD 20899
737 (301) 975-3608
738 [email protected]
739
740 Brenda Gray/administrative information
741 OIW Registrar
742 Technology, B217
743 Gaithersburg, MD 20899
744 (301) 975-3664
745
746 Jerry Mulvenna
747 Technology, B217
748 Gaithersburg, MD 20899
749 (301) 975-3631
750 [email protected]
751
752 OTHER SOURCES OF DOCUMENTS
753
754 National Technical Information Service (NTIS)
755 U.S. Department of Commerce
756 5285 Port Royal Road
757 Springfield, VA 22161
758 (703)487-4650
759
760 IEEE Computer Society
761 Order Department
762 10662 Los Vaqueros Circle
763 Los Alamitos, CA 90720
764 1-800-272-6657
765
766 U.S. Government Printing Office
767 Washington, DC 20402
768 (202) 783-3238
769
770 Standards Processing Coordinator (ADP)
771 National Institute of Standards and Technology
772 Technology Building, Room B-64
773 Gaithersburg, MD 20899
774 (301) 975-2816
775
776
777
778
779
780 <span class="grey">Cerf &amp; Mills [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1169">RFC 1169</a> Explaining the Role of GOSIP August 1990</span>
783
784
785 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Security Considerations</span>
786
787 Security issues are not discussed in this memo.
788
789 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Authors' Addresses</span>
790
791 Vinton G. Cerf
792 Chairman, IAB
793 Corporation for National Research Initiatives
794 1895 Preston White Drive, Suite 100
795 Reston, VA 22091
796
797 Phone: (703) 620-8990
798
799 EMail: [email protected]
800
801
802 Kevin L. Mills
803 National Institute of Standards and Technology
804 Building 225, Room B217
805 Gaithersburg, MD 20899
806
807 Phone: (301) 975-3618
808
809 EMail: [email protected]
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836 Cerf &amp; Mills [Page 15]
837 </pre>