Re: [ftpext] End byte of transfer in FTP

John C Klensin <john-ietf@jck.com> Mon, 06 December 2010 14:56 UTC

Return-Path: <john-ietf@jck.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 DB17A3A67FF for <ftpext@core3.amsl.com>; Mon, 6 Dec 2010 06:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level:
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 h2CsLVW6iBE8 for <ftpext@core3.amsl.com>; Mon, 6 Dec 2010 06:56:36 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id ECC513A67B4 for <ftpext@ietf.org>; Mon, 6 Dec 2010 06:56:35 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PPcVk-0008pW-Jp; Mon, 06 Dec 2010 09:57:52 -0500
Date: Mon, 06 Dec 2010 09:57:51 -0500
From: John C Klensin <john-ietf@jck.com>
To: Daniel Stenberg <daniel@haxx.se>, Anthony Bryan <anthonybryan@gmail.com>
Message-ID: <A6BF1C5A1E1A999D1A7D33E3@PST.JCK.COM>
In-Reply-To: <alpine.DEB.2.00.1012060855010.19637@tvnag.unkk.fr>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr> <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com> <alpine.DEB.2.00.1012060855010.19637@tvnag.unkk.fr>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ftpext@ietf.org
Subject: Re: [ftpext] End byte of transfer in FTP
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: Mon, 06 Dec 2010 14:56:36 -0000

--On Monday, December 06, 2010 08:55 +0100 Daniel Stenberg
<daniel@haxx.se> wrote:

> On Sat, 4 Dec 2010, Anthony Bryan wrote:
> 
>> would it be possible to modify REST so that if the FEAT reply
>> included  RANGE:
> 
> I don't see much point in that. I'd rather see a new range
> function or possibly one that sets the end point in the same
> style REST sets the start point.

Yes.  I'm still not convinced trying to specify fragments of
stream files is a good idea at all but, if it is to be done,
let's do it with a new command and very clearly-specified
semantics.  Remember that, if transfers are done in TYPE I, 

	-- not only can one have any of the usual
	line-separation characters, but one can have other sorts
	of record markers or length-delimited lines or blocks.
	
	-- if Unicode is being sent consistent with the base
	spec), one gets internal storage forms (often UTF-16LE
	or UTF-16BE) not only UTF-8, and certainly does not get
	one octet per character.

So specifying fragments clearly is not a trivial piece of work
unless the new command also requires a new file STRUcture
variation.

      john