Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/pdfrfc/rfc480.txt.pdf Дата изменения: Wed Mar 27 23:47:22 2002 Дата индексирования: Tue Oct 2 16:27:36 2012 Кодировка:

Network Working Group RFC #480 NIC #14949

James E. White SRI-ARC 8 March 73

Host-Dependent FTP Parameters This memo Bob Braden PROTOCOL" Dependent The NIC decided enable VIEW of is in response to (and support of) one of the points raised by (RTB) of UCLA-CCN in RFC #430, "COMMENTS ON FILE TRANSFER (see -- 13299,), namely that raised in Section D., "SiteFTP Parameters".

has been confronted with similar problems (and tentatively upon similar solutions) in designing mechanisms which would a user to use FTP to retrieve from the NIC, in sequential form, a some portion for an NLS tree-structured file. this task requires the user to a statement address, viewspecs, -- to SRI-ARC's server FTP to the user's user FTP process.

To be done without modification to FTP, communicate information -- a filename, and the name of a conversion algorithm process in a manner that is transparent

We currently intend to require the user to embed this information in the pathname of FTP's STOR and RETR commands by appending to a standard TENEX filename, a field of the form: ;x [ / ] where identifies an arbitrary program to be dispatched by SRI-ARC's server FTP process, with a pointer to the file being stored or retrieved as an argument. is optional and, if present, is also passed to the program. To store and retrieve NLS files in sequential form, we will require that be 'NLS' and be of the form. [ T: ] [ S: ] [ V: ] where each of the three items is optional, and any that appear are separated 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]