Re: Some non-expert additions to the proposed Internet Draft

Stephen Tihor 212 998 3052 <TIHOR@acfcluster.nyu.edu> Sat, 07 November 1992 01:08 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11289; 6 Nov 92 20:08 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11285; 6 Nov 92 20:08 EST
Received: from kona.CC.McGill.CA by CNRI.Reston.VA.US id aa23374; 6 Nov 92 20:09 EST
Received: by kona.cc.mcgill.ca (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA17364 on Fri, 6 Nov 92 18:12:54 -0500
Received: from ACF1.NYU.EDU by kona.cc.mcgill.ca with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA17360 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Fri, 6 Nov 92 18:12:50 -0500
Received: from ACFcluster.NYU.EDU by ACFcluster.NYU.EDU (PMDF #2884 ) id <01GQU9L4EZ1YA8ET01@ACFcluster.NYU.EDU>; Fri, 6 Nov 1992 18:11:57 EDT
Date: 06 Nov 1992 18:11:57 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Stephen Tihor 212 998 3052 <TIHOR@acfcluster.nyu.edu>
Subject: Re: Some non-expert additions to the proposed Internet Draft
To: eanders+@cmu.edu
Cc: iafa@cc.mcgill.ca
Message-Id: <01GQU9L4FRZCA8ET01@ACFcluster.NYU.EDU>
X-Vms-To: IN%"eanders+@cmu.edu"
X-Vms-Cc: IN%"iafa@cc.mcgill.ca"
Mime-Version: 1.0
Content-Transfer-Encoding: 7BIT

There is a difference from running in production and being production grade
software.  Probably a difference in local terminology.

I do not think we should recomend the use of any specific tool that omits a
number of the anonymous FTP sites I maintain or use most often.   Some UNIX
bigots assert that VMS, TOPS, MS-DOS, etc do not matter.  I am afraid that I 
disagree.  

I have made suggestions in the past that the archie project propose whatever
modifications to the FTP spec they require to automate their function. 
and the IAFA standardization work should help archie handle systems whose 
directory listing format it does not grok much better.   

But until one of those efforts reachs general availability allr eferences to
archie must be qualified by the restrictions that it ignores a chunk of the
filespace available and thus must not be treated as cannonical or even optimal.

The process involving add request and feeding archie filenames is one whose
documentation has never come to my attention.   Perhaps I missed the RFC or 
perhaps its only documented informally.  In our space, the Internet world,
I assume serious players generate at least an informational rfc or related
document.  [Can someone point me to the document I missed?]