|
|
1.1 ! root 1: % run this through LaTeX with the appropriate wrapper ! 2: ! 3: \section {Conclusions} ! 4: In this paper we have suggested that it is better to perform ! 5: {\em interface translation\/} rather than {\em protocol translation\/} ! 6: when one is interested in migrating between two protocol suites. ! 7: In our method, ! 8: which uses such an interface translation approach, ! 9: we implement the interface to the OSI Transport Services on top of the TCP. ! 10: This has the additional advantage of facilitating the development of OSI ! 11: applications in a robust and mature network environment, ! 12: and in allowing us to avoid any additional work in the future when we migrate. ! 13: In short, ! 14: we are able to make use of a complementary co-existence between the two ! 15: suites, ! 16: utilizing the best of both. ! 17: Our fundamental assumption in doing this is that the lower levels of the OSI ! 18: protocol suite will become fully supported as we follow our ! 19: migration strategy. ! 20: ! 21: Furthermore, ! 22: we have discussed the difficulties inherent in providing interoperability at ! 23: the application level, ! 24: and concluded that, as a part of a migration strategy, ! 25: building the special-purpose gateways required for each pair of related ! 26: applications is not a practical approach. ! 27: Neither the protocol translation or the interface translation approach is of ! 28: any benefit in building these gateways. ! 29: ! 30: Finally, ! 31: we have demonstrated that the DDN protocol suite, ! 32: because of both its maturity and closeness to to the OSI suite at the TSAP ! 33: provides an excellent migration vehicle for those users in need of ! 34: immediate electronic communications. ! 35: In view of the many new major investments being made in TCP/IP networks ! 36: (e.g., by the NSF and NASA), ! 37: we feel that our approach, ! 38: which emphasizes {\em evolution\/} rather than {\em revolution\/}, ! 39: is a useful solution.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.