![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to a-apps.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-apps.tex CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / practical-osi1 |
1.1 root 1: \begin{bwslide}
2: \part {APPLICATIONS}
3: \end{bwslide}
4:
5:
6: \begin{bwslide}
7: \ctitle {APPLICATIONS}
8:
9: \begin{nrtc}
10: \item AS AN EXAMPLE OF HOW ALL THE PARTS FIT TOGETHER,
11: WE WILL TAKE A QUICK LOOK AT:
12: \begin{nrtc}
13: \item FILE TRANSFER, ACCESS AND MANAGEMENT (FTAM)
14: \item MESSAGE HANDLING SYSTEMS (X.400)
15: \item DIRECTORY SERVICES (X.500)
16: \item NETWORK MANAGEMENT (CMISE)
17: \item VIRTUAL TERMINAL (VT)
18: \end{nrtc}
19: \item AND THEN LOOK AT HOW APPLICATIONS ARE BUILT
20: \end{nrtc}
21: \end{bwslide}
22:
23:
24: % \begin{bwslide}
25: %\ctitle {APPLICATIONS (cont.)}
26: %
27: %\begin{nrtc}
28: %\item FINALLY, WE WILL CONSIDER APPLICATION LAYER REQUIREMENTS FOR DEFINING
29: % A NEW SERVICE
30: %\end{nrtc}
31: %\end{bwslide}
32:
33:
34: \begin{bwslide}
35: \ctitle {FILE TRANSFER, ACCESS AND MANAGEMENT (FTAM)}
36:
37: \vskip.5in
38: \diagram[p]{figureA-19}
39: \end{bwslide}
40:
41:
42: \begin{bwslide}
43: \ctitle {THE OSI FILE SERVICE --- FTAM}
44:
45: \begin{nrtc}
46: \item NOT ``JUST'' FILE TRANSFER
47: \item BUILDING BLOCK FOR OSI:
48: \begin{nrtc}
49: \item FILESTORE TO FILESTORE TRANSFER
50: \item WORKSTATION FILE RETRIEVAL
51: \item DISKLESS WORKSTATION PROTOCOL
52: \item SPECIAL APPLICATIONS (e.g., PRINTING, SPOOLING)
53: \item REMOTE FILE ACCESS
54: \end{nrtc}
55: \end{nrtc}
56: \end{bwslide}
57:
58:
59: \begin{bwslide}
60: \ctitle {FTAM PHILOSOPHY}
61:
62: \begin{nrtc}
63: \item AS WITH ALL ``OPEN SYSTEM'' SERVICES
64: \begin{nrtc}
65: \item DESCRIBES A CONCEPTUAL MODEL OF THE VIRTUAL SERVICE
66: \item SPECIFIES THE SERVICE AND THE PROTOCOL
67: \item INDEPENDENT OF ACTUAL LOCAL SYSTEMS
68: \begin{nrtc}
69: \item PROGRAMMING LANGUAGE BINDINGS ARE NOT SPECIFIED
70: \end{nrtc}
71: \end{nrtc}
72: \item THE FUNDAMENTAL ABSTRACTION:
73: \begin{nrtc}
74: \item THE VIRTUAL FILESTORE
75: \end{nrtc}
76: \item PROVIDES A CONCEPTUAL MODEL OF A FILE SERVICE ON A LOCAL SYSTEM (LOCALSTORE)
77: \item DIFFICULT TASK --- EXISTING FILE SERVICE ARE QUITE DIFFERENT
78: \item POTENTIALLY VERY REWARDING!
79: \end{nrtc}
80: \end{bwslide}
81:
82:
83: % \begin{bwslide}
84: %\ctitle {RELATIONSHIP OF THE VIRTUAL FILESTORE AND LOCALSTORE}
85: %
86: %diagram
87: %\end{bwslide}
88:
89:
90: \begin{bwslide}
91: \ctitle {FTAM --- ELEMENTS}
92:
93: \begin{nrtc}
94: \item A (VIRTUAL) FILESTORE IS A COLLECTION OF FILES
95: \item A FILENAME IDENTIFIES EXACTLY ONE FILE IN THE FILESTORE
96: \item THERE IS NO EXPLICIT RELATIONSHIP BETWEEN DIFFERENT FILES IN THE FILESTORE
97: \begin{nrtc}
98: \item i.e., NO DIRECTORY STRUCTURE
99: \end{nrtc}
100: \item FILES HAVE
101: \begin{nrtc}
102: \item ATTRIBUTES (e.g., OWNERSHIP INFORMATION)
103: \item CONTENTS (e.g., RANDOM--ACCESS RECORDS)
104: \end{nrtc}
105: \end{nrtc}
106: \end{bwslide}
107:
108:
109: % \begin{bwslide}
110: %\ctitle {FTAM ELEMENTS --- ATTRIBUTES}
111: %
112: %\begin{nrtc}
113: %\item TWO KINDS OF ATTRIBUTES ARE DEFINED
114: %\item FILE ATTRIBUTES, WHICH EXIST ON A PER-FILE BASIS
115: % \begin{nrtc}
116: % \item SIMULTANEOUS CLIENTS OF THE FILESTORE SEE THE SAME INFORMATION
117: % \item e.g., THE NAME OF THE FILE
118: % \end{nrtc}
119: %\item ACTIVITY ATTRIBUTES, WHICH EXIST ON A PER-CLIENT BASIS
120: % \begin{nrtc}
121: % \item INTERACTIONS BY A CLIENT ARE NOT DIRECTLY VISIBLE TO OTHER CLIENTS
122: % \item e.g., HOW THE FILE IS BEING TRAVERSED
123: % \end{nrtc}
124: %\item THE CLIENT INTERACTS ON AT MOST ONE FILE
125: % \begin{nrtc}
126: % \item THE ``SELECTED'' FILE
127: % \end{nrtc}
128: %\end{nrtc}
129: %\end{bwslide}
130:
131:
132: % \begin{bwslide}
133: %\ctitle {FTAM ELEMENTS --- CONTENTS}
134: %
135: %\begin{nrtc}
136: %\item TYPICALLY, FILES ARE DEFINED IN TERMS OF A ``DOCUMENT TYPE''
137: %\item STATIC CHARACTERISTICS
138: % \begin{nrtc}
139: % \item THE COMPOSITION OF THE FILE IN TERMS OF FILE ACCESS DATA UNITS (FADUs)
140: % \begin{nrtc}
141: % \item e.g., A SEQUENTIAL COLLECTION OF RECORDS
142: % \end{nrtc}
143: % \item THE STRUCTURE OF EACH DATA UNIT (DUs)
144: % \begin{nrtc}
145: % \item e.g., EACH RECORD CONTAINS A PERSONNEL RECORD
146: % \end{nrtc}
147: % \end{nrtc}
148: %\item DYNAMIC CHARACTERISTICS
149: % \begin{nrtc}
150: % \item HOW DATA UNITS ARE ENCODED ON THE NETWORK
151: % \item HOW DATA UNITS ARE REFERENCED (e.g., CURRENT POSITION)
152: % \end{nrtc}
153: %\end{nrtc}
154: %\end{bwslide}
155:
156:
157: % \begin{bwslide}
158: %\ctitle {FTAM --- FILE ATTRIBUTES}
159: %
160: %\begin{nrtc}
161: %\item 4 GROUPS OF FILE ATTRIBUTES
162: %\item KERNEL GROUP (REQUIRED)
163: % \begin{nrtc}
164: % \item NECESSARY FOR FILE SELECTION AND BASIC FILE TRANSFER
165: % \end{nrtc}
166: %\item STORAGE GROUP (OPTIONAL)
167: % \begin{nrtc}
168: % \item DESCRIBES THE STORAGE CHARACTERISTICS FOR THE FILE
169: % \end{nrtc}
170: %\item SECURITY GROUP (OPTIONAL)
171: % \begin{nrtc}
172: % \item DESCRIBES THE ACCESS CONTROL MECHANISMS FOR THE FILE
173: % \end{nrtc}
174: %\item PRIVATE GROUP (OPTIONAL)
175: % \begin{nrtc}
176: % \item A MECHANISM TO CAPTURE NON-STANDARD (PROPRIETARY) MECHANISMS
177: % THAT CAN'T BE OTHERWISE REPRESENTED
178: % \end{nrtc}
179: %\end{nrtc}
180: %\end{bwslide}
181:
182:
183: % \begin{bwslide}
184: %\ctitle {FTAM --- KERNEL GROUP}
185: %
186: %\begin{nrtc}
187: %\item FILENAME: A SEQUENCE OF STRINGS
188: % \begin{nrtc}
189: % \item MAPPING TO THE LOCALSTORE NAMING CONVENTIONS IS A
190: % ``LOCAL IMPLEMENTATION CHOICE''
191: % \end{nrtc}
192: %\item CONTENTS TYPE: STRUCTURING INFORMATION
193: %\item PERMITTED ACTIONS
194: % \begin{nrtc}
195: % \item DESCRIBES THE TYPES OF DATA ACCESS THAT CAN BE PERFORMED ON THE FILE
196: % \item HOW DATA UNITS MAY BE ACCESSED (READ, WRITE, EXTEND, etc.)
197: % \item HOW THE FILE MAY BE TRAVERSED (MOVING FROM ONE DATA UNIT TO ANOTHER)
198: % \end{nrtc}
199: %\end{nrtc}
200: %\end{bwslide}
201:
202:
203: % \begin{bwslide}
204: %\ctitle {FTAM --- STORAGE GROUP}
205: %
206: %\begin{nrtc}
207: %\item STORAGE ACCOUNT: A STRING
208: % \begin{nrtc}
209: % \item ENTITY ACCRUING FILE STORAGE CHARGES
210: % \end{nrtc}
211: %\item IDENTITY OF USER AND THE DATE/TIME OF
212: % \begin{nrtc}
213: % \item FILE CREATION
214: % \item LAST READ \& LAST MODIFICATION OF FILE CONTENTS
215: % \item LAST MODIFICATION OF FILE ATTRIBUTES
216: % \end{nrtc}
217: %\item FILE AVAILABILITY
218: % \begin{nrtc}
219: % \item IMMEDIATE (FILE IS ``ON-LINE'')
220: % \item DEFERRED (ACCESS TO FILE MAY ENCOUNTER DELAY, e.g., AWAITING
221: % ARCHIVE RETRIEVAL
222: % \end{nrtc}
223: %\end{nrtc}
224: %\end{bwslide}
225:
226:
227: % \begin{bwslide}
228: %\ctitle {FTAM --- STORAGE GROUP (cont.)}
229: %
230: %\begin{nrtc}
231: %\item FILESIZE (IN OCTETS)
232: % \begin{nrtc}
233: % \item AN ESTIMATE OF THE TOTAL SIZE OF THE FILE'S CONTENTS
234: % \end{nrtc}
235: %\item FUTURE FILESIZE (IN OCTETS)
236: % \begin{nrtc}
237: % \item A SOFT LIMIT ON THE TOTAL SIZE OF THE FILE'S CONTENTS
238: % \end{nrtc}
239: %\end{nrtc}
240: %\end{bwslide}
241:
242:
243: % \begin{bwslide}
244: %\ctitle {FTAM --- SECURITY GROUP}
245: %
246: %\begin{nrtc}
247: %\item ACCESS CONTROL (AN ACCESS CONTROL LIST) FOR EACH ELEMENT OF THE LIST:
248: % \begin{nrtc}
249: % \item FILE ACTION PERMITTED
250: % \item CONCURRENCY CONSTRAINTS
251: % \item ENTITY PERMITTED TO REQUEST ACTION (OPTIONAL)
252: % \item PASSWORDS REQUIRED TO VALIDATE EACH ACTION
253: % \end{nrtc}
254: %\item LEGAL QUALIFICATIONS
255: % \begin{nrtc}
256: % \item DEFINED THE ``LEGAL STATUS'' OF THE FILE
257: % \item MEANT TO BE USED WITH A NATIONAL PRIVACY LEGISLATION
258: % \end{nrtc}
259: %\end{nrtc}
260: %\end{bwslide}
261:
262:
263: % \begin{bwslide}
264: %\ctitle {FTAM --- PRIVATE GROUP}
265: %
266: %\begin{nrtc}
267: %\item A ``CATCH--ALL''
268: %\item USE IS STRONGLY DISCOURAGED
269: %\end{nrtc}
270: %\end{bwslide}
271:
272:
273: % \begin{bwslide}
274: %\ctitle {FTAM --- ACTIVITY ATTRIBUTES}
275: %
276: %\begin{nrtc}
277: %\item ACTIVITY ATTRIBUTES ARE ALSO DEFINED IN TERMS OF GROUPS
278: % \begin{nrtc}
279: % \item KERNEL, STORAGE, AND SECURITY (NO PRIVATE GROUP, OBVIOUSLY)
280: % \end{nrtc}
281: %\item THESE ARE USUALLY INITIALIZED WHEN A FILE IS EITHER
282: % \begin{nrtc}
283: % \item SELECTED
284: % \item OPENED FOR TRANSFER/ACCESS
285: % \end{nrtc}
286: %\end{nrtc}
287: %\end{bwslide}
288:
289:
290: % \begin{bwslide}
291: %\ctitle {FTAM --- DOCUMENT TYPES}
292: %
293: %\begin{nrtc}
294: %\item STATIC CHARACTERISTICS
295: % \begin{nrtc}
296: % \item THE FILE ACCESS STRUCTURE (CONSTRAINT SET NAME)
297: % \item THE PRESENTATION STRUCTURE (ABSTRACT SYNTAX NAME)
298: % \end{nrtc}
299: %\item DYNAMIC CHARACTERISTICS
300: % \begin{nrtc}
301: % \item THE TRANSFER STRUCTURE (TRANSFER SYNTAX NAME)
302: % \item A IDENTIFICATION STRUCTURE (ACCESS CONTEXTS)
303: % \end{nrtc}
304: %\item ``REGISTERED'' AND REFERENCED VIA A UNIQUE IDENTIFIER
305: %\end{nrtc}
306: %\end{bwslide}
307:
308:
309: % \begin{bwslide}
310: %\ctitle {FTAM --- SUMMARY}
311: %
312: %\begin{nrtc}
313: %\item THE VIRTUAL FILESTORE IS THE OSI ABSTRACTION OF A LOCALSTORE
314: %\item FILES CONTAIN ATTRIBUTES AND STRUCTURING INFORMATION IN ADDITION
315: % TO ``TYPED'' DATA
316: %\item FILES ARE DISTINGUISHED BY NAME
317: %\item SOME ATTRIBUTES ARE DYNAMIC, ON A PER-CLIENT BASIS
318: %\item STRUCTURE IS BASED ON A HIERARCHAL MODEL
319: %\item DATA A STRUCTURE ARE SEPARATE AND DISTINCT
320: %\item DOCUMENT TYPES PROVIDE AN ABBREVIATED METHOD FOR REFERRING TO THE
321: % FILE STRUCTURE
322: %\end{nrtc}
323: %\end{bwslide}
324:
325:
326: % \begin{bwslide}
327: %\ctitle {FILE TRANSFER, ACCESS AND MANAGEMENT \\ REFERENCES}
328: %
329: %\begin{description}
330: %\item[ISO/IEC 8571:] File Transfer, Access and Management (Parts 1---4)
331: % \begin{description}
332: % \item[Part 1:] General Information
333: % \item[Part 2:] Virtual Filestore Definition
334: % \item[Part 3:] The Filestore Definition
335: % \item[Part 4:] File Protocol Specification
336: % \end{description}
337: %\end{description}
338: %\end{bwslide}
339:
340:
341: \begin{bwslide}
342: \ctitle {MESSAGE HANDLING SYSTEMS (MHS)\\ X.400}
343:
344: \vskip.5in
345: \diagram[p]{figureA-20}
346: \end{bwslide}
347:
348:
349: \begin{bwslide}
350: \ctitle {MESSAGE HANDLING SYSTEMS}
351:
352: \begin{nrtc}
353: \item ELECTRONIC MESSAGING SERVICE
354: \item PURPOSE
355: \begin{nrtc}
356: \item A GENERAL PURPOSE STORE--AND--FORWARD ENVIRONMENT
357: \item AN ENVIRONMENT WHICH SUPPORTS HUMAN TO HUMAN ELECTRONIC MESSAGING
358: \item A SERVICE WHICH CAN BE USED BY OTHER APPLICATIONS
359: \item TRANSPORT STRUCTURE MESSAGES
360: \end{nrtc}
361: \end{nrtc}
362: \end{bwslide}
363:
364:
365: \begin{bwslide}
366: \ctitle {MHS}
367:
368: \begin{nrtc}
369: \item ALMOST CERTAINLY TO BE THE MOST ``POPULAR'' OSI APPLICATION
370: \item TECHNICALLY A VERY COMPREHENSIVE \& LARGE STANDARD
371: \item DEVELOPMENT OF MHS RESULTED IN MUCH OF THE OSI UPPER LAYER DEVELOPMENT
372: \item THE MOST COMPLEX OSI APPLICATION DUE TO ITS SIZE
373: \end{nrtc}
374: \end{bwslide}
375:
376:
377: % \begin{bwslide}
378: %\ctitle {MHS VERSIONS}
379: %
380: %\begin{nrtc}
381: %\item 1984 --- FIRST PASS, PROVIDES A VERY EXTENSIVE FACILITY
382: %\item 1988 --- SECOND PASS, REFLECTS A TREMENDOUS AMOUNT OF EXPERIENCE
383: % WITH THE 1984 WORK. A SIGNIFICANTLY MORE ``MATURE'' STANDARD
384: %\end{nrtc}
385: %\end{bwslide}
386:
387:
388: \begin{bwslide}
389: \ctitle {MHS PIECES}
390:
391: \vskip.5in
392: \diagram[p]{figureA-36}
393: \end{bwslide}
394:
395:
396: % \begin{bwslide}
397: %\ctitle {MESSAGE HANDLING SYSTEMS \\ REFERENCES}
398: %
399: %\begin{description}
400: %\item[ISO/IEC 10021:] Message Handling Systems (Parts 1---7)
401: % \begin{description}
402: % \item[Part 1:] System and Service Overview
403: % \item[Part 2:] Overall Architecture
404: % \item[Part 3:] Abstract Service Definition Conventions
405: % \item[Part 4:] Abstract Service Definition Procedures
406: % \item[Part 5:] Message Store Abstract Service Definition
407: % \item[Part 6:] Protocol SPecifications
408: % \item[Part 7:] Interpersonal Messaging System
409: % \end{description}
410: %\end{description}
411: %\end{bwslide}
412:
413:
414: \begin{bwslide}
415: \ctitle {DIRECTORY SERVICES (DS)\\ X.500}
416:
417: \vskip.5in
418: \diagram[p]{figureA-17}
419: \end{bwslide}
420:
421:
422: \begin{bwslide}
423: \ctitle {DIRECTORY SERVICES}
424:
425: \begin{nrtc}
426: \item PURPOSE
427: \begin{nrtc}
428: \item PROVIDE A MECHANISM TO DISTRIBUTE AND RETRIEVE INFORMATION
429: \item LET APPLICATIONS MAP FROM NAMES TO ADDRESSES {\em (RECALL
430: DISCUSSION OF THE DSE)}
431: \item ALLOW HUMAN USERS TO ``INTUIT'' NAMES OF OBJECTS AND THEN
432: RETRIEVE INFORMATION FROM THOSE OBJECTS
433: \begin{nrtc}
434: \item e.g., ELECTRONIC MAIL ADDRESSES FOR OTHER USERS
435: \end{nrtc}
436: \end{nrtc}
437: \end{nrtc}
438: \end{bwslide}
439:
440:
441: \begin{bwslide}
442: \ctitle {DIRECTORY SERVICES (cont.)}
443:
444: \begin{nrtc}
445: \item INFORMATION IS ARRANGED HIERARCHICALLY
446: \item TOP LEVEL IS IMAGINED TO BE PRIMARILY COUNTRIES
447: \item RULES ABOUT WHAT APPEARS BENEATH A GIVEN POINT
448: ARE LEFT TO INDIVIDUAL ADMINISTRATORS
449: \end{nrtc}
450: \end{bwslide}
451:
452:
453: \begin{bwslide}
454: \ctitle {THE DIRECTORY INFORMATION TREE}
455:
456: \vskip.5in
457: \diagram[p]{figureA-37}
458: \end{bwslide}
459:
460:
461: \begin{bwslide}
462: \ctitle {HOW THE DIRECTORY IS DISTRIBUTED}
463:
464: \begin{nrtc}
465: \item MANY SERVERS (DSAs) COOPERATE TO PROVIDE THE HIERARCHICAL DIRECTORY
466: \item USERS (DUAs) COMMUNICATE WITH SERVERS
467: \item SERVERS ALSO COMMUNICATE WITH OTHER SERVERS
468: \item OPERATIONS MAY BE PASSED FROM ONE SERVER TO ANOTHER FOR THE USER {\em (CHAINING)}
469: \item SERVERS MAY RETURN REFERRALS TO OTHER SERVERS TO THE USER
470: \end{nrtc}
471: \end{bwslide}
472:
473:
474: \begin{bwslide}
475: \ctitle {DIRECTORY OPERATION}
476:
477: \vskip.5in
478: \diagram[p]{figureA-38}
479: \end{bwslide}
480:
481:
482: \begin{bwslide}
483: \ctitle {SECURITY AND THE DIRECTORY}
484:
485: \begin{nrtc}
486: \item OSI APPLICATIONS MAY USE THE DIRECTORY TO PROVIDE AUTHENTICATION INFORMATION
487: \item USERS MAY STORE PUBLIC ENCRYPTION KEYS IN THE DIRECTORY
488: \item OTHER USERS MAY READ THOSE KEYS TO VALIDATE DIGITAL SIGNATURES AND THE LIKE
489: \end{nrtc}
490: \begin{nrtc}
491: \item SIMPLE AUTHENTICATION MAY JUST STORE PASSWORDS IN THE DIRECTORY
492: \item OTHER USERS MAY ONLY BE ALLOWED TO \underline{COMPARE} A VALUE TO
493: SEE IF IT MATCHES
494: \end{nrtc}
495: \end{bwslide}
496:
497:
498: % \begin{bwslide}
499: %\ctitle {DIRECTORY SERVICES \\ REFERENCES}
500: %
501: %\begin{description}
502: %\item[ISO/IEC 9594:] The Directory (Parts 1-8)
503: % \begin{description}
504: % \item[Part 1:] Overview of Concepts, Models and Services
505: % \item[Part 2:] Models
506: % \item[Part 3:] Abstract Service Definition
507: % \item[Part 4:] Procedures for Distributed Operation
508: % \item[Part 5:] Protocol Specifications
509: % \item[Part 6:] Selected Attribute Types
510: % \item[Part 7:] Selected Object Classes
511: % \item[Part 8:] Authentication Framework
512: % \end{description}
513: %\end{description}
514: %\end{bwslide}
515:
516:
517: \begin{bwslide}
518: \ctitle {NETWORK MANAGEMENT (CMISE)}
519:
520: \vskip.5in
521: \diagram[p]{figureA-21}
522: \end{bwslide}
523:
524:
525: \begin{bwslide}
526: \ctitle {\small COMMON MANAGEMENT INFORMATION SERVICE ELEMENT}
527:
528: \begin{nrtc}
529: \item PURPOSE
530: \begin{nrtc}
531: \item PROVIDE A COMMON PROTOCOL FOR MANAGING OSI AND NON-OSI NETWORKS
532: \item MANAGEMENT STANDARDS ALSO DEFINE MANAGED OBJECT IN THE
533: MANAGEMENT INFORMATION BASE (MIB)
534: \end{nrtc}
535: \end{nrtc}
536: \end{bwslide}
537:
538:
539: % \begin{bwslide}
540: %\ctitle {NETWORK MANAGEMENT \\ REFERENCES}
541: %
542: %\begin{description}
543: %\item[ISO/IEC 9595:] Management Information Service Definition
544: % \begin{description}
545: % \item[Part 1:] Overview
546: % \item[Part 2:] Common Management Information Service
547: % \end{description}
548: %\item[ISO/IEC 9596:] Management Information Protocol Specification
549: % \begin{description}
550: % \item[Part 1:] Overview
551: % \item[Part 2:] Common Management Information Protocol
552: % \end{description}
553: %\end{description}
554: %\end{bwslide}
555:
556:
557: \begin{bwslide}
558: \ctitle {VIRTUAL TERMINAL (VT)}
559:
560: \vskip.5in
561: \diagram[p]{figureA-22}
562: \end{bwslide}
563:
564:
565: \begin{bwslide}
566: \ctitle {VIRTUAL TERMINAL}
567:
568: \begin{nrtc}
569: \item PURPOSE
570: \begin{nrtc}
571: \item PROVIDE REMOTE TERMINAL CAPABILITY
572: \item ALLOW ACCESS TO REMOTE COMPUTER SYSTEMS ACROSS AN OSI NETWORK
573: \item ULTIMATELY ALLOW A MAPPING BETWEEN ANY APPLICATION AND ANY TERMINAL
574: \end{nrtc}
575: \end{nrtc}
576: \end{bwslide}
577:
578:
579: % \begin{bwslide}
580: %\ctitle {VIRTUAL TERMINAL \\ REFERENCES}
581: %
582: %\begin{description}
583: %\item[ISO/IEC 9040:] Virtual Terminal Service --- Basic Class
584: %\item[ISO/IEC 9041:] Virtual Terminal Protocol --- Basic Class
585: %\end{description}
586: %\end{bwslide}
587:
588:
589: % \begin{bwslide}
590: %\ctitle {INTRODUCTION}
591: %
592: %\begin{nrtc}
593: %\item LOOSELY COUPLED SYSTEMS THAT ARE BUILT USING REMOTE PROCEDURE CALLS
594: % (RPC) ARE GAINING POPULARITY, e.g., NFS
595: %
596: %\item THE OSI REMOTE OPERATIONS CONCEPT IS INTENDED TO PROVIDE THIS
597: % FUNCTIONALITY FOR:
598: % \begin{nrtc}
599: % \item MESSAGING
600: %
601: % \item DIRECTORY SERVICES
602: %
603: % \item NETWORK MANAGEMENT
604: %
605: % \item REMOTE DATABASE ACCESS
606: % \end{nrtc}
607: %\end{nrtc}
608: %\end{bwslide}
609: %
610: %
611: % \begin{bwslide}
612: %\ctitle {MOTIVATION}
613: %
614: %\begin{nrtc}
615: %\item MANY FEEL THAT THIS CAPABILITY MAY BE A KEY FACTOR IN THE OVERALL
616: % SUCCESS OF OSI STANDARDIZATION
617: %
618: %\item BUT, REMOTE OPERATIONS ARE SUFFICIENTLY GENERAL TO REQUIRE
619: % ADDITIONAL DISCIPLINE, BEYOND THE ISO/CCITT STANDARDS,
620: % FOR THEIR USE AS AN RPC MECHANISM
621: %\end{nrtc}
622: %\end{bwslide}
623: %
624: %
625: % \begin{bwslide}
626: %\ctitle {THE APPLICATIONS COOKBOOK}
627: %
628: %\begin{nrtc}
629: %\item THE SET OF RULES AND LOCAL IMPLEMENTATION DECISIONS PLACED ON REMOTE
630: % OPERATIONS TO MAKE THE PROBLEM MANAGEABLE:
631: % \begin{nrtc}
632: % \item LANGUAGE BINDINGS (``C'')
633: %
634: % \item TOOLS FOR AUTOMATICALLY GENERATING PARTS OF THE
635: % PROGRAMS WHICH USE REMOTE OPERATIONS
636: %
637: % \item A RUN-TIME ENVIRONMENT AND SOME BOILERPLATE
638: %
639: % \item CONVENTIONS FOR NAMING AND ADDRESSING SERVICES AND ENTITIES
640: % \end{nrtc}
641: %\end{nrtc}
642: %\end{bwslide}
643: %
644: %
645: % \begin{bwslide}
646: %\part* {\bf DEFINING A SERVICE}
647: %
648: %\begin{nrtc}
649: %\item TWO ASPECT TO SERVICE DEFINITION
650: %\item STATIC CHARACTERISTICS
651: % \begin{nrtc}
652: % \item DEFINED IN SERVICE DEFINITION
653: % \item GENERIC TO ANY ENTITY REALIZING THE SERVICE
654: % \end{nrtc}
655: %\item DYNAMIC CHARACTERISTICS
656: % \begin{nrtc}
657: % \item DEFINED BY SERVICE PROVIDER
658: % \item VARIES BETWEEN ENTITIES
659: % \end{nrtc}
660: %\end{nrtc}
661: %\end{bwslide}
662: %
663: %
664: % \begin{bwslide}
665: %\ctitle {STATIC CHARACTERISTICS: \\ ABSTRACT SYNTAX}
666: %
667: %\begin{nrtc}
668: %\item DEFINES THE DATA STRUCTURES BEING EXCHANGED BY THE SERVICE
669: %\item VALUE IS AN OBJECT IDENTIFIER, e.g.:
670: % \begin{quote}\small
671: % ftam pci 1.0.8571.2.1
672: % \end{quote}
673: %\item ALL SERVICES USE AT LEAST TWO
674: % \begin{nrtc}
675: % \item ``PRIMARY'' PROTOCOL
676: % \item ASSOCIATION CONTROL
677: % \end{nrtc}
678: %\item SOME USE MORE, e.g., FTAM USES AN ABSTRACT SYNTAX FOR EACH NEGOTIATED
679: % DOCUMENT TYPE
680: %\end{nrtc}
681: %\end{bwslide}
682: %
683: %
684: % \begin{bwslide}
685: %\ctitle {STATIC CHARACTERISTICS: \\ APPLICATION CONTEXT NAME}
686: %
687: %\begin{nrtc}
688: %\item DEFINES THE APPLICATION SERVICE ELEMENTS (ASEs) USED BY THE SERVICE AND
689: % HOW THEY INTERACT
690: %\item VALUE IS AN OBJECT IDENTIFIER, e.g.:
691: % \begin{quote}\small
692: % iso ftam 1.0.8571.1.1
693: % \end{quote}
694: % INDICATES USE OF THE FTAM ASE AND THE ACSE
695: %\item SOME RELATIONSHIPS ARE MORE COMPLICATED, e.g., USE PROTOCOL ``p17''
696: % ON TOP OF ROSE ON TOP OF RTSE ON TOP OF ACSE
697: %\end{nrtc}
698: %\end{bwslide}
699: %
700: %
701: % \begin{bwslide}
702: %\ctitle {DYNAMIC CHARACTERISTICS: \\ APPLICATION ENTITY TITLE}
703: %
704: %\begin{nrtc}
705: %\item UNIQUELY NAMES AN ENTITY IN THE NETWORK
706: %\item VALUE IS A DISTINGUISHED NAME, e.g.,
707: % \begin{quote}\small\begin{verbatim}
708: % c=US@o=TWG@ou=Software Engineering@cn=boomer@cn=filestore
709: % \end{verbatim}\end{quote}
710: % (THIS IS A STRING REPRESENTATION OF A COMPLEX ASN.1 TYPE!)
711: %\item SIMPLER APPROACH IS TO USE LOCAL ALIASING (``boomer-filestore'') PRIOR TO
712: % RESOLUTION:
713: % \begin{nrtc}
714: % \item LHS (QUALIFIER) MAPS TO INITIAL PART OF DISTINGUISHED NAME
715: % \item RHS (DESIGNATOR) MAPS TO SUFFIX
716: % \end{nrtc}
717: %\end{nrtc}
718: %\end{bwslide}
719: %
720: %
721: % \begin{bwslide}
722: %\ctitle {APPLICATION ENTITY TITLE}
723: %
724: %\begin{nrtc}
725: %\item FOR INITIATORS, THE DIRECTORY IS ASKED TO RETURN THE ``PRESENTATION ADDRESS''
726: % ATTRIBUTE OF THIS OBJECT
727: %\item CONCEPTUALLY, RESPONDERS STORE THIS INFORMATION IN THE DIRECTORY
728: %\end{nrtc}
729: %\end{bwslide}
730: %
731: %
732: % \begin{bwslide}
733: %\ctitle {DYNAMIC CHARACTERISTICS: \\ PRESENTATION ADDRESS}
734: %
735: %\begin{nrtc}
736: %\item UNIQUELY IDENTIFIES THE LOCATION OF AN ENTITY
737: %\item VALUE IS
738: % \begin{nrtc}
739: % \item PRESENTATION SELECTOR (0+ OCTETS)
740: % \item SESSION SELECTOR (0+ OCTETS)
741: % \item TRANSPORT SELECTOR (0+ OCTETS)
742: % \item NETWORK ADDRESSES (AT LEAST 1)
743: % \end{nrtc}
744: %\end{nrtc}
745: %\end{bwslide}
746: %
747: %
748: % \begin{bwslide}
749: %\ctitle {LOCAL ENVIRONMENT: \\ CURRENT METHOD}
750: %
751: %\begin{nrtc}
752: %\item TRANSPORT LISTENER RESIDES ON EACH END-SYSTEM
753: %\item FOR EACH SERVICE LISTED IN LOCAL DATABASE
754: % \begin{nrtc}
755: % \item LISTEN ON ASSOCIATED TRANSPORT ADDRESS
756: % \item UPON RECEIVING AN INCOMING CONNECTION, TSAPD
757: % INVOKES ASSOCIATED PROGRAM
758: % \end{nrtc}
759: %\item PROGRAM IS CALLED A DYNAMIC RESPONDER
760: %\end{nrtc}
761: %\end{bwslide}
762: %
763: %
764: % \begin{bwslide}
765: %\ctitle {LOCAL ENVIRONMENT: \\ CURRENT METHOD (cont.)}
766: %
767: %\begin{nrtc}
768: %\item SOME RESPONDERS MAY WISH TO SERVICE MULTIPLE INITIATORS
769: %\item DIFFERENT APPROACH:
770: % \begin{nrtc}
771: % \item SERVICE NOT LISTED IN LOCAL DATABASE
772: % \item PROGRAM LISTENS ON OWN TRANSPORT ADDRESS
773: % \end{nrtc}
774: %\item PROGRAM IS CALLED A STATIC RESPONDER
775: %\end{nrtc}
776: %\end{bwslide}
777: %
778: %
779: % \begin{bwslide}
780: %\ctitle {LOCAL ENVIRONMENT: \\ FUTURE METHOD}
781: %
782: %\begin{nrtc}
783: %\item LOCAL DATABASE CONTAINS
784: % \begin{nrtc}
785: % \item SERVICE NAME
786: % \item LOCAL PROGRAM
787: % \end{nrtc}
788: % BUT NOT TRANSPORT ADDRESS
789: %\item FOR EACH SERVICE
790: % \begin{nrtc}
791: % \item TRANSPORT LISTENER LISTENS ON RANDOM TRANSPORT ADDRESS
792: % \item LISTENER REGISTERS SERVICE \& TRANSPORT ADDRESS WITH THE DIRECTORY
793: % \end{nrtc}
794: %\item SIMILAR APPROACH IS USED BY STATIC RESPONDERS
795: %\end{nrtc}
796: %\end{bwslide}
797: %
798: %
799: % \begin{bwslide}
800: %\ctitle {UPPER--LAYER ADDRESSING}
801: %
802: %\begin{nrtc}
803: %\item TOO MUCH FREEDOM
804: %\item DYNAMIC RESPONDER PREFER TO ``DISPATCH'' ON TRANSPORT SELECTOR
805: %\item STATIC RESPONDERS MAY REQUIRE A UNIQUE NETWORK ADDRESS
806: %\end{nrtc}
807: %\end{bwslide}
808: %
809: %
810: %\begin{bwslide}
811: %\ctitle {UPPER--LAYER ADDRESSING}
812: %
813: %\begin{nrtc}
814: %\item U.S. GOSIP CALLS FOR DISPATCHING ON PRESENTATION SELECTOR
815: %\item OKAY FOR DYNAMIC RESPONDERS
816: %\item STATIC RESPONDERS MAY STILL REQUIRE A UNIQUE NETWORK ADDRESS
817: % \begin{nrtc}
818: % \item WITH REAL OSI NETWORK SERVICE, STATIC RESPONDERS CAN DISPATCH
819: % ON TRANSPORT SELECTOR
820: % \end{nrtc}
821: %\end{nrtc}
822: %\end{bwslide}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.