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

Mat Berchtold <mb@smartftp.com> Sat, 07 April 2012 03:14 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 0C44921F84FF for <ftpext@ietfa.amsl.com>; 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 <ftpext@ietfa.amsl.com>; 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 <ftpext@ietf.org>; 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 <mb@smartftp.com>
To: Sob <sob@nvnet.cz>, Anthony Bryan <anthonybryan@gmail.com>
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> <CANqTPejDknRFSGg_0Gm_24GKbiZ9-yfMBW2A9kTibAcdeh97Ag@mail.gmail.com> <36F3A30DD743D74C9BE4FF935AB5B5F30E259865@m.smartsoft.local> <CANqTPeh_FJNCT5gpnNyVTEQQKt8FUxUaDxmKJv6CHcFQb+yfUA@mail.gmail.com> <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" <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: <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: 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 [RFC3659] as currently proposed I agree with you. But I'm also okay with the mandatory start/stop points:
>hash-command = "HASH" SP start-point SP end-point SP pathname

The main concern I have is with the dependency on RANG in HASH. 

-----Original Message-----
From: Sob [mailto:sob@nvnet.cz] 
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 = "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?

--