Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!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: <8902131453.AA04179@sneezy.lanl.gov>
Date: 13 Feb 89 14:53:41 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 11

I vote for something that provides "interoperability".  But,
interoperability is not the ability of one VMS system to talk to
another.  The mechanism I would vote for would create an eXternal File
Representation (XFR), which would allow for REAL "interoperability"
between HETEROGENEOUS hosts.  It would take care of mapping file
attributes to and from the file attribute scheme of all time.  And, if
a mapping was impossible, it would give the phone number of the nearest
XYZ vendor sales office, so the user could switch to an OS that was
flexible enough to handle the problem.

Phil Wood,  cpw@lanl.gov