draft-bryan-ftp-hash-00 -- items for discussion
Alfred Hönes <ah@TR-Sys.de> Thu, 01 April 2010 19:54 UTC
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA9073A6A4C for <apps-discuss@core3.amsl.com>; Thu, 1 Apr 2010 12:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.818
X-Spam-Level:
X-Spam-Status: No, score=-94.818 tagged_above=-999 required=5 tests=[AWL=0.942, BAYES_20=-0.74, CHARSET_FARAWAY_HEADER=3.2, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, 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 i0cT6Bjd0BEx for <apps-discuss@core3.amsl.com>; Thu, 1 Apr 2010 12:54:26 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id C5CAB3A6A22 for <apps-discuss@ietf.org>; Thu, 1 Apr 2010 12:54:25 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA106811668; Thu, 1 Apr 2010 21:54:28 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id VAA28916; Thu, 1 Apr 2010 21:54:26 +0200 (MESZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <201004011954.VAA28916@TR-Sys.de>
Subject: draft-bryan-ftp-hash-00 -- items for discussion
To: apps-discuss@ietf.org
Date: Thu, 01 Apr 2010 21:54:26 +0200
In-Reply-To:
References: <201003231642.RAA04676@TR-Sys.de>
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 8bit
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Apr 2010 19:54:28 -0000
I have been asked to respin on apps-discuss a summary of concerns raised in the pre-draft stage for draft-bryan-ftp-hash-00 and communicated to the authors after draft submisison. Here we go ... -------- forwarded content of message to the authors ------- It looks like the concerns raised so far have not been adressed. [ Thus, the first part of Appendix C, which pretends "no known issues", sounds ironical. :-) ] In particular: a) untypical use of a command with a file path argument *and* another argument -- consider using: OPTS HASH <hash> HASH <filepath> b) underspecification of the representation of the file that shall undergo the hash calculation; a canonical form of the file is essential here for interoperability; I already have discussed some of the options that came to my mind: using the current transfer mode settings, defining a specific overriding set of mode settings, or requiring a single specific set of mode settings to be active (or a small choice of such). I cannot imagine how verification would be possible without a well defined canonical file representation in a heterogenous systems environment where e.g. one system uses record-oriented file storage and another one uses byte-stream storage with either <NL> or <CRLF> convention, one system pads records with blanks to an alignment boundary and another system truncates trailing blanks on file lines, ... (all that behavior exists in my office!) Further, I'd like to draw your attention to RFC 5797 and the FTP Commands and Extensions IANA Registry it has established now, at <http://www.IANA.ORG/assignments/ftp-commands-extensions/ ftp-commands-extensions.xhtml> ). So you might wish to amend your proposal with substantial IANA considerations for the registration of the proposed extension and the associated FEAT strings. Also, it might make sense to give reference to prior work; I'm aware of an old expired I-D, draft-twine-ftpmd5-00, May 2002. Typos: - Abstract: s/intergrity/integrity/ - Sect.1: s/from a FTP server/from an FTP server/ Kind regards, Alfred Hönes. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+
- draft-bryan-ftp-hash-00 -- items for discussion Alfred Hönes
- Re: draft-bryan-ftp-hash-00 -- items for discussi… Anthony Bryan
- Re: draft-bryan-ftp-hash-00 -- items for discussi… Tim Kosse
- Re: draft-bryan-ftp-hash-00 -- items for discussi… Daniel Stenberg
- Re: draft-bryan-ftp-hash-00 -- items for discussi… Tim Kosse
- Re: draft-bryan-ftp-hash-00 -- items for discussi… Daniel Stenberg
- Re: draft-bryan-ftp-hash-00 -- items for discussi… Anthony Bryan