Re: FTP or ftp, mailing lists?

April Marine <> Tue, 17 November 1992 00:10 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa13979; 16 Nov 92 19:10 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13975; 16 Nov 92 19:10 EST
Received: from kona.CC.McGill.CA by CNRI.Reston.VA.US id aa07240; 16 Nov 92 19:11 EST
Received: by (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA21075 on Mon, 16 Nov 92 15:18:43 -0500
Received: from by with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA21069 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Mon, 16 Nov 92 15:18:14 -0500
Received: by (5.64/SRI-NISC1.1) id AA05755; Mon, 16 Nov 92 12:16:47 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: April Marine <>
Message-Id: <>
To: Stephen Tihor 212 998 3052 <>
Subject: Re: FTP or ftp, mailing lists?
In-Reply-To: Your message of 16 Nov 92 09:38:28 -0400. <01GR7QSNEI0YB2ATRK@ACFcluster.NYU.EDU>
Date: Mon, 16 Nov 92 12:16:47 PST

>No but the DOCUMENTATIOn convention is to capitialize the actual commands 
>to make them stand out fromthe surrousing text without including quotes that 
>some users might well type in.

This is the very reason I think this doc should be issued in a parallel
postscript version--so that the various elements can be more clearly

However, in the text version, I favor the commands being in lowercase
and the name of the protocol/program in upppercase, with some other
convension used to show clearly when we are talking about commands.
Which is why sometimes the doc has "ftp" and sometimes "FTP", although
there may be times I'm inconsistent myself in using the right version.

Thanks to everyone who sent more comments.  I'm going to wait till after
the WG mtg this week before taking any more action on the thing.