RE: fodder for the proposed FTP feature/cmd registry

Robert McMurray <robmcm@microsoft.com> Mon, 05 October 2009 20:09 UTC

Return-Path: <robmcm@microsoft.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46C443A68D3 for <apps-discuss@core3.amsl.com>; Mon, 5 Oct 2009 13:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZ8LfSH8Wo3b for <apps-discuss@core3.amsl.com>; Mon, 5 Oct 2009 13:09:14 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id B0A7D3A6835 for <apps-discuss@ietf.org>; Mon, 5 Oct 2009 13:08:59 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 5 Oct 2009 13:10:38 -0700
Received: from TK5EX14MBXC127.redmond.corp.microsoft.com ([169.254.6.18]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi; Mon, 5 Oct 2009 13:10:28 -0700
From: Robert McMurray <robmcm@microsoft.com>
To: "'ah@TR-Sys.de'" <ah@TR-Sys.de>, "john+ietf@jck.com" <john+ietf@jck.com>
Subject: RE: fodder for the proposed FTP feature/cmd registry
Thread-Topic: fodder for the proposed FTP feature/cmd registry
Thread-Index: AQHKPtvgRYpMR6Mu40mGaip3215Cs5D3cV9A
Date: Mon, 05 Oct 2009 20:10:27 +0000
Message-ID: <A5FC996C3C37DC4DA5076F1046B5674C082F5114@TK5EX14MBXC127.redmond.corp.microsoft.com>
References: <200909251700.TAA11690@TR-Sys.de>
In-Reply-To: <200909251700.TAA11690@TR-Sys.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Content-Type: multipart/mixed; boundary="_002_A5FC996C3C37DC4DA5076F1046B5674C082F5114TK5EX14MBXC127r_"
MIME-Version: 1.0
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2009 20:09:15 -0000

I'm not sure if the attached file helps, but I put it together some months ago as a quick reference to the list of FTP commands, their syntax, and any possible reply codes that I could find. The introduction lists the RFCs that I used to gather the information.

Thanks!

Robert McMurray
US-IIS Product Unit
Email: robmcm@microsoft.com

-----Original Message-----
From: ah@TR-Sys.de [mailto:ah@TR-Sys.de] 
Sent: Friday, September 25, 2009 10:01 AM
To: john+ietf@jck.com
Cc: apps-discuss@ietf.org
Subject: fodder for the proposed FTP feature/cmd registry

John,
as promised recently, I have performed some harvesting of RFCs and I-Ds to collect material for the initial content of the IANA registry proposed in your I-D, draft-klensin-ftp-registry.

Enclosed is a (still rough) tabulation of my results, listing all FTP commands and FTP Features I found specified in RFCs (since roughly RFC 600, but excluding gravestone dead FTP Mail
stuff) and recent I-Ds.

Kind regards,
  Alfred.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+