[ftpext] draft-bryan-ftp-hash
Anthony Bryan <anthonybryan@gmail.com> Fri, 11 June 2010 16:24 UTC
Return-Path: <anthonybryan@gmail.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 41B4A3A68DA for <ftpext@core3.amsl.com>; Fri, 11 Jun 2010 09:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 L0RLH-tscbFQ for <ftpext@core3.amsl.com>; Fri, 11 Jun 2010 09:24:10 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 424323A6933 for <ftpext@ietf.org>; Fri, 11 Jun 2010 09:24:07 -0700 (PDT)
Received: by iwn42 with SMTP id 42so1336574iwn.31 for <ftpext@ietf.org>; Fri, 11 Jun 2010 09:24:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=pvj5kg6LOLs4sFYg340h7FBOX27WC+1SRi3OSBtUAQo=; b=gnvFAYf3vMtoMayx1rvVhpFnQFwVTZFCvH5WKc4Eddd3yPpHv/JHdswh+W6FIPF2ge JcB1smWq4x9eTu7Grvohq9Akb3IchlTgxokDL1viuXmHu/1r8Kr5HTw4qt0uF5+utR5a H2trmXimXqO16WdQxmIOSPNV6oq2t+V9J+d1w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=UNqCEekcu2I8/fs4vRcDJ+n5ozBMa9/8+UYVf+ZJlJqeALiqR7GKEGezTUr1R2uHfh fkh9n1p/vtj1SC0jTsxDbo2zSOBeF6/DBCX7MmRvZX2LZrtmISiJVI9mV/madpdkQQpo uBU3u2UCjBpwAooJ5F5nGmJBZlq0A1n0ipQjk=
MIME-Version: 1.0
Received: by 10.231.140.69 with SMTP id h5mr2119788ibu.153.1276273446515; Fri, 11 Jun 2010 09:24:06 -0700 (PDT)
Received: by 10.231.152.65 with HTTP; Fri, 11 Jun 2010 09:24:06 -0700 (PDT)
Date: Fri, 11 Jun 2010 12:24:06 -0400
Message-ID: <AANLkTim5h4H1gg4tD8J4DVq3QTNvpJIBiD-FEtE0BHX4@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [ftpext] draft-bryan-ftp-hash
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: Fri, 11 Jun 2010 16:24:12 -0000
It's nice to see this new list for FTP extension discussion! We're working on an FTP HASH command: The File Transfer Protocol [RFC0959] 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. HTTP has a similar feature named Instance Digests [RFC3230] which allows a client to request the cryptographic hash of a file. We have a couple issues we'd like to discuss: Should HASH support partial file hashes, similar to the Content-MD5 HTTP Header? (Some of the non-standard hash commands allow this). Should the server response include the algorithm? i.e. "S> 213 SHA-256 xxxxxxxxxxxxxxx" -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] )) Easier, More Reliable, Self Healing Downloads
- [ftpext] draft-bryan-ftp-hash Anthony Bryan