Re: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-hash-00.txt

Bruce Blackshaw <bblackshaw@gmail.com> Fri, 06 April 2012 23:38 UTC

Return-Path: <bblackshaw@gmail.com>
X-Original-To: ftpext@ietfa.amsl.com
Delivered-To: ftpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63DD621F8542 for <ftpext@ietfa.amsl.com>; Fri, 6 Apr 2012 16:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V5UpwyulbKqo for <ftpext@ietfa.amsl.com>; Fri, 6 Apr 2012 16:38:04 -0700 (PDT)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB1521F853F for <ftpext@ietf.org>; Fri, 6 Apr 2012 16:38:04 -0700 (PDT)
Received: by dady13 with SMTP id y13so4436807dad.27 for <ftpext@ietf.org>; Fri, 06 Apr 2012 16:38:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=jERwTOswPMxddoTDs/AUqeaEwqVbTA91IOxq8XVBbuI=; b=hKa1il0gklmmG1BWIEPKZbSZAyYs0utDZY/B7xTDlogRVzW2x+y0A0uKFhCaDSIRWy hUmo/3O5Xf+3030bu4RKvC/ZRYd7ZwB4b1OQfdQRr/vrzxs/7u4tGAZFTVTQoDbzOOII EuL7KaPga1dcqTBE87fLIq06uabSA4RR3C6cmgwIikyM/akZ6voQSOhAqIw8OXLkyn2e DcH2GpMg7svI1MLX30xfyrDdfVw/DXnefH/mREZb2yuFJjrBSibmRljFg4WdpXEfwEUD TOhetngo9rzxZT3rNKUwo9iCw+rONvNCqPW47FhmsbhTUA2Xm2QOHfG8Dmlx9PFQZTxg 6baQ==
Received: by 10.68.221.10 with SMTP id qa10mr18966546pbc.139.1333755483890; Fri, 06 Apr 2012 16:38:03 -0700 (PDT)
Received: from [192.168.1.5] (ppp167-208-56.static.internode.on.net. [59.167.208.56]) by mx.google.com with ESMTPS id i1sm7504536pbj.70.2012.04.06.16.38.00 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 Apr 2012 16:38:02 -0700 (PDT)
Message-ID: <4F7F7E51.2010400@gmail.com>
Date: Sat, 07 Apr 2012 09:37:53 +1000
From: Bruce Blackshaw <bblackshaw@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ftpext@ietf.org
References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> <CANqTPejDknRFSGg_0Gm_24GKbiZ9-yfMBW2A9kTibAcdeh97Ag@mail.gmail.com>
In-Reply-To: <CANqTPejDknRFSGg_0Gm_24GKbiZ9-yfMBW2A9kTibAcdeh97Ag@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-hash-00.txt
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: bblackshaw@gmail.com
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 06 Apr 2012 23:38:05 -0000

Given that XCRC is quite widely implemented, it is worth considering 
adding support for CRCs so that clients and servers that implement XCRC 
could easily be modified to comply with this new command.  That would 
certainly encourage acceptance.

If this was done then SHA-1 support wouldn't be mandatory. Of course 
CRCs aren't hashes so the name of the command might need to be modified 
to CHCK or something like that.

Also, in the reply, I would prefer the order to be altered so that the 
hash comes first, and also make the other fields optional, e.g.

213 f0ad929cd259957e160ea442eb8098... [filename.txt SHA-256 0-99]


Actually 99% of the time you aren't going to care about the range, and 
as you've just requested the file by name there's probably no need to 
return the filename at all.

I would consider just returning this:

213 f0ad929cd259957e160ea442eb8098 [0-99]


where the range is only returned if RANG has been used.

regards

Bruce Blackshaw
Enterprise Distributed Technologies
http://www.enterprisedt.com

On 7/04/2012 9:02 AM, Anthony Bryan wrote:
> we've updated the HASH&  RANGe drafts.
>
> any comments?
>
> http://tools.ietf.org/html/draft-bryan-ftpext-hash
> http://tools.ietf.org/html/draft-bryan-ftp-range
>
> ---------- Forwarded message ----------
> From:<internet-drafts@ietf.org>
> Date: Fri, Apr 6, 2012 at 4:47 PM
> Subject: New Version Notification for draft-bryan-ftpext-hash-00.txt
> To: anthonybryan@gmail.com
> Cc: tim.kosse@filezilla-project.org, daniel@haxx.se
>
>
> A new version of I-D, draft-bryan-ftpext-hash-00.txt has been
> successfully submitted by Anthony Bryan and posted to the IETF
> repository.
>
> Filename:        draft-bryan-ftpext-hash
> Revision:        00
> Title:           File Transfer Protocol HASH Command for Cryptographic Hashes
> Creation date:   2012-04-06
> WG ID:           Individual Submission
> Number of pages: 16
>
> Abstract:
>    The File Transfer Protocol does not offer any method to verify the
>    integrity of a transferred file, nor can two files be compared
>    against each other without actually transferring them first.
>    Cryptographic hashes are a possible solution to this problem.  In the
>    past, several attempts have been made to add commands to obtain
>    checksums and hashes, however none have been formally specified,
>    leading to non-interoperability and confusion.  To solve these
>    issues, this document specifies a new FTP command to be used by
>    clients to request cryptographic hashes of files.
>
>
>
>
> The IETF Secretariat
>
>


-- 
---------------------------------
Want some help around the house?
http://www.helparoundthehouse.com.au