IETF Logo Mail Archive

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

Daniel Stenberg <daniel@haxx.se> Wed, 19 January 2011 10:13 UTC

Return-Path: <daniel@haxx.se>
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 56E4B3A6FC2 for <ftpext@core3.amsl.com>; Wed, 19 Jan 2011 02:13:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level:
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[AWL=-0.886, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 W-GJG3h8w9My for <ftpext@core3.amsl.com>; Wed, 19 Jan 2011 02:13:42 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id D015F3A6FB5 for <ftpext@ietf.org>; Wed, 19 Jan 2011 02:13:41 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0JAGG6m030276; Wed, 19 Jan 2011 11:16:16 +0100
Date: Wed, 19 Jan 2011 11:16:16 +0100
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Anthony Bryan <anthonybryan@gmail.com>
In-Reply-To: <AANLkTi=HwXvyPZ6UebBDA=WBOcLPzjP2qNWCReRLPUbg@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1101191112170.25160@tvnag.unkk.fr>
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>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: "ftpext@ietf.org" <ftpext@ietf.org>, Robert Oslin <rto@globalscape.com>
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 10:13:43 -0000

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

v2.23.0 | Report a Bug | By Email