IETF Logo Mail Archive

Re: [ftpext] A few comments on draft-bryan-ftp-hash-05

Robert McMurray <robmcm@microsoft.com> Tue, 13 July 2010 22:01 UTC

Return-Path: <robmcm@microsoft.com>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 688C33A6A4D for <ftpext@core3.amsl.com>; Tue, 13 Jul 2010 15:01:12 -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 LW0r8VH+FirY for <ftpext@core3.amsl.com>; Tue, 13 Jul 2010 15:01:11 -0700 (PDT)
Received: from smtp.microsoft.com (mail1.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 6E3B33A6A15 for <ftpext@ietf.org>; Tue, 13 Jul 2010 15:01:11 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 13 Jul 2010 15:01:19 -0700
Received: from TK5EX14MBXC129.redmond.corp.microsoft.com ([169.254.8.169]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.01.0180.004; Tue, 13 Jul 2010 15:01:18 -0700
From: Robert McMurray <robmcm@microsoft.com>
To: Anthony Bryan <anthonybryan@gmail.com>, "ftpext@ietf.org" <ftpext@ietf.org>
Thread-Topic: [ftpext] A few comments on draft-bryan-ftp-hash-05
Thread-Index: AQHLIGJRsnqG6pQWMEyywDXSJO7fBZKvYmRg
Date: Tue, 13 Jul 2010 22:01:15 +0000
Message-ID: <A5FC996C3C37DC4DA5076F1046B5674C3685A295@TK5EX14MBXC129.redmond.corp.microsoft.com>
References: <OF5B8F7FAC.BDF21341-ON80257752.00272796-80257752.002FC71F@uk.ibm.com> <4C2F1B7A.2040707@filezilla-project.org> <AANLkTinkcSl8PaGIQpJtGPfgGds5MvjXyxZYo1bJVDrJ@mail.gmail.com>
In-Reply-To: <AANLkTinkcSl8PaGIQpJtGPfgGds5MvjXyxZYo1bJVDrJ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ftpext] A few comments on draft-bryan-ftp-hash-05
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2010 22:01:12 -0000

In response to the following question that Anthony had posted:

>>  What should happen if somebody attempts to HASH
>>  something that isn't a file (e.g. it's a directory)?

I have a suggestion - why not return a list of filenames with their associated hashes for the directory using the algorithm that was specified by an earlier OPTS command? For example:

C> HASH /foo/
S> 125 Data connection already open; transfer starting.
S> MD5 F0E1D2C3B4A5968778695A4B3C2D1E0F file1.txt
S> MD5 78695A4B3C2D1E0FF0E1D2C3B4A59687 file2.txt
S> MD5 0F1E2D3C4B5A69788796A5B4C3D2E1F0 file3.txt
S> 226 Transfer complete.

This has obvious benefits when considering an FTP client that is trying to synchronize a list of files between locations, and it's much more reliable than file sizes and date/time stamps. In addition, allowing for the HASH command to be requested for a directory would be much better than trying to implement hashes in the response to a LIST request.

v2.46.0 | Report a Bug | By Email | System Status