Re: [ftpext] draft-ietf-ftpext2-hash command name and default algorithm

Robert Oslin <rto@globalscape.com> Wed, 19 January 2011 14:17 UTC

Return-Path: <rto@globalscape.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 037EC3A713D for <ftpext@core3.amsl.com>; Wed, 19 Jan 2011 06:17:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.134
X-Spam-Level:
X-Spam-Status: No, score=-2.134 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599]
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 b7BT0b9NpQUF for <ftpext@core3.amsl.com>; Wed, 19 Jan 2011 06:17:32 -0800 (PST)
Received: from webmail.globalscape.com (exchange.globalscape.com [208.89.186.61]) by core3.amsl.com (Postfix) with ESMTP id E8A193A7139 for <ftpext@ietf.org>; Wed, 19 Jan 2011 06:17:31 -0800 (PST)
Received: from exchange.forest.intranet.gs ([127.0.0.1]) by exchange ([127.0.0.1]) with mapi; Wed, 19 Jan 2011 08:20:11 -0600
From: Robert Oslin <rto@globalscape.com>
To: "ftpext@ietf.org" <ftpext@ietf.org>
Date: Wed, 19 Jan 2011 08:19:54 -0600
Thread-Topic: [ftpext] draft-ietf-ftpext2-hash command name and default algorithm
Thread-Index: Acu3weqY+pNcBnWMQ7ywBOrGhi5l+wAIdyuA
Message-ID: <F15941D3C8A2D54D92B341C20CACDF2311979DCA18@exchange>
References: <F15941D3C8A2D54D92B341C20CACDF2311976FECC9@exchange> <20110117175600.2F89028C1A2@core3.amsl.com> <F15941D3C8A2D54D92B341C20CACDF2311976FF0A8@exchange> <alpine.DEB.2.00.1101181545230.988@tvnag.unkk.fr> <F15941D3C8A2D54D92B341C20CACDF2311979DC5FE@exchange> <alpine.DEB.2.00.1101181656420.988@tvnag.unkk.fr> <F15941D3C8A2D54D92B341C20CACDF2311979DC643@exchange> <AANLkTi=HwXvyPZ6UebBDA=WBOcLPzjP2qNWCReRLPUbg@mail.gmail.com> <alpine.DEB.2.00.1101191112170.25160@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1101191112170.25160@tvnag.unkk.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ftpext] draft-ietf-ftpext2-hash command name and default algorithm
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: Wed, 19 Jan 2011 14:17:34 -0000

Correct. I meant "SHOULD" return an intermediate (213) reply for long-running...

-----Original Message-----
From: Daniel Stenberg [mailto:daniel@haxx.se] 
Sent: Wednesday, January 19, 2011 4:16 AM
To: Anthony Bryan
Cc: Robert Oslin; ftpext@ietf.org
Subject: Re: [ftpext] draft-ietf-ftpext2-hash command name and default algorithm

On Wed, 19 Jan 2011, Anthony Bryan wrote:

>> Anthony, could a provision be made such that a server MAY return a 213 
>> reply every N seconds (5, 15, other) for long running hash operations? I 
>> think that would be especially useful if SHA-256 ends up being the default 
>> recommended and implemented hash algorithm.
>
> I think we can do anything that is internally consistent within the FTP 
> universe and seems logical for the published FTP RFCs. :)

Right. I was only suggesting a "213-" response line, which isn't the final 
line of a 213 so I don't think we'd have to write anything in particular to 
allow a server to do that. It would be following standard FTP behavior.

We could of course still add something in the spec to make it more obvious 
that this might be a good idea for servers to do.

-- 

  / daniel.haxx.se