From iesg-secretary@ietf.org Tue Apr 3 15:24:02 2012 Return-Path: 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 596AF11E80C7; Tue, 3 Apr 2012 15:24:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 Cnc9Gs6j3zSp; Tue, 3 Apr 2012 15:24:02 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F109811E8074; Tue, 3 Apr 2012 15:24:01 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: IESG Secretary To: IETF Announcement List X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120403222401.11218.62366.idtracker@ietfa.amsl.com> Date: Tue, 03 Apr 2012 15:24:01 -0700 Cc: ftpext@ietf.org Subject: [ftpext] WG Action: Conclusion of FTP Extensions, 2nd edition (ftpext2) X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2012 22:24:02 -0000 The FTP Extensions, 2nd edition (ftpext2) in the Applications Area has conc= luded. The IESG contact person is Pete Resnick. The mailing list will remain active. From anthonybryan@gmail.com Fri Apr 6 16:02:18 2012 Return-Path: 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 137B011E80AB for ; Fri, 6 Apr 2012 16:02:18 -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 p69Ek5HHpWAn for ; Fri, 6 Apr 2012 16:02:14 -0700 (PDT) Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 858CB11E80A0 for ; Fri, 6 Apr 2012 16:02:14 -0700 (PDT) Received: by ggmi1 with SMTP id i1so1564096ggm.31 for ; Fri, 06 Apr 2012 16:02:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=JOAQjTF21J4kkBskUxUD4+3MQPPuW1xN3oR9qI40sxs=; b=KD+s8CKHBBKs6Izsz+xSM8Q3FoUFxcggh4jui9ZiaykFQp5obdmMXwiG+7TZrDswq8 Vf3tKTngDnz93I1gMRig+0AmcUuBAAQcyJT+aqAWvWCUURYoTTrDPbMSM1seJlTPwWOo zrSqStGldLNv5SFWs5ba8Zh9sqg4SI9bnoJ4aEY+hEzctdX5dLwgODMmYIeffrNP03hK MLcfKu7OXR1GxhqYbcVZ6IA0Nc4bkhKV1g/Uxmr+QqeiUZ8em11JlxblLhO/Mac7rDsO 7SXO0UuD+yQqRs2DkvLQEPmgvg92kJx2ZhSnigA2fnJwaZeZnGGl5OG4BG9LCE2CWHyB O13A== MIME-Version: 1.0 Received: by 10.236.175.164 with SMTP id z24mr8341836yhl.101.1333753334094; Fri, 06 Apr 2012 16:02:14 -0700 (PDT) Received: by 10.146.95.15 with HTTP; Fri, 6 Apr 2012 16:02:14 -0700 (PDT) In-Reply-To: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> Date: Fri, 6 Apr 2012 19:02:14 -0400 Message-ID: From: Anthony Bryan To: ftpext@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2012 23:02:18 -0000 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: 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: =A0 =A0 =A0 =A0draft-bryan-ftpext-hash Revision: =A0 =A0 =A0 =A000 Title: =A0 =A0 =A0 =A0 =A0 File Transfer Protocol HASH Command for Cryptogr= aphic Hashes Creation date: =A0 2012-04-06 WG ID: =A0 =A0 =A0 =A0 =A0 Individual Submission Number of pages: 16 Abstract: =A0 The File Transfer Protocol does not offer any method to verify the =A0 integrity of a transferred file, nor can two files be compared =A0 against each other without actually transferring them first. =A0 Cryptographic hashes are a possible solution to this problem. =A0In the =A0 past, several attempts have been made to add commands to obtain =A0 checksums and hashes, however none have been formally specified, =A0 leading to non-interoperability and confusion. =A0To solve these =A0 issues, this document specifies a new FTP command to be used by =A0 clients to request cryptographic hashes of files. The IETF Secretariat --=20 (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From mb@smartftp.com Fri Apr 6 16:35:29 2012 Return-Path: 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 ; 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 ; 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 ; 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 To: "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> In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 partia= l hashes specification. How does the client know if partial hashes are supported without trial&erro= r?=20 Let's assume the following: 1. Server supports partial transfers (draft-bryan-ftp-range) and announces = it in the FEAT as: RANG STREAM.=20 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 HAS= H) 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: 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: =A0 =A0 =A0 =A0draft-bryan-ftpext-hash Revision: =A0 =A0 =A0 =A000 Title: =A0 =A0 =A0 =A0 =A0 File Transfer Protocol HASH Command for Cryptogr= aphic Hashes Creation date: =A0 2012-04-06 WG ID: =A0 =A0 =A0 =A0 =A0 Indiv= idual Submission Number of pages: 16 Abstract: =A0 The File Transfer Protocol does not offer any method to verify the =A0 integrity of a transferred file, nor can two files be compared =A0 against each other without actually transferring them first. =A0 Cryptographic hashes are a possible solution to this problem. =A0In the =A0 past, several attempts have been made to add commands to obtain =A0 checksums and hashes, however none have been formally specified, =A0 leading to non-interoperability and confusion. =A0To solve these =A0 issues, this document specifies a new FTP command to be used by =A0 clients to request cryptographic hashes of files. The IETF Secretariat -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads ______________________= _________________________ ftpext mailing list ftpext@ietf.org https://www.ietf.org/mailman/listinfo/ftpext From bblackshaw@gmail.com Fri Apr 6 16:38:05 2012 Return-Path: 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 ; 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 ; 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 ; Fri, 6 Apr 2012 16:38:04 -0700 (PDT) Received: by dady13 with SMTP id y13so4436807dad.27 for ; 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 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> In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: > 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 From anthonybryan@gmail.com Fri Apr 6 17:35:44 2012 Return-Path: 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 51F2D21F8587 for ; Fri, 6 Apr 2012 17:35:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.299 X-Spam-Level: X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, 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 1GPgJw28OFUK for ; Fri, 6 Apr 2012 17:35:43 -0700 (PDT) Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE2211E8085 for ; Fri, 6 Apr 2012 17:35:43 -0700 (PDT) Received: by yhkk25 with SMTP id k25so1565168yhk.31 for ; Fri, 06 Apr 2012 17:35:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=7vp3D+movQCvdo2Fu8712pa2XqkK/OoS4MYVKjSYWsA=; b=EI8L+8/HRWbaQyCmR3zHs7WcFkvlWMIyKo5tmGnlaMBKVeGn+N6F+AZqsb+M46mYAp b0CYVn+FOlIhwvlv+HrEitFwwtBBgWaPfRlKzIUlb1i0rRFyYUvxVwcL/rzT05lOYxK5 OonVp9XHRNfVpFYNi1L/Ok6OeQhS7bYitihiOXnxytmLx5iRBUH9DpS5aEtqOOc64CzW ZIa+WiV5pPY4OgnxkLGDmEHzYEZzD11u3kE9OL8WRPgfkpblj0kpKmOWsclCSMYHh9vy GPTly0pnKVMgNG+fUfbUo35HGo+LDFAn3R66p3JpNT7SHxa/HrS6qPyJ8i/Q1GCIDaIC VSmw== MIME-Version: 1.0 Received: by 10.236.184.202 with SMTP id s50mr8361495yhm.84.1333758943202; Fri, 06 Apr 2012 17:35:43 -0700 (PDT) Received: by 10.146.95.15 with HTTP; Fri, 6 Apr 2012 17:35:43 -0700 (PDT) In-Reply-To: <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> Date: Fri, 6 Apr 2012 20:35:43 -0400 Message-ID: From: Anthony Bryan To: Mat Berchtold Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "ftpext@ietf.org" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2012 00:35:44 -0000 On Fri, Apr 6, 2012 at 7:35 PM, Mat Berchtold wrote: >>draft-bryan-ftpext-hash >>3.3. =A0Partial File Hashes with RANG > I have some concerns or better a lack of understanding regarding the part= ial hashes specification. > > How does the client know if partial hashes are supported without trial&er= ror? > Let's assume the following: > 1. Server supports partial transfers (draft-bryan-ftp-range) and announce= s 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 H= ASH) are supported as well? my quick Friday night answer, we should announce partial hashes in HASH's F= EAT and maybe a specific error code for when partial hashes aren't supported? any suggestions? from RFC 959: 503 Bad sequence of commands. 504 Command not implemented for that parameter. "A refinement of that is the 504 reply for a command that is implemented, but that requests an unimplemented parameter." --=20 (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From mb@smartftp.com Fri Apr 6 18:10:12 2012 Return-Path: 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 7C88911E8086 for ; Fri, 6 Apr 2012 18:10:12 -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 QudYjoVoqmr2 for ; Fri, 6 Apr 2012 18:10:11 -0700 (PDT) Received: from mail.smartftp.com (mail.smartftp.com [75.126.59.172]) by ietfa.amsl.com (Postfix) with ESMTP id C905911E8074 for ; Fri, 6 Apr 2012 18:10:11 -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 18:10:15 -0700 From: Mat Berchtold To: Anthony Bryan Thread-Topic: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-hash-00.txt Thread-Index: AQHNFFZg8N/9bftxY0ett47c6YlCdJaOhFrw Date: Sat, 7 Apr 2012 01:10:14 +0000 Message-ID: <36F3A30DD743D74C9BE4FF935AB5B5F30E2599A5@m.smartsoft.local> References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> In-Reply-To: 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 Cc: "ftpext@ietf.org" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2012 01:10:12 -0000 >any suggestions? In my opinion the dependency on RANG for partial hashes adds unnecessary co= mplexity and hinders adoption. The range can be passed directly to the comm= and as optional arguments: hash-command =3D "HASH" SP pathname [ SP start-point [ SP end-point ] ] start-point =3D 1*DIGIT end-point =3D 1*DIGIT I would like to see support for partial hashes as mandatory (MUST) for HASH= . This way no special announcement in FEAT is required. If the server canno= t calculate the hash over a range it still can return an error like 504. Th= e important part is that the server won't return the hash value for the ful= l range if a range is specified. -----Original Message----- From: Anthony Bryan [mailto:anthonybryan@gmail.com]=20 Sent: Saturday, 07 April, 2012 02:36 To: Mat Berchtold Cc: ftpext@ietf.org Subject: Re: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-= hash-00.txt On Fri, Apr 6, 2012 at 7:35 PM, Mat Berchtold wrote: >>draft-bryan-ftpext-hash >>3.3. =A0Partial File Hashes with RANG > I have some concerns or better a lack of understanding regarding the part= ial hashes specification. > > How does the client know if partial hashes are supported without trial&er= ror? > Let's assume the following: > 1. Server supports partial transfers (draft-bryan-ftp-range) and announce= s it in the FEAT as: RANG STREAM. > 2. Server announces the HASH command in the FEAT reply as HASH=20 > SHA-256* > > Does this now automatically imply that partial hashes (RANG followed by H= ASH) are supported as well? my quick Friday night answer, we should announce partial hashes in HASH's F= EAT and maybe a specific error code for when partial hashes aren't supporte= d? any suggestions? from RFC 959: 503 Bad sequence of commands. 504 Command not implemented for that parameter. "A refinement of that is the 504 reply for a command that is implemented, b= ut that requests an unimplemented parameter." -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From sob@nvnet.cz Fri Apr 6 19:34:35 2012 Return-Path: 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 527E521F857D for ; Fri, 6 Apr 2012 19:34:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.603 X-Spam-Level: X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_CZ=0.445, RDNS_NONE=0.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 QTXcelcERqJR for ; Fri, 6 Apr 2012 19:34:34 -0700 (PDT) Received: from mail.nvnet.cz (mail.nvnet.cz [IPv6:2002:d5d3:2ff6:80::3]) by ietfa.amsl.com (Postfix) with ESMTP id 05B5421F8559 for ; Fri, 6 Apr 2012 19:34:33 -0700 (PDT) X-AuthUser: sob@nvnet.cz Received: from Sob-PC.nvnet.cz ([213.211.47.246]:60807) by mail.nvnet.cz with [XMail 1.25 ESMTP Server] id for from ; Sat, 7 Apr 2012 04:34:04 +0200 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sat, 07 Apr 2012 04:32:47 +0200 To: Mat Berchtold ,Anthony Bryan From: Sob In-Reply-To: <36F3A30DD743D74C9BE4FF935AB5B5F30E2599A5@m.smartsoft.local > References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> <36F3A30DD743D74C9BE4FF935AB5B5F30E2599A5@m.smartsoft.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-Id: <20120407023434.05B5421F8559@ietfa.amsl.com> Cc: "ftpext@ietf.org" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2012 02:34:35 -0000 At 03:10 7.4.2012, Mat Berchtold wrote: >The range can be passed directly to the command as optional arguments: >hash-command = "HASH" SP pathname [ SP start-point [ SP end-point ] ] It can't, at least not like this, simply because if the server gets, e.g.: HASH somepath 10 20 .. it can mean any of the following and it's impossible to tell which one: a) pathname = "somepath", start-point = 10, end-point = 20 b) pathname = "somepath 10", start-point = 20 c) pathname = "somepath 10 20" It would work with reversed order, with mandatory start and end points before pathname, but if RANG catches up (and it should, because it has big potential), wouldn't it be a little weird to have separate way for using ranges with HASH? -- From mb@smartftp.com Fri Apr 6 20:14:18 2012 Return-Path: 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 0C44921F84FF for ; Fri, 6 Apr 2012 20:14:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599] 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 bEDWBjPdOs2C for ; Fri, 6 Apr 2012 20:14:17 -0700 (PDT) Received: from mail.smartftp.com (mail.smartftp.com [75.126.59.172]) by ietfa.amsl.com (Postfix) with ESMTP id 874C221F84FB for ; Fri, 6 Apr 2012 20:14:17 -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 20:14:17 -0700 From: Mat Berchtold To: Sob , Anthony Bryan Thread-Topic: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-hash-00.txt Thread-Index: AQHNFGbsqJtXCOP+r0a9i3jOxsJ6xZaOpSkw Date: Sat, 7 Apr 2012 03:14:16 +0000 Message-ID: <36F3A30DD743D74C9BE4FF935AB5B5F30E259B08@m.smartsoft.local> References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> <36F3A30DD743D74C9BE4FF935AB5B5F30E2599A5@m.smartsoft.local> <3a874f0f-d9c2-4bc7-b80b-62f40ea0c4ac@M.smartsoft.local> In-Reply-To: <3a874f0f-d9c2-4bc7-b80b-62f40ea0c4ac@M.smartsoft.local> 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "ftpext@ietf.org" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2012 03:14:18 -0000 > It can't, at least not like this, simply because if the server gets, e.g.= : It depends how pathname is defined. If it's imported from Section 2.2 of [R= FC3659] as currently proposed I agree with you. But I'm also okay with the = mandatory start/stop points: >hash-command =3D "HASH" SP start-point SP end-point SP pathname The main concern I have is with the dependency on RANG in HASH.=20 -----Original Message----- From: Sob [mailto:sob@nvnet.cz]=20 Sent: Saturday, 07 April, 2012 04:33 To: Mat Berchtold; Anthony Bryan Cc: ftpext@ietf.org Subject: Re: [ftpext] Fwd: New Version Notification for draft-bryan-ftpext-= hash-00.txt At 03:10 7.4.2012, Mat Berchtold wrote: >The range can be passed directly to the command as optional arguments: >hash-command =3D "HASH" SP pathname [ SP start-point [ SP end-point ] ] It can't, at least not like this, simply because if the server gets, e.g.: HASH somepath 10 20 .. it can mean any of the following and it's impossible to tell which one: a) pathname =3D "somepath", start-point =3D 10, end-point =3D 20 b) pathname =3D "somepath 10", start-point =3D 20 c) pathname =3D "somepath 10 20" It would work with reversed order, with mandatory start and end points befo= re pathname, but if RANG catches up (and it should, because it has big pote= ntial), wouldn't it be a little weird to have separate way for using ranges= with HASH? --=20 From tim.kosse@filezilla-project.org Sun Apr 8 09:54:12 2012 Return-Path: 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 0088B21F851D for ; Sun, 8 Apr 2012 09:54:12 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ... [score: 0.0000]\n \n autolearn: ha[...] X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 CAtdZbGPK4ch for ; Sun, 8 Apr 2012 09:54:11 -0700 (PDT) Received: from filezilla-project.org (filezilla-project.org [IPv6:2a01:4f8:61:61a3::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6607A21F8525 for ; Sun, 8 Apr 2012 09:54:11 -0700 (PDT) Received: from p5dd92871.dip.t-dialin.net ([93.217.40.113] helo=[10.0.0.103]) by filezilla-project.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1SGvNP-00043T-Ck; Sun, 08 Apr 2012 18:54:08 +0200 Message-ID: <4F81C2A4.8000401@filezilla-project.org> Date: Sun, 08 Apr 2012 18:53:56 +0200 From: Tim Kosse User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Mat Berchtold References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> <36F3A30DD743D74C9BE4FF935AB5B5F30E2599A5@m.smartsoft.local> <3a874f0f-d9c2-4bc7-b80b-62f40ea0c4ac@M.smartsoft.local> <36F3A30DD743D74C9BE4FF935AB5B5F30E259B08@m.smartsoft.local> In-Reply-To: <36F3A30DD743D74C9BE4FF935AB5B5F30E259B08@m.smartsoft.local> X-Enigmail-Version: 1.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig206380E92209CF7C240FDA47" Cc: "ftpext@ietf.org" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2012 16:54:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig206380E92209CF7C240FDA47 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2012-04-07 05:14, Mat Berchtold wrote: > But I'm also okay with the mandatory start/stop points: > hash-command =3D "HASH" SP start-point SP end-point SP pathname Then we need a special designator to indicate that the whole file should be hashed if its size is unknown, e.g. both start-point and end-point set to 0. Regards, Tim Kosse --------------enig206380E92209CF7C240FDA47 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+BwqkACgkQ8N9+lcqiUkVOEQCbB73BSbhtneMn2oFAzzOqKw1o TsUAn2z8OvcwttSzefVaOglDGLY9l3JP =kULx -----END PGP SIGNATURE----- --------------enig206380E92209CF7C240FDA47-- From tj@castaglia.org Mon Apr 9 12:03:09 2012 Return-Path: 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 43F1421F87C4 for ; Mon, 9 Apr 2012 12:03:09 -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 Q6mdpRuqi7L4 for ; Mon, 9 Apr 2012 12:03:08 -0700 (PDT) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 97EBD21F87AE for ; Mon, 9 Apr 2012 12:03:08 -0700 (PDT) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C06D32129C for ; Mon, 9 Apr 2012 15:03:07 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 09 Apr 2012 15:03:07 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=castaglia.org; h= date:from:to:cc:subject:in-reply-to:message-id:references :mime-version:content-type; s=mesmtp; bh=OK6zPVugoNhe3F7y2yn6mZr o7EU=; b=nDVPBbhnMwqHW2qY/PbMC6a3CbQn8kb5FLxUPL78QMaCgjYM19l9g0v G3bPUDOh5JPx8c/kWFYs/vUvlQqYYhtOGydvB6DVy3N2r8pvxKt/AVktmGGDNVQU lxHmNDSDVHkrx4XaYkoFef2WZ4o8hv0SL8lH30R+WxWPTEAEr9EA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:in-reply-to :message-id:references:mime-version:content-type; s=smtpout; bh= OK6zPVugoNhe3F7y2yn6mZro7EU=; b=hcJcuIpI3XNfyHgz5/qC3gp+KeUyz+eu q+UZI6eBrYiYyQPTUZKv+Z4PZVkATOMqFnAOzmmOMv9nwJ2rLXqARMbhHqbBdUxE 1U1naikM0llZ35OA1FEu03nxT0ifUFakCcZZw19jQQ1dhkV1Gymk+YFz2iRNrE6U uTUGnzo8VZc= X-Sasl-enc: oLLB//wxWQ8fvqcxW0Ax/iyCYAPzQXFHvBqKLe1f7X0q 1333998187 Received: from familiar.local (64-71-23-251.static.wiline.com [64.71.23.251]) by mail.messagingengine.com (Postfix) with ESMTPSA id 328388E00AE; Mon, 9 Apr 2012 15:03:07 -0400 (EDT) Date: Mon, 9 Apr 2012 12:03:05 -0700 (PDT) From: TJ Saunders To: Tim Kosse In-Reply-To: <4F81C2A4.8000401@filezilla-project.org> Message-ID: References: <20120406204700.15838.17811.idtracker@ietfa.amsl.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> <36F3A30DD743D74C9BE4FF935AB5B5F30E2599A5@m.smartsoft.local> <3a874f0f-d9c2-4bc7-b80b-62f40ea0c4ac@M.smartsoft.local> <36F3A30DD743D74C9BE4FF935AB5B5F30E259B08@m.smartsoft.local> <4F81C2A4.8000401@filezilla-project.org> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "ftpext@ietf.org" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 19:03:09 -0000 > Then we need a special designator to indicate that the whole file should > be hashed if its size is unknown, e.g. both start-point and end-point > set to 0. I think that using 0 (zero) for both start and end offsets to indicate the entire file is acceptable, even encouragable: it is similar to the fcntl(2) locking API on Unix. TJ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I wanted only to try to live in accord with the promptings which came from my true self. Why was that so very difficult? -Herman Hesse ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~