Re: [ftpext] draft-bryan-ftp-range-01 - reset

Anthony Bryan <anthonybryan@gmail.com> Fri, 28 January 2011 04:51 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 EB0CC3A6BDF for <ftpext@core3.amsl.com>; Thu, 27 Jan 2011 20:51:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.637
X-Spam-Level:
X-Spam-Status: No, score=-3.637 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 TS4+oW2HhDv7 for <ftpext@core3.amsl.com>; Thu, 27 Jan 2011 20:51:45 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 031BD3A6BCB for <ftpext@ietf.org>; Thu, 27 Jan 2011 20:51:38 -0800 (PST)
Received: by ewy8 with SMTP id 8so1430033ewy.31 for <ftpext@ietf.org>; Thu, 27 Jan 2011 20:54:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=f72Xyz3i4rWZvvx3Bm/43jKZDsF8u7pE0r+dzC4H8zo=; b=kr1qShlgpiDF5CNNlrh2hTcBN4qP4PVbyJVVFjISriVBzawBFRVRJb6um9NXCtCk+e euAdZsRDQ4dDubR5uO8gmzByAQhg3d606ipHOyI3wets+m/O9WEpKWmJqihSSFUONUb1 12EZVWVknl62ikEc+ez/QCsExb1qtfOJjBY+g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Rue6NxXHu46RFHNO+kGiHK8ZcC4VJ4UoSytp8CgITaXnLFkzgIlh9APeJZ4VHBa8VH tmMZoKeMZTWrven15DKmxg1jpK31QelA1k/G23PQv0de4KIza2d0kxgbB7zbh8FuQZqs KkFt9J97unb+iM+wdTJH5X/JFXiqK42JQWPbk=
MIME-Version: 1.0
Received: by 10.213.104.143 with SMTP id p15mr4135755ebo.92.1296190483271; Thu, 27 Jan 2011 20:54:43 -0800 (PST)
Received: by 10.213.112.209 with HTTP; Thu, 27 Jan 2011 20:54:43 -0800 (PST)
In-Reply-To: <AANLkTimYAAkSX8AV1CSYwqgxXFOngafzSd1MJhhYU-bj@mail.gmail.com>
References: <AANLkTimYAAkSX8AV1CSYwqgxXFOngafzSd1MJhhYU-bj@mail.gmail.com>
Date: Thu, 27 Jan 2011 23:54:43 -0500
Message-ID: <AANLkTimKUwuy=yZaCpXFH+FQ61f_bbeSFPm0B4Sxb=5S@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-bryan-ftp-range-01 - reset
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, 28 Jan 2011 04:51:47 -0000

On Thu, Jan 27, 2011 at 7:11 AM, Tatsuhiro Tsujikawa
<tatsuhiro.t@gmail.com> wrote:
> Hi,
>
> draft-bryan-ftp-range-01 changed the way to reset the range command
> previously issued.
>
> 4.  The RANGe Command (RANG)
>
>  To reset the range command, "RANG 1 0" should be issued.  Invalid
>   RANG requests where 'start-point' is larger than 'end-point'
>   automatically reset the byte selection to the default, which is the
>   whole file.
>
> But currently, it states that server should respond with a 5yz reply
> with "RANG 1 0".
>
> 4.3.  RANG Command Errors
>   ...
>   The server-PI SHOULD reply with a 5yz reply if the specified end
>   point is larger than the actual file or the end point is before the
>   start point.
>
> I think "RANG 1 0" is a recommended way of reseting range, I think server must
> reply with 200 reply. So I propose to add following sentence to the
> above paragraph:
>
>   But the server-PI MUST reply with a 200 reply if "RANG 1 0" is issued
>   by client-PI because it is a valid way of reseting range.

yes sir, good catch. I added the text:

   The server-PI MUST reply with a 350 reply if "RANG 1 0"
   is issued by client-PI because it is a valid way of resetting range.
   (The range would also be reset if the session is reinitialized with
   REIN but this terminates the user and resets all parameters).

and also a short section

5.  RANG Command Use with Other Commands

   This specification defines the use of RANG in a certain way.  Other
   commands could decide to use RANG in a similar way, to select a byte
   range, and their specification would define how they operate with
   RANG.  The HASH command [draft-ietf-ftpext2-hash] uses RANG to select
   a byte range for partial file hashing.

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads