![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to ncf.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 / ncf|
Return to ncf.tex CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / ncf |
1.1 root 1: % run this through SLiTeX
2:
3: \documentstyle[blackandwhite,landscape,oval,pagenumbers,plain,small]{NRslides}
4:
5: \raggedright
6:
7: \input trademark
8:
9: \begin{document}
10:
11: \title {FOCUS ON OSI FOR\\ NETWORKED APPLICATIONS}
12: \author {Marshall T.~Rose\\ The Wollongong Group}
13: \date {November 18, 1987}
14: \maketitlepage
15:
16:
17: \begin{note}\em
18: all of the original work reported herein was done at the Northrop Research
19: and Technology Center
20: \begin{quote}
21: in particular, the support of Dr.~Stephen J.~Lukasik,\\
22: Vice President~---~Technology is gratefully acknowledged
23: \end{quote}
24:
25: other individuals contributing to this work include:
26: \begin{nrtc}\em
27: \item at UCL: Steve Kille
28:
29: \item at NPL: John Pavel
30:
31: \item at Nott: Julian Onions
32:
33: \item at NMA: Einar Stefferud
34: \end{nrtc}
35: \end{note}
36:
37:
38: \begin{bwslide}
39: \ctitle {FUNDAMENTAL PREMISES}
40:
41: \begin{nrtc}
42: \item OSI/ISO WILL DOMINATE COMPUTER COMMUNICATIONS
43:
44: \item EXISTING INVESTMENTS (IN NON-OSI TECHNOLOGY) SHOULD BE PROTECTED
45:
46: \item BUT REALISTICALLY, EQUIPMENT HAS A HALF-LIFE OF 5 YEARS, SO$\ldots$
47:
48: \item NEW INVESTMENTS SHOULD EITHER BE OSI OR HAVE A HIGH DEGREE OF
49: OSI-COMPATIBILITY
50: \end{nrtc}
51: \end{bwslide}
52:
53:
54: \begin{bwslide}
55: \ctitle {WHAT IS OSI/ISO?}
56:
57: \begin{nrtc}
58: \item A LAYERED ARCHITECTURE FOR COMPUTER COMMUNICATIONS
59:
60: \item STANDARDIZED IN THE INTERNATIONAL COMMUNITY
61:
62: \item NON-PROPRIETARY IN NATURE
63: \end{nrtc}
64: \end{bwslide}
65:
66:
67: \begin{bwslide}
68: \ctitle {FROM A COMMUNICATIONS VIEWPOINT}
69:
70: \vskip.5in
71: \diagram[p]{figure1}
72: \end{bwslide}
73:
74:
75: \begin{bwslide}
76: \ctitle {FROM A COMPUTER VIEWPOINT}
77:
78: \vskip.5in
79: \diagram[p]{figure2}
80: \end{bwslide}
81:
82:
83: \begin{bwslide}
84: \ctitle {(OBLIGATORY SLIDE SHOWING)\\ THE 7--LAYER STACK}
85:
86: \vskip.5in
87: \diagram[p]{figure3}
88: \end{bwslide}
89:
90:
91: \begin{bwslide}
92: \ctitle {THE UPPER-LAYER ARCHITECTURE}
93:
94: \vskip.15in
95: \diagram[p]{figure4}
96: \end{bwslide}
97:
98:
99: \begin{bwslide}
100: \ctitle {THE OSI APPLICATION LAYER}
101:
102: \begin{nrtc}
103: \item MANY STANDARD SERVICE ELEMENTS
104: \begin{nrtc}
105: \item ASSOCIATION CONTROL
106:
107: \item REMOTE OPERATIONS
108:
109: \item RELIABLE TRANSFER
110:
111: \item COMMITMENT, CONCURRENCY AND RECOVERY
112:
113: \item DIRECTORY SERVICES
114:
115: \item ABSTRACT SYNTAX NOTATION ONE\\
116: (really a concept not an element, per se)
117: \end{nrtc}
118: \end{nrtc}
119: \end{bwslide}
120:
121:
122: \begin{bwslide}
123: \ctitle {FTAM USE OF UPPER-LAYER SERVICES}
124:
125: \vskip.5in
126: \diagram[p]{figure5}
127: \end{bwslide}
128:
129:
130: \begin{bwslide}
131: \ctitle {OSI SERVICES IN NON-OSI ENVIRONMENTS}
132:
133: \begin{nrtc}
134: \item START BUILDING AN OSI ENVIRONMENT ON TOP OF EXISTING ENVIRONMENTS
135:
136: \item BUILD SELECTED NEW APPLICATION SYSTEMS WITH OSI
137:
138: \item MIGRATE EXISTING APPLICATIONS TO AN OSI FRAMEWORK AS THE TECHNOLOGY
139: BECOMES AVAILABLE
140:
141: \item CONTINUE RUNNING SELECTED SYSTEMS ``AS IS''
142:
143: \item PROOF OF CONCEPT: DECnet/ISO, STREAMS/TLI, ISODE
144: \end{nrtc}
145: \end{bwslide}
146:
147:
148: \begin{bwslide}
149: \ctitle {SERVICE EMULATOR AT TRANSPORT}
150:
151: \vskip.5in
152: \diagram[p]{figure6}
153: \end{bwslide}
154:
155:
156: \begin{bwslide}
157: \ctitle {AN EXAMPLE:\\ ISO TRANSPORT SERVICES ON TOP OF DoD TCP}
158: \vskip-0.1in
159: \diagram[p]{figure7}
160: \end{bwslide}
161:
162:
163: \begin{bwslide}
164: \ctitle {ISODE: THE ISO DEVELOPMENT ENVIROMENT}
165:
166: \begin{nrtc}
167: \item AN OPENLY AVAILABLE IMPLEMENTATION OF THE OSI UPPER-LAYERS
168:
169: \item CODED ENTIRELY IN C
170:
171: \item OPERATING SYSTEMS: BERKELEY AND AT\&T \unix/
172: \begin{nrtc}
173: \item REQUIRES NO KERNEL MODIFICATIONS
174: \end{nrtc}
175:
176: \item ALIGNED WITH THE U.S. GOSIP
177:
178: \item AT THE APPLICATION INTERFACE (ABOVE ACSE/ROSE),
179: THROUGHPUT IS ONLY 10\%-12\% WORSE THAN RAW TCP FOR DATA TRANSFER
180: \end{nrtc}
181: \end{bwslide}
182:
183:
184: \begin{bwslide}
185: \ctitle {THE APPLICATION ENVIRONMENT}
186:
187: \vskip.15in
188: \diagram[p]{figure8}
189: \end{bwslide}
190:
191:
192: \begin{bwslide}
193: \ctitle {AN ALTERNATE ENVIRONMENT:\\ MHS ARCHITECTURE (c.~1984)}
194:
195: \vskip.15in
196: \diagram[p]{figure9}
197: \end{bwslide}
198:
199:
200: \begin{bwslide}
201: \ctitle {TRANSPORT SERVICES}
202:
203: \begin{nrtc}
204: \item CURRENTLY A TP0 TRANSPORT SERVICE IS USED
205: \begin{nrtc}
206: \item OVER X.25 (FOR EUROPEANS, et. al.)
207:
208: \item OVER TCP (FOR DEFENSE DATA NETWORK)
209: \end{nrtc}
210:
211: \item TCP-BASED SERVICE IS INDISTINGUISHABLE FROM A CONNECTION-ORIENTED
212: NETWORK SERVICE
213:
214: \item WORK WILL START SOON ON INTEGRATING A NATIVE TP4
215: \end{nrtc}
216: \end{bwslide}
217:
218:
219: \begin{bwslide}
220: \ctitle {WHERE NEXT?}
221:
222: \begin{nrtc}
223: \item UPGRADE TO FINAL (IS) SPECIFICATIONS
224:
225: \item ``COOKED'' SUPPORT FOR REMOTE OPERATIONS
226:
227: \item INTEGRATION OF:
228: \begin{nrtc}
229: \item MHS
230:
231: \item DIRECTORY SERVICES
232:
233: \item VIRTUAL TERMINAL
234: \end{nrtc}
235: IMPLEMENTATIONS DONE AT OTHER SITES
236:
237: \item INTEROPERABILITY/CONFORMANCE TESTING
238: \end{nrtc}
239: \end{bwslide}
240:
241:
242: \begin{bwslide}
243: \ctitle {AVAILABILITY INFORMATION}
244:
245: \begin{nrtc}
246: \item VERSION 3 AVAILABLE OCTOBER 14, 1987
247:
248: \item USPS: SEND CHECK OR INVOICE FOR \$200 US DOLLARS TO:
249: \[\begin{tabular}{l}
250: ISODE DISTRIBUTION\\
251: DEPARTMENT OF ELECTRICAL ENGINEERING\\
252: UNIVERSITY OF DELAWARE\\
253: NEWARK, DE 19716\\[0.25in]
254: TELCO: 302--451--1163
255: \end{tabular}\]
256:
257: \item DISTRIBUTION CONTAINS:
258: \begin{nrtc}
259: \item 1600bpi TAR TAPE
260:
261: \item 3 VOLUME DOCUMENTATION SET
262: \end{nrtc}
263: \end{nrtc}
264: \end{bwslide}
265:
266:
267: \begin{bwslide}
268: \ctitle {FOCUS ON OSI FOR NETWORKED APPLICATIONS}
269:
270: \begin{nrtc}
271: \item TOOLS TO FACILITATE DEVELOPMENT OF APPLICATIONS ARE CRITICAL
272:
273: \item IDEA IS TO DEVELOP TOOLS TO AUTOMATE USE OF OSI REMOTE OPERATIONS
274: SERVICE AS A GENERAL REMOTE PROCEDURE CALL FACILITY
275:
276: \item ECMA TR/31: REMOTE OPERATIONS -- CONCEPTS, NOTATION AND
277: CONNECTION-ORIENTED MAPPINGS (SECTIONS 1--4)
278: \end{nrtc}
279: \end{bwslide}
280:
281:
282: \begin{bwslide}
283: \ctitle {ABSTRACT SYNTAX NOTATION 1 (ASN.1)}
284:
285: \begin{nrtc}
286: \item UNIVERSAL LANGUAGE TO DESCRIBE INFORMATION OBJECTS WITH STRONG TYPING
287:
288: \item RICH, EXTENSIBLE SYNTAX
289:
290: \item USEFUL FOR SPECIFICATION OF NEW PROTOCOLS
291: \begin{nrtc}
292: \item CLEAR TO READ SPECIFICATIONS
293:
294: \item NOT TIED TO MACHINE-ORIENTED STRUCTURES AND RESTRICTIONS
295: \end{nrtc}
296:
297: \item REPRESENTATION CURRENTLY USED BY ALL OSI APPLICATIONS
298: \end{nrtc}
299: \end{bwslide}
300:
301:
302: \begin{bwslide}
303: \ctitle {REMOTE OPERATIONS SERVICE (ROS)}
304:
305: \begin{nrtc}
306: \item STANDARDIZED MECHANISM FOR SPECIFYING TRANSACTIONS
307:
308: \item EMPLOYS FULL POWER OF ASN.1
309:
310: \item USED IN MANY INTERESTING OSI APPLICATIONS
311: \begin{nrtc}
312: \item MESSAGING
313:
314: \item DIRECTORY SERVICES
315:
316: \item NETWORK MANAGEMENT
317:
318: \item REMOTE DATABASE ACCESS
319: \end{nrtc}
320: \end{nrtc}
321: \end{bwslide}
322:
323: \begin{bwslide}
324: \ctitle {GENERAL ORGANIZATION}
325:
326: \begin{nrtc}
327: \item AT COMPILE-TIME:
328: \begin{nrtc}
329: \item USE RO-SPECIFICATION TO GENERATE SUPPORT FACILITIES
330: \end{nrtc}
331:
332: \item AT RUN-TIME:
333: \begin{nrtc}
334: \item USE DIRECTORY SERVICES TO LOCATE/REGISTER NETWORK SERVICES
335:
336: \item USE ASSOCIATION CONTROL TO BIND/UNBIND APPLICATIONS
337:
338: \item USE REMOTE OPERATIONS TO INVOKE TRANSACTIONS
339: \end{nrtc}
340: \end{nrtc}
341: \end{bwslide}
342:
343:
344: \begin{bwslide}
345: \ctitle {STATIC (COMPILE-TIME) ORGANIZATION}
346:
347: \vskip.15in
348: \diagram[p]{figure10}
349: \end{bwslide}
350:
351:
352: \begin{bwslide}
353: \ctitle {DYNAMIC (RUN-TIME) ORGANIZATION}
354:
355: \vskip.15in
356: \diagram[p]{figure11}
357: \end{bwslide}
358:
359:
360: \begin{bwslide}
361: \ctitle {CURRENT STATUS}
362:
363: \begin{nrtc}
364: \item STATIC FACILITIES
365: \begin{nrtc}
366: \item ALL TOOLS/LIBRARIES ARE DEVELOPED AND IN VARYING STAGES OF
367: BETA TESTING
368: \end{nrtc}
369:
370: \item DYNAMIC FACILITIES
371: \begin{nrtc}
372: \item MOST LIBRARIES ARE ALREADY WELL-TESTED
373:
374: \item ``REAL'' (DYNAMIC) DIRECTORY SERVICES IS TOO IMMATURE
375: FOR SERIOUS IMPLEMENTATION
376: \end{nrtc}
377:
378: \item AN ``APPLICATIONS COOKBOOK'' IS PLANNED BUT NOT YET WRITTEN
379: \end{nrtc}
380: \end{bwslide}
381:
382:
383: \end{document}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.