![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to a-overview.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 / practical-osi1|
Return to a-overview.tex CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / practical-osi1 |
1.1 root 1: % run this through LaTeX with the appropriate wrapper
2:
3: \dotopic{1}
4: \begin{bwslide}
5: \part {APPLICATION SERVICES}\bf
6: \end{bwslide}
7: \doparts
8:
9:
10: \begin{bwslide}
11: \part* {OUTLINE}\bf
12:
13: \begin{description}
14: \item[PART I:] BASIC CONCEPTS
15: \item[PART II:] SESSION SERVICES
16: \item[PART III:] ABSTRACT SYNTAX
17: \item[PART IV:] PRESENTATION SERVICES
18: \item[PART V:] APPLICATION SERVICE ELEMENTS
19: \item[PART VI:] BUILDING AN APPLICATION
20: \end{description}
21: \end{bwslide}
22:
23: % \begin{note}\em
24: %\begin{center}
25: %\underline{an audience survey}
26: %\end{center}
27: %
28: %who has heard of, is familiar with, or understands:
29: %\begin{quote}
30: %the osi model?
31: %
32: %abstract syntax notation one?
33: %
34: %remote operations in the context of OSI?
35: %
36: %sun rpc, or apollo ncs/nidl?
37: %\end{quote}
38: %
39: %who knows how to program under unix using:
40: %\begin{quote}
41: %the C programming language, make, shell, etc.?
42: %\end{quote}
43: %\end{note}
44:
45:
46: % \begin{note}\em
47: %everyone should be comfortable the material review
48: %\end{note}
49:
50:
51:
52: % \begin{bwslide}
53: %\part {\bf BASIC CONCEPTS}
54: %
55: %\begin{nrtc}
56: %\item OPEN SYSTEMS INTERCONNECTION
57: %
58: %\item OSI ITSELF IS QUITE SIMPLE
59: %
60: % \begin{nrtc}
61: % \item A METHODOLOGY FOR DESCRIBING OPEN SYSTEMS
62: % WHICH IS USED IN SPECIFICATIONS WHICH DESCRIBE HOW THESE
63: % SYSTEMS COMMUNICATE
64: % \end{nrtc}
65: %
66: %\end{nrtc}
67: %\end{bwslide}
68:
69: % \begin{bwslide}
70: %\ctitle {BASIC CONCEPTS}
71: %
72: %\begin{nrtc}
73: %\item CONCERNED WITH OPEN INTERCONNECTION OF SYSTEMS
74: %\item DOES NOT IMPLY OPENLY ACCESSIBLE SYSTEMS
75: %\end{nrtc}
76: %\end{bwslide}
77:
78:
79: % \begin{bwslide}
80: %\ctitle {BASIC CONCEPTS (cont.)}
81: %
82: %\begin{nrtc}
83: %\item AT FIRST GLANCE, OSI IS DESCRIBED IN A LANGUAGE ALL ITS OWN
84: %\item OSI STANDARDS USUALLY HAVE TWO PARTS:
85: % \begin{nrtc}
86: % \item A SERVICE DEFINITION
87: % \item A PROTOCOL SPECIFICATION
88: % \end{nrtc}
89: %\end{nrtc}
90: %\end{bwslide}
91:
92:
93: % \begin{bwslide}
94: %\ctitle {WHAT WE WILL DISCUSS}
95: %
96: %\begin{nrtc}
97: %\item A PRACTICAL LOOK
98: % \begin{nrtc}
99: % \item PIECES OF THE OSI MODEL
100: % \item ACTUAL SERVICES
101: % \item REAL WORLD USAGE
102: % \end{nrtc}
103: %\end{nrtc}
104: %\end{bwslide}
105:
106: % \begin{bwslide}
107: %\ctitle {OSI SAYS WHAT TO DO, NOT HOW TO DO IT}
108: %
109: %\begin{nrtc}
110: %\item IT SPECIFIES THE EXTERNAL BEHAVIOR OCCURRING BETWEEN SYSTEMS
111: %\item IT DOES NOT SPECIFY HOW LOCAL SYSTEMS ARE BUILT
112: %\item DOES SPECIFY
113: % \begin{nrtc}
114: % \item WHAT GOES ON THE ``WIRE'' AND WHEN
115: % \end{nrtc}
116: %
117: %\item IT DOES NOT SPECIFY
118: % \begin{nrtc}
119: % \item PROGRAMMING LANGUAGE BINDINGS
120: % \item OPERATING SYSTEMS BINDINGS
121: % \item APPLICATION INTERFACE ISSUES
122: % \item USER-INTERFACE ISSUES
123: % \end{nrtc}
124: %\end{nrtc}
125: %\end{bwslide}
126:
127:
128: % \begin{bwslide}
129: %\ctitle {WHO ARE THE PLAYERS}
130: %
131: %\begin{nrtc}
132: %\item THE INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO)
133: % \begin{nrtc}
134: % \item NATIONAL STANDARDS BODIES
135: % \end{nrtc}
136: %\item THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE (CCITT)
137: % \begin{nrtc}
138: % \item NATIONAL TELECOM ADMINISTRATIONS
139: % \end{nrtc}
140: %\end{nrtc}
141: %\end{bwslide}
142:
143:
144: % \begin{bwslide}
145: %\ctitle {WHO ARE THE PLAYERS (cont.)}
146: %
147: %\begin{nrtc}
148: %\item THE NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST)
149: % \begin{nrtc}
150: % \item CORRESPONDS TO OTHER REGIONAL BODIES, EWOS, AOWS, etc.
151: % \end{nrtc}
152: %\item THE CORPORATION FOR OPEN SYSTEMS (COS)
153: %\item THE TECHNICAL OFFICE PROTOCOLS USER'S GROUP \&
154: % THE MANUFACTURING AUTOMATION PROTOCOLS USER'S GROUP
155: % \begin{nrtc}
156: % \item (MAP/TOP)
157: % \end{nrtc}
158: %\item THE INTERNATIONAL FEDERATION OF INFORMATION PROCESSING (IFIP)
159: %\end{nrtc}
160: %\end{bwslide}
161:
162:
163: % \begin{bwslide}
164: %\ctitle {ISO}
165: %
166: %\begin{nrtc}
167: %\item ISO DOES NOT STAND FOR INTERNATIONAL STANDARDS ORGANIZATION
168: %\item DON'T CONFUSE OSI \& ISO:
169: % \begin{nrtc}
170: % \item ISO IS AN ORGANIZATION
171: % \item OSI IS A COMMUNICATIONS MODEL
172: % \end{nrtc}
173: %%\item ONLY ISO PRODUCES ``STANDARDS'', OTHERS PRODUCE OTHER THINGS, e.g.,
174: %% \begin{nrtc}
175: %% \item RECOMMENDATIONS --- CCITT
176: %% \end{nrtc}
177: %\end{nrtc}
178: %\end{bwslide}
179:
180:
181: % \begin{bwslide}
182: %\ctitle {US STANDARDS PROCESS}
183: %
184: %\vskip.5in
185: %\diagram[p]{figureA-1}
186: %\end{bwslide}
187:
188:
189: % \begin{bwslide}
190: %\ctitle {WHAT ABOUT THE INTERNET COMMUNITY}
191: %
192: %\begin{nrtc}
193: %\item DARPA/NSF INTERNET RESEARCH COMMUNITY IS NOTICEABLY ABSENT
194: %\item DIFFERENCES IN THE COMMUNITIES
195: % \begin{nrtc}
196: % \item e.g., FOCUS ON EXPERIMENTATION vs. WRITTEN CONTRIBUTIONS
197: % \end{nrtc}
198: %\item THIS HAS BEEN A STRATEGIC ERROR!
199: %\end{nrtc}
200: %\end{bwslide}
201:
202:
203: % \begin{bwslide}
204: %\ctitle {STATUS}
205: %
206: %\begin{nrtc}
207: %%\item OSI STANDARDS AND VENDOR AGREEMENTS ARE REACHING STABLE STATUS
208: %%\item THE U.S. GOSIP WILL PROVIDE THE INITIAL DEMAND FOR OSI IN THE U.S.
209: %% AND OTHER COUNTRIES
210: %\item TECHNOLOGY STILL NEEDS REFINEMENT
211: % \begin{nrtc}
212: % \item MANY CURRENT OSI OFFERINGS ARE CLOSER TO EXPERIMENTS THAN
213: % TO PRODUCTS
214: % \item MANY PRODUCTS ARE SPECIFIC TO MAP/TOP
215: % \end{nrtc}
216: %\end{nrtc}
217: %\end{bwslide}
218:
219:
220: % \begin{bwslide}
221: %\ctitle {U.S. GOSIP}
222: %
223: %\begin{nrtc}
224: %\item A FEDERAL INFORMATION PROCESSING STANDARD (FIPS~146)
225: %\item PROPOSED TO ENABLE USERS TO SPECIFY AND PROCURE
226: % \begin{nrtc}
227: % \item INTEROPERABLE
228: % \item MULTI-VENDOR
229: % \item OFF-THE-SHELF
230: % \end{nrtc}
231: % COMPUTER COMMUNICATIONS PRODUCTS
232: %\end{nrtc}
233: %\end{bwslide}
234:
235:
236: % \begin{note}
237: %protocols
238: %\end{note}
239:
240:
241: % \begin{note}
242: %services
243: %\end{note}
244:
245:
246: % \begin{note}
247: %provider/consumer, initiator/responder, client/server
248: %\end{note}
249:
250:
251: \begin{bwslide}
252: \part {BASIC CONCEPTS\\THE OSI MODEL}\bf
253:
254: \begin{nrtc}
255: \item A LAYERED ARCHITECTURE FOR COMPUTER COMMUNICATIONS
256:
257: \item STANDARDIZED IN THE INTERNATIONAL COMMUNITY
258:
259: \item NON-PROPRIETARY IN NATURE
260: \end{nrtc}
261: \end{bwslide}
262:
263:
264: \begin{bwslide}
265: \ctitle {UPPER-LAYER INFRASTRUCTURE}
266:
267: \begin{nrtc}
268: \item UPPER-LAYERS ARE EVERYTHING ABOVE TRANSPORT
269: \item THE SAME UPPER-LAYERS ARE USED REGARDLESS OF THE APPLICATION,
270: UNLIKE OTHER ARCHITECTURES (e.g., TCP/IP)
271: \item EACH APPLICATION MAY SELECT DIFFERENT FUNCTIONALITY FROM THE UPPER LAYERS
272: \item THE EMPHASIS IS ON FLEXIBILITY, TO SUPPORT MANY DIVERSE OSI APPLICATIONS
273: \end{nrtc}
274: \end{bwslide}
275:
276:
277: \begin{bwslide}
278: \ctitle {OSI UPPER-LAYER INFRASTRUCTURE}
279:
280: \vskip.5in
281: \diagram[p]{figureA-2}
282: \end{bwslide}
283:
284:
285: % \begin{bwslide}
286: %\ctitle {CORRESPONDING INTERNET \\ UPPER-LAYER INFRASTRUCTURE}
287: %
288: %\vskip.5in
289: %\diagram[p]{figureA-3}
290: %\end{bwslide}
291:
292:
293: \begin{bwslide}
294: \ctitle {BOTTOM LINE}
295:
296: \begin{nrtc}
297: \item STRENGTHS
298: \begin{nrtc}
299: \item COMMON INFRASTRUCTURE
300: \item MORE TECHNICALLY COMPREHENSIVE
301: \end{nrtc}
302: \item WEAKNESSES
303: \begin{nrtc}
304: \item COMPLEXITY
305: \item POLITICAL POLARIZATION
306: \item LACK OF PRACTICAL EXPERIENCE
307: \end{nrtc}
308: \end{nrtc}
309: \end{bwslide}
310:
311:
312: \begin{bwslide}
313: \ctitle {THE MODEL FROM A COMMUNICATIONS VIEWPOINT}
314:
315: \vskip.5in
316: \diagram[p]{figureA-4}
317: \end{bwslide}
318:
319:
320: \begin{bwslide}
321: \ctitle {THE MODEL FROM A COMPUTER VIEWPOINT}
322:
323: \vskip.5in
324: \diagram[p]{figureA-5}
325: \end{bwslide}
326:
327:
328: \begin{bwslide}
329: \ctitle {LAYERING}
330:
331: \vskip.5in
332: \diagram[p]{figureA-32}
333: \end{bwslide}
334:
335:
336: % \begin{bwslide}
337: %\ctitle {TERMINOLOGY}
338: %
339: %\begin{nrtc}
340: %\item SDU (SERVICE DATA UNIT) --- USER DATA
341: %\item PCI (PROTOCOL CONTROL INFORMATION) --- HEADER
342: %\item PDU (PROTOCOL DATA UNIT) --- PACKET
343: % \begin{nrtc}
344: % \item PDU = PCI + SDU
345: % \end{nrtc}
346: %\item ICI (INTERFACE CONTROL INFORMATION)~---~PROCEDURE
347: %\item IDU (INTERFACE DATA UNIT)~---~CALL
348: % \begin{nrtc}
349: % \item IDU = ICI + PDU
350: % \end{nrtc}
351: %\item SAP (SERVICE ACCESS POINT)
352: %\end{nrtc}
353: %\end{bwslide}
354:
355:
356: % \begin{bwslide}
357: %\ctitle {DATA TRANSIT}
358: %
359: %\vskip.5in
360: %\diagram[p]{figureA-14}
361: %\end{bwslide}
362:
363:
364: \begin{bwslide}
365: \ctitle {SERVICES vs. PROTOCOLS}
366:
367: \vskip.5in
368: \diagram[p]{figureA-39}
369: \end{bwslide}
370:
371:
372: \begin{bwslide}
373: \ctitle {SERVICES AND\\ SERVICE PRIMITIVES}
374:
375: \begin{nrtc}
376: \item PEERS COMMUNICATE VIA \emph{SERVICE PRIMITIVES}
377:
378: \item A PRIMITIVE IS AN ABSTRACTION
379: \begin{nrtc}
380: \item NOT AN INTERFACE
381: \end{nrtc}
382:
383: \item SERVICE PRIMITIVES, LIKE PROCEDURE CALLS, HAVE TYPED PARAMETERS
384: \end{nrtc}
385: \end{bwslide}
386:
387:
388: % \begin{bwslide}
389: %\ctitle {SERVICE}
390: %
391: %\begin{nrtc}
392: %\item IN GENERAL, THERE ARE THREE KINDS OF SERVICES
393: % \begin{nrtc}
394: % \item \emph{CONFIRMED}
395: % \begin{nrtc}
396: % \item IN WHICH A REQUEST ALWAYS RESULTS IN A RESPONSE
397: % \end{nrtc}
398: %
399: % \item \emph{UNCONFIRMED}
400: % \begin{nrtc}
401: % \item IN WHICH NO RESPONSE IS RETURNED
402: % \end{nrtc}
403: %
404: % \item \emph{PROVIDER-INITIATED}
405: % \begin{nrtc}
406: % \item IN WHICH THE SERVICE PROVIDER INDICATES SOME SITUATION
407: % \end{nrtc}
408: % \end{nrtc}
409: %
410: %\item CONFIRMATION IS UNRELATED TO RELIABILITY
411: %\end{nrtc}
412: %\end{bwslide}
413:
414:
415: \begin{bwslide}
416: \ctitle {SERVICE PRIMITIVES}
417:
418: \begin{nrtc}
419: \item EACH LAYER (OR ELEMENT) OFFERS ONE OR MORE SERVICES (VERBS)
420: \begin{nrtc}
421: \item e.g., A-ASSOCIATE
422: \end{nrtc}
423:
424: \item A SERVICE CONSISTS OF ONE OR MORE PRIMITIVES
425:
426: \item A CONFIRMED SERVICE HAS FOUR PRIMITIVES
427: \begin{nrtc}
428: \item .REQUEST, .INDICATION, .RESPONSE, and .CONFIRMATION
429: \end{nrtc}
430:
431: \item AN UNCONFIRMED SERVICE HAS TWO PRIMITIVES:
432: \begin{nrtc}
433: \item .REQUEST, and .INDICATION
434: \end{nrtc}
435:
436: \item A PROVIDER-INITIATED SERVICE HAS ONE PRIMITIVE:
437: \begin{nrtc}
438: \item .INDICATION
439: \end{nrtc}
440: \end{nrtc}
441: \end{bwslide}
442:
443:
444: \begin{bwslide}
445: \ctitle {SERVICE PRIMATIVES}
446:
447: \vskip.5in
448: \diagram[p]{figureA-24}
449: \end{bwslide}
450:
451:
452: % \begin{bwslide}
453: %\ctitle {CONFIRMED SERVICE}
454: %
455: %\vskip.5in
456: %\diagram[p]{figureA-40}
457: %\end{bwslide}
458:
459:
460: % \begin{bwslide}
461: %\ctitle {CONFIRMED SERVICE}
462: %
463: %\vskip.5in
464: %\diagram[p]{figureA-41}
465: %\end{bwslide}
466:
467:
468: % \begin{bwslide}
469: %\ctitle {CONNECTION ORIENTED}
470: %
471: %\begin{nrtc}
472: %\item AVAILABLE UPPER-LAYERS ASSUME CONNECTION ORIENTED SERVICES
473: %\item CONNECTIONLESS ADDENDA BEING DEVELOPED
474: %\end{nrtc}
475: %\end{bwslide}
476:
477:
478: % \begin{bwslide}
479: %\ctitle {SESSION LAYER --- OVERVIEW}
480: %
481: %\begin{nrtc}
482: %\item ESTABLISH, RELEASE, MANAGE TRANSPORT CONNECTIONS
483: %\item NEGOTIATE AND POLICE COMMUNICATION PARAMETERS
484: %\end{nrtc}
485: %\end{bwslide}
486:
487:
488: % \begin{bwslide}
489: %\ctitle {ABSTRACT SYNTAX --- OVERVIEW}
490: %
491: %\begin{nrtc}
492: %\item DEFINES ENCODING \& DECODING RULES
493: %\item IN PRACTICE, FACILITIES USED BY
494: % \begin{nrtc}
495: % \item PRESENTATION
496: % \item APPLICATION
497: % \end{nrtc}
498: %\item MACHINE INDEPENDENT ENCODINGS
499: %\item FORMAL LANGUAGE
500: %\end{nrtc}
501: %\end{bwslide}
502:
503:
504: % \begin{bwslide}
505: %\ctitle {PRESENTATION LAYER --- OVERVIEW}
506: %
507: %\begin{nrtc}
508: %\item ESTABLISHES (NEGOTIATES) ``SYNTACTIC'' CONVENTIONS FOR PEER
509: % APPLICATION ENTITY COMMUNICATION
510: %\item ENCODES \& DECODES APPLICATION AND PRESENTATION
511: % LAYER STRUCTURES AND DATA UNITS
512: %\end{nrtc}
513: %\end{bwslide}
514:
515:
516: % \begin{bwslide}
517: %\ctitle {THE OSI APPLICATION LAYER}
518: %
519: %\begin{nrtc}
520: %\item MANY STANDARD ``APPLICATION'' SERVICE ELEMENTS
521: % \begin{nrtc}
522: % \item ASSOCIATION CONTROL
523: %
524: % \item REMOTE OPERATIONS
525: %
526: % \item RELIABLE TRANSFER
527: %
528: % \item DIRECTORY SERVICES
529: % \end{nrtc}
530: %
531: %\item ABSTRACT SYNTAX NOTATION ONE (ASN.1)\\
532: % (not really a layer, more of a concept)
533: %
534: %\end{nrtc}
535: %\end{bwslide}
536:
537:
538: % \begin{bwslide}
539: %\ctitle {APPLICATION SERVICE ELEMENTS --- OVERVIEW}
540: %
541: %\begin{nrtc}
542: %\item PROVIDES ``COMMON'' SERVICES IN APPLICATION LAYER
543: %\item APPLICATION BUILDING BLOCKS FOR STANDARD FUNCTIONALITY
544: % \begin{nrtc}
545: % \item ASSOCIATION CONTROL (ACSE)
546: % \item REMOTE OPERATIONS (ROSE)
547: % \item etc.
548: % \end{nrtc}
549: %\end{nrtc}
550: %\end{bwslide}
551:
552: % \begin{bwslide}
553: %\ctitle {APPLICATION SERVICE ELEMENTS}
554: %
555: %\begin{nrtc}
556: %\item A USEFUL MECHANISM FOR DIVIDING RESPONSIBILITY OF THE ``TOTAL''
557: % APPLICATION PROTOCOL
558: %
559: %\item PROMOTES ``REUSE'' OF APPLICATION LAYER FACILITIES
560: %\end{nrtc}
561: %\end{bwslide}
562:
563:
564: % \begin{bwslide}
565: %\ctitle {EXAMPLE:\\ FTAM USE OF LOWER-LAYER SERVICES}
566: %
567: %\vskip.5in
568: %\diagram[p]{figureA-42}
569: %\end{bwslide}
570:
571:
572:
573: % \begin{bwslide}
574: %\ctitle {APPLICATIONS --- OVERVIEW}
575: %
576: %\begin{nrtc}
577: %\item THE REAL WORKER ON TOP OF THE STACK
578: %\item DOES NOT INCLUDE USER INTERFACES
579: %\item EXAMPLES
580: % \begin{nrtc}
581: % \item MESSAGE HANDLING (X.400)
582: % \item DIRECTORY (X.500)
583: % \item FILE TRANSFER (FTAM)
584: % \item etc.
585: % \end{nrtc}
586: %\end{nrtc}
587: %\end{bwslide}
588:
589:
590: % \begin{bwslide}
591: %\ctitle {ABOVE THE APPLICATION LAYER}
592: %
593: %\begin{nrtc}
594: %\item OUTSIDE THE SCOPE OF THE OSI/RM \& STANDARDS
595: %\item ENTITIES (APPLICATION PROCESSES) MAKING USE OF OSI SERVICES
596: %\item EXAMPLES
597: % \begin{nrtc}
598: % \item USER INTERFACES
599: % \item DATABASE APPLICATION PROCESSES
600: % \end{nrtc}
601: %\end{nrtc}
602: %\end{bwslide}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.