Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!agate!ucbvax!LANL.GOV!cpw%sneezy
From: cpw%sneezy@LANL.GOV (C. Philip Wood)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: FTP "STRU VMS" extension
Message-ID: <8902021658.AA01193@sneezy.lanl.gov>
Date: 2 Feb 89 16:58:06 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

One more thing and I'll leave it to the experts.

Rather than STRU VMS, make it STRU {LOCAL|EXOTIC}.  If two VMS hosts
were "inter-operating" than either option would work correctly.

	STRU LOCAL means that files transfered from the local host
	to the "exotic" host (I could not use Foreign or Remote because
	of File and Record) would be in a standard-for-local-operating-system
	format (SFLOS) ('tar;compressed' for UNIX, 'cpio;???' for ATT, ...).
	Conversely, files transfered to the local host would be in this
	"standard" format.  The "Exotic" host would have to understand
	this "standard".

	STRU EXOTIC means that the structure for a "file" transfer
	would be in standard-for-remote-operating-system  (SFROS) format.
	
That way we don't run out of single character mneumonics for all the
"Open" operating systems coming down the line.

Phil Wood,  cpw@lanl.gov