![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to osi-update.tex CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / osi-update|
Return to osi-update.tex CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / osi-update |
1.1 root 1: % run this through SLiTeX
2:
3: \documentstyle[blackandwhite,landscape,oval,pagenumbers,plain,small]{NRslides}
4:
5: \input trademark
6:
7: \raggedright
8:
9: \begin{document}
10:
11: \title {RECENT DEVELOPMENTS WITH\\ OSI IMPLEMENTATIONS}
12: \author {Marshall T.~Rose\\The Wollongong Group}
13: \date {January 13, 1988}
14: \maketitlepage
15:
16:
17: \begin{bwslide}
18: \part* {AGENDA}\bf
19:
20: \begin{description}
21: \item[PART I:] OSI PROTOCOLS WITHIN AN OPENLY AVAILABLE, POSIX CONFORMANT,
22: BERKELEY UNIX ENVIRONMENT
23:
24: \item[PART II:] EXPERIMENTAL OSI-BASED NETWORK
25:
26: \item[PART III:]TRANSPORT-LEVEL BRIDGES
27: \end{description}
28: \end{bwslide}
29:
30:
31: \begin{bwslide}
32: \part {OSI PROTOCOLS WITHIN AN\\
33: OPENLY AVAILABLE\\ POSIX CONFORMANT\\ BERKELEY UNIX ENVIRONMENT}
34: \end{bwslide}
35:
36:
37: \begin{note}\em
38: if i've left out any
39: \begin{quote}
40: buzzwords\\
41: jargon\\
42: marketing hype\\
43: \end{quote}
44: please let me know and i'll add them!
45:
46: also, henceforth ``users'' means ``u.s.~govt. users''
47: \end{note}
48:
49:
50: \begin{bwslide}
51: \ctitle {STANDARD DISCLAIMER}
52:
53: \begin{nrtc}
54: \item THE VIEWS PRESENTED HERE ARE NOT NECESSARILY THOSE OF:
55: \begin{quote}
56: TWG, DoD, MITRE, NBS, U.C.~BERKELEY, UCL, UWISC, THE U.S.~GOVT,
57: OR ANY OTHER ACRONYM, AGENCY, OR ORGANIZATION
58: \end{quote}
59:
60: \item I APOLOGIZE ONLY TO THOSE WHOM I HAVE UNINTENTIONALLY OFFENDED
61: \end{nrtc}
62: \end{bwslide}
63:
64:
65: \begin{bwslide}
66: \ctitle {FUNDAMENTAL PREMISES:\\ NETWORKING}
67:
68: \begin{nrtc}
69: \item OSI/ISO WILL EVENTUALLY DOMINATE COMPUTER COMMUNICATIONS
70:
71: \item THE U.S. GOVERNMENT OSI PROFILE (GOSIP) WILL BE THE INITIAL SET OF
72: GUIDELINES FOR PROCUREMENT OF OSI FOR USERS
73: \end{nrtc}
74: \end{bwslide}
75:
76:
77: \begin{bwslide}
78: \ctitle {GOSIP}
79:
80: \begin{nrtc}
81: \item A (SOON-TO-BE) FEDERAL INFORMATION PROCESSING STANDARD
82:
83: \item PROPOSED TO ENABLE USERS TO SPECIFY AND PROCURE
84: \begin{nrtc}
85: \item INTEROPERABLE
86:
87: \item MULTI-VENDOR
88:
89: \item OFF-THE-SHELF
90: \end{nrtc}
91: COMPUTER COMMUNICATIONS PRODUCTS
92:
93: \item THE \dod/:
94: \begin{nrtc}
95: \item IS ADOPTING GOSIP AS A CO-STANDARD WITH TCP/IP
96:
97: \item INTENDS (IN APPROX.~TWO YEARS) TO SPECIFY GOSIP AS THE
98: \underbar{ONLY} STANDARD FOR NON-PROPRIETARY, INTEROPERABLE
99: COMPUTER COMMUNICATIONS
100: \end{nrtc}
101: \end{nrtc}
102: \end{bwslide}
103:
104:
105: \begin{bwslide}
106: \ctitle {FUNDAMENTAL PREMISES:\\ OPERATING SYSTEMS}
107:
108: \begin{nrtc}
109: \item THE \unix/ FAMILY WILL DOMINATE OPERATING SYSTEMS
110:
111: \item THE EMERGING IEEE \unix/-BASED PORTABLE OPERATING SYSTEM
112: STANDARD (POSIX) WILL BE THE BASELINE FOR THESE SYSTEMS
113:
114: \item ANOTHER FIPS IS UNDER DEVELOPMENT TO BE THE INITIAL SET OF
115: GUIDELINES FOR PROCUREMENT OF OPERATING SYSTEMS FOR USERS
116: \end{nrtc}
117: \end{bwslide}
118:
119:
120: \begin{bwslide}
121: \ctitle {POSIX}
122:
123: \begin{nrtc}
124: \item CURRENTLY POSIX SPECIFIES ONLY THE \unix/ KERNEL INTERFACE
125: \begin{nrtc}
126: \item INFLUENCED MOSTLY BY AT\&T \unix/ (SVID) WITH SOME BERKELEY
127: ENHANCEMENTS
128: \end{nrtc}
129:
130: \item WORK IS UNDERWAY ON A SHELL AND TOOLS STANDARD
131:
132: \item A STANDARD INTERFACE FOR NETWORKING IS NOTABLY MISSING
133: \end{nrtc}
134: \end{bwslide}
135:
136:
137: \begin{bwslide}
138: \ctitle {A MODEST OBSERVATION}
139:
140: \begin{nrtc}
141: \item TCP/IP BECAME WIDESPREAD AFTER IT WAS INCLUDED IN BERKELEY \unix/
142:
143: \item QUESTIONS:
144: \begin{nrtc}
145: \item CAN WE PUT A REFERENCE VERSION OF THE OSI PROTOCOLS INTO
146: BERKELEY \unix/?
147:
148: \item CAN WE MAKE BERKELEY \unix/ POSIX COMPLIANT?
149:
150: \item CAN WE EXTEND POSIX TO DEFINE AN INTERFACE TO NETWORK SERVICES?
151:
152: \item CAN WE MAKE THE WORK OPENLY AVAILABLE AND HAVE IT READY FOR
153: 4.4\bsd/~\unix/?
154: \end{nrtc}
155:
156: \item ANSWER: YES
157:
158: \item THIS SHOULD RESULT IN ACCELERATING THE UBIQUITY OF OSI
159: \end{nrtc}
160: \end{bwslide}
161:
162:
163: \begin{bwslide}
164: \ctitle {EXPLANATION}
165:
166: \begin{nrtc}
167: \item A LARGE NUMBER OF THE PIECES ARE ALREADY OPENLY AVAILABLE
168:
169: \item SO, THE WORK CONSISTS MAINLY OF:
170: \begin{nrtc}
171: \item FILLING IN THE GAPS
172:
173: \item INTEGRATING THE COMPONENTS
174:
175: \item TESTING THE SYSTEM\\ (INTEROPERABILITY AND CONFORMANCE)
176: \end{nrtc}
177:
178: \item THIS MODEST AMOUNT OF WORK SHOULD RESULT IN ACCELERATING THE UBIQUITY
179: OF OSI
180: \end{nrtc}
181: \end{bwslide}
182:
183:
184: \begin{bwslide}
185: \ctitle {APPROACH:\\ OSI PROTOCOLS}
186:
187: \begin{nrtc}
188: \item AN IMPLEMENTATION OF THE OSI UPPER-LAYERS (ISODE) IS ALREADY AVAILABLE
189:
190: \item OTHER ORGANIZATIONS HAVE DEVELOPED OR PLAN TO DEVELOP:
191: \begin{nrtc}
192: \item THE LOWER LAYERS
193:
194: \item SOME OSI APPLICATIONS
195: \end{nrtc}
196:
197: \item MOST STANDARDS HAVE PROGRESSED FROM DRAFT (DIS) TO FINAL (IS) STATUS
198: \end{nrtc}
199: \end{bwslide}
200:
201:
202: \begin{bwslide}
203: \diagram[p]{figure1}
204: \end{bwslide}
205:
206:
207: \begin{bwslide}
208: \diagram[p]{figure2}
209: \end{bwslide}
210:
211:
212: \begin{bwslide}
213: \ctitle {THE WORK PLAN}
214:
215: \begin{nrtc}
216: \item UPGRADE ISODE AND OTHER OSI APPLICATIONS TO FINAL (IS) STATUS
217:
218: \item INTEGRATE OTHER OSI APPLICATIONS INTO ISODE
219:
220: \item PERFORM INTEROPERABILITY TESTING ON OSInet
221:
222: \item PERFORM CONFORMANCE TESTING WITH COS
223: \end{nrtc}
224: \end{bwslide}
225:
226:
227: \begin{bwslide}
228: \ctitle {APPROACH:\\ POSIX COMPLIANCE}
229:
230: \begin{nrtc}
231: \item MINOR WORK TO MODIFY THE BERKELEY \unix/ KERNEL TO SUPPORT THE POSIX
232: STANDARD
233:
234: \item PERFORM CONFORMANCE TESTING WITH NBS
235:
236: \item ISODE AND OSI APPLICATIONS WILL BE CONVERTED TO USE THE POSIX
237: INTERFACE AS APPLICABLE
238: \end{nrtc}
239: \end{bwslide}
240:
241:
242: \begin{bwslide}
243: \ctitle {APPROACH:\\ POSIX NETWORK SERVICE}
244:
245: \begin{nrtc}
246: \item A /usr/group COMMITTEE WAS FORMED OVER A YEAR AGO
247:
248: \item U.C.~BERKELEY (AND FRIENDS) WILL EXAMINE THE OUTPUT OF THIS
249: GROUP AND EITHER:
250: \begin{nrtc}
251: \item ADOPT THIS INTERFACE (IF ACCEPTED BY POSIX), OR
252:
253: \item SUBMIT A NEW DRAFT PROPOSAL TO THE POSIX COMMITEE
254: \end{nrtc}
255: \end{nrtc}
256: \end{bwslide}
257:
258:
259: \begin{bwslide}
260: \ctitle {SCHEDULE}
261:
262: \begin{nrtc}
263: \item WOULD YOU BELIEVE 18~CALENDAR-MONTHS?
264:
265: \item ACTUALLY 120~MAN-MONTHS%
266: \footnote{You may have read Brooks' {\em The Mythical Man-Month}.}
267: \end{nrtc}
268: \end{bwslide}
269:
270:
271: \begin{bwslide}
272: \part {EXPERIMENTAL\\ OSI-BASED NETWORK}
273: \end{bwslide}
274:
275:
276: \begin{bwslide}
277: \ctitle {MOTIVATION}
278:
279: \begin{nrtc}
280: \item GOAL: WANT TO SPEED DEVELOPMENT OF AND EXPERIMENTATION WITH
281: LOWER-LAYER ISO PROTOCOLS, e.g.,
282: \begin{nrtc}
283: \item TP4, CLNP, ES-IS
284:
285: \item IS-IS
286: \end{nrtc}
287:
288: \item AND WITH NETWORK MANAGEMENT, e.g., NETWORK LAYER SUPPORT FOR CMIS
289:
290:
291: \item ASIDE: IN ADDITION TO AREAS SUCH AS PERFORMANCE TUNING, etc.,
292: ALSO INTERESTED IN PROMOTING INTEROPERABILITY TESTING AMONGST
293: VARIOUS IMPLEMENTATIONS
294: \end{nrtc}
295: \end{bwslide}
296:
297:
298: \begin{bwslide}
299: \ctitle {REQUIREMENTS}
300:
301: \begin{nrtc}
302: \item A ``TYPICAL'' DATAGRAM SERVICE
303: \begin{nrtc}
304: \item POSSIBLE PACKET LOSS, CORRUPTION, DUPLICATION, AND
305: RE-ORDERING, etc.
306: \end{nrtc}
307:
308: \item OFFERED OVER A HETEROGENEOUS COLLECTION OF SUBNETS
309: \begin{nrtc}
310: \item MULTIPLE PATHS, VARYING LINK AND MEDIA CHARACTERISTICS, etc.
311: \end{nrtc}
312:
313: \item WHICH IS WELL-USED (OVER-SUBSCRIBED).
314: \begin{nrtc}
315: \item CONGESTION, VARIABLE DELAY, etc.
316: \end{nrtc}
317:
318: \item IN SHORT, WE WANT A RICH LOWER-LAYER INFRASTRUCTURE
319: \begin{nrtc}
320: \item e.g., A NATIONAL CLNP-BASED INTERNET
321: \end{nrtc}
322: \end{nrtc}
323: \end{bwslide}
324:
325:
326: \begin{bwslide}
327: \ctitle {OBSERVATION}
328:
329: \begin{nrtc}
330: \item WHERE HAVE WE SEEN ONE OF THOSE?
331: \begin{nrtc}
332: \item $\ldots$ THE DARPA/NSF INTERNET!
333: \end{nrtc}
334:
335: \item THE INTERNET MEETS ALL THE REQUIREMENTS BUT ONE:
336: \begin{nrtc}
337: \item IT IS IP-BASED RATHER THAN CLNP-BASED
338: \end{nrtc}
339:
340: \item SO, WHAT IS NEEDED IS A WAY TO EMULATE A CLNP-BASED NETWORK
341: ON TOP OF THE EXISTING DARPA/NSF INTERNET
342: \end{nrtc}
343: \end{bwslide}
344:
345:
346: \begin{bwslide}
347: \ctitle {EON:\\ AN EXPERIMENTAL\\ OSI-BASED NETWORK}
348:
349: \begin{nrtc}
350: \item AN RFC HAS BEEN SUBMITTED BY UWISC AND TWG DESCRIBING:
351: \begin{nrtc}\em
352: \item USE OF THE DARPA/NSF INTERNET AS A SUBNETWORK FOR
353: EXPERIMENTATION WITH THE OSI NETWORK LAYER
354: \end{nrtc}
355:
356: \item PARTICIPATING IP-NODES FORM A LOGICAL ISO NETWORK
357: \begin{nrtc}
358: \item A NODE PARTICIPATES AS AN IS, ES, OR BOTH
359:
360: \item SEVERAL LOGICAL ISO SUBNETS CAN EXIST ON THE DARPA/NSF INTERNET
361: \end{nrtc}
362:
363: \item IT IS NON-DESTRUCTIVE IN THE SENSE THAT IT DOES NOT AFFECT THE
364: EXISTING IP-BASED CONNECTIVITY (CORE GATEWAYS, etc.)
365: \end{nrtc}
366: \end{bwslide}
367:
368:
369: \begin{bwslide}
370: \ctitle {EON DEFINES PROCEDURES FOR}
371:
372: \begin{nrtc}
373: \item ENCAPSULATION OF NPDUs
374:
375: \item FORMATION AND MAPPING OF SNPA-ADDRESSES
376:
377: \item USE OF SUBNET MULTICASTING IN CLNL
378:
379: \item DISSEMINATION OF TOPOLOGICAL INFORMATION
380: \end{nrtc}
381: \end{bwslide}
382:
383:
384: \begin{bwslide}
385: \ctitle {SCHEDULE}
386:
387: \begin{nrtc}
388: \item EON IS NEW, THE RFC, ALTHOUGH SUBMITTED, HASN'T BEEN RELEASED YET
389:
390: \item BUT, BY APRIL, UWISC AND TWG EXPECT TO BE PARTICIPATING IN INTERNET
391: EXPERIMENTS
392: \end{nrtc}
393: \end{bwslide}
394:
395:
396:
397: \begin{bwslide}
398: \part {TRANSPORT-LEVEL BRIDGES}
399: \end{bwslide}
400:
401:
402: \begin{bwslide}
403: \ctitle {MOTIVATION}
404:
405: \begin{nrtc}
406: \item THERE ARE MANY TCP/IP NETWORKS TODAY, THERE WILL BE MORE TOMMORROW
407:
408: \item BY THE TIME OSI/OSI BECOMES A WORTHWHILE OPERATION ALTERNATIVE,
409: THERE WILL BE MANY MORE TCP/IP NETWORKS THAN THERE ARE TODAY!
410:
411: \item PREDICTION: AT THAT TIME, TCP/IP NETWORKS WILL
412: OFFER A MIX OF SERVICES:
413: \begin{nrtc}
414: \item SUCH AS FTAM AND X.400, IN ADDITION TO FTP AND SMTP
415: \end{nrtc}
416:
417: \item FURTHER PREDICATION: THIS MIX WILL PROLIFERATE TO PERMEATE
418: BOTH TCP/IP AND OSI/ISO NETWORKS
419: \end{nrtc}
420: \end{bwslide}
421:
422:
423: \begin{bwslide}
424: \ctitle {OBSERVATION}
425:
426: \begin{nrtc}
427: \item GIVEN THE ASSUMPTION ABOVE, IT SHOULD BE NOTED THAT:
428: \begin{nrtc}
429: \item THE TWO COMMUNITIES ARE USING THE SAME APPLICATIONS,
430: AND
431:
432: \item ONLY THE UNDERLYING NETWORK AND TRANSPORT PROTOCOLS WILL
433: DIFFER BETWEEN THE TWO
434: \end{nrtc}
435:
436: \item THIS LEADS US TO POSTULATE AN INTERESTING COEXISTENCE
437: STRATEGY:
438: \begin{nrtc}
439: \item LET'S RUN ISO APPLICATIONS BETWEEN THE TWO COMMUNITIES
440: \end{nrtc}
441: \end{nrtc}
442: \end{bwslide}
443:
444:
445: \begin{bwslide}
446: \ctitle {TRANSPORT-LEVEL BRIDGES}
447:
448: \begin{nrtc}
449: \item IDEA: OFFER THE SAME TRANSPORT SERVICE INTERFACE IN BOTH
450: COMMUNITIES (THE ISO TRANSPORT SERVICE)
451: \begin{nrtc}
452: \item USE RFC1006 TO OFFER THE ISO TRANSPORT SERVICE ON TOP OF
453: THE TCP
454: \end{nrtc}
455:
456: \item INTRODUCE A TRANSPORT ENTITY CALLED THE ``TS-BRIDGE''
457:
458: \item THE TS-BRIDGE ``COPIES'' SERVICE PRIMITIVES FROM ONE COMMUNITY TO THE
459: OTHER, e.g.,
460: \begin{nrtc}
461: \item UPON RECEIVING A T-CONNECT.INDICATION PRIMITIVE FROM ONE
462: NETWORK,
463:
464: \item IT ISSUES A T-CONNECT.REQUEST PRIMITIVE TO THE OTHER NETWORK
465: \end{nrtc}
466:
467: \item THE TS-BRIDGE MAINTAINS STATE AS TO THE EXISTING CONNECTIONS
468: (AND AS SUCH IS A SINGLE POINT OF FAILURE)
469: \end{nrtc}
470: \end{bwslide}
471:
472:
473: \begin{note}\em
474: perhaps these should be called ``gateways'' instead of ``ts-bridges''
475:
476: well, they are *so* simple that ``gateway'' really seems to be an overloaded
477: term in this circumstance$\ldots$
478:
479: in fact, simplicity is one reason why this approach was chosen over a
480: network-level solution
481: \end{note}
482:
483:
484: \begin{bwslide}
485: \ctitle {TRANSPARENT USE OF TS-BRIDGES}
486:
487: \begin{nrtc}
488: \item BY JUDICIOUS USE OF DIRECTORY SERVICES, SELECTION OF THE
489: TS-BRIDGE CAN BE MADE TRANSPARENT ON BOTH ENDPOINTS
490:
491: \item CONSIDER A ``TYPICAL'' PRESENTATION ADDRESS:
492: \[\begin{tabular}{ll}
493: network address:& CLNP 4700050017000008002000405301\\
494: transport selector:& 1\\
495: session selector:& ``FTAM''\\
496: presentation selector:& null
497: \end{tabular}\]
498:
499: \item A SLIGHTLY DIFFERENT ENTRY IS RETURNED FOR HOSTS IN THE
500: OPPOSITE COMMUNITY:
501: \[\begin{tabular}{ll}
502: network address:& ts-bridge's network address\\
503: transport selector:& \begin{tabular}[t]{ll}
504: network address:&
505: CLNP 47 $\ldots$\\
506: transport selector:& 1
507: \end{tabular}\\
508: session selector:& ``FTAM''\\
509: presentation selector:& null
510: \end{tabular}\]
511: \end{nrtc}
512: \end{bwslide}
513:
514:
515: \begin{bwslide}
516: \ctitle {ANOTHER PROBLEM SOLVED:\\ ISO CONS versus CLNS}
517:
518: \begin{nrtc}
519: \item IN GENERAL, THE TS-BRIDGE SHOWS HOW TO PERFORM
520: ``IMPEDANCE MATCHING'' BETWEEN TWO PROTOCOLS WHICH OFFER THE
521: SAME SERVICE INTERFACE, e.g., OUR USE IS:
522: \begin{nrtc}
523: \item PROTOCOLS: TP4/CLNP AND TP0/TCP
524:
525: \item SERVICE: ISO TRANSPORT SERVICE
526: \end{nrtc}
527:
528: \item THIS IS SUSPICIOUSLY SIMILAR TO THE ISO CONS vs. CLNS PROBLEM:
529: \begin{nrtc}
530: \item PROTOCOLS: TP4/CLNP AND TP0/X.25
531:
532: \item SERVICE: ISO TRANSPORT SERVICE
533: \end{nrtc}
534:
535: \item THE TS-BRIDGE WILL ALSO WORK IN THIS ENVIRONMENT WITHOUT
536: MEANINGFUL LOSS OF GENERALITY:
537: \begin{nrtc}
538: \item EXPEDITED DATA IS NEGOTIATED AWAY, AND
539:
540: \item USER DATA ON CONNECTION PRIMITIVE IS DISREGARDED
541: \end{nrtc}
542: \end{nrtc}
543: \end{bwslide}
544:
545:
546: \end{document}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.