|
|
1.1 root 1: % run this through SLiTeX
2:
3: \documentstyle[blackandwhite,landscape,oval,pagenumbers,small]{NRslides}
4:
5: \raggedright
6:
7: \input trademark
8:
9: \begin{document}
10:
11: \title {TREKKING TO ISO:\\ BEAM US OVER, SCOTTY}
12: \author {Marshall T.~Rose\\
13: Computer Science Laboratory\\
14: Northrop Research and Technology Center}
15: \date {October 7, 1987}
16: \maketitlepage
17:
18:
19: \begin{note}\em
20: first a disclaimer:
21:
22: \begin{quote}
23: i didn't get to choose the title for this talk!
24: \end{quote}
25: \end{note}
26:
27:
28: \begin{bwslide}
29: \ctitle {FUNDAMENTAL PREMISES}
30:
31: \begin{nrtc}
32: \item OSI/ISO WILL DOMINATE COMPUTER COMMUNICATIONS
33:
34: \item EXISTING INVESTMENTS (IN NON-OSI TECHNOLOGY) SHOULD BE PROTECTED
35: \begin{nrtc}
36: \item BUT REALISTICALLY, EQUIPMENT HAS A HALF-LIFE OF 5 YEARS
37: \end{nrtc}
38:
39: \item NEW INVESTMENTS SHOULD EITHER BE OSI OR HAVE A HIGH DEGREE OF
40: OSI-COMPATIBILITY
41: \end{nrtc}
42: \end{bwslide}
43:
44:
45: \begin{bwslide}
46: \ctitle {WHAT IS OSI/ISO?}
47:
48: \begin{nrtc}
49: \item A LAYERED ARCHITECTURE FOR COMPUTER COMMUNICATIONS
50:
51: \item STANDARDIZED IN THE INTERNATIONAL COMMUNITY
52:
53: \item NON-PROPRIETARY IN NATURE
54: \end{nrtc}
55: \end{bwslide}
56:
57:
58: \begin{bwslide}
59: \ctitle {FROM A COMMUNICATIONS VIEWPOINT}
60:
61: \vskip.5in
62: \diagram[p]{figure0a}
63: \end{bwslide}
64:
65:
66: \begin{bwslide}
67: \ctitle {FROM A COMPUTER VIEWPOINT}
68:
69: \vskip.5in
70: \diagram[p]{figure0b}
71: \end{bwslide}
72:
73:
74: \begin{bwslide}
75: \ctitle {THE 7--LAYER STACK}
76:
77: \vskip.5in
78: \diagram[p]{figure0c}
79: \end{bwslide}
80:
81:
82: \begin{bwslide}
83: \ctitle {THE OSI APPLICATION LAYER}
84:
85: \begin{nrtc}
86: \item MANY STANDARD SERVICE ELEMENTS
87: \begin{nrtc}
88: \item ASSOCATION CONTROL
89:
90: \item REMOTE OPERATIONS
91:
92: \item RELIABLE TRANSFER
93:
94: \item COMMITMENT, CONCURRENCY AND RECOVERY
95:
96: \item ABSTRACT SYNTAX NOTATION ONE\\
97: (REALLY PRESENTATION LAYER)
98: \end{nrtc}
99: \end{nrtc}
100: \end{bwslide}
101:
102:
103: \begin{bwslide}
104: \ctitle {FTAM USE OF UPPER-LAYER ELEMENTS}
105:
106: \vskip.5in
107: \diagram[p]{figure3}
108: \end{bwslide}
109:
110:
111: \begin{note}\em
112: will use the terms ISO and OSI interchangeably from now on
113:
114: ISO will provide the dominant communication protocol family in the 1990's
115: \end{note}
116:
117:
118: \begin{bwslide}
119: \ctitle {POSSIBLE SOLUTION \#1\\ EXAGERATED, OBVIOUSLY}
120:
121: \begin{nrtc}
122: \item FIRE ALL NON-OSI PERSONNEL
123:
124: \item SELL ALL NON-OSI EQUIPMENT
125:
126: \item BANKROLL ONLY PURE-OSI INVESTMENTS
127: \end{nrtc}
128: \end{bwslide}
129:
130:
131: \begin{bwslide}
132: \ctitle {NOT A VERY GOOD IDEA\\ (NOT RECOMMENDED)}
133:
134: \begin{nrtc}
135: \item CAPABILITY OF {\bf CURRENT\/} OSI PRODUCTS
136: NOT AS GOOD AS OTHER EXISTING NETWORKING PRODUCTS
137:
138: \item WE CAN'T SHUTDOWN THE FACTORY/OFFICE
139:
140: \item A REVOLUTIONARY APPROACH WHEN WE NEED EVOLUTION
141: \end{nrtc}
142: \end{bwslide}
143:
144:
145: \begin{note}\em
146: in fact, at one map/top meeting, it was noted that
147:
148: \begin{quote}
149: ``NORTHROP has shipped more OSI software than any OSI vendor''
150: \end{quote}
151:
152: by one of the leading OSI vendors!
153: \end{note}
154:
155:
156: \begin{bwslide}
157: \ctitle {POSSIBLE SOLUTION \#2\\ NOT SO EXAGERATED}
158:
159: \begin{nrtc}
160: \item START BUILDING A SEPARATE OSI ENVIRONMENT INDEPENDENT OF THE EXISTING
161: ENVIRONMENT
162:
163: \item SWITCH WHEN OSI TECHNOLOGY REACHES SUPERIOR CAPABILITY
164:
165: \item EMPLOY HIGH-LEVEL GATEWAYS TO SHUTTLE INFORMATION BETWEEN ENVIRONMENTS
166: (e.g., PROFS TO X.400)
167: \end{nrtc}
168: \end{bwslide}
169:
170:
171: \begin{bwslide}
172: \diagram[p]{figure1}
173: \end{bwslide}
174:
175:
176: \begin{bwslide}
177: \ctitle {A BETTER IDEA, BUT NOT PERFECT}
178:
179: \begin{nrtc}
180: \item PERMITS US TO GAIN EXPERIENCE WITH THE NEW TECHNOLOGY
181:
182: \item HOPEFULLY DOESN'T INTERFERE WITH EXISTING OPERATIONS
183:
184: \item SOME DUPLICATION OF EFFORT
185:
186: \item HIGH-LEVEL GATEWAYS OFTEN DON'T WORK VERY WELL
187: \begin{nrtc}
188: \item ``SOMETIMES WHEN YOU TRY TO TURN AN APPLE INTO AN ORANGE YOU
189: GET BACK A LEMON''
190: \end{nrtc}
191: \end{nrtc}
192: \end{bwslide}
193:
194:
195: \begin{bwslide}
196: \ctitle {POSSIBLE SOLUTION \#3}
197:
198: \begin{nrtc}
199: \item START BUILDING AN OSI ENVIRONMENT ON TOP OF EXISTING ENVIRONMENTS
200:
201: \item BUILD SELECTED NEW SYSTEMS WITH OSI
202:
203: \item MIGRATE EXISTING APPLICATIONS TO AN OSI FRAMEWORK AS THE TECHNOLOGY
204: BECOMES AVAILABLE
205:
206: \item CONTINUE RUNNING SELECTED SYSTEMS ``AS IS''
207: \end{nrtc}
208: \end{bwslide}
209:
210:
211: \begin{bwslide}
212: \diagram[p]{figure2a}
213: \end{bwslide}
214:
215:
216: \begin{bwslide}
217: \ctitle {AN EXAMPLE:\\ ISO TRANSPORT SERVICES ON TOP OF DoD TCP}
218:
219: \vskip-0.1in
220: \diagram[p]{figure2b}
221: \end{bwslide}
222:
223:
224: \begin{bwslide}
225: \ctitle {THE GOOD NEWS}
226:
227: \begin{nrtc}
228: \item AN ORDERLY AND GRADUAL MIGRATION
229:
230: \item MAXIMIZES USE OF EXISTING RESOURCES
231:
232: \item PROOF OF CONCEPT: ISODE, DECnet/ISO
233:
234: \item FACILITATES BEST TOOL FOR THE JOB
235: \end{nrtc}
236: \end{bwslide}
237:
238:
239: \begin{bwslide}
240: \ctitle {THE BAD NEWS}
241:
242: \begin{nrtc}
243: \item A ``NON-PURE'' SOLUTION (PURITY IS A RELIGION!)
244:
245: \item DOES NOT SUPPORT A SINGLE TOOL FOR THE JOB
246: \end{nrtc}
247: \end{bwslide}
248:
249:
250: \begin{bwslide}
251: \ctitle {SUMMARY}
252:
253: \begin{nrtc}
254: \item THE GOOD: INTEGRATED (USE SERVICE EMULATORS)
255:
256: \item THE BAD: SEPARATE (USE APPLICATION GATEWAYS)
257:
258: \item THE UGLY: REVOLUTION (START FROM SCRATCH)
259: \end{nrtc}
260: \end{bwslide}
261:
262:
263: \begin{bwslide}
264: \ctitle {ISODE}
265:
266: \begin{nrtc}
267: \item AN OPENLY AVAILABLE ISO DEVELOPMENT ENVIRONMENT
268:
269: \item CODED ENTIRELY IN C
270:
271: \item OPERATING SYSTEMS: BERKELEY AND AT\&T \unix/
272: \begin{nrtc}
273: \item REQUIRES NO KERNEL MODIFICATIONS
274: \end{nrtc}
275:
276: \item INFLUENCED A LOT BY GOSIP GUIDELINES
277: \end{nrtc}
278: \end{bwslide}
279:
280:
281: \begin{bwslide}
282: \ctitle {THE APPLICATION ENVIRONMENT}
283:
284: \vskip.15in
285: \diagram[p]{figure4}
286: \end{bwslide}
287:
288:
289: \begin{bwslide}
290: \ctitle {AN ALTERNATE ENVIRONMENT:\\ MHS ARCHITECTURE (c.~1984)}
291:
292: \vskip.15in
293: \diagram[p]{figure5}
294: \end{bwslide}
295:
296:
297: \begin{bwslide}
298: \ctitle {TRANSPORT SERVICES}
299:
300: \begin{nrtc}
301: \item CURRENTLY A TP0 TRANSPORT SERVICE IS USED
302: \begin{nrtc}
303: \item OVER X.25 (FOR EUROPEANS, et. al.)
304:
305: \item OVER TCP (FOR DEFENSE DATA NETWORK)
306: \end{nrtc}
307:
308: \item TCP-BASED SERVICE IS INDISTINGUISHABLE FROM A CONNECTION-ORIENTED
309: NETWORK SERVICE\\ (SEE RFC1006 FOR THE DETAILS)
310:
311: \item WORK WILL START SOON ON INTEGRATING A NATIVE TP4
312: \end{nrtc}
313: \end{bwslide}
314:
315:
316: \begin{bwslide}
317: \ctitle {WHERE NEXT?}
318:
319: \begin{nrtc}
320: \item UPGRADE TO FINAL (IS) SPECIFICATIONS
321:
322: \item ``COOKED'' SUPPORT FOR REMOTE OPERATIONS
323:
324: \item INTEGRATION OF:
325: \begin{nrtc}
326: \item MHS
327:
328: \item DIRECTORY SERVICES
329:
330: \item VIRTUAL TERMINAL
331: \end{nrtc}
332: IMPLEMENTATIONS DONE AT OTHER SITES
333: \end{nrtc}
334: \end{bwslide}
335:
336:
337: \begin{bwslide}
338: \ctitle {AVAILABILITY INFORMATION}
339:
340: \begin{nrtc}
341: \item VERSION 3 AVAILABLE OCTOBER 14, 1987
342:
343: \item USPS: SEND CHECK OR INVOICE FOR \$200 US DOLLARS TO:
344: \[\begin{tabular}{l}
345: ISODE DISTRIBUTION\\
346: DEPARTMENT OF ELECTRICAL ENGINEERING\\
347: UNIVERSITY OF DELAWARE\\
348: NEWARK, DE 19716\\[0.25in]
349: TELCO: 302--451--1163
350: \end{tabular}\]
351:
352: \item DISTRIBUTION CONTAINS:
353: \begin{nrtc}
354: \item 1600bpi TAR TAPE
355:
356: \item 3 VOLUME DOCUMENTATION SET
357: \end{nrtc}
358: \end{nrtc}
359: \end{bwslide}
360:
361:
362: \end{document}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.