FTP-FTAM Gateway Specification
RFC 1415
Document | Type |
RFC - Historic
(January 1993; No errata)
Was draft-slaski-ftpftam (individual)
|
|
---|---|---|---|
Last updated | 2013-03-02 | ||
Stream | Legacy | ||
Formats | plain text pdf html bibtex | ||
Stream | Legacy state | (None) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | RFC 1415 (Historic) | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group J. Mindel Request for Comments: 1415 R. Slaski Open Networks, Inc. January 1993 FTP-FTAM Gateway Specification Status of the Memo This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This memo describes a dual protocol stack application layer gateway that performs protocol translation, in an interactive environment, between the FTP and FTAM file transfer protocols. Two key assumptions are made: 1) POSIX file naming conventions and hierarchical organization, rather than proprietary conventions are in use; and 2) X.500 Directory Services are available. Acknowledgments The authors of this RFC would like to express their appreciation to the individuals and organizations that participated in the implementation of the FTP-FTAM Application Layer Gateway and its fielding on the MILNET. Implementation credits go to Mr. John Scott, formerly of the MITRE Corporation, while fielding credits are extended to James Graham and R. Greg Lavender of Open Networks, Inc. (formerly NetWorks One) and Robert Cooney of the Naval Computer and Telecommunications Station (NCTS) Washington. Dr. Marshall Rose is to be commended for recognizing the importance of the FTP-FTAM gateway and promulgating it as a part of the ISO Development Environment (ISODE). The following individuals have provided valuable editorial comments: Larry Friedman, Donna Vincent and Michael Resnick of Digital Equipment Corporation; Robert Cooney of NCTS; and S.E. Hardcastle-Kille of University College London. Funding of the FTP-FTAM Gateway Request for Comments effort was provided by Open Networks Inc. and the Defense Information Systems Agency (DISA), formerly the Defense Communications Agency. DISA sponsors include Len Tabacchi, George Bradshaw, Tom Clarke, and Betsy Turner. Mindel & Slaski [Page 1] RFC 1415 FTP-FTAM Gateway Specification January 1993 Table of Contents 1. Introduction..................................................2 1.1. Relationship to Other Work ................................3 1.2. Overview of Gateway Operation .............................4 2. Gateway Architecture..........................................6 3. Network Naming and Addressing.................................8 4. Use of the Gateway Services...................................9 4.1. FTP-Initiated Gateway Service .............................9 4.2. FTAM-Initiated Gateway Service ...........................11 4.3. Summary of Usage .........................................12 5. Gateway State Variables and Transitions......................13 5.1. FTP-Initiated Gateway Service ............................14 5.2. FTAM-Initiated Gateway Service ...........................16 6. Document Type Support........................................18 6.1. Notes on NBS-9 ...........................................18 7. Functional Comparison of FTP and FTAM........................19 7.1. Loss of Functionality ....................................20 8. Mapping of Protocol Functions and Representations.............20 8.1. FTP-Initiated Gateway Service .............................22 8.2. FTAM-Initiated Gateway Service ............................38 9. Mapping between FTP Reply Codes and FTAM Parameters...........47 9.1. FTP Reply Codes to FTAM Parameters ........................48 9.2. FTAM Parameters to FTP Reply Codes ........................50 9.3. Future Mapping Problem ....................................54 9.4. Error Handling ............................................54 10. Implementation and Configuration Guidelines..................54 10.1. Robustness ...............................................54 10.2. Well-Known TCP/IP Port ...................................55 10.3. Gateway Listener Processes ...............................55 10.4. Implementation Testing ...................................55 10.5. POSIX File Naming and Organization .......................55 11. Security Considerations......................................55 12. References...................................................56 13. Authors' Addresses...........................................58 1. Introduction The TCP/IP and OSI protocol suites will coexist in the Internet community for several years to come. As more and more OSI hosts areShow full document text