Re: [ftpext] Question about draft-bryan-ftp-hash-07

Anthony Bryan <anthonybryan@gmail.com> Sat, 21 August 2010 20:06 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 E3C993A6966 for <ftpext@core3.amsl.com>; Sat, 21 Aug 2010 13:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.299, 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 N9Lfo1cwmLG1 for <ftpext@core3.amsl.com>; Sat, 21 Aug 2010 13:06:25 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 997833A67FE for <ftpext@ietf.org>; Sat, 21 Aug 2010 13:06:25 -0700 (PDT)
Received: by iwn3 with SMTP id 3so4676325iwn.31 for <ftpext@ietf.org>; Sat, 21 Aug 2010 13:06:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=naz/zgg1KQUbhoLunmpAak+qhBtC27yJVGlN0rj+yY4=; b=HAjCGrRqUiceyLlyXIuhuFEGSsXtZF/6tglZm5w5FapCLApDVKGx6WBMJ5qkZ0gZQw T6WfpZDHowxhNbM7kXqh0beXYX+eyb13v/OfdK6+L28GPhMaaci8ZTy3fRmZ1w/ZZTt6 5KlKgF50Igp/Jo/8OzbfIQbvUjcewg2vSlOVc=
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=gaQXK/3NURV5pEW4p4PBtv+ASbQXbTihZg2xlNvcjzHj+y6Sflbg5PnkblEkOrwKco QSBaO9ITOvOfx71TWXBwdSh7sbKrsex0qyivG4rKJZsw8N5Vs8PGWx6eyZNpChDrPQTT F9ebm6AqKEaKsC9EidTppslq+xCgLNOqZraGA=
MIME-Version: 1.0
Received: by 10.231.157.212 with SMTP id c20mr3776318ibx.186.1282421216800; Sat, 21 Aug 2010 13:06:56 -0700 (PDT)
Received: by 10.231.49.199 with HTTP; Sat, 21 Aug 2010 13:06:56 -0700 (PDT)
In-Reply-To: <A5FC996C3C37DC4DA5076F1046B5674C3D2B92DA@TK5EX14MBXC127.redmond.corp.microsoft.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C3D2B58B3@TK5EX14MBXC127.redmond.corp.microsoft.com> <4C6EFFEB.4060805@filezilla-project.org> <A5FC996C3C37DC4DA5076F1046B5674C3D2B92DA@TK5EX14MBXC127.redmond.corp.microsoft.com>
Date: Sat, 21 Aug 2010 16:06:56 -0400
Message-ID: <AANLkTinbFrJn3aS6Yim72FwzNeym3_=CHiibKnWzU5+w@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Robert McMurray <robmcm@microsoft.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: "ftpext@ietf.org" <ftpext@ietf.org>
Subject: Re: [ftpext] Question about draft-bryan-ftp-hash-07
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: Sat, 21 Aug 2010 20:06:27 -0000

On Fri, Aug 20, 2010 at 6:42 PM, Robert McMurray <robmcm@microsoft.com> wrote:
>>> The server-PI SHOULD reply with a 504 reply if the HASH command is
>>> used on a file that cannot be processed for policy reasons. (For
>>> example, the file size exceeds the server's hashing policy.)
>>
>> So far 504 is used for "Command not implemented for that parameter"
>> which doesn't seem to fit too well.
>>
>> What about 554?
>
> RFC 1123 lists the 554 reply as "Requested action not taken: invalid REST parameter," so this wouldn't seem to make sense for HASH.
>
> RFC 2228 lists the 534 reply as "Request denied for policy reasons," but that has always seemed to me to be more specific as a response to the security extensions that are defined in that RFC so I hadn’t suggested it, but I'll open that for debate. ;-]

thanks, Robert. good suggestion. I've added this text while we iron
out the reply code:

Server operators might wish to allow the HASH command but restrict its
use to certain files, for example, if the file size exceeds the
server's hashing policy. A client MUST be able to understand that
refusal to process HASH commands may be permanent (if indicated by a
5yz response) and will not be honoured later.

The server-PI SHOULD reply with a 5yz reply if the HASH command is
used on a file that cannot be processed for policy reasons. (For
example, if the file size exceeds the server's hashing policy.)


suggestions?

btw, for anyone interested I believe I have all reply codes listed in
http://www.metalinker.org/test/ftp/draft-bryan-ftpbis-00.html#sec-4.2.3

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