![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to monterey.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 / monterey|
Return to monterey.tex CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / monterey |
1.1 root 1: % run this through SLiTeX
2:
3: \documentstyle
4: [blackandwhite,landscape,oval,pagenumbers,small,plain]{NRslides}
5:
6: \input trademark
7: \def\tradeORGfont{\rm}
8: \def\tradeNAMfont{\rm}
9:
10: \raggedright
11:
12: \begin{document}
13:
14: \title {PROTOCOL ADVANCES 3:\\ ISO DEVELOPMENT ENVIRONMENT}
15: \author {Stephen E.~Kille\\ University College, London\\[0.15in]
16: Ronald G.~Minnich\\ University of Delaware\\[0.15in]
17: Marshall T.~Rose\\ Northrop Corporation}
18: \date {March 17, 1987}
19: \maketitlepage
20:
21:
22: \begin{bwslide}
23: \part* {AGENDA}\bf
24:
25: \begin{nrtc}
26: \item ISODE: INTRODUCTION AND STATUS REPORT (ROSE)
27:
28: \item PUTTING ISODE TO WORK (KILLE)
29:
30: \item ISODE AT THE UNIVERSITY OF DELAWARE (MINNICH)
31:
32: \item A STRATEGY FOR CONVERGENCE WITH ISO\\
33: (ANOTHER SERMON FROM MT.~ROSE?)
34: \end{nrtc}
35: \end{bwslide}
36:
37:
38: \begin{bwslide}
39: \part {ISODE:\\ INTRODUCTION AND\\ STATUS REPORT}
40: \end{bwslide}
41:
42:
43: \begin{bwslide}
44: \ctitle {ISODE}
45:
46: \begin{nrtc}
47: \item AN OPENLY AVAILABLE ISO DEVELOPMENT ENVIRONMENT
48:
49: \item ISO APPLICATION, PRESENTATION, SESSION, AND LAYERED TRANSPORT
50:
51: \item CODED ENTIRELY IN C
52:
53: \item OPERATING SYSTEMS
54: \begin{nrtc}
55: \item 4.2\bsd/ \unix/
56:
57: \item SVR2 AT\&T \unix/ WITH AN EXCELAN \exos/~8044 TCP/IP PACKAGE
58:
59: \item \vms/ AND \pcdos/ (STILL) UNDER DEVELOPMENT
60: \end{nrtc}
61: \end{nrtc}
62: \end{bwslide}
63:
64:
65: \begin{bwslide}
66: \ctitle {MOTIVATION}
67:
68: \begin{nrtc}
69: \item WANT TO BE CONSISTENT WITH ISO'S DIRECTION,
70: BUT WANT TO GET WORK DONE NOW
71: \begin{nrtc}
72: \item MANY NEW, MAJOR INVESTMENTS BEING MADE IN CURRENT TECHNOLOGY
73: (e.g., NSFnet, NASA's NEW INTERNET, etc.)
74: \end{nrtc}
75:
76: \item CURRENTLY, TCP/IP HAS SEVERAL ADVANTAGES OVER TP4/IP:
77: \begin{nrtc}
78: \item WORKING IS-IS (GATEWAY-GATEWAY) PROTOCOL
79:
80: \item MATURITY
81:
82: \item VENDOR SUPPORT
83:
84: \item LARGE BODY OF EXPERTISE
85: \end{nrtc}
86:
87: \item WOULD LIKE TO WORK IN AN ISO ENVIRONMENT,
88: BUT WILL USE TCP/IP's STRENGTHS TO DO SO NOW
89: \end{nrtc}
90: \end{bwslide}
91:
92:
93: \begin{bwslide}
94: \ctitle {THE APPLICATION ENVIRONMENT}
95:
96: \vskip.15in
97: \diagram[p]{figure1}
98: \end{bwslide}
99:
100:
101: \begin{note}\em
102: other ASEs: RTSE, CCR, and so on
103:
104: presentation: manage presentation contexts~---~abstract syntax and transfer
105:
106: session: manage tokens, activities, checkpointing, and so on
107:
108: about 35K lines of code
109: \end{note}
110:
111:
112: \begin{bwslide}
113: \ctitle {AN ALTERNATE ENVIRONMENT:\\ MHS ARCHITECTURE (c.~1984)}
114:
115: \vskip.15in
116: \diagram[p]{figure2}
117: \end{bwslide}
118:
119:
120: \begin{bwslide}
121: \ctitle {APPLICATIONS IN PROGRESS}
122:
123: \begin{nrtc}
124: \item FTAM - FILE TRANSFER, ACCESS AND MANAGEMENT (NRTC)
125:
126: \item MHS - MESSAGE HANDLING SYSTEM (UCL)
127:
128: \item DS - DIRECTORY SERVICES (UCL)
129: \end{nrtc}
130: \end{bwslide}
131:
132:
133: \begin{bwslide}
134: \ctitle {PERFORMANCE OBSERVATIONS}
135:
136: \begin{nrtc}
137: \item THE 5-P PRINCIPLE:\\
138: PROPER PLANNING PREVENTS POOR PERFORMANCE
139:
140: \item INITIAL BENCHMARKING SUGGESTS THROUGHPUT RATES VERY CLOSE TO RAW TCP
141: FOR BOTH TRANSPORT AND SESSION ECHO AND SINK ENTITIES
142:
143: \item AT THE APPLICATION INTERFACE (ABOVE ACSE/ROSE),
144: THROUGHPUT IS ONLY 10\%-12\% WORSE THAN RAW TCP FOR DATA TRANSFER
145:
146: \item RESULTS PRIMARILY DUE TO MINIMIZED BYTE-COPYING BETWEEN LAYERS
147: \end{nrtc}
148: \end{bwslide}
149:
150:
151: \begin{bwslide}
152: \ctitle {WHERE NEXT?}
153:
154: \begin{nrtc}
155: \item VALIDATE/TEST AGAINST PURE ISO\\
156: (SOMEBODY ELSE'S IMPLEMENTATION)
157:
158: \item SYNCHRONIZE WITH GOSIP SPECIFICATION
159:
160: \item EXPAND SOME MODULES AS NEW APPLICATIONS REQUIRE
161:
162: \item CONVERGENCE WORK (DESCRIBED LATER)
163: \end{nrtc}
164: \end{bwslide}
165:
166:
167: \begin{bwslide}
168: \ctitle {AVAILABILITY INFORMATION}
169:
170: \begin{nrtc}
171: \item VERSION 2 AVAILABLE MARCH 15, 1987
172:
173: \item USPS: SEND TAPE AND PREPAID MAILER TO:
174: \begin{small}
175: \[\begin{tabular}{l}
176: NORTHROP RESEARCH AND TECHNOLOGY CENTER\\
177: ATTN: AUTOMATION SCIENCES LABORATORY (0330/T30)\\
178: ONE RESEARCH PARK\\
179: PALOS VERDES PENINSULA, CA 90274\\
180: USA\\
181: \end{tabular}\]
182: \end{small}
183: \begin{nrtc}
184: \item ADD 3 POUNDS AND 1--1/2 INCHES FOR DOCUMENTATION SET
185:
186: \item SEND ONLY POSTAGE, NO MONEY
187:
188: \item TELCO: 213--544--5393
189: \end{nrtc}
190:
191: \item ANONYMOUS FTP: HOST louie.udel.edu, FILE portal/isode-2.tar
192: \end{nrtc}
193: \end{bwslide}
194:
195:
196: \begin{bwslide}
197: \part {PUTTING ISODE TO WORK}\large\bf
198:
199: \vskip-0.5in
200: \[\begin{tabular}[t]{c}\large\bf
201: Stephen E.~Kille\\
202: Department of Computer Science\\
203: University College, London
204: \end{tabular}\]
205: \end{bwslide}
206:
207:
208: \begin{note}\em
209: with credits to:
210:
211: \begin{nrtc}
212: \item at UCL:\\
213: George G.~Michaelson, Stephen E.~Easterbrook, Thomas Woo
214:
215: \item at the Department of Computer Science, Nottingham University:\\
216: Julian P.~Onions
217: \end{nrtc}
218: \end{note}
219:
220:
221: \begin{bwslide}
222: \ctitle {OVERVIEW}
223:
224: \begin{nrtc}
225: \item DISCUSSION OF WORK AT UCL USING ISODE
226:
227: \item WORK ON DISTRIBUTED APPLICATIONS
228:
229: \item EMPHASIS ON MESSAGE HANDLING AND DIRECTORY SERVICES
230:
231: \item FOCUS ON WORK ALIGNED WITH INTERNATIONAL STANDARDS
232:
233: \item AIM TO DESCRIBE HOW ISODE FACILITATES THIS WORK
234: \end{nrtc}
235: \end{bwslide}
236:
237:
238: \begin{bwslide}
239: \ctitle {OSI INFRASTRUCTURE}
240:
241: \begin{nrtc}
242: \item UCL RUNS A WIDE VARIETY OF UNIX SYSTEMS
243:
244: \item NEEDS OSI ENVIRONMENT WHICH CAN OPERATE ON ALL OF THESE,
245: FOR WORKING IN BOTH LANs AND WANs
246:
247: \item CURRENTLY USE TCP/IP OVER THE LAN,
248: AS THIS IS THE ONLY PROTOCOL COMMON TO ALL OF THE MACHINES IN QUESTION
249:
250: \item TP0/X.25 WILL BE USED FOR WAN ACCESS
251:
252: \item TP4 MAY ALSO BE USED (IF WE HAVE TO)
253: \end{nrtc}
254: \end{bwslide}
255:
256:
257: \begin{bwslide}
258: \ctitle {ADVANTAGES OF TP0/X.25}
259:
260: \begin{nrtc}
261: \item THE PREFERRED EUROPEAN APPROACH
262:
263: \item EFFICIENT UTILIZATION OF PTT X.25 SERVICES
264:
265: \item UTILIZATION OF X.25 HARDWARE TO REDUCE CPU LOAD
266:
267: \item WILL ALLOW FOR EXTENSIVE TESTING OF ISODE AGAINST OTHER OSI
268: IMPLEMENTATIONS AT UCL AND ELSEWHERE
269:
270: \item MIGRATION TO USE OF X.25 OVER IEEE~802 LLC
271: \end{nrtc}
272: \end{bwslide}
273:
274:
275: \begin{bwslide}
276: \ctitle {ABSTRACT SYNTAX NOTATION 1 (ASN.1)}
277:
278: \begin{nrtc}
279: \item REPRESENTATION CURRENTLY USED BY ALL OSI APPLICATIONS
280:
281: \item RICH, EXTENSIBLE SYNTAX
282:
283: \item USEFUL FOR SPECIFICATION OF NEW PROTOCOLS
284: \begin{nrtc}
285: \item CLEAR TO READ SPECIFICATIONS
286:
287: \item NOT TIED TO MACHINE-ORIENTED STRUCTURES AND RESTRICTIONS
288: \end{nrtc}
289: \end{nrtc}
290: \end{bwslide}
291:
292:
293: \begin{bwslide}
294: \ctitle {REMOTE OPERATIONS SERVICE (ROS)}
295:
296: \begin{nrtc}
297: \item STANDARDIZED MECHANISM FOR SPECIFYING TRANSACTIONS
298:
299: \item MAKES FULL POWER OF ASN.1 AVAILABLE
300:
301: \item USED IN MANY INTERESTING OSI APPLICATIONS
302: \begin{nrtc}
303: \item MESSAGING
304:
305: \item DIRECTORY SERVICES
306:
307: \item NETWORK MANAGEMENT
308:
309: \item REMOTE DATABASE ACCESS
310: \end{nrtc}
311: \end{nrtc}
312: \end{bwslide}
313:
314:
315: \begin{bwslide}
316: \ctitle{WHY ISODE}
317:
318: \begin{nrtc}
319: \item FULL AND UP-TO-DATE IMPLEMENTATION OF OSI LAYERS
320:
321: \item REMOTE OPERATIONS SERVICE
322:
323: \item ASN.1 ELEMENT HANDLING
324:
325: \item COMPILER FOR DECODING ASN.1 (PEPY)
326:
327: \item FLEXIBILITY TO USE DIFFERENT TRANSPORT SERVICES
328:
329: \item GOOD PERFORMANCE
330: \end{nrtc}
331: \end{bwslide}
332:
333:
334: \begin{bwslide}
335: \ctitle{RARE DIRECTORY SERVICES}
336:
337: \begin{nrtc}
338: \item R\'{E}SEAUX ASSOCI\'{E}S POUR LA RECHERCHE EUROP\'{E}ENNE (RARE)
339:
340: \item TRANSLATION: EUROPEAN ACADEMIC RESEARCH NETWORK
341:
342: \item AN ASSOCIATION OF THE VARIOUS NATIONAL RESEARCH NETS
343:
344: \item WISH TO PROVIDE EARLY DIRECTORY SERVICES, UTILIZING
345: A CENTRAL DATABASE (LIKE THE ARPA ``WHOIS'')
346:
347: \item CONTAINS FACILITY, PROJECT, AND PERSON DATA
348:
349: \item THE DATA IS MORE VALUABLE THAN THE INITIAL SERVICE
350:
351: \item DATA STANDARD FORMAT IS DESIRED
352: \end{nrtc}
353: \end{bwslide}
354:
355:
356: \begin{bwslide}
357: \ctitle{RARE ASN.1 STRUCTURE}
358:
359: \begin{nrtc}
360: \item UCL HAS SPECIFIED A FIRST VERSIONS OF THE DATA STRUCTURE
361:
362: \item ASN.1 USED
363:
364: \item CAN REPRESENT DETAILED STRUCTURE, WHICH WILL BE USEFUL IN
365: LATER DISTRIBUTED DIRECTORY SERVICES
366:
367: \item PEPY (ISODE) MADE ASN.1 VERIFICATION STRAIGHTFORWARD IN THE
368: DESIGN PHASE
369:
370: \item ALLOWED EASY IMPLEMENTATION OF ``PRETTY PRINTER'' AND
371: ENCODING OF TEST DATA
372:
373: \item IS LIKELY TO BE USED TO SUPPORT THE WIDER INTRODUCTION OF
374: THIS FORMAT FOR ENCODING AND DECODING
375: \end{nrtc}
376: \end{bwslide}
377:
378:
379: \begin{bwslide}
380: \ctitle{NRS LOOKUP PROTOCOL}
381:
382: \begin{nrtc}
383: \item NAME REGISTRATION SCHEME (NRS) IS A DATABASE OF THE HOSTS
384: (DOMAINS) IN THE UK ACADEMIC COMMUNITY.
385:
386: \item CURRENTLY CONTAINS ABOUT 1000 HOSTS, AND IS GROWING RAPIDLY
387:
388: \item THE CENTRALIZED DATABASE HAS DISTRIBUTED MANAGEMENT AND
389: IS WIDELY REPLICATED
390:
391: \item NRS LOOKUP PROTOCOL SPECIFIES A LIGHTWEIGHT TRANSACTION
392: OVER X.25, TO ENABLE LOOKUP OF INFORMATION IN THE NRS
393:
394: \item THE PACKET FORMATS ARE SPECIFIED IN ASN.1
395:
396: \item HANDLES BOTH CURRENT ``COLOURED BOOK'' APPLICATIONS AND
397: PLANNED OSI APPLICATIONS
398: \end{nrtc}
399: \end{bwslide}
400:
401:
402: \begin{bwslide}
403: \ctitle{NRS LOOKUP PROTOCOL IMPLEMENTATION}
404:
405: \begin{nrtc}
406: \item IMPLEMENTATION DONE IN PARALLEL WITH FINAL WORK ON SPECIFICATION
407:
408: \item 3RD YEAR STUDENT PROJECT (3 MONTHS)
409:
410: \item PEPY FOUND A NUMBER OF ERRORS IN THE PROTOCOL SPECIFICATION
411:
412: \item PEPY ALLOWED A FULL PROTOCOL DECODER TO BE BUILT WITH MINIMUM EFFORT
413:
414: \item EARLY RESULTS SUGGEST GOOD PERFORMANCE
415: \end{nrtc}
416: \end{bwslide}
417:
418:
419: \begin{bwslide}
420: \ctitle{MESSAGE HANDLING}
421:
422: \begin{nrtc}
423: \item UCL AND NOTTINGHAM UNIVERSITY ARE DEVELOPING AN X.400 SYSTEM (PP)
424:
425: \item OWES MANY OF ITS DESIGN IDEAS TO MMDF (THE CSNET MESSAGE SYSTEM)
426:
427: \item FLEXIBLE HANDLING OF MULTI-MEDIA
428:
429: \item PROTOCOL AND FORMAT CONVERSION
430:
431: \item UTILIZATION WITH DIRECTORY SERVICES
432:
433: \item MAY BE DISTRIBUTED WITH LATER VERSIONS OF ISODE
434: \end{nrtc}
435: \end{bwslide}
436:
437:
438: \begin{bwslide}
439: \ctitle{CURRENT USE OF ISODE IN PP}
440:
441: \begin{nrtc}
442: \item MOST OF THE EARLY WORK HAS NOT NEEDED ISODE
443:
444: \item PEPY CAN HANDLE P1 AND P2
445:
446: \item INTEGRATION OF P1 AND ISODE'S RELIABLE TRANSFER SERVICE (RTS) HAS
447: STARTED AND HAS BEEN SATISFYINGLY STRAIGHTFORWARD
448: \end{nrtc}
449: \end{bwslide}
450:
451:
452: \begin{bwslide}
453: \ctitle{PLANNED USE OF ISODE IN PP}
454:
455: \begin{nrtc}
456: \item RFC987 WILL BE IMPLEMENTED, TO PROVIDE FULL MAPPINGS
457: BETWEEN X.400 AND RFC822 MAIL
458:
459: \item QUEUE MANAGEMENT WILL UTILIZE A ROS PROTOCOL
460: \begin{nrtc}
461: \item THIS WILL PROVIDE HIGH FUNCTIONALITY, AND ALLOW FOR REMOTE
462: MANAGEMENT
463: \end{nrtc}
464:
465: \item A SYSTEM FOR MANAGING LOCAL LISTS WILL BE SPECIFIED IN ROS
466: \end{nrtc}
467: \end{bwslide}
468:
469:
470: \begin{bwslide}
471: \ctitle{UCL DIRECTORIES}
472:
473: \begin{nrtc}
474: \item HAVE ESTABLISHED DATABASE OF UCL USERS IN CENTRAL DATABASE
475: \begin{nrtc}
476: \item DATA SEEMS TO BE A PRE-REQUISITE OF A DIRECTORY SERVICE!
477: \end{nrtc}
478:
479: \item ACCESS USING ROS TO ALLOW INFORMATION TO BE UPDATED AND QUERIED
480:
481: \item GENERATION OF LOCAL MAIL TABLES IS AUTOMATED FROM THIS DATABASE
482:
483: \item ALL UCL PASSWORD FILES ARE MANAGED FROM THIS DATABASE
484: \begin{nrtc}\small
485: \item MUCH HARDER THAN WE THOUGHT
486:
487: \item ALL PASSWORD FILE RELATED TOOLS (passwd(1), chsh(1), etc.)
488: EMULATED OVER ROS
489:
490: \item SOME EXTENSIONS
491: (E.G., ABILITY TO CHANGE PASSWORDS ON ALL MACHINES)
492:
493: \item PASSWORD FILES PULLED BY MACHINES USING ROS
494:
495: \item UCL SPECIFIC (SIMPLE) APPROACH TO AUTHENTICATION
496: \end{nrtc}
497:
498: \item CURRENT SYSTEM IS SEEN AS A STEPPING STONE TO FULL OSI
499: DIRECTORY SERVICES
500: \end{nrtc}
501: \end{bwslide}
502:
503:
504: \begin{bwslide}
505: \ctitle{WORK AT UCL TO EXTEND ISODE}
506:
507: \begin{nrtc}
508: \item TOOLS TO FACILITATE DEVELOPMENT OF APPLICATIONS ARE SEEN AS CRITICAL
509:
510: \item CURRENTLY EXTENDING PEPY TO PERFORM ENCODING AS WELL AS DECODING
511:
512: \item WILL EXTEND PEPY TO SUPPORT ROS IN AN AUTOMATIC MANNER,
513: MIXING ENCODING AND DECODING FUNCTIONS
514:
515: \item ENABLE ROS TO BE USED IN A MANNER VERY LIKE
516: SOME REMOTE PROCEDURE CALL APPROACHES
517: \end{nrtc}
518: \end{bwslide}
519:
520:
521: \begin{bwslide}
522: \part {ISODE AT\\ THE UNIVERSITY OF DELAWARE}\bf
523:
524: \vskip-0.5in
525: \[\begin{tabular}[t]{c}\large\bf
526: Ronald G.~Minnich\\
527: Dept. of Electrical Engineering\\
528: University of Delaware
529: \end{tabular}\hskip1em plus.17fil
530: \begin{tabular}[t]{c}\large\bf
531: David J.~Farber\\
532: Dept. of Electrical Engineering\\
533: Dept. of Computer and Information Sciences\\
534: University of Delaware
535: \end{tabular}\]
536: \end{bwslide}
537:
538:
539: \begin{bwslide}
540: \ctitle {STANDARD DISCLAIMER}
541:
542: \begin{nrtc}
543: \item ISODE HAS JUST COME INTO USE AT UDEL AS OF 1987
544:
545: \item WE KNOW ABOUT ISO BUT HAVE NEVER USED ISO OR ISODE~---
546: \begin{nrtc}
547: \item WE ARE NOT ALONE IN THAT; THAT IS WHY ISODE EXISTS
548: \end{nrtc}
549: \end{nrtc}
550: \end{bwslide}
551:
552:
553: \begin{bwslide}
554: \ctitle {ISODE AFFECTS THREE AREAS}
555:
556: \begin{nrtc}
557: \item EXPERIMENTAL COMPUTER NETWORK RESEARCH
558:
559: \item SYSTEMS PROGRAMMING
560:
561: \item APPLICATIONS PROGRAMMING
562: \end{nrtc}
563: \end{bwslide}
564:
565:
566: \begin{bwslide}
567: \ctitle {IMPLICATIONS OF ISO FOR OUR NETWORK RESEARCH}
568:
569: \begin{nrtc}
570: \item IF THE ISO MODEL IS THE FUTURE,
571: THEN xxxNET HAD BETTER SUPPORT IT EFFECTIVELY
572:
573: \item WE HAVE SEEN A SIMILAR PHENOMENON WITH UNIX AND COMPUTER ARCHITECTURE
574: \end{nrtc}
575: \end{bwslide}
576:
577: \begin{bwslide}
578: \ctitle {EXPERIMENTAL COMPUTER NETWORK RESEARCH}
579:
580: \begin{nrtc}
581: \item MEMNET[DELP86]~---~LARGE PHYSICALLY DISTRIBUTED MEMORY CONNECTED BY A
582: TOKEN RING
583: \begin{nrtc}
584: \item IT IS UNDER CONSTRUCTION NOW AND SIMULATIONS PREDICT VERY HIGH
585: THROUGHPUT
586:
587: \item WE ARE CONSIDERING PUTTING ISODE ON TOP OF MEMNET;
588: MEMNET BECOMES THE TRANSPORT
589:
590: \item WE CONSIDER THIS A GOOD TEST OF MEMNET'S CAPABILITIES AS WELL
591: AS BEING POTENTIALLY WORTHWHILE IN AND OF ITSELF
592: \end{nrtc}
593:
594: \item NOAHNET[PARULKAR86]~---~FLOOD NETWORK
595: \begin{nrtc}
596: \item WHAT IMPLICATIONS DOES THE ISO MODEL HAVE FOR NOAHNET?
597: \end{nrtc}
598: \end{nrtc}
599: \end{bwslide}
600:
601:
602: \begin{bwslide}
603: \ctitle {ISO FOR SYSTEMS PROGRAMMING}
604:
605: \begin{nrtc}
606: \item WE NEED TO LEARN HOW TO USE IT FOR `HOUSEKEEPING'\\
607: (e.g. KERNAL DATA STRUCTURE MONITORS, FONT LOADERS,\\
608: MAN PAGE PROGRAMS, etc.)
609:
610: \item WHERE WE HAVE BEEN USING THE UNSTRUCTURED ``PIPE''-LIKE CHANNEL
611: PROVIDED BY TCP/IP, WE NOW USE THE HIGHER-LEVEL ISO CONSTRUCTS
612:
613: \item A LOGICAL CONSEQUENCE OF THE ABOVE IS THAT WE WILL NOT NEED AS
614: MANY CUSTOM PROTOCOLS (e.g., rdump, rman, etc.)
615: AND WILL THUS (WE HOPE) HAVE LESS CONFUSION WHEN AN 'r'-PROGRAM
616: BREAKS (AND THEY HAVE~---~EXAMPLE ON REQUEST)
617:
618: \item ISODE AND PEPY MAKE THE PROCESS MUCH EASIER
619: \end{nrtc}
620: \end{bwslide}
621:
622:
623: \begin{note}\em
624: example slides here...
625: \end{note}
626:
627: \begin{bwslide}
628: \ctitle {WHERE DO I SIGN?}
629:
630: \begin{nrtc}
631: \item BUT: WE HAVE TO CLIMB A STEEP LEARNING CURVE
632:
633: \item MUCH BIGGER BUT: WE HAVE TO CONVINCE OTHERS TO CLIMB IT TOO
634: \end{nrtc}
635: \end{bwslide}
636:
637:
638: \begin{bwslide}
639: \ctitle {ISO FOR THE APPLICATIONS PROGRAMMER}
640:
641: \begin{nrtc}
642: \item MAIL SYSTEMS
643:
644: \item MULTI-MEDIA SYSTEMS (E.G. NETWORKED APA DISPLAYS)
645:
646: \item NETWORK MONITORING PROGRAMS[AMER87]
647:
648: \item IMAGE PROCESSING
649:
650: \item SPEECH PROCESSING
651:
652: \item NETWORKED PCs~---~USING PCs TO HELP MANAGE VAX RESOURCES
653: \end{nrtc}
654: \end{bwslide}
655:
656:
657: \begin{bwslide}
658: \ctitle {TWO PROBLEMS}
659: \begin{nrtc}
660: \item CONVINCING VERY BUSY PEOPLE TO TAKE THE TIME TO LEARN IT
661:
662: \item ONCE THEY LEARN IT, DO THEY FIND IT BOTH USABLE AND USEFUL?
663: \end{nrtc}
664:
665: SO FAR, AT UDEL, THERE IS NOT ENOUGH TIME TO TELL
666: \end{bwslide}
667:
668:
669: \begin{bwslide}
670: \ctitle {CONCLUSIONS}
671:
672: \begin{nrtc}
673: \item EXPERIMENTAL NETWORKS AT UDEL WILL SUPPORT ISODE
674: \begin{nrtc}
675: \item BOTH AS A TEST OF ISODE\\ AND AS A TEST OF THE NETWORK
676: \end{nrtc}
677:
678: \item WE ARE PLANNING TO USE ISODE FOR SYSTEM PROGRAMS THAT
679: PREVIOUSLY WOULD HAVE BEEN IMPLEMENTED IN THE 'r'-PROGRAM STYLE OR
680: THAT COULD NOT HAVE BEEN EASILY WRITTEN AT ALL
681:
682: \item WE ARE ENCOURAGING OTHER RESEARCHERS AT UDEL TO USE ISODE FOR THEIR
683: APPLICATIONS
684: \end{nrtc}
685: \end{bwslide}
686:
687:
688: \begin{bwslide}
689: \part {A STRATEGY FOR CONVERGENCE WITH ISO}\bf
690:
691: \vskip-0.5in
692: \[\begin{tabular}[t]{c}\large\bf
693: Marshall T.~Rose\\
694: Computer Science Laboratory\\
695: Northrop Research and Technology Center
696: \end{tabular}\]
697: \end{bwslide}
698:
699:
700: \begin{bwslide}
701: \ctitle {THE PROBLEM}
702:
703: \begin{nrtc}
704: \item TCP/IP IS HERE NOW AND IT WORKS
705:
706: \item ISO IS INEVITABLE!
707:
708: \item HOW DO WE GET TO THERE FROM HERE?
709: \end{nrtc}
710: \end{bwslide}
711:
712:
713: \begin{bwslide}
714: \ctitle {PREMISES}
715:
716: \begin{nrtc}
717: \item START WITH AN EXISTING TCP/IP INTERNET
718:
719: \item ADD SOME ISO-ONLY HOSTS/NETWORKS
720:
721: \item MAKE NO MODIFICATIONS TO ISO-ONLY HOSTS
722: (AND MINIMIZE CHANGES TO TCP/IP HOSTS)
723: \end{nrtc}
724: \end{bwslide}
725:
726:
727: \begin{bwslide}
728: \ctitle {DESIRED INTEROPERABILITY}
729:
730: \begin{nrtc}
731: \item WANT SERVICES BETWEEN END-SYSTEMS AT HIGHER-LEVELS
732:
733: \item AVOID APPLICATION-LEVEL GATEWAYS
734:
735: \item IMPLIES INTEROPERABILITY AT TRANSPORT LAYER AND ABOVE
736:
737: \item CONVERGE ON HIGHER-LEVELS IN THE ISO SUITE
738:
739: \item NEEDED: VIRTUAL TRANSPORT SERVICE
740: \end{nrtc}
741: \end{bwslide}
742:
743:
744: \begin{bwslide}
745: \ctitle {TCP TRANSPORT SERVICE}
746:
747: \vspace{0.25in}
748: \diagram[p]{figure3a}
749: \end{bwslide}
750:
751:
752: \begin{bwslide}
753: \ctitle {ISO TRANSPORT SERVICE}
754:
755: \vspace{0.25in}
756: \diagram[p]{figure3b}
757: \end{bwslide}
758:
759:
760: \begin{bwslide}
761: \ctitle {A CONVERGENCE STRATEGY}
762:
763: \begin{nrtc}
764: \item NEED TWO THINGS:
765: \begin{nrtc}
766: \item HIGHER-LEVEL ISO SERVICES FOR TCP/IP HOSTS
767:
768: \item ISO-IP ENCAPSULATION ON DDN-IP
769: \end{nrtc}
770: \end{nrtc}
771: \end{bwslide}
772:
773:
774: \begin{bwslide}
775: \ctitle {VIRTUAL ISO TRANSPORT SERVICE}
776:
777: \vspace{0.25in}
778: \diagram[p]{figure3c}
779: \end{bwslide}
780:
781:
782: \begin{bwslide}
783: \ctitle {ISO DEVELOPMENT ENVIRONMENT}
784:
785: \begin{nrtc}
786: \item PROVIDES HIGHER-LEVEL ISO SERVICES FOR TCP/IP HOSTS
787:
788: \item A MAGIC-BOX OFFERS TP4 SERVICE OVER TCP (RFC983)
789:
790: \item GAIN EXPERIENCE WITH THE ISO SUITE
791: \end{nrtc}
792: \end{bwslide}
793:
794:
795: \begin{bwslide}
796: \ctitle {ISO TRANSPORT SERVICES ON TOP OF THE TCP}
797:
798: \diagram[p]{figure4}
799: \end{bwslide}
800:
801:
802: \begin{bwslide}
803: \ctitle {MIXED ISO TRANSPORT SERVICE}
804:
805: \vspace{0.25in}
806: \diagram[p]{figure3d}
807: \end{bwslide}
808:
809:
810: \begin{bwslide}
811: \ctitle {DUAL-IP ``GATEWAYS''}
812:
813: \begin{nrtc}
814: \item NEED TWO MORE THINGS:
815: \begin{nrtc}
816: \item PUT A REAL TP4 AND ISO-IP IN THE HYBRID HOST
817:
818: \item WITH ISO-IP ENCAPSULATED IN DDN-IP
819: \end{nrtc}
820: \end{nrtc}
821: \end{bwslide}
822:
823:
824: \begin{bwslide}
825: \ctitle {HYBRID HOST}
826:
827: \diagram[p]{figure5}
828: \end{bwslide}
829:
830:
831: \begin{bwslide}
832: \ctitle {THE BIG PICTURE}
833:
834: \vspace{0.25in}
835: \diagram[p]{figure6}
836: \end{bwslide}
837:
838:
839: \begin{bwslide}
840: \ctitle {VIRTUAL TRANSPORT SERVICES (REVIEW)}
841:
842: \vspace{0.25in}
843: \diagram[p]{figure7}
844: \end{bwslide}
845:
846:
847: \begin{note}\em
848: to migrate: just stop buying tcp/ip when both of these are done
849:
850: you need an application gateway to go from tcp/ip-only to iso-only
851: (essential for mail, probably not needed otherwise)
852: \end{note}
853:
854:
855: \end{document}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.