Movatterモバイル変換

Network Working Group                                     James E. WhiteRFC #480                                                  SRI-ARCNIC #14949                                                8 March 73                     Host-Dependent FTP ParametersThis memo is in response to (and support of) one of the points raised byBob Braden (RTB) of UCLA-CCN in RFC #430, "COMMENTS ON FILE TRANSFERPROTOCOL" (see -- 13299,), namely that raised in Section D., "Site-Dependent FTP Parameters".The NIC has been confronted with similar problems (and tentativelydecided upon similar solutions) in designing mechanisms which wouldenable a user to use FTP to retrieve from the NIC, in sequential form, aVIEW of some portion for an NLS tree-structured file.To be done without modification to FTP, this task requires the user tocommunicate information -- a filename, a statement address, viewspecs,and the name of a conversion algorithm -- to SRI-ARC's server FTPprocess in a manner that is transparent to the user's user FTP process.We currently intend to require the user to embed this information in thepathname of FTP's STOR and RETR commands by appending to a standardTENEX filename, a field of the form:    ;x <program> [ / <parameters> ]where <program> identifies an arbitrary program to be dispatched bySRI-ARC's server FTP process, with a pointer to the file being stored orretrieved as an argument.  <parameters> is optional and, if present, isalso passed to the program.To store and retrieve NLS files in sequential form, we will require that<program> be 'NLS' and <parameters> be of the form.    [ T: <conversion-algorithm> ] [ S: <statement address> ] [ V:    <viewspecs> ]where each of the three items is optional, and any that appear areseparated by commas.       [ This RFC was put into machine readable form for entry ]       [ into the online RFC archives by Alex McKenzie with    ]       [ support from GTE, formerly BBN Corp.             9/99 ]White                                                           [Page 1]