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

Mat Berchtold <mb@smartftp.com> Fri, 06 April 2012 23:35 UTC

Return-Path: <mb@smartftp.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 1A71711E80AB for <ftpext@ietfa.amsl.com>; Fri, 6 Apr 2012 16:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_55=0.6]
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 u6BWMRQndoE7 for <ftpext@ietfa.amsl.com>; Fri, 6 Apr 2012 16:35:28 -0700 (PDT)
Received: from mail.smartftp.com (mail.smartftp.com [75.126.59.172]) by ietfa.amsl.com (Postfix) with ESMTP id 31A6411E80AA for <ftpext@ietf.org>; Fri, 6 Apr 2012 16:35:28 -0700 (PDT)
Received: from M.smartsoft.local ([fe80::fd57:1201:8518:71bc]) by m.smartsoft.local ([fe80::fd57:1201:8518:71bc%12]) with mapi id 14.02.0283.003; Fri, 6 Apr 2012 16:35:31 -0700
From: Mat Berchtold <mb@smartftp.com>
To: "ftpext@ietf.org" <ftpext@ietf.org>
Thread-Topic: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-hash-00.txt
Thread-Index: AQHNFElcwlphNKYTVUeQ+MH8gB0mKpaOcKAw
Date: Fri, 6 Apr 2012 23:35:29 +0000
Message-ID: <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local>
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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.16.0.202]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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
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:35:29 -0000

>draft-bryan-ftpext-hash
>3.3.  Partial File Hashes with RANG
I have some concerns or better a lack of understanding regarding the partial hashes specification.

How does the client know if partial hashes are supported without trial&error? 
Let's assume the following:
1. Server supports partial transfers (draft-bryan-ftp-range) and announces it in the FEAT as: RANG STREAM. 
2. Server announces the HASH command in the FEAT reply as HASH SHA-256*

Does this now automatically imply that partial hashes (RANG followed by HASH) are supported as well?


-----Original Message-----
From: ftpext-bounces@ietf.org [mailto:ftpext-bounces@ietf.org] On Behalf Of Anthony Bryan
Sent: Saturday, 07 April, 2012 01:02
To: ftpext@ietf.org
Subject: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-hash-00.txt

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


--
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads _______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext