
From wwwrun@core3.amsl.com  Mon Nov  1 14:04:52 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ftpext@ietf.org
Delivered-To: ftpext@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id C214A3A6A76; Mon,  1 Nov 2010 14:04:52 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20101101210452.C214A3A6A76@core3.amsl.com>
Date: Mon,  1 Nov 2010 14:04:52 -0700 (PDT)
Cc: ftpext@ietf.org
Subject: [ftpext] WG Review: FTP Extensions, 2nd edition (ftpext2)
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
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, 01 Nov 2010 21:04:52 -0000

A new IETF working group has been proposed in the Applications Area.  The
IESG has not made any determination as yet. The following draft charter
was submitted, and is provided for informational purposes only. Please
send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,
November 9, 2010                           

FTP Extensions, 2nd edition (ftpext2)
------------------------------------------
Current Status: Proposed Working Group 
Last updated: 2010-10-28

Chair(s): 
 TBD

Applications Area Directors:
  Alexey Melnikov <alexey.melnikov@isode.com>
  Peter Saint-Andre <stpeter@stpeter.im>

Applications Area Advisor:
  Alexey Melnikov <alexey.melnikov@isode.com>

Mailing Lists:
 General Discussion: ftpext@ietf.org
 To subscribe: https://www.ietf.org/mailman/listinfo/ftpext
 Archive: http://www.ietf.org/mail-archive/web/ftpext/

Description of Working Group:

The Standard File Transfer Protocol specification in RFC 959
has been updated several times with command extensions of one
sort or another, including those based on the extension
mechanism of RFC 2389 (a complete list appears in RFC 5797 and
the corresponding IANA registry at
http://www.iana.org/assignments/ftp-commands-extensions).

The following are active FTP related drafts:

  draft-bryan-ftp-hash
  draft-hethmon-mcmurray-ftp-hosts
  FTP extensions to support IPv4/IPv6 translation scenario
  draft-klensin-ftp-typeu-00 - FTP Extension for Internationalized Text

The Working Group will:
* Review and finalize drafts listed above.
* Review and confirm or reject errata of current FTP RFCs.
* Investigate the differences between FTP in theory
 (current RFCs) and practice, and recommend future work to align them.
 Any future work would require rechartering of the WG.

The Working Group's specification deliverables are:
* A document that specifies the HOST command (Proposed Standard).
* A document that specifies the HASH command (Proposed Standard).
* A document that specifies FTP extensions to support IPv4/IPv6
translation scenario.
* A document that specifies FTP extensions for Internationalized Text.

The Working Group must not introduce a new version of FTP, e.g.
an incompatible FTP 2.0.

Goals and Milestones:
Nov 2010  Submit 'File Transfer Protocol HOST Command for Virtual
         Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts 
         will be used as a starting point)
Nov 2010  Submit 'File Transfer Protocol HASH Command for
         Cryptographic Hashes' as working group item (draft-bryan-ftp-
         hash will be used as a starting point)
Nov 2010  Submit 'FTP extensions to support IPv4/IPv6 translation'
         as working group item (draft-liu-ftp64-extension will be used 
         as a starting point)
Dec 2010  Working group Last Call of HOST document
Jan 2011  Submit 'File Transfer Protocol HOST Command for Virtual
         Hosts' to the IESG for consideration as a Proposed Standard
Jan 2011  Working group Last Call of HASH document
Feb 2011  Submit 'File Transfer Protocol HASH Command for
         Cryptographic Hashes' to the IESG for consideration as a 
         Proposed Standard
Mar 2011  Working group Last Call of 'FTP extensions to support
         IPv4/IPv6 translation' document
Apr 2011  Submit 'FTP Extension for Internationalized Text'
         as working group item
May 2011  Submit 'FTP extensions to support IPv4/IPv6 translation'
         to the IESG for consideration as Proposed Standard
Jul 2011  Working group Last Call of 'FTP Extension for 
         Internationalized Text'
Aug 2011  Submit 'FTP Extension for Internationalized Text'
         to the IESG for consideration as Proposed Standard
Sep 2011  Close or recharter

From anthonybryan@gmail.com  Wed Nov  3 17:28:33 2010
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 BB64728C0DD for <ftpext@core3.amsl.com>; Wed,  3 Nov 2010 17:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 08Pj4RXi2CjW for <ftpext@core3.amsl.com>; Wed,  3 Nov 2010 17:28:32 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 394B128C0CF for <ftpext@ietf.org>; Wed,  3 Nov 2010 17:28:32 -0700 (PDT)
Received: by eyd10 with SMTP id 10so755670eyd.31 for <ftpext@ietf.org>; Wed, 03 Nov 2010 17:28:40 -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=OY4g0xZ/cLo67ZxH70YH7KMffojDcJYbBGbgrvf00p4=; b=X9Xa4RtIVQ3isbBbqzoYFxCTp0Pd9KzawhbuJUle6wE4eB5Z2MhgwRh4LRRUiIstq4 ZmAhuDRVI8w0Zosd3cZ2EvS59BpEFc73e3LNkNnx9G9CUkzigkUPmBwQC+p9K/D8x3VC Ul9mhWtZyL+3lo6QnMw0oPIS0LWEQxzB9Ti+A=
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=cnTehcBRepuVH2bXRR8w/kkZXbGfzL6LphWoJEv5ZnyAro+Iq9ypWRS1gswzFemuBt IbMUxWm6yNNWbgxA5YshHDTz5e65PTvfAuW+GuPrt2qLPqZlkoFpXrw9H90phgyGprp8 DbulxthwT6/W1tMm9LvTefgzmwrU3ptctBvyQ=
MIME-Version: 1.0
Received: by 10.213.23.15 with SMTP id p15mr40248ebb.63.1288830519850; Wed, 03 Nov 2010 17:28:39 -0700 (PDT)
Received: by 10.213.28.2 with HTTP; Wed, 3 Nov 2010 17:28:39 -0700 (PDT)
In-Reply-To: <AANLkTikG8XVKQ7pLq+bcGhAk=UrJiS05vbkib7jQde_Y@mail.gmail.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C3D2B58B3@TK5EX14MBXC127.redmond.corp.microsoft.com> <AANLkTikG8XVKQ7pLq+bcGhAk=UrJiS05vbkib7jQde_Y@mail.gmail.com>
Date: Wed, 3 Nov 2010 20:28:39 -0400
Message-ID: <AANLkTi=kP7j1Q4JmWSeG-qsuCwGdWoAAGbujbpCjOERE@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Robert McMurray <robmcm@microsoft.com>, mb@smartftp.com
Content-Type: text/plain; charset=ISO-8859-1
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: Thu, 04 Nov 2010 00:28:33 -0000

On Thu, Sep 16, 2010 at 1:28 AM, Anthony Bryan <anthonybryan@gmail.com> wro=
te:
> On Fri, Aug 20, 2010 at 6:01 PM, Robert McMurray <robmcm@microsoft.com> w=
rote:
>> With that in mind, I've been thinking through implementation scenarios i=
n the wake of the denial-of-service discussion that took place before IETF =
78. More specifically, I've thinking about a scenario where the maximum fil=
e size could be configured at the server, so HASH commands could be prevent=
ed from stealing too many server resources when larger files are involved. =
This is purely a server implementation detail that has nothing to do with t=
he draft with the exception of considering which reply code to return.
>>
>> Looking at section "3.4. HASH Command Errors" in the draft it would seem=
 that none of the 5yz errors that are listed would apply, but returning a 5=
04 reply might seem to make sense in this scenario. If so, would it be wort=
hwhile to add a statement like the following to the draft?
>>
>> =A0 The server-PI SHOULD reply with a 504 reply if the HASH command is
>> =A0 used on a file that cannot be processed for policy reasons. (For
>> =A0 example, the file size exceeds the server's hashing policy.)
>>
>> Or would a 4yz reply be better since this is a configurable option at th=
e server? Perhaps a 452 reply?
>
> revisiting this, Mathias Berchtold is an implementer (ProFTPD module
> mod_digest, http://www.smartftp.com/oss/proftpd/mod_digest.html ) of
> the alternate non-standard commands (XCRC, XMD5, XSHA1, SHA256) that
> HASH is trying to standardize.
>
> mod_digest uses 550 reply code for the case that Robert mentioned of a
> file not being allowed to be hashed because of a policy.
>
> "The DigestMaxSize directive configures the maximum number of bytes a
> single hash command is allowed to read from a file. If the number of
> bytes to be read from the file is greater than the configured limit
> the server will return an error. If no DigestMaxSize directive is
> configured, then there is no limit. It is stronly recommended to set
> an upper limit."
>
> R_550, "%s: Length (%zu) greater than " CONFIG_DIGEST_MAXSIZE " (%zu)
> config value", cmd->arg, lLength, lMaxSize);
>
> Mathias, any suggestions as an implementer?
>
> we use 550 already for file not found.
>
> =A0 =A0 =A0550 Requested action not taken.
> =A0 =A0 =A0 =A0 =A0File unavailable (e.g., file not found, no access).
>
> we don't seem to have a specific reply code that fits this case currently=
.
> should we mint a new reply code (55z since it's permanent & deals with
> file system) or use another existing code that isn't an exact fit?

the newest HASH draft uses a new code: 556.

http://tools.ietf.org/html/draft-bryan-ftp-hash

comments? here's the new text.

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

later:

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

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

From alun@texis.com  Sat Nov  6 14:48:01 2010
Return-Path: <alun@texis.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 808613A687C for <ftpext@core3.amsl.com>; Sat,  6 Nov 2010 14:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001]
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 8yh+QtqjFk3e for <ftpext@core3.amsl.com>; Sat,  6 Nov 2010 14:47:52 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 7554A3A68D1 for <ftpext@ietf.org>; Sat,  6 Nov 2010 14:47:52 -0700 (PDT)
Received: from Parnassus (c-76-22-68-139.hsd1.wa.comcast.net [76.22.68.139]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MN23M-1PCekv0Na4-006wsH; Sat, 06 Nov 2010 17:48:06 -0400
From: "Alun Jones" <alun@wftpd.com>
Sender: "Alun Jones" <alun@texis.com>
To: <ftpext@ietf.org>
Date: Sat, 6 Nov 2010 14:48:03 -0700
Organization: Texas Imperial Software
Message-ID: <058201cb7dfc$4bd03d00$e370b700$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0583_01CB7DC1.9F716500"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Act978W85xf5b2CRTTaUmeVMZOObkA==
Content-Language: en-us
X-Provags-ID: V02:K0:X7AGKCaoSeWn5d77QSq7BK3/S1r/mwjUSHBepic3cdQ 0Vq88GZ9UrlHdr1xbQjlq7KDM+2ZOdbeoIhW163zDcBbe4oIRH nlZFw9XUXgoJXyK4YC1Un2WIr8+6XwW9LYMSgNxXC3ZuOT4q8B mrpfBjfeaVpjXYZV/TLchAUivJMHwlFhT9ReBPnEHdFvPdtJLi kgiohIL5BY8imnzqcf6nA==
Subject: [ftpext] 1st post; miscellaneous FTP additions.
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: alun@texis.com
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, 06 Nov 2010 21:48:02 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0583_01CB7DC1.9F716500
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

First, thanks to everyone here for starting up another FTP extensions
Working Group. I enjoyed the last one and look forward to hearing much more
on the ways we can move FTP forward.

 

Having read the mailing list archives to date, here are a relatively random
list of observations:

1.       I found this mailing list through a rather random reading of the
IETF mailing list. Pure chance. Should this WG perhaps reach out to members
of the previous WG's mailing list to let them know that there is a new WG to
which they might wish to subscribe? [Or was there an announcement that I
simply missed?]

2.       I would very much like to see us address not only new and
interesting features, but some of the issues that cause enterprises to avoid
using FTP. Particularly, I note that there's a perception that FTP is
unsecure, that it's not standard (peculiarly enough, SFTP is given as the
standard alternative, despite not actually having any standards
documentation), that it's inefficient (not sure what is meant by that), that
it requires massive firewall holes, and that it frequently fails through
firewalls even if you think you have the right holes open. To that end:

a.       I would like to suggest the use of MODE B with the default data
port as common practice. In the absence of errors in communication, or
client-requested aborts, this works well through existing firewalls, as well
as with TLS, is portable to IPv6, has been a standard since at least RFC 959
days, and only requires that clients request and support MODE B as an
option. Some steps to improve this would include:

                                                               i.
Document how MODE B should recover from client-requested aborts, even if the
recovery is simply "close all connections and try again".

                                                             ii.
Augment MODE B - for instance, specify options to state that TYPE I, STRU F,
can avoid sending REST markers in the data stream.

b.      Where port assignments are made, use random port assignments as
specified in the recent BCP draft
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-randomization/ to
improve protection against port guessing. Are there any standard protocols
to use to open firewall holes in relation to existing traffic? UPnP springs
to mind, but if there are any other protocols we could use as FTP server /
client authors to open these ports (or avoid having to), it is important
that we document the use of these for FTP.

c.       To address storage security of transferred files, it may be
appropriate to add commands and responses for the following cases:

                                                               i.
Client requests that server receive next STOR / STOU as sensitive file, and
stores it in encrypted storage (with affirmative response if it can do this)

                                                             ii.      Server
refuses to send file in response to RETR until client asserts that it will
be storing it in encrypted storage.

3.       It was suggested earlier in the mailing list that a command be
provided for encrypting passwords in transit in some way. While I agree with
the general sentiment that TLS should be used for such cases (because the
password is generally only sensitive because of the data it protects, and
therefore the commands and data should be encrypted and integrity-protected
also), there is, or was, a standard for SASL passwords in FTP - I simply
can't find it right now.

4.       Keeping firewalls open through long data transfers can adequately
be achieved using the NOOP command at regular intervals, or if that command
is not supported, the STAT command, which is already documented to give a
user-readable status during a data transfer.

5.       GSSAPI FTP as defined in RFC 2228 should be deprecated, as it does
not provide for separate encryption contexts between the command and data
ports - because they share an encryption context, if a command is sent
during a transfer, the synchronization is lost, and all further data and
commands are garbled and unreadable.

6.       FTP URIs don't work as documented. I have yet to see a single
client implementation that treats "ftp://example.com/foo" as an invitation
to connect to example.com and issue the "CWD foo" command - they all issue
"CWD /foo". Clinging to ancient documentation that is always ignored seems
to be a waste of time. Deprecate the old behaviour, and as crappy as it may
be, adopt and accept the behaviour that "all paths are from the root unless
they begin with a dot. (ftp://example.com/./foo)"

 

Well, that's enough to be getting on with - let me know if any of these
ideas are worth considering, or should be discarded immediately.

 

Thanks again for setting this list up,

 

Alun Jones

[Author, WFTPD and WFTPD Pro - http://www.wftpd.com] 


------=_NextPart_000_0583_01CB7DC1.9F716500
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
 /* List Definitions */
 @list l0
	{mso-list-id:994189111;
	mso-list-type:hybrid;
	mso-list-template-ids:1598596622 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal>First, thanks to everyone here for starting up =
another FTP
extensions Working Group. I enjoyed the last one and look forward to =
hearing
much more on the ways we can move FTP forward.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Having read the mailing list archives to date, here =
are a
relatively random list of observations:<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>I found this mailing list through a rather =
random
reading of the IETF mailing list. Pure chance. Should this WG perhaps =
reach out
to members of the previous WG&#8217;s mailing list to let them know that =
there
is a new WG to which they might wish to subscribe? [Or was there an
announcement that I simply missed?]<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>I would very much like to see us address not =
only new
and interesting features, but some of the issues that cause enterprises =
to
avoid using FTP. Particularly, I note that there&#8217;s a perception =
that FTP
is unsecure, that it&#8217;s not standard (peculiarly enough, SFTP is =
given as
the standard alternative, despite not actually having any standards =
documentation),
that it&#8217;s inefficient (not sure what is meant by that), that it =
requires
massive firewall holes, and that it frequently fails through firewalls =
even if
you think you have the right holes open. To that end:<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span =
style=3D'mso-list:Ignore'>a.<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>I
would like to suggest the use of MODE B with the default data port as =
common
practice. In the absence of errors in communication, or client-requested
aborts, this works well through existing firewalls, as well as with TLS, =
is
portable to IPv6, has been a standard since at least RFC 959 days, and =
only
requires that clients request and support MODE B as an option. Some =
steps to
improve this would include:<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2'><![if =
!supportLists]><span
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
</span>i.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Document how MODE B should recover from
client-requested aborts, even if the recovery is simply &#8220;close all
connections and try again&#8221;.<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2'><![if =
!supportLists]><span
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
</span>ii.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Augment MODE B &#8211; for instance, specify =
options to
state that TYPE I, STRU F, can avoid sending REST markers in the data =
stream.<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span =
style=3D'mso-list:Ignore'>b.<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Where
port assignments are made, use random port assignments as specified in =
the
recent BCP draft <a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-randomizati=
on/">http://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-randomization/=
</a>
to improve protection against port guessing. Are there any standard =
protocols
to use to open firewall holes in relation to existing traffic? UPnP =
springs to
mind, but if there are any other protocols we could use as FTP server / =
client
authors to open these ports (or avoid having to), it is important that =
we
document the use of these for FTP.<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo2'><![if !supportLists]><span =
style=3D'mso-list:Ignore'>c.<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>To
address storage security of transferred files, it may be appropriate to =
add
commands and responses for the following cases:<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2'><![if =
!supportLists]><span
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
</span>i.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Client requests that server receive next STOR / =
STOU as
sensitive file, and stores it in encrypted storage (with affirmative =
response
if it can do this)<o:p></o:p></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;
mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2'><![if =
!supportLists]><span
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
</span>ii.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Server refuses to send file in response to RETR =
until
client asserts that it will be storing it in encrypted =
storage.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>It was suggested earlier in the mailing list =
that a
command be provided for encrypting passwords in transit in some way. =
While I
agree with the general sentiment that TLS should be used for such cases
(because the password is generally only sensitive because of the data it
protects, and therefore the commands and data should be encrypted and
integrity-protected also), there is, or was, a standard for SASL =
passwords in
FTP &#8211; I simply can&#8217;t find it right now.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Keeping firewalls open through long data =
transfers can
adequately be achieved using the NOOP command at regular intervals, or =
if that
command is not supported, the STAT command, which is already documented =
to give
a user-readable status during a data transfer.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>GSSAPI FTP as defined in RFC 2228 should be =
deprecated,
as it does not provide for separate encryption contexts between the =
command and
data ports &#8211; because they share an encryption context, if a =
command is
sent during a transfer, the synchronization is lost, and all further =
data and
commands are garbled and unreadable.<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>FTP URIs don&#8217;t work as documented. I have =
yet to
see a single client implementation that treats
&#8220;ftp://example.com/foo&#8221; as an invitation to connect to =
example.com
and issue the &#8220;CWD foo&#8221; command &#8211; they all issue =
&#8220;CWD
/foo&#8221;. Clinging to ancient documentation that is always ignored =
seems to
be a waste of time. Deprecate the old behaviour, and as crappy as it may =
be,
adopt and accept the behaviour that &#8220;all paths are from the root =
unless
they begin with a dot. (ftp://example.com/./foo)&#8221;<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Well, that&#8217;s enough to be getting on with =
&#8211; let
me know if any of these ideas are worth considering, or should be =
discarded
immediately.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Thanks again for setting this list =
up,<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Alun Jones<o:p></o:p></p>

<p class=3DMsoNormal>[Author, WFTPD and WFTPD Pro &#8211; <a
href=3D"http://www.wftpd.com">http://www.wftpd.com</a>] <o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0583_01CB7DC1.9F716500--


From daniel@haxx.se  Sun Nov  7 10:29:16 2010
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 688843A6884 for <ftpext@core3.amsl.com>; Sun,  7 Nov 2010 10:29:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.249
X-Spam-Level: 
X-Spam-Status: No, score=-4.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, 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 cPXQRQ2V5ce2 for <ftpext@core3.amsl.com>; Sun,  7 Nov 2010 10:29:15 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id CF7AF3A688E for <ftpext@ietf.org>; Sun,  7 Nov 2010 10:29:14 -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 oA7ITXXB026098; Sun, 7 Nov 2010 19:29:33 +0100
Date: Sun, 7 Nov 2010 19:29:33 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: alun@texis.com
In-Reply-To: <058201cb7dfc$4bd03d00$e370b700$@com>
Message-ID: <alpine.DEB.2.00.1011071918120.21451@tvnag.unkk.fr>
References: <058201cb7dfc$4bd03d00$e370b700$@com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Sun, 07 Nov 2010 19:29:33 +0100 (CET)
Cc: ftpext@ietf.org
Subject: Re: [ftpext] 1st post; miscellaneous FTP additions.
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: Sun, 07 Nov 2010 18:29:16 -0000

On Sat, 6 Nov 2010, Alun Jones wrote:

> c.       To address storage security of transferred files, it may be
> appropriate to add commands and responses for the following cases:

I must say that I'm very skeptical about such peculiar and specific commands, 
and if you want to move ahead and suggest those they should be in a separate 
draft imho.

> 4.  Keeping firewalls open through long data transfers can adequately be 
> achieved using the NOOP command at regular intervals, or if that command is 
> not supported, the STAT command, which is already documented to give a 
> user-readable status during a data transfer.

Sorry, but I've tried this and it turned out that is not a reliable way to 
keep a connection alive. Several FTP server implementations just don't read 
the control connection while the data is being transfered.

We got better functionality by simply using the TCP KEEPALIVE option and 
setting the timers small enough (on the systems that allow that sort of 
configurability).

> 5.       GSSAPI FTP as defined in RFC 2228 should be deprecated, as it does
> not provide for separate encryption contexts between the command and data
> ports - because they share an encryption context, if a command is sent
> during a transfer, the synchronization is lost, and all further data and
> commands are garbled and unreadable.

We can't just deprecate it because it one or more flaws if there are still 
users of that protocol in the wild. Can we?

> 6.       FTP URIs don't work as documented. I have yet to see a single
> client implementation that treats "ftp://example.com/foo" as an invitation
> to connect to example.com and issue the "CWD foo" command - they all issue
> "CWD /foo".

What are you talking about? curl has done "CWD foo" since 1998 and I would 
strongly disagree to changing that URI definition at this point.

If I remember things correctly, there's a flaw in how empty path parts are 
supposed to be handled, as in ftp://example.com/foo//bar.

-- 

  / daniel.haxx.se

From anthonybryan@gmail.com  Sun Nov  7 14:08:14 2010
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 257C93A68A6 for <ftpext@core3.amsl.com>; Sun,  7 Nov 2010 14:08:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 FUVRoWZhv00W for <ftpext@core3.amsl.com>; Sun,  7 Nov 2010 14:08:13 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id BFA243A6802 for <ftpext@ietf.org>; Sun,  7 Nov 2010 14:08:12 -0800 (PST)
Received: by eyd10 with SMTP id 10so2630191eyd.31 for <ftpext@ietf.org>; Sun, 07 Nov 2010 14:08:31 -0800 (PST)
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=GPgS1kaAe6HbBpEikXll9JtMcYfNmu4Qk0GcXTiqyck=; b=bY7FZF2w+KXut3jR79Dy3lsQj3RTwQ668KRWYKOTLR9jAykfBfxdc/IE8v2r4gz+jG xKpW4JrVypDzpUsCurzilSXw78RVS0NxLTPGVTkvEEnIlttYZPm4OXkLfT/0ELC8M2cm 2RHU+LY8Qlbgk1Wr1qMmP4GZZHL3iS0d58Ouo=
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=dfUm1O89SUVy1pZ+5kXqFCtobDq0i6PJNSGMg1l9XRL9AT3X332HFQAzw2nswvyTG8 F8R4i3hZK+kaNOg88LvQ7XcaT74Ci4wCrlBVO7fQhsfYmvSr2vsY0xtFFnBlPj3j+odx b67K7carLXw0ajC2EXEB2l2Q4CdW8SONRGeEs=
MIME-Version: 1.0
Received: by 10.213.15.209 with SMTP id l17mr641976eba.63.1289167709877; Sun, 07 Nov 2010 14:08:29 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Sun, 7 Nov 2010 14:08:29 -0800 (PST)
In-Reply-To: <058201cb7dfc$4bd03d00$e370b700$@com>
References: <058201cb7dfc$4bd03d00$e370b700$@com>
Date: Sun, 7 Nov 2010 17:08:29 -0500
Message-ID: <AANLkTin9Twb1t50SYbquHfCoo66G0NCzOcwU88mYLKBQ@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: alun@texis.com
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] 1st post; miscellaneous FTP additions.
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: Sun, 07 Nov 2010 22:08:14 -0000

On Sat, Nov 6, 2010 at 5:48 PM, Alun Jones <alun@wftpd.com> wrote:
> First, thanks to everyone here for starting up another FTP extensions
> Working Group. I enjoyed the last one and look forward to hearing much mo=
re
> on the ways we can move FTP forward.
>
>
>
> Having read the mailing list archives to date, here are a relatively rand=
om
> list of observations:
>
> 1.=A0=A0=A0=A0=A0=A0 I found this mailing list through a rather random re=
ading of the
> IETF mailing list. Pure chance. Should this WG perhaps reach out to membe=
rs
> of the previous WG=92s mailing list to let them know that there is a new =
WG to
> which they might wish to subscribe? [Or was there an announcement that I
> simply missed?]

hi, Alun, welcome!

that's a good idea, we should invite the previous members. (this isn't
quite a WG yet, but things should be finalized one way or another in
about 2 weeks).

there is talk of possible work on an "FTP in the 21st century" draft
and also a FTP URI scheme draft. these could address some of your
other issues.

from the draft charter http://www.ietf.org/iesg/evaluation/ftpext2-charter.=
txt

* Investigate the differences between FTP in theory
 (current RFCs) and practice, and recommend future work to align them.
 Any future work would require rechartering of the WG.

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

From daniel@haxx.se  Wed Nov 10 01:10:48 2010
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 34D373A69DF for <ftpext@core3.amsl.com>; Wed, 10 Nov 2010 01:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=-1.000, 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 2lUzvwb-bOrS for <ftpext@core3.amsl.com>; Wed, 10 Nov 2010 01:10:47 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id BE8533A6A18 for <ftpext@ietf.org>; Wed, 10 Nov 2010 01:10:46 -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 oAA9BC90019222 for <ftpext@ietf.org>; Wed, 10 Nov 2010 10:11:12 +0100
Date: Wed, 10 Nov 2010 10:11:12 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: ftpext@ietf.org
Message-ID: <alpine.DEB.2.00.1011101009580.17851@tvnag.unkk.fr>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Wed, 10 Nov 2010 10:11:12 +0100 (CET)
Subject: [ftpext] "Distributed Transfer Support for 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: Wed, 10 Nov 2010 09:10:48 -0000

Hi

I just noticed this and thought people in this group might be interested:

Abstract
          This document specifies new File Transfer Protocol (FTP)
          commands to allow for a distributed FTP server to operate
          correctly. The purpose is to address an issue in the FTP
          Protocol which causes a truely distributed FTP server from
          being possible.

 	http://tools.ietf.org/html/draft-dd-pret-00
-- 

  / daniel.haxx.se

From alun@texis.com  Fri Nov 12 08:46:54 2010
Return-Path: <alun@texis.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 318313A6A1F for <ftpext@core3.amsl.com>; Fri, 12 Nov 2010 08:46:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 zX5vdjfp+Kmp for <ftpext@core3.amsl.com>; Fri, 12 Nov 2010 08:46:47 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 2C6DB3A68CE for <ftpext@ietf.org>; Fri, 12 Nov 2010 08:46:34 -0800 (PST)
Received: from Parnassus (c-76-22-68-139.hsd1.wa.comcast.net [76.22.68.139]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MXZCY-1P36dT08gg-00WgeI; Fri, 12 Nov 2010 11:47:06 -0500
From: "Alun Jones" <alun@texis.com>
To: <ftpext@ietf.org>
References: <alpine.DEB.2.00.1011101009580.17851@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1011101009580.17851@tvnag.unkk.fr>
Date: Fri, 12 Nov 2010 08:47:03 -0800
Organization: Texas Imperial Software
Message-ID: <039101cb8289$3d6041c0$b820c540$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuAtzsnlmxSau0qS+eWT10v3Kv7kABz/Ucw
Content-Language: en-us
X-Provags-ID: V02:K0:mhI6lPQHLch8mj1PlWU9dMQLDYlKtDg3iZk+JJYM/9E zQGmtFO+7Mln0BLMf9JnCopVjvMytA7eVhrOf99N9M/+Emu327 EJLig+giOaIe3L9+ejjFWa99a+FJ3momJhMN2kFTQ7Q6GF9Bvz faHkNHyZUEdLeofL1UHkWaFmoyZSdTKMtssttAy7zawBI+WCwO JXy44i/XwK5Fr9O+/zFsw==
Subject: Re: [ftpext] "Distributed Transfer Support for FTP"
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: alun@texis.com
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: Fri, 12 Nov 2010 16:46:54 -0000

This seems a little related to the HOST extension.

For those situations where the HOST extension would not apply, I think it's
more appropriate (and better backward compatibility) for clients to CWD
before transfer (so as to avoid paths in the transfer command), and for the
server to ensure that different back-end services are hosted in different
[virtual] subdirectories from one another.

Perhaps I don't understand the nature of the problem, or the solutions that
already exist.

Alun.
~~~~

> -----Original Message-----
> From: ftpext-bounces@ietf.org [mailto:ftpext-bounces@ietf.org] On
> Behalf Of Daniel Stenberg
> Sent: Wednesday, November 10, 2010 1:11 AM
> To: ftpext@ietf.org
> Subject: [ftpext] "Distributed Transfer Support for FTP"
> 
> Hi
> 
> I just noticed this and thought people in this group might be
> interested:
> 
> Abstract
>           This document specifies new File Transfer Protocol (FTP)
>           commands to allow for a distributed FTP server to operate
>           correctly. The purpose is to address an issue in the FTP
>           Protocol which causes a truely distributed FTP server from
>           being possible.
> 
>  	http://tools.ietf.org/html/draft-dd-pret-00
> --
> 
>   / daniel.haxx.se
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext


From damin@emuxperts.net  Fri Nov 12 14:11:08 2010
Return-Path: <damin@emuxperts.net>
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 A36613A6B5F for <ftpext@core3.amsl.com>; Fri, 12 Nov 2010 14:11:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
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 bK4rKD3nAU1v for <ftpext@core3.amsl.com>; Fri, 12 Nov 2010 14:11:00 -0800 (PST)
Received: from ca0.emuxperts.net (unknown [96.45.180.106]) by core3.amsl.com (Postfix) with ESMTP id C11B33A6B5D for <ftpext@ietf.org>; Fri, 12 Nov 2010 14:10:58 -0800 (PST)
Received: from localhost.localdomain (localhost [127.0.0.1]) by ca0.emuxperts.net (Postfix) with ESMTPA id 3E5F71FC070 for <ftpext@ietf.org>; Fri, 12 Nov 2010 22:11:32 +0000 (GMT)
Message-ID: <4CDD9161.70709@emuxperts.net>
Date: Fri, 12 Nov 2010 14:11:29 -0500
From: Damin Daster <damin@emuxperts.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc13 Thunderbird/3.1.6
MIME-Version: 1.0
To: ftpext@ietf.org
References: <alpine.DEB.2.00.1011101009580.17851@tvnag.unkk.fr> <039101cb8289$3d6041c0$b820c540$@com>
In-Reply-To: <039101cb8289$3d6041c0$b820c540$@com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [ftpext] "Distributed Transfer Support for 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: Fri, 12 Nov 2010 22:11:08 -0000

I might as well introduce this now;

This draft is meant to extend FTP in a way that allows for a distributed 
server. That is, a set of servers which act together as a single FTP site.

Distributed FTP Servers have many great benefits:
Disk Sharing (one "giant" filesystem)
Bandwidth Aggregation
Load-Balancing
Geo-Balancing (something similar to CDN?)
High-Availability for FTP Site (multi-mastered)
High-Availability for Files (one file on multiple slaves)

Hereīs the basic idea...
A Distributed FTP site is a group of servers; masters and slaves
Masters hold a List of files. (and know where each file is)
Slaves transfer and store files.

If a client wants to download a file;
It connects to a master.
It tells the master it wants to download a file...
The master determines what slave has that file and instructs that slave 
and the client to connect to each other (depends on PASV or PORT)
The slave then sends the file DIRECTLY to the client.

Why this isnīt possible now;
FTP initiates a connection before we know what will be transferred 
through it.
If the master doesnīt know what the user is going to ask for, how would 
it know who it should instruct to connect?

The solution;
The client should tell the master what it wants before it asks to connect.
The master can then make an educated choice on who should connect.

Compatibility;
The proposal is very unobtrusive, backwards compatible, and forwards 
compatible for the most part.

Of course let me know if you see any problems or have any questions.

On 11/12/2010 11:47 AM, Alun Jones wrote:
> This seems a little related to the HOST extension.
>
> For those situations where the HOST extension would not apply, I think it's
> more appropriate (and better backward compatibility) for clients to CWD
> before transfer (so as to avoid paths in the transfer command), and for the
> server to ensure that different back-end services are hosted in different
> [virtual] subdirectories from one another.
>
> Perhaps I don't understand the nature of the problem, or the solutions that
> already exist.
>
> Alun.
> ~~~~
>
>> -----Original Message-----
>> From: ftpext-bounces@ietf.org [mailto:ftpext-bounces@ietf.org] On
>> Behalf Of Daniel Stenberg
>> Sent: Wednesday, November 10, 2010 1:11 AM
>> To: ftpext@ietf.org
>> Subject: [ftpext] "Distributed Transfer Support for FTP"
>>
>> Hi
>>
>> I just noticed this and thought people in this group might be
>> interested:
>>
>> Abstract
>>            This document specifies new File Transfer Protocol (FTP)
>>            commands to allow for a distributed FTP server to operate
>>            correctly. The purpose is to address an issue in the FTP
>>            Protocol which causes a truely distributed FTP server from
>>            being possible.
>>
>>   	http://tools.ietf.org/html/draft-dd-pret-00
>> --
>>
>>    / daniel.haxx.se
>> _______________________________________________
>> ftpext mailing list
>> ftpext@ietf.org
>> https://www.ietf.org/mailman/listinfo/ftpext
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext


From prvs=1936d8d952=mpp@rhinosoft.com  Tue Nov 16 05:07:27 2010
Return-Path: <prvs=1936d8d952=mpp@rhinosoft.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 B5DE43A6C61 for <ftpext@core3.amsl.com>; Tue, 16 Nov 2010 05:07:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001]
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 VyL2BJ6PFfsY for <ftpext@core3.amsl.com>; Tue, 16 Nov 2010 05:07:26 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id AA82B3A6A73 for <ftpext@ietf.org>; Tue, 16 Nov 2010 05:07:23 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009925166.msg for <ftpext@ietf.org>; Tue, 16 Nov 2010 07:08:05 -0600
X-Spam-Processed: rhinosoft.com, Tue, 16 Nov 2010 07:08:05 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=1936d8d952=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <F1714E4C4C6E44CDAB8FD961B5C5368B@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: <ftpext@ietf.org>
Date: Tue, 16 Nov 2010 07:08:01 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 16 Nov 2010 13:07:27 -0000

Hi Everyone,

I just wanted to mention that my document, "draft-peterson-streamlined-ftp-command-extensions"
is alive and I would like it to remain in consideration within this
discussion and the charter.  Could we get some feedback regarding
its priority and content.

Just for the sake of getting this discussion rolling, as with "HOST"
there are a few FTP clients and servers that already support the
commands documented in this proposal.  End-users are already
very happy with the results and would probably like to see these
commands extended to other servers and clients.

Thank you,

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628  
 


From anthonybryan@gmail.com  Tue Nov 16 16:16:47 2010
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 C3ABA3A6895 for <ftpext@core3.amsl.com>; Tue, 16 Nov 2010 16:16:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 xPfuZ3SucCAZ for <ftpext@core3.amsl.com>; Tue, 16 Nov 2010 16:16:46 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 511D13A68A2 for <ftpext@ietf.org>; Tue, 16 Nov 2010 16:16:43 -0800 (PST)
Received: by ewy8 with SMTP id 8so442013ewy.31 for <ftpext@ietf.org>; Tue, 16 Nov 2010 16:17:27 -0800 (PST)
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=TKjZBNZlHhi/4sO19OrhnxfQX9sQ47zodSNeJ1I9stM=; b=OEqiTrQNcSF9e/k5jp/SldCt2MPQX9vSw9sZuB1Z2XURt7yTrhX3FgIA8RykrCCa5N kAiEGtRyA34RWQAXCH9k4pXKCopnQKoGhDUduiE8enFWOVvSP5jSw8RIIcb60tCAYLm/ hJHYMIK/8tLHuoIMtvDQ3mMO12DLPDp9OYLWk=
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=b+5GXZ01rsOgDdEDicO9MfHcX+DxSg41FtFMzCLtsShTz+s88/Y0UU20g9FGMm6KRx i/4SlD/726i/vDkpkrYiMJNNeeIdLdb/XvtQtv7fbIJxHMxX9eT/uxsxmCxozFb0+ynz hVXq9psdscLhRAYAhNqZh27V9prVJAS/YGV+Y=
MIME-Version: 1.0
Received: by 10.213.4.135 with SMTP id 7mr4524835ebr.89.1289953045438; Tue, 16 Nov 2010 16:17:25 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Tue, 16 Nov 2010 16:17:25 -0800 (PST)
In-Reply-To: <F1714E4C4C6E44CDAB8FD961B5C5368B@rhinooffice.net>
References: <F1714E4C4C6E44CDAB8FD961B5C5368B@rhinooffice.net>
Date: Tue, 16 Nov 2010 19:17:25 -0500
Message-ID: <AANLkTi=oYgkcJ7LDjmnS=yw6B+SJA1uVoFR=+JpN4iU6@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 17 Nov 2010 00:16:47 -0000

hi Mark,

On Tue, Nov 16, 2010 at 8:08 AM, Mark P. Peterson <mpp@rhinosoft.com> wrote=
:
> Hi Everyone,
>
> I just wanted to mention that my document, "draft-peterson-streamlined-ft=
p-command-extensions"
> is alive and I would like it to remain in consideration within this

I think it would be helpful if you could respond to my review of your
draft a few months ago & update it if need be.

http://www.ietf.org/mail-archive/web/ftpext/current/msg00130.html

if I didn't already mention it, I see CSID isn't in the IANA section.

> discussion and the charter. =A0Could we get some feedback regarding
> its priority and content.

one reason it was dropped from the charter is because I asked publicly
and privately for help with the charter and dates for the
goals/milestones. you didn't provide any. as you are the one pushing
this forward, you have to be more involved and at least reply where
your draft is concerned.

you kinda have to "defend" your work, when people ask questions or
wonder about things. besides my review left hanging, there was also
this msg: http://www.ietf.org/mail-archive/web/ftpext/current/msg00029.html

> Just for the sake of getting this discussion rolling, as with "HOST"
> there are a few FTP clients and servers that already support the
> commands documented in this proposal. =A0End-users are already
> very happy with the results and would probably like to see these
> commands extended to other servers and clients.

which clients & servers?

can we involve the developers who have implemented them on this list?
I would like to have more people behind this.

can other people on the list give their opinion on the draft?


here's the quick summary of the 5 commands.

Remove Directory All (RMDA)

   The FTP command REMOVE DIRECTORY ALL (RMDA) removes a directory from
   the server and all of its contents including all files and
   subdirectories.  The RMDA command is considered analogous to
   recursively deleting all files and directories contained in a given
   remote directory (including the directory itself) one at a time.

Directory Size (DSIZ)

   The FTP command DIRECTORY SIZE (DSIZ) returns the number of octets
   (8-bit bytes) on the remote file system occupied by a given directory
   and its contents.

Available Octets (AVBL)

   The FTP command AVAILABLE OCTETS (AVBL) can be used to retrieve the
   number of octets available to receive uploads in a specified remote
   directory.

Retrieve Thumbnail of Remote Image File (THMB)

   The THMB FTP command allows the server-FTP process to locally
   generate a thumbnail of a requested image type and transfer the
   resulting image instead of the entire contents of the original image
   file.

Client / Server Identification (CSID)

   The FTP command CLIENT / SERVER IDENTIFICATION (CSID) allows the
   client and server to exchange relevant identifying information about
   the programs and underlying platforms being used for the FTP
   communication.
--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads

From prvs=1939d99d31=mpp@rhinosoft.com  Fri Nov 19 08:24:28 2010
Return-Path: <prvs=1939d99d31=mpp@rhinosoft.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 058223A6872 for <ftpext@core3.amsl.com>; Fri, 19 Nov 2010 08:24:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=0.350,  BAYES_00=-2.599, J_CHICKENPOX_43=0.6]
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 Ge9O2elCFHRs for <ftpext@core3.amsl.com>; Fri, 19 Nov 2010 08:24:26 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id 5A6ED3A680B for <ftpext@ietf.org>; Fri, 19 Nov 2010 08:24:26 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009930510.msg for <ftpext@ietf.org>; Fri, 19 Nov 2010 10:25:14 -0600
X-Spam-Processed: rhinosoft.com, Fri, 19 Nov 2010 10:25:14 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=1939d99d31=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <D22AFE44108D486EB4C6F469A61BFB2B@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "Anthony Bryan" <anthonybryan@gmail.com>
References: <1791E3B42BE242848B7FFFC7015B4563@rhinooffice.net><AANLkTimeH+O4E4XEq6cdw0UaM4UpDTo6EKB9kB1x4PJh@mail.gmail.com><139EAF2195BC496AA3F25288D56BFB43@rhinooffice.net> <AANLkTinriyMy5_thOnx29HbGQ41NcYW+MS27YGDAjoNT@mail.gmail.com>
In-Reply-To: <AANLkTinriyMy5_thOnx29HbGQ41NcYW+MS27YGDAjoNT@mail.gmail.com>
Date: Fri, 19 Nov 2010 10:25:12 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ftpext@ietf.org
Subject: Re: [ftpext] Posted Update to "draft-peterson-streamlined-ftp-command-extensions"
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: Fri, 19 Nov 2010 16:24:28 -0000

Hi Anthony,

I submitted a new revision which I believe addresses your comments below.
It appears I still have some "idnets" issues even though I attempted to make
the corrections you mention below.  Thank you for your assistance with this
draft.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628  


--------------------------------------------------
From: "Anthony Bryan" <anthonybryan@gmail.com>
Sent: Saturday, September 18, 2010 3:13 AM
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: <ftpext@ietf.org>
Subject: Re: [ftpext] Posted Update to "draft-peterson-streamlined-ftp-command-extensions"

idnits gives you some issues to work on (keep in mind, you don't need
to submit new versions as soon as you make changes, you can wait until
a small amount of changes pile up):

http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-peterson-streamlined-ftp-command-extensions-09.txt

  == Unrecognized Status in 'Intended status: Streamlined FTP Command
     Extensions  September 17, 2010', assuming Proposed Standard

     (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard',
     'Proposed Standard', 'Best Current Practice', 'Informational',
     'Experimental', 'Informational', 'Historic'.)

  == The document seems to lack a disclaimer for pre-RFC5378 work, but was
     first submitted before 10 November 2008.  Should you add the disclaimer?
     (See the Legal Provisions document at
     http://trustee.ietf.org/license-info for more information.) -- however,
     there's a paragraph with a matching beginning. Boilerplate error?


  == Unused Reference: 'RFC1035' is defined on line 818, but no explicit
     reference was found in the text

some other issues...

1) I also think RFC 5797 is an informative ref rather than normative.

2) what does this mean?

   The 213 reply is formatted in such a way that the returned size value
   can be machine parsed.

from the example

         C> DSIZ A
         S> 213 123456

it looks like a straight up integer w/ no commas or other characters
delimiting it.

3) would it be useful to have more exact error responses like we are
talking about for HASH? (same for section 4.2).

3.2. DSIZ Error Responses


   In the event that the pathname is not a directory, the server MUST
   return a permanent 550 error reply.  Where the command cannot be
   parsed, a 500 or 501 reply SHOULD be sent.  The client MUST NOT
   assume that the presence of a 550 reply indicates that it cannot
   access the directory or its contents.  The server may generate this
   error for other reasons, for example the overhead required for the
   operation is too great.

4a) I have questions for each sentence of the AVBL intro:


4. Available Octets (AVBL)

   The FTP command AVAILABLE OCTETS (AVBL) can be used to retrieve the
   number of octets available to receive uploads in a specified remote
   directory.

to the currently logged in user? on a drive as a whole?

4b)

   Many server-FTP processes have implemented proprietary
   methods for restricting the amount of space available, either to the
   user as a whole or within a specified remote location.

I don't understand. does AVBL restrict the amount of space available
(above sentence) or show how much space is available (first sentence)?

4c)

   The AVBL
   command offers an interface for retrieving this value in a way that
   can be machine parsed.

also mentioned a few lines later in 4.1 (I think once in 4.1 is enough):

   The 213 reply is formatted in such a way that the returned size can
   be machine parsed.

5) see 4a. don't you want some consistency here?

   A successful response includes a numeric value that may be the number
   of octets available as dictated by the physical limitations of the
   underlying storage mechanism.  It may also be a limit imposed upon
   <pathname> or even the user that issued the command.  The exact
   method for calculating this numeric value is up to the specific
   server-FTP process implementation.

6) THMB FEAT response is in 5.3

   Image formats supported by the server are listed in the THMB FEAT
Response [6.3].

7) for this sentence, I think you should mention media subtype name
like you do later.

Its value corresponds to the commonly accepted file extension
   used for the requested image format.

8) you might want to mention this earlier:

5.4. THMB Examples

   Assuming the existence of image file "widget.png" on the server and
   that the client has all necessary permissions to access and transfer
   the "widget.png" file, a request for a "widget.png" thumbnail might
   look like this:


9) for the last sentence, you may want to make it clear that "Bytes"
is the descriptive text.

   The syntax of a positive response is:

      thmb-response  = "150" SP *TCHAR "(" 1*DIGIT 1*TCHAR ")" CRLF /
                        error-response

   '1*DIGIT' represents the size in octets of the forthcoming file
   transfer.  The value within the parentheses MAY include descriptive
   text, for example (123456 Bytes)

10) maybe use the IANA registry Operating System Names?
http://www.iana.org/assignments/operating-system-names/operating-system-names.xhtml

Windows XP includes the version and is listed in this registry as
"WINDOWS-NT-5.1" but not all are.

   "OS" is an optional argument identifying the operating system name,
   i.e., "Windows XP", "BSD UNIX", etc.

   "OSVer" is an optional argument identifying the operating system
   version number.



On Fri, Sep 17, 2010 at 5:44 PM, Mark P. Peterson <mpp@rhinosoft.com> wrote:
> Hi Anthony,
>
> Thank you.  I have updated the draft.  It can be found here:
>
> https://datatracker.ietf.org/doc/draft-peterson-streamlined-ftp-command-extensions/
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Anthony Bryan" <anthonybryan@gmail.com>
> Sent: Friday, September 17, 2010 3:08 AM
> To: "Mark P. Peterson" <mpp@rhinosoft.com>
> Cc: <ftpext@ietf.org>
> Subject: Re: [ftpext] Posted Update to "draft-peterson-streamlined-ftp-command-extensions"
>
> On Wed, Sep 15, 2010 at 8:20 AM, Mark P. Peterson <mpp@rhinosoft.com> wrote:
>> Hello,
>>
>> I have updated "draft-peterson-streamlined-ftp-command-extensions"
>> as per some suggestions from Anthony Bryan.  The IANA Considerations
>> section has been updated to reflect his suggestions.  The draft is
>> located here:
>>
>> https://datatracker.ietf.org/doc/draft-peterson-streamlined-ftp-command-extensions/
>
> thanks, Mark! I plan to give this a more thorough review soon, & I
> hope others will too.
>
>
> looking at the last example in each of these, should the last line of each be
>
>         S> 550 file.fid: Is a file.
>
> ?
>
> 3.4. DSIZ Examples
>
>   Assuming the presence of directory "A" on the server and that the
>   client has the necessary permissions to access and list it, a typical
>   DSIZ client-server exchange would be:
>
>         C> DSIZ A
>         S> 213 123456
>
>   Where 123456 is the number of octets on the server's file system
>   occupied by the directory "A" and its contents.
>
>   Assuming directory "A" cannot be listed due to client permissions,
>   the client-server exchange would be:
>
>         C> DSIZ A
>         S> 550 A: Permission denied.
>
>   Assuming the client provides the argument "file.fid" where "file.fid"
>   is an existing file, the client-server exchange would be:
>
>         C> DSIZ file.fid
>         S> 550 A: Is a file.
>
>
> 4.4. AVBL Examples
>
>   Assuming the client provides the argument "file.fid" where "file.fid"
>   is an existing file, the client-server exchange would be:
>
>         C> AVBL file.fid
>         S> 550 A: Is a file.
>
>
> --
> (( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
>  )) Easier, More Reliable, Self Healing Downloads
>
>



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


From anthonybryan@gmail.com  Mon Nov 22 11:12:42 2010
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 B53323A6A2A for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 11:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 tagged_above=-999 required=5 tests=[AWL=0.239,  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 4S5mKIc4T8+l for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 11:12:40 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 353663A69C2 for <ftpext@ietf.org>; Mon, 22 Nov 2010 11:12:36 -0800 (PST)
Received: by ewy8 with SMTP id 8so3845743ewy.31 for <ftpext@ietf.org>; Mon, 22 Nov 2010 11:13:32 -0800 (PST)
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=vQWTThLV5fgpCNT7bgyI7WkKCbJuBoS5lnYXr79cwMw=; b=wdPowappI5Gt5hMX4cXbiEVDyiu8CamYyMSEXAM4RrnngB6lq3TfEcH8H+eBshzMOH X7/tSgGyKJT2YJQuh5cKsy+JEjMZs4leBXRH4o9LaxSFO0UNGNFlAfFbApbmElkmGJD3 wZvowqdgA5XV9pAiDUjZEopVEtAlFoexB+FbI=
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=oYV7GTx3YLGfEKp2olU/eiIDM3uF+Ai+TgLJSk1ECdlA7NIkjMK2dk4DTD3otIXkmy XQoguXzCYVvQiNSxxlmKHpTXdTf5+Qv7miT44R/wtgEJcXNicigie+Z8EdMMgwJVPPjF heyjUcsq+5UHzGIyPLmH1b8h5dXb2uffhJ+Qs=
MIME-Version: 1.0
Received: by 10.213.34.131 with SMTP id l3mr8047274ebd.63.1290453212389; Mon, 22 Nov 2010 11:13:32 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Mon, 22 Nov 2010 11:13:32 -0800 (PST)
In-Reply-To: <C56AF6DA66D1C2B0530A1972@PST.JCK.COM>
References: <201010291746.TAA10758@TR-Sys.de> <C56AF6DA66D1C2B0530A1972@PST.JCK.COM>
Date: Mon, 22 Nov 2010 14:13:32 -0500
Message-ID: <AANLkTinMuUKi=VSN7Y71WTZhUpGbk8+KtnubNX5Cny33@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] RFC 959Re: Followup on FTPEXT2 BOF in Maastricht
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, 22 Nov 2010 19:12:42 -0000

On Fri, Oct 29, 2010 at 3:54 PM, John C Klensin <john-ietf@jck.com> wrote:
> p.s. This list is not on the non-WG mailing lists page. =A0Unless
> we anticipate a charter approval _really_ quickly, that should
> probably be fixed.

that may be because it was on this page, albeit w/ an outdated link
(now updated):

http://datatracker.ietf.org/list/wg/

the archives of the old list, along with the new, are here:

http://www.ietf.org/mail-archive/text/ftpext/


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

From anthonybryan@gmail.com  Mon Nov 22 11:34:16 2010
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 4288328C10B for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 11:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level: 
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[AWL=0.209,  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 dbaIQENA7gmD for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 11:34:12 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 3DE773A69C2 for <ftpext@ietf.org>; Mon, 22 Nov 2010 11:34:12 -0800 (PST)
Received: by eyd10 with SMTP id 10so4249116eyd.31 for <ftpext@ietf.org>; Mon, 22 Nov 2010 11:35:07 -0800 (PST)
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=k0RKBt4vj5S9VrkOxar7ZIvZbSo8YLjC0CN+/Q9WvP0=; b=gTUcOrhmFQvuwVtObPqQnyCy52QhUDeAJQlh9llSp6jZbLLxnQW9yySEhQ0Z5u1vi4 ZE9EzTBYsqlITJdYE6TYKupIETbleJLZ9xslHt72znrL0JzXDu9stIPMouAu77fTBR+G 61+tq6KdB7b6NJL85dcWZMNNgGw0yEGjFiXYU=
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=boO0dnht1/7SNpGcFIqBWJBpbQRK4Gj5dJcRRUxIsG9zjpIUYn2+kaSi5ElBtBT3BT ycZntKWXf0hFIwIaoJZWSRfztixcM1Mso2RUFmYZ8dnP8yzlw0tXo9P32+4/+pfk4y+u m8SjC6+iuDfCeUxExCS2A+rW4/INjfegaApQo=
MIME-Version: 1.0
Received: by 10.213.15.135 with SMTP id k7mr3484706eba.76.1290454506250; Mon, 22 Nov 2010 11:35:06 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Mon, 22 Nov 2010 11:35:06 -0800 (PST)
In-Reply-To: <A5FC996C3C37DC4DA5076F1046B5674C432154AC@TK5EX14MBXC125.redmond.corp.microsoft.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C431FD205@TK5EX14MBXC127.redmond.corp.microsoft.com> <Pine.LNX.4.64.1010171017300.14040@iskra.ottix.net> <AANLkTimFkMmNnpAWWwx9xmJzGoJCHAwqvMrOMoZ-bHZ+@mail.gmail.com> <A5FC996C3C37DC4DA5076F1046B5674C431FF311@TK5EX14MBXC127.redmond.corp.microsoft.com> <AANLkTimv_RW3nxRq8=F47rOKTe4MscMkvFA0J67Fa_Dh@mail.gmail.com> <A5FC996C3C37DC4DA5076F1046B5674C432154AC@TK5EX14MBXC125.redmond.corp.microsoft.com>
Date: Mon, 22 Nov 2010 14:35:06 -0500
Message-ID: <AANLkTimp3+s7V_c17Lvyo8XLtt-4Pj9SEPj9yjW5Mzvt@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Robert McMurray <robmcm@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "mark.peterson@rhinosoft.com" <mark.peterson@rhinosoft.com>, "ftpext@ietf.org" <ftpext@ietf.org>
Subject: Re: [ftpext] Submitting new drafts
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, 22 Nov 2010 19:34:16 -0000

Robert,

I don't mean to single you out, but you showed interest in an CSID/AGNT com=
mand.

do you have any opinion on the other 4 commands in the draft?

something as simple as "XXXX appears useful, YYYY not as much" could
be helpful information.

I'd like to get other people's opinions too, if anyone could just read
the sentence about each command & comment. I'm not asking for anyone
to read the whole draft unless they have time.

http://tools.ietf.org/html/draft-peterson-streamlined-ftp-command-extension=
s

Remove Directory All (RMDA)

   The FTP command REMOVE DIRECTORY ALL (RMDA) removes a directory from
   the server and all of its contents including all files and
   subdirectories.  The RMDA command is considered analogous to
   recursively deleting all files and directories contained in a given
   remote directory (including the directory itself) one at a time.

Directory Size (DSIZ)

   The FTP command DIRECTORY SIZE (DSIZ) returns the number of octets
   (8-bit bytes) on the remote file system occupied by a given directory
   and its contents.

Available Octets (AVBL)

   The FTP command AVAILABLE OCTETS (AVBL) can be used to retrieve the
   number of octets available to receive uploads in a specified remote
   directory.

Retrieve Thumbnail of Remote Image File (THMB)

   The THMB FTP command allows the server-FTP process to locally
   generate a thumbnail of a requested image type and transfer the
   resulting image instead of the entire contents of the original image
   file.

Client / Server Identification (CSID)

   The FTP command CLIENT / SERVER IDENTIFICATION (CSID) allows the
   client and server to exchange relevant identifying information about
   the programs and underlying platforms being used for the FTP
   communication.


On Mon, Oct 18, 2010 at 6:57 PM, Robert McMurray <robmcm@microsoft.com> wro=
te:
> Anthony - great catch!
>
> Mark - I sincerely apologize, I had not seen the CSID addition to draft-p=
eterson-streamlined-ftp-command-extensions; I had only seen earlier drafts =
before that was added. You are welcome to scavenge anything that you might =
find useful from the AGNT draft that I sent out last week to ftpext@ietf.or=
g. ;-]
>
> -----Original Message-----
> From: Anthony Bryan [mailto:anthonybryan@gmail.com]
> Sent: Monday, October 18, 2010 1:20 PM
> To: Robert McMurray
> Cc: William F. Maton; ftpext@ietf.org
> Subject: Re: [ftpext] Submitting new drafts
>
> I would say submit it now (you only have a few hours left) under Apps,
> or you won't have it for discussion at the IETF meeting or be able to
> submit it until November 8.
>
> I'll add it to the draft charter once I see it's submitted.
>
> btw, (this is to everyone) any comments on how to improve the draft chart=
er?
>
> "The pre-meeting cutoff date for new documents (i.e., version -00
> Internet-Drafts) is 2010-10-18 at 5 PM (PT). You will not be able to
> submit a new document after this time until 2010-11-08, at midnight"
>
> also, I think there is some overlap between AGNT from your draft &
> CSID from http://tools.ietf.org/html/draft-peterson-streamlined-ftp-comma=
nd-extensions
>
> On Mon, Oct 18, 2010 at 2:06 PM, Robert McMurray <robmcm@microsoft.com> w=
rote:
>> Thanks, Anthony.
>>
>> The lack of an FTPEXT WG is the problem that I was referring to - I'd li=
ke to add the proposed draft that I sent out last week to the proposed FTPE=
XT WG's charter, but since it isn't a formal WG yet then I wasn't sure how =
best to proceed. (e.g. Should I submit the draft to the applications area f=
or now just to start the peer review process while awaiting the next phase =
of the FTPEXT WG process? )
>>
>> Thanks again.
>
>



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

From robmcm@microsoft.com  Mon Nov 22 15:00:56 2010
Return-Path: <robmcm@microsoft.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 0D58C28C155 for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 15:00:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_HI=-8]
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 oVwyESE4hGHV for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 15:00:54 -0800 (PST)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 90FF428C119 for <ftpext@ietf.org>; Mon, 22 Nov 2010 15:00:54 -0800 (PST)
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (157.54.80.25) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 22 Nov 2010 15:01:50 -0800
Received: from TK5EX14MBXC127.redmond.corp.microsoft.com ([169.254.6.27]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.01.0255.003; Mon, 22 Nov 2010 15:01:48 -0800
From: Robert McMurray <robmcm@microsoft.com>
To: "ftpext@ietf.org" <ftpext@ietf.org>, 'Anthony Bryan' <anthonybryan@gmail.com>, "mark.peterson@rhinosoft.com" <mark.peterson@rhinosoft.com>
Thread-Topic: draft-peterson-streamlined-ftp-command-extensions
Thread-Index: AcuKmTvkbDnCespiQ8mhziICo1jv5g==
Date: Mon, 22 Nov 2010 23:01:46 +0000
Message-ID: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.76]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 22 Nov 2010 23:00:56 -0000

[Note: Renaming the thread from 'Submitting new drafts'.]

> Anthony Bryan wrote:
>=20
> I don't mean to single you out, but
> you showed interest in an CSID/AGNT
> command. Do you have any opinion on
> the other 4 commands in the draft?

Thanks, Anthony.

No worries - I meant to send a better response in the wake of my withdrawn =
AGNT draft and Mark's current Streamlined FTP Command Extensions draft, but=
 I had been remiss at taking the time to collect my thoughts in a more mean=
ingful way. But since you asked, this seems like as good at time as any. ;-=
]

CSID - As evidenced by my short-lived AGNT proposal, I think it's very usef=
ul to have some sort of client/server discovery command. FEAT does a good j=
ob of advertising the list of commands that are supported by a server, but =
Mark's proposed CSID command sequence provides a much better way for server=
s and client to identify their features to each other in detail. For securi=
ty reasons I would probably want the CSID exchange to occur AFTER the clien=
t has logged in, but I might be overreacting.

RMDA - This could be a very useful command, and it would parallel the funct=
ionality that I'm sure we all typically use in a native operating system en=
vironment. In a server implementation I would probably make this command co=
nfigurable, so administrators would have an option to disable the feature. =
In which case I would probably hide the command from a FEAT response so it =
would not be discoverable and have the server return a 500 or 502 reply whe=
n RMDA is sent by the client and disabled at the server.

(Note: I mention my thoughts about server implementation details just to op=
en up the discussion as to whether any implementation details should be cal=
led out in the draft, or if we should leave that up to the implementers to =
decide.)

AVBL - This command could be very useful in a client/server world; our FTP =
server implementation currently returns the available size after a successf=
ul login sequence, and the available size is based on server disk quotas an=
d such. That being said, not every FTP client will bubble that information =
up to the user interface. Having an AVBL command would make it possible for=
 a client to determine whether enough storage space is available at the ser=
ver BEFORE sending a file, which would be great when you're about to send a=
 10GB file and you only have 9.99GB of storage space left. ;-]
=20
DSIZ - This could certainly be useful, although I would probably want a use=
r to be logged in (not anonymous) before I supported this command in order =
to reduce the risk of denial-of-service. I'd probably make it configurable =
so as not to tie up too many server resources for large directory structure=
s; and once again, if the feature were disabled I would probably hide the c=
ommand from a FEAT response so it would not be discoverable and return a 50=
0 or 502 reply when DSIZ is sent by the client and disabled at the server.

THMB - I have to admit, I don't work on a graphical FTP client, so this com=
mand is less useful to me personally, but I can see the merit that it might=
 have to someone that designs a graphical client. That being said, I'm not =
a big fan of computing the thumbnail dynamically, nor am I fond of allowing=
 the client to specify the thumbnail format and size. I think that it would=
 be better if the server could pre-cache thumbnails for any file type in a =
server-determined size and image format, and then return the binary data an=
d image format information to the client. For example, most graphically-bas=
ed operating systems have some method for displaying file icons to a user t=
hat is seated at a computer terminal, so an FTP server implementation could=
 simply return that same icon to a client in response to a THMB request.

Please bear in mind, I haven't given a lot of thought as to what the client=
/server interchange might look like if the server were more in control of t=
he response to a THMB request, but it would probably be sufficient to simpl=
y return the image type as part of the response and let the client determin=
e the image dimensions based on the client's capabilities for reading the i=
mage data. (As a server guy I like to push any client-friendly processing o=
n the client whenever possible. ;-]) You could borrow an idea from the HASH=
 discussion that we've been having and make the thumbnail image type config=
urable for the client by using an OPTS command, which might look like the f=
ollowing examples.

In this first example, the server has a pre-configured thumbnail image type=
 of JPG, and may have pre-cached the thumbnails for files; any THMB request=
 with no OPTS specified would use the server's pre-configured thumbnail ima=
ge type of JPG and image type is specified in the command channel response:

  C> THMB widget.png
  S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
  S> 226 Transfer complete.

In these next examples a client is asking for different thumbnail image typ=
es by using OPTS commands, and the thumbnail image types would still be spe=
cified in the command channel responses:

  C> OPTS THMB GIF
  S> 200 OPTS THMB GIF command successful.

  C> THMB widget.psp
  S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
  S> 226 Transfer complete.

  C> OPTS THMB PNG
  S> 200 OPTS THMB PNG command successful.

  C> THMB widget.doc
  S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
  S> 226 Transfer complete.

In this next example a client is asking for an unsupported image type, so t=
he server would simply return the appropriate error reply:

  C> OPTS THMB FOO
  S> 501 Unsupported thumbnail format.

In this next example a client is asking for the currently-configured thumbn=
ail image type, so the server would return the appropriate response:

  C> OPTS THMB
  S> 200 JPG

You might take this one step further - the server might choose to only supp=
ort its pre-configured thumbnail image type, thereby allowing pre-caching o=
f all thumbnails in one specific image format. In this example a client is =
asking for PNG thumbnails, which SHOULD be a supported image type, but the =
server only supports a pre-configured thumbnail image type for JPG files an=
d returns the appropriate error reply (504?) and the server's pre-configure=
d thumbnail image type is specified in the subsequent command channel respo=
nse to a THMB request:

  C> OPTS THMB PNG
  S> 504 Specifying thumbnail formats is unsupported.

  C> THMB widget.xls
  S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
  S> 226 Transfer complete.

As I said earlier, I hadn't given much thought as to what the client/server=
 THMB interchange might look like if you put the server in control instead =
of the client, but as a server guy I'd rather see THMB look a little more l=
ike the examples that I gave. ;-]

Thanks again!

Robert McMurray
robmcm@microsoft.com


From prvs=19431281bb=mpp@rhinosoft.com  Mon Nov 22 16:31:54 2010
Return-Path: <prvs=19431281bb=mpp@rhinosoft.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 794B528C0F8 for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 16:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.766
X-Spam-Level: 
X-Spam-Status: No, score=-1.766 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
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 vRi6acIx+xzB for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 16:31:52 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id 7CDCF3A6B02 for <ftpext@ietf.org>; Mon, 22 Nov 2010 16:31:52 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009934868.msg for <ftpext@ietf.org>; Mon, 22 Nov 2010 18:32:48 -0600
X-Spam-Processed: rhinosoft.com, Mon, 22 Nov 2010 18:32:48 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=19431281bb=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "Robert McMurray" <robmcm@microsoft.com>, <ftpext@ietf.org>, "'Anthony Bryan'" <anthonybryan@gmail.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com>
In-Reply-To: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com>
Date: Mon, 22 Nov 2010 18:32:39 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 00:31:54 -0000

Hi Robert,

Thank you for taking the time to review the commands.  If you don't mind I would
like to respond to your comments:

CSID:
> For security reasons I would probably want the CSID exchange to occur AFTER the client has logged in, but I might be overreacting.

There is a lot of discussion on the Internet about servers providing "too" much information, especially prior to login.  But having 
worked on both sides of the FTP process, it's usually very easy for the client to identify what brand or flavor the server is. 
There are details which usually identify the server such as the completeness of the FEAT response, the welcome message, responses to 
certain messages, etc.  So, I think it's okay to be available prior to login.  I could change the document to read that it should be 
up to the server's implementation whether or not it's available.

RMDA:
> In a server implementation I would probably make this command configurable, so administrators would have an option to disable the 
> feature.  In which case I would probably hide the command from a FEAT response so it would not be discoverable and have the server 
> return a 500 or 502 reply when RMDA is sent by the client and disabled at the server.

I don't think my document specifies that it isn't configurable.  My implementation in Serv-U is configurable as is almost all other 
FTP commands.  I think this can be left up to the server implementation.  Your possible implementation is exactly how Serv-U 
implements it.  If the feature is disabled, it doesn't appear in the FEAT response, nor is it available through the HELP command.

AVBL:
> ...

Your comments address the reason for its existence.  The client-side implementation in SmartFTP uses the command in this manner.

DSIZ:
> This could certainly be useful, although I would probably want a user to be logged in...

Any information about paths or files requires login in FTP.  I am sure this is the case here as well.  If a server wouldn't want the 
"anonymous" user to have access to this command it could be configured to disallow this command at the server's implementation or 
configuration.  This should be left up to the implementation of the server or administrator of the server.

> I'd probably make it configurable so as not to tie up too many server resources for large directory structures;...

Agreed, the time-consuming nature of the implementation is discussed but configuration by an administrator or server-implementation 
is not.   Do you think such verbiage is required?

THMB:
> I'm not a big fan of computing the thumbnail dynamically, nor am I fond of allowing the client to specify the thumbnail format and 
> size.

That's the point of the command, though.  It's to reduce the amount of data that is required to travel over the wire.  The idea is 
to shorten delivery time to the client, letting the client decide what is best for the client, not the server.  Some clients may 
want very small images, say for a Windows Explorer style listing, others may want larger images (640x480 for example) to show a 
slide show.  I think the client needs to make that determination.  If the server decides to cache these generated images it can.

> I think that it would be better if the server could pre-cache thumbnails for any file type in a server-determined size and image 
> format, and then return the binary data and image format information to the client.

This could waste server-side resources, the client might not even make a request for thumbnail images.

> For example, most graphically-based operating systems have some method for displaying file icons to a user that is seated at a 
> computer terminal, so an FTP server implementation could simply return that same icon to a client in response to a THMB request.

Right, but this isn't really the purpose of this command.  The purpose is to take an original image file and reduce it to a 
specified size, not to return the OS's icon representation for that particular file type (i.e., not SHGetFileInfo() in Windows).

My proposed implementation is fairly straightforward.  If supported the FEAT command replies with THMB and the supported file types. 
When the client wants a thumbnail it asks for it with a single command.  Here is a sample result from FTP Voyager and Serv-U:

PORT 192,168,0,30,199,53
200 PORT command successful.
THMB PNG 98 88 Thomas.JPG
150 Opening thumbnail image transfer BINARY mode data connection (19738 Bytes) for Thomas.JPG.
226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%) transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.

The client opens a data channel just like any other file transfer, then requests the file using THMB, followed by the output type, 
width, height, and the file name.  The server responds just like a file transfer but also includes the resulting size in 
parentheses.

While designing this command the idea was to first make it simple for both sides, second to make it operate as any other download, 
and third to make it as flexible as possible, allowing the client to decide how the resulting data is to be used and what is needed. 
Of course the server could be configured in any way needed.  For example if the server wanted to limit the size of the thumbnails, 
the server could do that.  Our implementation limits the number of simultaneous threads allowed to create the thumbnails at any 
given time.  I think these details need to be left to the server implementation.

As for using an OPT command to configure an upcoming THMB command for its image type and the thumbnail size, that seems to 
complicate the command.  It's very easy to add these parameters into a single command, eliminating the required handshaking between 
the client and server.  An added benefit is that neither the client nor the server are required to maintain these "options" 
throughout a session, rather all of the information required is sent in a single command.

If you're interested in seeing it in action, download Serv-U and FTP Voyager or SmartFTP.  Login to the server, switch FTP Voyager 
to "Thumbnails" view.  With SmartFTP simply select an image file and a thumbnail image, of dynamic size, will appear in the preview 
pane.

Thank you again for taking the time to provide your feedback.  I look forward to your comments to the above.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "Robert McMurray" <robmcm@microsoft.com>
Sent: Monday, November 22, 2010 5:01 PM
To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>; <mark.peterson@rhinosoft.com>
Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions

[Note: Renaming the thread from 'Submitting new drafts'.]

> Anthony Bryan wrote:
>
> I don't mean to single you out, but
> you showed interest in an CSID/AGNT
> command. Do you have any opinion on
> the other 4 commands in the draft?

Thanks, Anthony.

No worries - I meant to send a better response in the wake of my withdrawn AGNT draft and Mark's current Streamlined FTP Command 
Extensions draft, but I had been remiss at taking the time to collect my thoughts in a more meaningful way. But since you asked, 
this seems like as good at time as any. ;-]

CSID - As evidenced by my short-lived AGNT proposal, I think it's very useful to have some sort of client/server discovery command. 
FEAT does a good job of advertising the list of commands that are supported by a server, but Mark's proposed CSID command sequence 
provides a much better way for servers and client to identify their features to each other in detail. For security reasons I would 
probably want the CSID exchange to occur AFTER the client has logged in, but I might be overreacting.

RMDA - This could be a very useful command, and it would parallel the functionality that I'm sure we all typically use in a native 
operating system environment. In a server implementation I would probably make this command configurable, so administrators would 
have an option to disable the feature. In which case I would probably hide the command from a FEAT response so it would not be 
discoverable and have the server return a 500 or 502 reply when RMDA is sent by the client and disabled at the server.

(Note: I mention my thoughts about server implementation details just to open up the discussion as to whether any implementation 
details should be called out in the draft, or if we should leave that up to the implementers to decide.)

AVBL - This command could be very useful in a client/server world; our FTP server implementation currently returns the available 
size after a successful login sequence, and the available size is based on server disk quotas and such. That being said, not every 
FTP client will bubble that information up to the user interface. Having an AVBL command would make it possible for a client to 
determine whether enough storage space is available at the server BEFORE sending a file, which would be great when you're about to 
send a 10GB file and you only have 9.99GB of storage space left. ;-]

DSIZ - This could certainly be useful, although I would probably want a user to be logged in (not anonymous) before I supported this 
command in order to reduce the risk of denial-of-service. I'd probably make it configurable so as not to tie up too many server 
resources for large directory structures; and once again, if the feature were disabled I would probably hide the command from a FEAT 
response so it would not be discoverable and return a 500 or 502 reply when DSIZ is sent by the client and disabled at the server.

THMB - I have to admit, I don't work on a graphical FTP client, so this command is less useful to me personally, but I can see the 
merit that it might have to someone that designs a graphical client. That being said, I'm not a big fan of computing the thumbnail 
dynamically, nor am I fond of allowing the client to specify the thumbnail format and size. I think that it would be better if the 
server could pre-cache thumbnails for any file type in a server-determined size and image format, and then return the binary data 
and image format information to the client. For example, most graphically-based operating systems have some method for displaying 
file icons to a user that is seated at a computer terminal, so an FTP server implementation could simply return that same icon to a 
client in response to a THMB request.

Please bear in mind, I haven't given a lot of thought as to what the client/server interchange might look like if the server were 
more in control of the response to a THMB request, but it would probably be sufficient to simply return the image type as part of 
the response and let the client determine the image dimensions based on the client's capabilities for reading the image data. (As a 
server guy I like to push any client-friendly processing on the client whenever possible. ;-]) You could borrow an idea from the 
HASH discussion that we've been having and make the thumbnail image type configurable for the client by using an OPTS command, which 
might look like the following examples.

In this first example, the server has a pre-configured thumbnail image type of JPG, and may have pre-cached the thumbnails for 
files; any THMB request with no OPTS specified would use the server's pre-configured thumbnail image type of JPG and image type is 
specified in the command channel response:

  C> THMB widget.png
  S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
  S> 226 Transfer complete.

In these next examples a client is asking for different thumbnail image types by using OPTS commands, and the thumbnail image types 
would still be specified in the command channel responses:

  C> OPTS THMB GIF
  S> 200 OPTS THMB GIF command successful.

  C> THMB widget.psp
  S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
  S> 226 Transfer complete.

  C> OPTS THMB PNG
  S> 200 OPTS THMB PNG command successful.

  C> THMB widget.doc
  S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
  S> 226 Transfer complete.

In this next example a client is asking for an unsupported image type, so the server would simply return the appropriate error 
reply:

  C> OPTS THMB FOO
  S> 501 Unsupported thumbnail format.

In this next example a client is asking for the currently-configured thumbnail image type, so the server would return the 
appropriate response:

  C> OPTS THMB
  S> 200 JPG

You might take this one step further - the server might choose to only support its pre-configured thumbnail image type, thereby 
allowing pre-caching of all thumbnails in one specific image format. In this example a client is asking for PNG thumbnails, which 
SHOULD be a supported image type, but the server only supports a pre-configured thumbnail image type for JPG files and returns the 
appropriate error reply (504?) and the server's pre-configured thumbnail image type is specified in the subsequent command channel 
response to a THMB request:

  C> OPTS THMB PNG
  S> 504 Specifying thumbnail formats is unsupported.

  C> THMB widget.xls
  S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
  S> 226 Transfer complete.

As I said earlier, I hadn't given much thought as to what the client/server THMB interchange might look like if you put the server 
in control instead of the client, but as a server guy I'd rather see THMB look a little more like the examples that I gave. ;-]

Thanks again!

Robert McMurray
robmcm@microsoft.com

_______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext 



From damin@emuxperts.net  Mon Nov 22 20:16:25 2010
Return-Path: <damin@emuxperts.net>
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 A30E728C0E5 for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 20:16:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.676
X-Spam-Level: 
X-Spam-Status: No, score=-1.676 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6]
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 vTrjdNbfLMoT for <ftpext@core3.amsl.com>; Mon, 22 Nov 2010 20:16:22 -0800 (PST)
Received: from ca0.emuxperts.net (ca0.emuxperts.net [96.45.180.106]) by core3.amsl.com (Postfix) with ESMTP id 81CA53A6A0D for <ftpext@ietf.org>; Mon, 22 Nov 2010 20:16:22 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ca0.emuxperts.net (Postfix) with ESMTPSA id 7B1E71FC075 for <ftpext@ietf.org>; Tue, 23 Nov 2010 04:17:17 +0000 (GMT)
Received: by ewy8 with SMTP id 8so4166770ewy.31 for <ftpext@ietf.org>; Mon, 22 Nov 2010 20:17:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.213.8.70 with SMTP id g6mr5897554ebg.44.1290485835610; Mon, 22 Nov 2010 20:17:15 -0800 (PST)
Received: by 10.213.114.139 with HTTP; Mon, 22 Nov 2010 20:17:15 -0800 (PST)
In-Reply-To: <D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com> <D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net>
Date: Mon, 22 Nov 2010 23:17:15 -0500
Message-ID: <AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com>
From: Damin <damin@emuxperts.net>
To: ftpext@ietf.org
Content-Type: multipart/alternative; boundary=0015174bdef6d1bbc50495b0a589
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 04:16:25 -0000

--0015174bdef6d1bbc50495b0a589
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:

> Hi Robert,
>
> Thank you for taking the time to review the commands.  If you don't mind =
I
> would
> like to respond to your comments:
>
> CSID:
> > For security reasons I would probably want the CSID exchange to occur
> AFTER the client has logged in, but I might be overreacting.
>
> There is a lot of discussion on the Internet about servers providing "too=
"
> much information, especially prior to login.  But having
> worked on both sides of the FTP process, it's usually very easy for the
> client to identify what brand or flavor the server is.
> There are details which usually identify the server such as the
> completeness of the FEAT response, the welcome message, responses to
> certain messages, etc.  So, I think it's okay to be available prior to
> login.  I could change the document to read that it should be
> up to the server's implementation whether or not it's available.
>
I prefer to edge on the side of caution. I don=C2=B4t see any good reason t=
hat
this SHOULD be available before login. Commands available prior to login
should be as limited as possible.

>
> RMDA:
> > In a server implementation I would probably make this command
> configurable, so administrators would have an option to disable the
> > feature.  In which case I would probably hide the command from a FEAT
> response so it would not be discoverable and have the server
> > return a 500 or 502 reply when RMDA is sent by the client and disabled =
at
> the server.
>
> I don't think my document specifies that it isn't configurable.  My
> implementation in Serv-U is configurable as is almost all other
> FTP commands.  I think this can be left up to the server implementation.
>  Your possible implementation is exactly how Serv-U
> implements it.  If the feature is disabled, it doesn't appear in the FEAT
> response, nor is it available through the HELP command.
>
>
AVBL:
> > ...
>
> Your comments address the reason for its existence.  The client-side
> implementation in SmartFTP uses the command in this manner.
>
> DSIZ:
> > This could certainly be useful, although I would probably want a user t=
o
> be logged in...
>
> Any information about paths or files requires login in FTP.  I am sure th=
is
> is the case here as well.  If a server wouldn't want the
> "anonymous" user to have access to this command it could be configured to
> disallow this command at the server's implementation or
> configuration.  This should be left up to the implementation of the serve=
r
> or administrator of the server.
>
> > I'd probably make it configurable so as not to tie up too many server
> resources for large directory structures;...
>
> Agreed, the time-consuming nature of the implementation is discussed but
> configuration by an administrator or server-implementation
> is not.   Do you think such verbiage is required?
>

> THMB:
> > I'm not a big fan of computing the thumbnail dynamically, nor am I fond
> of allowing the client to specify the thumbnail format and
> > size.
>
> That's the point of the command, though.  It's to reduce the amount of da=
ta
> that is required to travel over the wire.  The idea is
> to shorten delivery time to the client, letting the client decide what is
> best for the client, not the server.  Some clients may
> want very small images, say for a Windows Explorer style listing, others
> may want larger images (640x480 for example) to show a
> slide show.  I think the client needs to make that determination.  If the
> server decides to cache these generated images it can.
>
> > I think that it would be better if the server could pre-cache thumbnail=
s
> for any file type in a server-determined size and image
> > format, and then return the binary data and image format information to
> the client.
>
> This could waste server-side resources, the client might not even make a
> request for thumbnail images.
>
> > For example, most graphically-based operating systems have some method
> for displaying file icons to a user that is seated at a
> > computer terminal, so an FTP server implementation could simply return
> that same icon to a client in response to a THMB request.
>
> Right, but this isn't really the purpose of this command.  The purpose is
> to take an original image file and reduce it to a
> specified size, not to return the OS's icon representation for that
> particular file type (i.e., not SHGetFileInfo() in Windows).
>
> My proposed implementation is fairly straightforward.  If supported the
> FEAT command replies with THMB and the supported file types.
> When the client wants a thumbnail it asks for it with a single command.
>  Here is a sample result from FTP Voyager and Serv-U:
>
> PORT 192,168,0,30,199,53
> 200 PORT command successful.
> THMB PNG 98 88 Thomas.JPG
> 150 Opening thumbnail image transfer BINARY mode data connection (19738
> Bytes) for Thomas.JPG.
> 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%)
> transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.
>
> The client opens a data channel just like any other file transfer, then
> requests the file using THMB, followed by the output type,
> width, height, and the file name.  The server responds just like a file
> transfer but also includes the resulting size in
> parentheses.
>
> While designing this command the idea was to first make it simple for bot=
h
> sides, second to make it operate as any other download,
> and third to make it as flexible as possible, allowing the client to deci=
de
> how the resulting data is to be used and what is needed.
> Of course the server could be configured in any way needed.  For example =
if
> the server wanted to limit the size of the thumbnails,
> the server could do that.  Our implementation limits the number of
> simultaneous threads allowed to create the thumbnails at any
> given time.  I think these details need to be left to the server
> implementation.
>
> As for using an OPT command to configure an upcoming THMB command for its
> image type and the thumbnail size, that seems to
> complicate the command.  It's very easy to add these parameters into a
> single command, eliminating the required handshaking between
> the client and server.  An added benefit is that neither the client nor t=
he
> server are required to maintain these "options"
> throughout a session, rather all of the information required is sent in a
> single command.
>
> If you're interested in seeing it in action, download Serv-U and FTP
> Voyager or SmartFTP.  Login to the server, switch FTP Voyager
> to "Thumbnails" view.  With SmartFTP simply select an image file and a
> thumbnail image, of dynamic size, will appear in the preview
> pane.
>

> Thank you again for taking the time to provide your feedback.  I look
> forward to your comments to the above.
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Robert McMurray" <robmcm@microsoft.com>
> Sent: Monday, November 22, 2010 5:01 PM
> To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>; <
> mark.peterson@rhinosoft.com>
> Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
> [Note: Renaming the thread from 'Submitting new drafts'.]
>
> > Anthony Bryan wrote:
> >
> > I don't mean to single you out, but
> > you showed interest in an CSID/AGNT
> > command. Do you have any opinion on
> > the other 4 commands in the draft?
>
> Thanks, Anthony.
>
> No worries - I meant to send a better response in the wake of my withdraw=
n
> AGNT draft and Mark's current Streamlined FTP Command
> Extensions draft, but I had been remiss at taking the time to collect my
> thoughts in a more meaningful way. But since you asked,
> this seems like as good at time as any. ;-]
>
> CSID - As evidenced by my short-lived AGNT proposal, I think it's very
> useful to have some sort of client/server discovery command.
> FEAT does a good job of advertising the list of commands that are support=
ed
> by a server, but Mark's proposed CSID command sequence
> provides a much better way for servers and client to identify their
> features to each other in detail. For security reasons I would
> probably want the CSID exchange to occur AFTER the client has logged in,
> but I might be overreacting.
>
> RMDA - This could be a very useful command, and it would parallel the
> functionality that I'm sure we all typically use in a native
> operating system environment. In a server implementation I would probably
> make this command configurable, so administrators would
> have an option to disable the feature. In which case I would probably hid=
e
> the command from a FEAT response so it would not be
> discoverable and have the server return a 500 or 502 reply when RMDA is
> sent by the client and disabled at the server.
>
> (Note: I mention my thoughts about server implementation details just to
> open up the discussion as to whether any implementation
> details should be called out in the draft, or if we should leave that up =
to
> the implementers to decide.)
>
> AVBL - This command could be very useful in a client/server world; our FT=
P
> server implementation currently returns the available
> size after a successful login sequence, and the available size is based o=
n
> server disk quotas and such. That being said, not every
> FTP client will bubble that information up to the user interface. Having =
an
> AVBL command would make it possible for a client to
> determine whether enough storage space is available at the server BEFORE
> sending a file, which would be great when you're about to
> send a 10GB file and you only have 9.99GB of storage space left. ;-]
>
> DSIZ - This could certainly be useful, although I would probably want a
> user to be logged in (not anonymous) before I supported this
> command in order to reduce the risk of denial-of-service. I'd probably ma=
ke
> it configurable so as not to tie up too many server
> resources for large directory structures; and once again, if the feature
> were disabled I would probably hide the command from a FEAT
> response so it would not be discoverable and return a 500 or 502 reply wh=
en
> DSIZ is sent by the client and disabled at the server.
>
> THMB - I have to admit, I don't work on a graphical FTP client, so this
> command is less useful to me personally, but I can see the
> merit that it might have to someone that designs a graphical client. That
> being said, I'm not a big fan of computing the thumbnail
> dynamically, nor am I fond of allowing the client to specify the thumbnai=
l
> format and size. I think that it would be better if the
> server could pre-cache thumbnails for any file type in a server-determine=
d
> size and image format, and then return the binary data
> and image format information to the client. For example, most
> graphically-based operating systems have some method for displaying
> file icons to a user that is seated at a computer terminal, so an FTP
> server implementation could simply return that same icon to a
> client in response to a THMB request.
>
> Please bear in mind, I haven't given a lot of thought as to what the
> client/server interchange might look like if the server were
> more in control of the response to a THMB request, but it would probably =
be
> sufficient to simply return the image type as part of
> the response and let the client determine the image dimensions based on t=
he
> client's capabilities for reading the image data. (As a
> server guy I like to push any client-friendly processing on the client
> whenever possible. ;-]) You could borrow an idea from the
> HASH discussion that we've been having and make the thumbnail image type
> configurable for the client by using an OPTS command, which
> might look like the following examples.
>
> In this first example, the server has a pre-configured thumbnail image ty=
pe
> of JPG, and may have pre-cached the thumbnails for
> files; any THMB request with no OPTS specified would use the server's
> pre-configured thumbnail image type of JPG and image type is
> specified in the command channel response:
>
>  C> THMB widget.png
>  S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
>  S> 226 Transfer complete.
>
> In these next examples a client is asking for different thumbnail image
> types by using OPTS commands, and the thumbnail image types
> would still be specified in the command channel responses:
>
>  C> OPTS THMB GIF
>  S> 200 OPTS THMB GIF command successful.
>
>  C> THMB widget.psp
>  S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
>  S> 226 Transfer complete.
>
>  C> OPTS THMB PNG
>  S> 200 OPTS THMB PNG command successful.
>
>  C> THMB widget.doc
>  S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
>  S> 226 Transfer complete.
>
> In this next example a client is asking for an unsupported image type, so
> the server would simply return the appropriate error
> reply:
>
>  C> OPTS THMB FOO
>  S> 501 Unsupported thumbnail format.
>
> In this next example a client is asking for the currently-configured
> thumbnail image type, so the server would return the
> appropriate response:
>
>  C> OPTS THMB
>  S> 200 JPG
>
> You might take this one step further - the server might choose to only
> support its pre-configured thumbnail image type, thereby
> allowing pre-caching of all thumbnails in one specific image format. In
> this example a client is asking for PNG thumbnails, which
> SHOULD be a supported image type, but the server only supports a
> pre-configured thumbnail image type for JPG files and returns the
> appropriate error reply (504?) and the server's pre-configured thumbnail
> image type is specified in the subsequent command channel
> response to a THMB request:
>
>  C> OPTS THMB PNG
>  S> 504 Specifying thumbnail formats is unsupported.
>
>  C> THMB widget.xls
>  S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
>  S> 226 Transfer complete.
>
> As I said earlier, I hadn't given much thought as to what the client/serv=
er
> THMB interchange might look like if you put the server
> in control instead of the client, but as a server guy I'd rather see THMB
> look a little more like the examples that I gave. ;-]
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

--0015174bdef6d1bbc50495b0a589
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<br><br><div class=3D"gmail_quote">On 22 November 2010 19:32, Mark P. Pe=
terson <span dir=3D"ltr">&lt;<a href=3D"mailto:mpp@rhinosoft.com">mpp@rhino=
soft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); p=
adding-left: 1ex;">
Hi Robert,<br>
<br>
Thank you for taking the time to review the commands. =C2=A0If you don&#39;=
t mind I would<br>
like to respond to your comments:<br>
<br>
CSID:<br>
<div class=3D"im">&gt; For security reasons I would probably want the CSID =
exchange to occur AFTER the client has logged in, but I might be overreacti=
ng.<br>
<br>
</div>There is a lot of discussion on the Internet about servers providing =
&quot;too&quot; much information, especially prior to login. =C2=A0But havi=
ng<br>
worked on both sides of the FTP process, it&#39;s usually very easy for the=
 client to identify what brand or flavor the server is.<br>
There are details which usually identify the server such as the completenes=
s of the FEAT response, the welcome message, responses to<br>
certain messages, etc. =C2=A0So, I think it&#39;s okay to be available prio=
r to login. =C2=A0I could change the document to read that it should be<br>
up to the server&#39;s implementation whether or not it&#39;s available.<br=
></blockquote><div>I prefer to edge on the side of caution. I don=C2=B4t se=
e any good reason that this SHOULD be available before login. Commands avai=
lable prior to login should be as limited as possible.<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex;=
 border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
RMDA:<br>
<div class=3D"im">&gt; In a server implementation I would probably make thi=
s command configurable, so administrators would have an option to disable t=
he<br>
&gt; feature. =C2=A0In which case I would probably hide the command from a =
FEAT response so it would not be discoverable and have the server<br>
&gt; return a 500 or 502 reply when RMDA is sent by the client and disabled=
 at the server.<br>
<br>
</div>I don&#39;t think my document specifies that it isn&#39;t configurabl=
e. =C2=A0My implementation in Serv-U is configurable as is almost all other=
<br>
FTP commands. =C2=A0I think this can be left up to the server implementatio=
n. =C2=A0Your possible implementation is exactly how Serv-U<br>
implements it. =C2=A0If the feature is disabled, it doesn&#39;t appear in t=
he FEAT response, nor is it available through the HELP command.<br>
=C2=A0<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: =
1ex;">
AVBL:<br>
&gt; ...<br>
<br>
Your comments address the reason for its existence. =C2=A0The client-side i=
mplementation in SmartFTP uses the command in this manner.<br>
<br>
DSIZ:<br>
&gt; This could certainly be useful, although I would probably want a user =
to be logged in...<br>
<br>
Any information about paths or files requires login in FTP. =C2=A0I am sure=
 this is the case here as well. =C2=A0If a server wouldn&#39;t want the<br>
&quot;anonymous&quot; user to have access to this command it could be confi=
gured to disallow this command at the server&#39;s implementation or<br>
configuration. =C2=A0This should be left up to the implementation of the se=
rver or administrator of the server.<br>
<br>
&gt; I&#39;d probably make it configurable so as not to tie up too many ser=
ver resources for large directory structures;...<br>
<br>
Agreed, the time-consuming nature of the implementation is discussed but co=
nfiguration by an administrator or server-implementation<br>
is not. =C2=A0 Do you think such verbiage is required?=C2=A0<br></blockquot=
e><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; bor=
der-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
THMB:<br>
<div class=3D"im">&gt; I&#39;m not a big fan of computing the thumbnail dyn=
amically, nor am I fond of allowing the client to specify the thumbnail for=
mat and<br>
&gt; size.<br>
<br>
</div>That&#39;s the point of the command, though. =C2=A0It&#39;s to reduce=
 the amount of data that is required to travel over the wire. =C2=A0The ide=
a is<br>
to shorten delivery time to the client, letting the client decide what is b=
est for the client, not the server. =C2=A0Some clients may<br>
want very small images, say for a Windows Explorer style listing, others ma=
y want larger images (640x480 for example) to show a<br>
slide show. =C2=A0I think the client needs to make that determination. =C2=
=A0If the server decides to cache these generated images it can.<br>
<div class=3D"im"><br>
&gt; I think that it would be better if the server could pre-cache thumbnai=
ls for any file type in a server-determined size and image<br>
&gt; format, and then return the binary data and image format information t=
o the client.<br>
<br>
</div>This could waste server-side resources, the client might not even mak=
e a request for thumbnail images.<br>
<div class=3D"im"><br>
&gt; For example, most graphically-based operating systems have some method=
 for displaying file icons to a user that is seated at a<br>
&gt; computer terminal, so an FTP server implementation could simply return=
 that same icon to a client in response to a THMB request.<br>
<br>
</div>Right, but this isn&#39;t really the purpose of this command. =C2=A0T=
he purpose is to take an original image file and reduce it to a<br>
specified size, not to return the OS&#39;s icon representation for that par=
ticular file type (i.e., not SHGetFileInfo() in Windows).<br>
<br>
My proposed implementation is fairly straightforward. =C2=A0If supported th=
e FEAT command replies with THMB and the supported file types.<br>
When the client wants a thumbnail it asks for it with a single command. =C2=
=A0Here is a sample result from FTP Voyager and Serv-U:<br>
<br>
PORT 192,168,0,30,199,53<br>
200 PORT command successful.<br>
THMB PNG 98 88 Thomas.JPG<br>
150 Opening thumbnail image transfer BINARY mode data connection (19738 Byt=
es) for Thomas.JPG.<br>
226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%) transfer=
red. 19.29 actual KB/sec, =C2=A019.28 effective KB/sec.<br>
<br>
The client opens a data channel just like any other file transfer, then req=
uests the file using THMB, followed by the output type,<br>
width, height, and the file name. =C2=A0The server responds just like a fil=
e transfer but also includes the resulting size in<br>
parentheses.<br>
<br>
While designing this command the idea was to first make it simple for both =
sides, second to make it operate as any other download,<br>
and third to make it as flexible as possible, allowing the client to decide=
 how the resulting data is to be used and what is needed.<br>
Of course the server could be configured in any way needed. =C2=A0For examp=
le if the server wanted to limit the size of the thumbnails,<br>
the server could do that. =C2=A0Our implementation limits the number of sim=
ultaneous threads allowed to create the thumbnails at any<br>
given time. =C2=A0I think these details need to be left to the server imple=
mentation.<br>
<br>
As for using an OPT command to configure an upcoming THMB command for its i=
mage type and the thumbnail size, that seems to<br>
complicate the command. =C2=A0It&#39;s very easy to add these parameters in=
to a single command, eliminating the required handshaking between<br>
the client and server. =C2=A0An added benefit is that neither the client no=
r the server are required to maintain these &quot;options&quot;<br>
throughout a session, rather all of the information required is sent in a s=
ingle command.<br>
<br>
If you&#39;re interested in seeing it in action, download Serv-U and FTP Vo=
yager or SmartFTP. =C2=A0Login to the server, switch FTP Voyager<br>
to &quot;Thumbnails&quot; view. =C2=A0With SmartFTP simply select an image =
file and a thumbnail image, of dynamic size, will appear in the preview<br>
pane.<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin: 0p=
t 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1=
ex;">
<br>
Thank you again for taking the time to provide your feedback. =C2=A0I look =
forward to your comments to the above.<br>
<br>
Mark P. Peterson - President<br>
<a href=3D"http://www.RhinoSoft.com" target=3D"_blank">http://www.RhinoSoft=
.com</a><br>
Voice: +1(262) 560-9627<br>
FAX: +1(262) 560-9628<br>
<br>
<br>
--------------------------------------------------<br>
From: &quot;Robert McMurray&quot; &lt;<a href=3D"mailto:robmcm@microsoft.co=
m">robmcm@microsoft.com</a>&gt;<br>
Sent: Monday, November 22, 2010 5:01 PM<br>
To: &lt;<a href=3D"mailto:ftpext@ietf.org">ftpext@ietf.org</a>&gt;; &quot;&=
#39;Anthony Bryan&#39;&quot; &lt;<a href=3D"mailto:anthonybryan@gmail.com">=
anthonybryan@gmail.com</a>&gt;; &lt;<a href=3D"mailto:mark.peterson@rhinoso=
ft.com">mark.peterson@rhinosoft.com</a>&gt;<br>

Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions<br>
<div><div></div><div class=3D"h5"><br>
[Note: Renaming the thread from &#39;Submitting new drafts&#39;.]<br>
<br>
&gt; Anthony Bryan wrote:<br>
&gt;<br>
&gt; I don&#39;t mean to single you out, but<br>
&gt; you showed interest in an CSID/AGNT<br>
&gt; command. Do you have any opinion on<br>
&gt; the other 4 commands in the draft?<br>
<br>
Thanks, Anthony.<br>
<br>
No worries - I meant to send a better response in the wake of my withdrawn =
AGNT draft and Mark&#39;s current Streamlined FTP Command<br>
Extensions draft, but I had been remiss at taking the time to collect my th=
oughts in a more meaningful way. But since you asked,<br>
this seems like as good at time as any. ;-]<br>
<br>
CSID - As evidenced by my short-lived AGNT proposal, I think it&#39;s very =
useful to have some sort of client/server discovery command.<br>
FEAT does a good job of advertising the list of commands that are supported=
 by a server, but Mark&#39;s proposed CSID command sequence<br>
provides a much better way for servers and client to identify their feature=
s to each other in detail. For security reasons I would<br>
probably want the CSID exchange to occur AFTER the client has logged in, bu=
t I might be overreacting.<br>
<br>
RMDA - This could be a very useful command, and it would parallel the funct=
ionality that I&#39;m sure we all typically use in a native<br>
operating system environment. In a server implementation I would probably m=
ake this command configurable, so administrators would<br>
have an option to disable the feature. In which case I would probably hide =
the command from a FEAT response so it would not be<br>
discoverable and have the server return a 500 or 502 reply when RMDA is sen=
t by the client and disabled at the server.<br>
<br>
(Note: I mention my thoughts about server implementation details just to op=
en up the discussion as to whether any implementation<br>
details should be called out in the draft, or if we should leave that up to=
 the implementers to decide.)<br>
<br>
AVBL - This command could be very useful in a client/server world; our FTP =
server implementation currently returns the available<br>
size after a successful login sequence, and the available size is based on =
server disk quotas and such. That being said, not every<br>
FTP client will bubble that information up to the user interface. Having an=
 AVBL command would make it possible for a client to<br>
determine whether enough storage space is available at the server BEFORE se=
nding a file, which would be great when you&#39;re about to<br>
send a 10GB file and you only have 9.99GB of storage space left. ;-]<br>
<br>
DSIZ - This could certainly be useful, although I would probably want a use=
r to be logged in (not anonymous) before I supported this<br>
command in order to reduce the risk of denial-of-service. I&#39;d probably =
make it configurable so as not to tie up too many server<br>
resources for large directory structures; and once again, if the feature we=
re disabled I would probably hide the command from a FEAT<br>
response so it would not be discoverable and return a 500 or 502 reply when=
 DSIZ is sent by the client and disabled at the server.<br>
<br>
THMB - I have to admit, I don&#39;t work on a graphical FTP client, so this=
 command is less useful to me personally, but I can see the<br>
merit that it might have to someone that designs a graphical client. That b=
eing said, I&#39;m not a big fan of computing the thumbnail<br>
dynamically, nor am I fond of allowing the client to specify the thumbnail =
format and size. I think that it would be better if the<br>
server could pre-cache thumbnails for any file type in a server-determined =
size and image format, and then return the binary data<br>
and image format information to the client. For example, most graphically-b=
ased operating systems have some method for displaying<br>
file icons to a user that is seated at a computer terminal, so an FTP serve=
r implementation could simply return that same icon to a<br>
client in response to a THMB request.<br>
<br>
Please bear in mind, I haven&#39;t given a lot of thought as to what the cl=
ient/server interchange might look like if the server were<br>
more in control of the response to a THMB request, but it would probably be=
 sufficient to simply return the image type as part of<br>
the response and let the client determine the image dimensions based on the=
 client&#39;s capabilities for reading the image data. (As a<br>
server guy I like to push any client-friendly processing on the client when=
ever possible. ;-]) You could borrow an idea from the<br>
HASH discussion that we&#39;ve been having and make the thumbnail image typ=
e configurable for the client by using an OPTS command, which<br>
might look like the following examples.<br>
<br>
In this first example, the server has a pre-configured thumbnail image type=
 of JPG, and may have pre-cached the thumbnails for<br>
files; any THMB request with no OPTS specified would use the server&#39;s p=
re-configured thumbnail image type of JPG and image type is<br>
specified in the command channel response:<br>
<br>
 =C2=A0C&gt; THMB widget.png<br>
 =C2=A0S&gt; 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.pn=
g<br>
 =C2=A0S&gt; 226 Transfer complete.<br>
<br>
In these next examples a client is asking for different thumbnail image typ=
es by using OPTS commands, and the thumbnail image types<br>
would still be specified in the command channel responses:<br>
<br>
 =C2=A0C&gt; OPTS THMB GIF<br>
 =C2=A0S&gt; 200 OPTS THMB GIF command successful.<br>
<br>
 =C2=A0C&gt; THMB widget.psp<br>
 =C2=A0S&gt; 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.ps=
p<br>
 =C2=A0S&gt; 226 Transfer complete.<br>
<br>
 =C2=A0C&gt; OPTS THMB PNG<br>
 =C2=A0S&gt; 200 OPTS THMB PNG command successful.<br>
<br>
 =C2=A0C&gt; THMB widget.doc<br>
 =C2=A0S&gt; 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.do=
c<br>
 =C2=A0S&gt; 226 Transfer complete.<br>
<br>
In this next example a client is asking for an unsupported image type, so t=
he server would simply return the appropriate error<br>
reply:<br>
<br>
 =C2=A0C&gt; OPTS THMB FOO<br>
 =C2=A0S&gt; 501 Unsupported thumbnail format.<br>
<br>
In this next example a client is asking for the currently-configured thumbn=
ail image type, so the server would return the<br>
appropriate response:<br>
<br>
 =C2=A0C&gt; OPTS THMB<br>
 =C2=A0S&gt; 200 JPG<br>
<br>
You might take this one step further - the server might choose to only supp=
ort its pre-configured thumbnail image type, thereby<br>
allowing pre-caching of all thumbnails in one specific image format. In thi=
s example a client is asking for PNG thumbnails, which<br>
SHOULD be a supported image type, but the server only supports a pre-config=
ured thumbnail image type for JPG files and returns the<br>
appropriate error reply (504?) and the server&#39;s pre-configured thumbnai=
l image type is specified in the subsequent command channel<br>
response to a THMB request:<br>
<br>
 =C2=A0C&gt; OPTS THMB PNG<br>
 =C2=A0S&gt; 504 Specifying thumbnail formats is unsupported.<br>
<br>
 =C2=A0C&gt; THMB widget.xls<br>
 =C2=A0S&gt; 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xl=
s<br>
 =C2=A0S&gt; 226 Transfer complete.<br>
<br>
As I said earlier, I hadn&#39;t given much thought as to what the client/se=
rver THMB interchange might look like if you put the server<br>
in control instead of the client, but as a server guy I&#39;d rather see TH=
MB look a little more like the examples that I gave. ;-]<br>
<br>
Thanks again!<br>
<br>
Robert McMurray<br>
<a href=3D"mailto:robmcm@microsoft.com">robmcm@microsoft.com</a><br>
<br>
_______________________________________________<br>
ftpext mailing list<br>
<a href=3D"mailto:ftpext@ietf.org">ftpext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ftpext" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/ftpext</a><br>
<br>
<br>
_______________________________________________<br>
ftpext mailing list<br>
<a href=3D"mailto:ftpext@ietf.org">ftpext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ftpext" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/ftpext</a><br>
</div></div></blockquote></div><br>

--0015174bdef6d1bbc50495b0a589--

From prvs=19431281bb=mpp@rhinosoft.com  Tue Nov 23 04:52:16 2010
Return-Path: <prvs=19431281bb=mpp@rhinosoft.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 EBFF13A6939 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 04:52:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.824
X-Spam-Level: 
X-Spam-Status: No, score=-1.824 tagged_above=-999 required=5 tests=[AWL=0.175,  BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
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 2xck7wcGrJP7 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 04:52:11 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id 0F23E3A693E for <ftpext@ietf.org>; Tue, 23 Nov 2010 04:52:10 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009935213.msg for <ftpext@ietf.org>; Tue, 23 Nov 2010 06:53:06 -0600
X-Spam-Processed: rhinosoft.com, Tue, 23 Nov 2010 06:53:06 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=19431281bb=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <914CA95DAC22422C825C665E4E76F860@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "Damin" <damin@emuxperts.net>, <ftpext@ietf.org>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net> <AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com>
In-Reply-To: <AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com>
Date: Tue, 23 Nov 2010 06:52:58 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 12:52:17 -0000

Hi All,

Is there anyone else that agrees with Damin about CSID?  He says it SHOULD be available only after login.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628



From: Damin
Sent: Monday, November 22, 2010 10:17 PM
To: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions


Hi,


On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:

Hi Robert,

Thank you for taking the time to review the commands.  If you don't mind I would
like to respond to your comments:

CSID:

> For security reasons I would probably want the CSID exchange to occur AFTER the client has logged in, but I might be overreacting.


There is a lot of discussion on the Internet about servers providing "too" much information, especially prior to login.  But having
worked on both sides of the FTP process, it's usually very easy for the client to identify what brand or flavor the server is.
There are details which usually identify the server such as the completeness of the FEAT response, the welcome message, responses to
certain messages, etc.  So, I think it's okay to be available prior to login.  I could change the document to read that it should be
up to the server's implementation whether or not it's available.

I prefer to edge on the side of caution. I donÂīt see any good reason that this SHOULD be available before login. Commands available 
prior to login should be as limited as possible.


RMDA:

> In a server implementation I would probably make this command configurable, so administrators would have an option to disable the
> feature.  In which case I would probably hide the command from a FEAT response so it would not be discoverable and have the server
> return a 500 or 502 reply when RMDA is sent by the client and disabled at the server.


I don't think my document specifies that it isn't configurable.  My implementation in Serv-U is configurable as is almost all other
FTP commands.  I think this can be left up to the server implementation.  Your possible implementation is exactly how Serv-U
implements it.  If the feature is disabled, it doesn't appear in the FEAT response, nor is it available through the HELP command.


AVBL:
> ...

Your comments address the reason for its existence.  The client-side implementation in SmartFTP uses the command in this manner.

DSIZ:
> This could certainly be useful, although I would probably want a user to be logged in...

Any information about paths or files requires login in FTP.  I am sure this is the case here as well.  If a server wouldn't want the
"anonymous" user to have access to this command it could be configured to disallow this command at the server's implementation or
configuration.  This should be left up to the implementation of the server or administrator of the server.

> I'd probably make it configurable so as not to tie up too many server resources for large directory structures;...

Agreed, the time-consuming nature of the implementation is discussed but configuration by an administrator or server-implementation
is not.   Do you think such verbiage is required?


THMB:

> I'm not a big fan of computing the thumbnail dynamically, nor am I fond of allowing the client to specify the thumbnail format and
> size.


That's the point of the command, though.  It's to reduce the amount of data that is required to travel over the wire.  The idea is
to shorten delivery time to the client, letting the client decide what is best for the client, not the server.  Some clients may
want very small images, say for a Windows Explorer style listing, others may want larger images (640x480 for example) to show a
slide show.  I think the client needs to make that determination.  If the server decides to cache these generated images it can.


> I think that it would be better if the server could pre-cache thumbnails for any file type in a server-determined size and image
> format, and then return the binary data and image format information to the client.


This could waste server-side resources, the client might not even make a request for thumbnail images.


> For example, most graphically-based operating systems have some method for displaying file icons to a user that is seated at a
> computer terminal, so an FTP server implementation could simply return that same icon to a client in response to a THMB request.


Right, but this isn't really the purpose of this command.  The purpose is to take an original image file and reduce it to a
specified size, not to return the OS's icon representation for that particular file type (i.e., not SHGetFileInfo() in Windows).

My proposed implementation is fairly straightforward.  If supported the FEAT command replies with THMB and the supported file types.
When the client wants a thumbnail it asks for it with a single command.  Here is a sample result from FTP Voyager and Serv-U:

PORT 192,168,0,30,199,53
200 PORT command successful.
THMB PNG 98 88 Thomas.JPG
150 Opening thumbnail image transfer BINARY mode data connection (19738 Bytes) for Thomas.JPG.
226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%) transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.

The client opens a data channel just like any other file transfer, then requests the file using THMB, followed by the output type,
width, height, and the file name.  The server responds just like a file transfer but also includes the resulting size in
parentheses.

While designing this command the idea was to first make it simple for both sides, second to make it operate as any other download,
and third to make it as flexible as possible, allowing the client to decide how the resulting data is to be used and what is needed.
Of course the server could be configured in any way needed.  For example if the server wanted to limit the size of the thumbnails,
the server could do that.  Our implementation limits the number of simultaneous threads allowed to create the thumbnails at any
given time.  I think these details need to be left to the server implementation.

As for using an OPT command to configure an upcoming THMB command for its image type and the thumbnail size, that seems to
complicate the command.  It's very easy to add these parameters into a single command, eliminating the required handshaking between
the client and server.  An added benefit is that neither the client nor the server are required to maintain these "options"
throughout a session, rather all of the information required is sent in a single command.

If you're interested in seeing it in action, download Serv-U and FTP Voyager or SmartFTP.  Login to the server, switch FTP Voyager
to "Thumbnails" view.  With SmartFTP simply select an image file and a thumbnail image, of dynamic size, will appear in the preview
pane.


Thank you again for taking the time to provide your feedback.  I look forward to your comments to the above.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "Robert McMurray" <robmcm@microsoft.com>
Sent: Monday, November 22, 2010 5:01 PM
To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>; <mark.peterson@rhinosoft.com>
Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions


[Note: Renaming the thread from 'Submitting new drafts'.]

> Anthony Bryan wrote:
>
> I don't mean to single you out, but
> you showed interest in an CSID/AGNT
> command. Do you have any opinion on
> the other 4 commands in the draft?

Thanks, Anthony.

No worries - I meant to send a better response in the wake of my withdrawn AGNT draft and Mark's current Streamlined FTP Command
Extensions draft, but I had been remiss at taking the time to collect my thoughts in a more meaningful way. But since you asked,
this seems like as good at time as any. ;-]

CSID - As evidenced by my short-lived AGNT proposal, I think it's very useful to have some sort of client/server discovery command.
FEAT does a good job of advertising the list of commands that are supported by a server, but Mark's proposed CSID command sequence
provides a much better way for servers and client to identify their features to each other in detail. For security reasons I would
probably want the CSID exchange to occur AFTER the client has logged in, but I might be overreacting.

RMDA - This could be a very useful command, and it would parallel the functionality that I'm sure we all typically use in a native
operating system environment. In a server implementation I would probably make this command configurable, so administrators would
have an option to disable the feature. In which case I would probably hide the command from a FEAT response so it would not be
discoverable and have the server return a 500 or 502 reply when RMDA is sent by the client and disabled at the server.

(Note: I mention my thoughts about server implementation details just to open up the discussion as to whether any implementation
details should be called out in the draft, or if we should leave that up to the implementers to decide.)

AVBL - This command could be very useful in a client/server world; our FTP server implementation currently returns the available
size after a successful login sequence, and the available size is based on server disk quotas and such. That being said, not every
FTP client will bubble that information up to the user interface. Having an AVBL command would make it possible for a client to
determine whether enough storage space is available at the server BEFORE sending a file, which would be great when you're about to
send a 10GB file and you only have 9.99GB of storage space left. ;-]

DSIZ - This could certainly be useful, although I would probably want a user to be logged in (not anonymous) before I supported this
command in order to reduce the risk of denial-of-service. I'd probably make it configurable so as not to tie up too many server
resources for large directory structures; and once again, if the feature were disabled I would probably hide the command from a FEAT
response so it would not be discoverable and return a 500 or 502 reply when DSIZ is sent by the client and disabled at the server.

THMB - I have to admit, I don't work on a graphical FTP client, so this command is less useful to me personally, but I can see the
merit that it might have to someone that designs a graphical client. That being said, I'm not a big fan of computing the thumbnail
dynamically, nor am I fond of allowing the client to specify the thumbnail format and size. I think that it would be better if the
server could pre-cache thumbnails for any file type in a server-determined size and image format, and then return the binary data
and image format information to the client. For example, most graphically-based operating systems have some method for displaying
file icons to a user that is seated at a computer terminal, so an FTP server implementation could simply return that same icon to a
client in response to a THMB request.

Please bear in mind, I haven't given a lot of thought as to what the client/server interchange might look like if the server were
more in control of the response to a THMB request, but it would probably be sufficient to simply return the image type as part of
the response and let the client determine the image dimensions based on the client's capabilities for reading the image data. (As a
server guy I like to push any client-friendly processing on the client whenever possible. ;-]) You could borrow an idea from the
HASH discussion that we've been having and make the thumbnail image type configurable for the client by using an OPTS command, which
might look like the following examples.

In this first example, the server has a pre-configured thumbnail image type of JPG, and may have pre-cached the thumbnails for
files; any THMB request with no OPTS specified would use the server's pre-configured thumbnail image type of JPG and image type is
specified in the command channel response:

 C> THMB widget.png
 S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
 S> 226 Transfer complete.

In these next examples a client is asking for different thumbnail image types by using OPTS commands, and the thumbnail image types
would still be specified in the command channel responses:

 C> OPTS THMB GIF
 S> 200 OPTS THMB GIF command successful.

 C> THMB widget.psp
 S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
 S> 226 Transfer complete.

 C> OPTS THMB PNG
 S> 200 OPTS THMB PNG command successful.

 C> THMB widget.doc
 S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
 S> 226 Transfer complete.

In this next example a client is asking for an unsupported image type, so the server would simply return the appropriate error
reply:

 C> OPTS THMB FOO
 S> 501 Unsupported thumbnail format.

In this next example a client is asking for the currently-configured thumbnail image type, so the server would return the
appropriate response:

 C> OPTS THMB
 S> 200 JPG

You might take this one step further - the server might choose to only support its pre-configured thumbnail image type, thereby
allowing pre-caching of all thumbnails in one specific image format. In this example a client is asking for PNG thumbnails, which
SHOULD be a supported image type, but the server only supports a pre-configured thumbnail image type for JPG files and returns the
appropriate error reply (504?) and the server's pre-configured thumbnail image type is specified in the subsequent command channel
response to a THMB request:

 C> OPTS THMB PNG
 S> 504 Specifying thumbnail formats is unsupported.

 C> THMB widget.xls
 S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
 S> 226 Transfer complete.

As I said earlier, I hadn't given much thought as to what the client/server THMB interchange might look like if you put the server
in control instead of the client, but as a server guy I'd rather see THMB look a little more like the examples that I gave. ;-]

Thanks again!

Robert McMurray
robmcm@microsoft.com

_______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext


_______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext






_______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext 



From wmaton@ottix.net  Tue Nov 23 05:54:23 2010
Return-Path: <wmaton@ottix.net>
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 4D9333A695F for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 05:54:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
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 627aM+tKGAoV for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 05:54:21 -0800 (PST)
Received: from iskra.ottix.net (iskra.ottix.net [IPv6:2001:410:90ff::2]) by core3.amsl.com (Postfix) with ESMTP id B22D33A6947 for <ftpext@ietf.org>; Tue, 23 Nov 2010 05:54:19 -0800 (PST)
Received: from iskra.ottix.net (localhost [127.0.0.1]) by iskra.ottix.net (8.14.4/8.14.4) with ESMTP id oANDtANM026294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2010 08:55:10 -0500
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 iskra.ottix.net oANDtANM026294
Received: from localhost (wmaton@localhost) by iskra.ottix.net (8.14.4/8.14.3/Submit) with ESMTP id oANDt8vU026282;  Tue, 23 Nov 2010 08:55:08 -0500
Date: Tue, 23 Nov 2010 08:55:08 -0500 (EST)
From: "William F. Maton" <wmaton@ottix.net>
To: "Mark P. Peterson" <mpp@rhinosoft.com>
In-Reply-To: <914CA95DAC22422C825C665E4E76F860@rhinooffice.net>
Message-ID: <Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net> <AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com> <914CA95DAC22422C825C665E4E76F860@rhinooffice.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-406846748-504006563-1290520508=:6921"
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 13:54:23 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---406846748-504006563-1290520508=:6921
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Tue, 23 Nov 2010, Mark P. Peterson wrote:

> Hi All,
>
> Is there anyone else that agrees with Damin about CSID?  He says it SHOUL=
D be available only after login.

Hi Mark,
 =09I'm certainly and old enough salt at systems administration to=20
think that identification before authentication or authorization is not a=
=20
good thing.  It makes it easier for the scanners to pick-off what servers=
=20
are running.  I'd like to force them into making the extra effort, since=20
it might as well cost them more work and I can monitor the activity=20
better.

 =09I think standardizing CSID (from the old non-standard CLNT) is a=20
good thing though.  It should be left up to the implementor to support it.

 =09I've also read he rest of that I-D and have more thoughts on it,=20
but that's for another email.


> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
>
> From: Damin
> Sent: Monday, November 22, 2010 10:17 PM
> To: ftpext@ietf.org
> Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> Hi,
>
>
> On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:
>
> Hi Robert,
>
> Thank you for taking the time to review the commands.  If you don't mind =
I would
> like to respond to your comments:
>
> CSID:
>
>> For security reasons I would probably want the CSID exchange to occur AF=
TER the client has logged in, but I might be overreacting.
>
>
> There is a lot of discussion on the Internet about servers providing "too=
" much information, especially prior to login.  But having
> worked on both sides of the FTP process, it's usually very easy for the c=
lient to identify what brand or flavor the server is.
> There are details which usually identify the server such as the completen=
ess of the FEAT response, the welcome message, responses to
> certain messages, etc.  So, I think it's okay to be available prior to lo=
gin.  I could change the document to read that it should be
> up to the server's implementation whether or not it's available.
>
> I prefer to edge on the side of caution. I don=C2=B4t see any good reason=
 that this SHOULD be available before login. Commands available
> prior to login should be as limited as possible.
>
>
> RMDA:
>
>> In a server implementation I would probably make this command configurab=
le, so administrators would have an option to disable the
>> feature.  In which case I would probably hide the command from a FEAT re=
sponse so it would not be discoverable and have the server
>> return a 500 or 502 reply when RMDA is sent by the client and disabled a=
t the server.
>
>
> I don't think my document specifies that it isn't configurable.  My imple=
mentation in Serv-U is configurable as is almost all other
> FTP commands.  I think this can be left up to the server implementation. =
 Your possible implementation is exactly how Serv-U
> implements it.  If the feature is disabled, it doesn't appear in the FEAT=
 response, nor is it available through the HELP command.
>
>
> AVBL:
>> ...
>
> Your comments address the reason for its existence.  The client-side impl=
ementation in SmartFTP uses the command in this manner.
>
> DSIZ:
>> This could certainly be useful, although I would probably want a user to=
 be logged in...
>
> Any information about paths or files requires login in FTP.  I am sure th=
is is the case here as well.  If a server wouldn't want the
> "anonymous" user to have access to this command it could be configured to=
 disallow this command at the server's implementation or
> configuration.  This should be left up to the implementation of the serve=
r or administrator of the server.
>
>> I'd probably make it configurable so as not to tie up too many server re=
sources for large directory structures;...
>
> Agreed, the time-consuming nature of the implementation is discussed but =
configuration by an administrator or server-implementation
> is not.   Do you think such verbiage is required?
>
>
> THMB:
>
>> I'm not a big fan of computing the thumbnail dynamically, nor am I fond =
of allowing the client to specify the thumbnail format and
>> size.
>
>
> That's the point of the command, though.  It's to reduce the amount of da=
ta that is required to travel over the wire.  The idea is
> to shorten delivery time to the client, letting the client decide what is=
 best for the client, not the server.  Some clients may
> want very small images, say for a Windows Explorer style listing, others =
may want larger images (640x480 for example) to show a
> slide show.  I think the client needs to make that determination.  If the=
 server decides to cache these generated images it can.
>
>
>> I think that it would be better if the server could pre-cache thumbnails=
 for any file type in a server-determined size and image
>> format, and then return the binary data and image format information to =
the client.
>
>
> This could waste server-side resources, the client might not even make a =
request for thumbnail images.
>
>
>> For example, most graphically-based operating systems have some method f=
or displaying file icons to a user that is seated at a
>> computer terminal, so an FTP server implementation could simply return t=
hat same icon to a client in response to a THMB request.
>
>
> Right, but this isn't really the purpose of this command.  The purpose is=
 to take an original image file and reduce it to a
> specified size, not to return the OS's icon representation for that parti=
cular file type (i.e., not SHGetFileInfo() in Windows).
>
> My proposed implementation is fairly straightforward.  If supported the F=
EAT command replies with THMB and the supported file types.
> When the client wants a thumbnail it asks for it with a single command.  =
Here is a sample result from FTP Voyager and Serv-U:
>
> PORT 192,168,0,30,199,53
> 200 PORT command successful.
> THMB PNG 98 88 Thomas.JPG
> 150 Opening thumbnail image transfer BINARY mode data connection (19738 B=
ytes) for Thomas.JPG.
> 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%) transf=
erred. 19.29 actual KB/sec,  19.28 effective KB/sec.
>
> The client opens a data channel just like any other file transfer, then r=
equests the file using THMB, followed by the output type,
> width, height, and the file name.  The server responds just like a file t=
ransfer but also includes the resulting size in
> parentheses.
>
> While designing this command the idea was to first make it simple for bot=
h sides, second to make it operate as any other download,
> and third to make it as flexible as possible, allowing the client to deci=
de how the resulting data is to be used and what is needed.
> Of course the server could be configured in any way needed.  For example =
if the server wanted to limit the size of the thumbnails,
> the server could do that.  Our implementation limits the number of simult=
aneous threads allowed to create the thumbnails at any
> given time.  I think these details need to be left to the server implemen=
tation.
>
> As for using an OPT command to configure an upcoming THMB command for its=
 image type and the thumbnail size, that seems to
> complicate the command.  It's very easy to add these parameters into a si=
ngle command, eliminating the required handshaking between
> the client and server.  An added benefit is that neither the client nor t=
he server are required to maintain these "options"
> throughout a session, rather all of the information required is sent in a=
 single command.
>
> If you're interested in seeing it in action, download Serv-U and FTP Voya=
ger or SmartFTP.  Login to the server, switch FTP Voyager
> to "Thumbnails" view.  With SmartFTP simply select an image file and a th=
umbnail image, of dynamic size, will appear in the preview
> pane.
>
>
> Thank you again for taking the time to provide your feedback.  I look for=
ward to your comments to the above.
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Robert McMurray" <robmcm@microsoft.com>
> Sent: Monday, November 22, 2010 5:01 PM
> To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>; <mark.=
peterson@rhinosoft.com>
> Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> [Note: Renaming the thread from 'Submitting new drafts'.]
>
>> Anthony Bryan wrote:
>>
>> I don't mean to single you out, but
>> you showed interest in an CSID/AGNT
>> command. Do you have any opinion on
>> the other 4 commands in the draft?
>
> Thanks, Anthony.
>
> No worries - I meant to send a better response in the wake of my withdraw=
n AGNT draft and Mark's current Streamlined FTP Command
> Extensions draft, but I had been remiss at taking the time to collect my =
thoughts in a more meaningful way. But since you asked,
> this seems like as good at time as any. ;-]
>
> CSID - As evidenced by my short-lived AGNT proposal, I think it's very us=
eful to have some sort of client/server discovery command.
> FEAT does a good job of advertising the list of commands that are support=
ed by a server, but Mark's proposed CSID command sequence
> provides a much better way for servers and client to identify their featu=
res to each other in detail. For security reasons I would
> probably want the CSID exchange to occur AFTER the client has logged in, =
but I might be overreacting.
>
> RMDA - This could be a very useful command, and it would parallel the fun=
ctionality that I'm sure we all typically use in a native
> operating system environment. In a server implementation I would probably=
 make this command configurable, so administrators would
> have an option to disable the feature. In which case I would probably hid=
e the command from a FEAT response so it would not be
> discoverable and have the server return a 500 or 502 reply when RMDA is s=
ent by the client and disabled at the server.
>
> (Note: I mention my thoughts about server implementation details just to =
open up the discussion as to whether any implementation
> details should be called out in the draft, or if we should leave that up =
to the implementers to decide.)
>
> AVBL - This command could be very useful in a client/server world; our FT=
P server implementation currently returns the available
> size after a successful login sequence, and the available size is based o=
n server disk quotas and such. That being said, not every
> FTP client will bubble that information up to the user interface. Having =
an AVBL command would make it possible for a client to
> determine whether enough storage space is available at the server BEFORE =
sending a file, which would be great when you're about to
> send a 10GB file and you only have 9.99GB of storage space left. ;-]
>
> DSIZ - This could certainly be useful, although I would probably want a u=
ser to be logged in (not anonymous) before I supported this
> command in order to reduce the risk of denial-of-service. I'd probably ma=
ke it configurable so as not to tie up too many server
> resources for large directory structures; and once again, if the feature =
were disabled I would probably hide the command from a FEAT
> response so it would not be discoverable and return a 500 or 502 reply wh=
en DSIZ is sent by the client and disabled at the server.
>
> THMB - I have to admit, I don't work on a graphical FTP client, so this c=
ommand is less useful to me personally, but I can see the
> merit that it might have to someone that designs a graphical client. That=
 being said, I'm not a big fan of computing the thumbnail
> dynamically, nor am I fond of allowing the client to specify the thumbnai=
l format and size. I think that it would be better if the
> server could pre-cache thumbnails for any file type in a server-determine=
d size and image format, and then return the binary data
> and image format information to the client. For example, most graphically=
-based operating systems have some method for displaying
> file icons to a user that is seated at a computer terminal, so an FTP ser=
ver implementation could simply return that same icon to a
> client in response to a THMB request.
>
> Please bear in mind, I haven't given a lot of thought as to what the clie=
nt/server interchange might look like if the server were
> more in control of the response to a THMB request, but it would probably =
be sufficient to simply return the image type as part of
> the response and let the client determine the image dimensions based on t=
he client's capabilities for reading the image data. (As a
> server guy I like to push any client-friendly processing on the client wh=
enever possible. ;-]) You could borrow an idea from the
> HASH discussion that we've been having and make the thumbnail image type =
configurable for the client by using an OPTS command, which
> might look like the following examples.
>
> In this first example, the server has a pre-configured thumbnail image ty=
pe of JPG, and may have pre-cached the thumbnails for
> files; any THMB request with no OPTS specified would use the server's pre=
-configured thumbnail image type of JPG and image type is
> specified in the command channel response:
>
> C> THMB widget.png
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
> S> 226 Transfer complete.
>
> In these next examples a client is asking for different thumbnail image t=
ypes by using OPTS commands, and the thumbnail image types
> would still be specified in the command channel responses:
>
> C> OPTS THMB GIF
> S> 200 OPTS THMB GIF command successful.
>
> C> THMB widget.psp
> S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
> S> 226 Transfer complete.
>
> C> OPTS THMB PNG
> S> 200 OPTS THMB PNG command successful.
>
> C> THMB widget.doc
> S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
> S> 226 Transfer complete.
>
> In this next example a client is asking for an unsupported image type, so=
 the server would simply return the appropriate error
> reply:
>
> C> OPTS THMB FOO
> S> 501 Unsupported thumbnail format.
>
> In this next example a client is asking for the currently-configured thum=
bnail image type, so the server would return the
> appropriate response:
>
> C> OPTS THMB
> S> 200 JPG
>
> You might take this one step further - the server might choose to only su=
pport its pre-configured thumbnail image type, thereby
> allowing pre-caching of all thumbnails in one specific image format. In t=
his example a client is asking for PNG thumbnails, which
> SHOULD be a supported image type, but the server only supports a pre-conf=
igured thumbnail image type for JPG files and returns the
> appropriate error reply (504?) and the server's pre-configured thumbnail =
image type is specified in the subsequent command channel
> response to a THMB request:
>
> C> OPTS THMB PNG
> S> 504 Specifying thumbnail formats is unsupported.
>
> C> THMB widget.xls
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
> S> 226 Transfer complete.
>
> As I said earlier, I hadn't given much thought as to what the client/serv=
er THMB interchange might look like if you put the server
> in control instead of the client, but as a server guy I'd rather see THMB=
 look a little more like the examples that I gave. ;-]
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
>
>
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

wfms
---406846748-504006563-1290520508=:6921--

From mb@smartftp.com  Tue Nov 23 06:12:46 2010
Return-Path: <mb@smartftp.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 9E0B028C0E4 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 06:12:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
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 k3luYDQMN44b for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 06:12:44 -0800 (PST)
Received: from mail.smartftp.com (mail.smartftp.com [75.126.59.172]) by core3.amsl.com (Postfix) with ESMTP id 851BF3A696C for <ftpext@ietf.org>; Tue, 23 Nov 2010 06:12:44 -0800 (PST)
Received: from mx.smartsoft.local ([2002:4b7e:3bac::4b7e:3bac]) by mx.smartsoft.local ([2002:4b7e:3bac::4b7e:3bac]) with mapi; Tue, 23 Nov 2010 08:13:43 -0600
From: Mat Berchtold <mb@smartftp.com>
To: "William F. Maton" <wmaton@ottix.net>, "Mark P. Peterson" <mpp@rhinosoft.com>
Date: Tue, 23 Nov 2010 08:13:37 -0600
Thread-Topic: [ftpext] draft-peterson-streamlined-ftp-command-extensions
Thread-Index: AcuLFhQelHAAXKvvSDWl2bSicPNSmQAAB6hA
Message-ID: <41871DBEA4CB724B93AC2D8CAADADBF41463C77079@mx.smartsoft.local>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net> <AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com> <914CA95DAC22422C825C665E4E76F860@rhinooffice.net> <Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net>
In-Reply-To: <Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "ftpext@ietf.org" <ftpext@ietf.org>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 14:12:46 -0000

SGVsbG8gTWFyayAuLg0KDQo+Q1NJRCBhZnRlciBsb2dpbg0KSSBhbHNvIHRoaW5rIHRoZSBDU0lE
IGNvbW1hbmQgc2hvdWxkIG9ubHkgYmUgYXZhaWxhYmxlIGFmdGVyIGxvZ2luLiBJIGNhbm5vdCB0
aGluayBvZiBhIGdvb2QgcmVhc29uIHdoZXJlIGEgIGNsaWVudCB3aXRoIGdvb2QgaW50ZW50aW9u
cyB3b3VsZCBuZWVkIGl0IGJlZm9yZS4gQnV0IG1heWJlIEknbSBtaXNzaW5nIHNvbWV0aGluZyBo
ZXJlPw0KDQo+RmFjdHMNCkZvciB0aGUgZmFjdHMsIEkgd291bGQgcHJvcG9zZSB0aGUgZm9sbG93
aW5nIGZhY3RzIHdoaWNoIHdvdWxkIHJlcGxhY2UgdGhlIGV4aXN0aW5nIE5hbWUgYW5kIFZlcnNp
b24gZmFjdHM6DQpWZW5kb3JOYW1lDQpQcm9kdWN0TmFtZQ0KUHJvZHVjdFZlcnNpb24NCldoZXJl
IFByb2R1Y3RWZXJzaW9uIG11c3QgYmUgaW4gdGhlIGZvbGxvd2luZyBmb3JtYXQgMSpESUdJVCAi
LiIgMSpESUdJVCAiLiIgMSpESUdJVCogIi4iIDEqRElHSVQgd2hpY2ggcmVwcmVzZW50cyB0aGUg
dmVyc2lvbiBhcyBmb2xsb3dpbmc6IG1ham9yLm1pbm9yLmJ1aWxkLnBhdGNoDQoNCkFuIGV4YW1w
bGU6DQpWZW5kb3JOYW1lOiBTbWFydFNvZnQgTHRkLg0KUHJvZHVjdE5hbWU6IFNtYXJ0RlRQDQpQ
cm9kdWN0VmVyc2lvbjogNC4wLjExNDUuMA0KDQo+U2VydmVyL0NsaWVudCBmYWN0IHJlcXVpcmVt
ZW50DQpUaGUgZHJhZnQgcHJvcG9zZXMgdGhhdCB0aGUgY2xpZW50IG11c3QgcHJvdmlkZSB0aGUg
bmFtZSBhbmQgdmVyc2lvbiBmYWN0IHdoZXJlIGZvciB0aGUgc2VydmVyIHRoZXNlIGZhY3RzIGFy
ZSBvcHRpb25hbC4gRm9yIGVxdWFsaXR5IGJvdGggcGFydGllcyBpbnZvbHZlZCBzaG91bGQgaGF2
ZSBlcXVhbCByZXF1aXJlbWVudHMvcmlnaHRzLiBNeSBwcm9wb3NhbCBpcyB0aGF0IGFsbCBmYWN0
cyBhcmUgb3B0aW9uYWwuIFRoZSByZWFzb25pbmcgaXMgdGhhdCB0aGVyZSBpcyBubyBuZWVkIGZv
ciB0aGUgY2xpZW50IHRvIGV4cG9zZSBpdHMgbmFtZSBvciB2ZXJzaW9uIGlmIGl0IG9ubHkgd2Fu
dHMgdG8gZmlndXJlIG91dCB0aGUgY2FzZSBzZW5zaXRpdml0eSBvZiB0aGUgc2VydmVyIGZpbGUg
c3lzdGVtLg0KDQpSZWdhcmRzLA0KTWF0DQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IGZ0cGV4dC1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86ZnRwZXh0LWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBXaWxsaWFtIEYuIE1hdG9uDQpTZW50OiBUdWVzZGF5LCAyMyBO
b3ZlbWJlciwgMjAxMCAxNDo1NQ0KVG86IE1hcmsgUC4gUGV0ZXJzb24NCkNjOiBmdHBleHRAaWV0
Zi5vcmcNClN1YmplY3Q6IFJlOiBbZnRwZXh0XSBkcmFmdC1wZXRlcnNvbi1zdHJlYW1saW5lZC1m
dHAtY29tbWFuZC1leHRlbnNpb25zDQoNCk9uIFR1ZSwgMjMgTm92IDIwMTAsIE1hcmsgUC4gUGV0
ZXJzb24gd3JvdGU6DQoNCj4gSGkgQWxsLA0KPg0KPiBJcyB0aGVyZSBhbnlvbmUgZWxzZSB0aGF0
IGFncmVlcyB3aXRoIERhbWluIGFib3V0IENTSUQ/ICBIZSBzYXlzIGl0IFNIT1VMRCBiZSBhdmFp
bGFibGUgb25seSBhZnRlciBsb2dpbi4NCg0KSGkgTWFyaywNCiAgICAgICAgSSdtIGNlcnRhaW5s
eSBhbmQgb2xkIGVub3VnaCBzYWx0IGF0IHN5c3RlbXMgYWRtaW5pc3RyYXRpb24gdG8gdGhpbmsg
dGhhdCBpZGVudGlmaWNhdGlvbiBiZWZvcmUgYXV0aGVudGljYXRpb24gb3IgYXV0aG9yaXphdGlv
biBpcyBub3QgYSBnb29kIHRoaW5nLiAgSXQgbWFrZXMgaXQgZWFzaWVyIGZvciB0aGUgc2Nhbm5l
cnMgdG8gcGljay1vZmYgd2hhdCBzZXJ2ZXJzIGFyZSBydW5uaW5nLiAgSSdkIGxpa2UgdG8gZm9y
Y2UgdGhlbSBpbnRvIG1ha2luZyB0aGUgZXh0cmEgZWZmb3J0LCBzaW5jZSBpdCBtaWdodCBhcyB3
ZWxsIGNvc3QgdGhlbSBtb3JlIHdvcmsgYW5kIEkgY2FuIG1vbml0b3IgdGhlIGFjdGl2aXR5IGJl
dHRlci4NCg0KICAgICAgICBJIHRoaW5rIHN0YW5kYXJkaXppbmcgQ1NJRCAoZnJvbSB0aGUgb2xk
IG5vbi1zdGFuZGFyZCBDTE5UKSBpcyBhIGdvb2QgdGhpbmcgdGhvdWdoLiAgSXQgc2hvdWxkIGJl
IGxlZnQgdXAgdG8gdGhlIGltcGxlbWVudG9yIHRvIHN1cHBvcnQgaXQuDQoNCiAgICAgICAgSSd2
ZSBhbHNvIHJlYWQgaGUgcmVzdCBvZiB0aGF0IEktRCBhbmQgaGF2ZSBtb3JlIHRob3VnaHRzIG9u
IGl0LCBidXQgdGhhdCdzIGZvciBhbm90aGVyIGVtYWlsLg0KDQoNCj4gTWFyayBQLiBQZXRlcnNv
biAtIFByZXNpZGVudA0KPiBodHRwOi8vd3d3LlJoaW5vU29mdC5jb20NCj4gVm9pY2U6ICsxKDI2
MikgNTYwLTk2MjcNCj4gRkFYOiArMSgyNjIpIDU2MC05NjI4DQo+DQo+DQo+DQo+IEZyb206IERh
bWluDQo+IFNlbnQ6IE1vbmRheSwgTm92ZW1iZXIgMjIsIDIwMTAgMTA6MTcgUE0NCj4gVG86IGZ0
cGV4dEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW2Z0cGV4dF0gZHJhZnQtcGV0ZXJzb24tc3Ry
ZWFtbGluZWQtZnRwLWNvbW1hbmQtZXh0ZW5zaW9ucw0KPg0KPg0KPiBIaSwNCj4NCj4NCj4gT24g
MjIgTm92ZW1iZXIgMjAxMCAxOTozMiwgTWFyayBQLiBQZXRlcnNvbiA8bXBwQHJoaW5vc29mdC5j
b20+IHdyb3RlOg0KPg0KPiBIaSBSb2JlcnQsDQo+DQo+IFRoYW5rIHlvdSBmb3IgdGFraW5nIHRo
ZSB0aW1lIHRvIHJldmlldyB0aGUgY29tbWFuZHMuICBJZiB5b3UgZG9uJ3QgbWluZCBJIHdvdWxk
DQo+IGxpa2UgdG8gcmVzcG9uZCB0byB5b3VyIGNvbW1lbnRzOg0KPg0KPiBDU0lEOg0KPg0KPj4g
Rm9yIHNlY3VyaXR5IHJlYXNvbnMgSSB3b3VsZCBwcm9iYWJseSB3YW50IHRoZSBDU0lEIGV4Y2hh
bmdlIHRvIG9jY3VyIEFGVEVSIHRoZSBjbGllbnQgaGFzIGxvZ2dlZCBpbiwgYnV0IEkgbWlnaHQg
YmUgb3ZlcnJlYWN0aW5nLg0KPg0KPg0KPiBUaGVyZSBpcyBhIGxvdCBvZiBkaXNjdXNzaW9uIG9u
IHRoZSBJbnRlcm5ldCBhYm91dCBzZXJ2ZXJzIHByb3ZpZGluZyAidG9vIiBtdWNoIGluZm9ybWF0
aW9uLCBlc3BlY2lhbGx5IHByaW9yIHRvIGxvZ2luLiAgQnV0IGhhdmluZw0KPiB3b3JrZWQgb24g
Ym90aCBzaWRlcyBvZiB0aGUgRlRQIHByb2Nlc3MsIGl0J3MgdXN1YWxseSB2ZXJ5IGVhc3kgZm9y
IHRoZSBjbGllbnQgdG8gaWRlbnRpZnkgd2hhdCBicmFuZCBvciBmbGF2b3IgdGhlIHNlcnZlciBp
cy4NCj4gVGhlcmUgYXJlIGRldGFpbHMgd2hpY2ggdXN1YWxseSBpZGVudGlmeSB0aGUgc2VydmVy
IHN1Y2ggYXMgdGhlIGNvbXBsZXRlbmVzcyBvZiB0aGUgRkVBVCByZXNwb25zZSwgdGhlIHdlbGNv
bWUgbWVzc2FnZSwgcmVzcG9uc2VzIHRvDQo+IGNlcnRhaW4gbWVzc2FnZXMsIGV0Yy4gIFNvLCBJ
IHRoaW5rIGl0J3Mgb2theSB0byBiZSBhdmFpbGFibGUgcHJpb3IgdG8gbG9naW4uICBJIGNvdWxk
IGNoYW5nZSB0aGUgZG9jdW1lbnQgdG8gcmVhZCB0aGF0IGl0IHNob3VsZCBiZQ0KPiB1cCB0byB0
aGUgc2VydmVyJ3MgaW1wbGVtZW50YXRpb24gd2hldGhlciBvciBub3QgaXQncyBhdmFpbGFibGUu
DQo+DQo+IEkgcHJlZmVyIHRvIGVkZ2Ugb24gdGhlIHNpZGUgb2YgY2F1dGlvbi4gSSBkb27CtHQg
c2VlIGFueSBnb29kIHJlYXNvbiB0aGF0IHRoaXMgU0hPVUxEIGJlIGF2YWlsYWJsZSBiZWZvcmUg
bG9naW4uIENvbW1hbmRzIGF2YWlsYWJsZQ0KPiBwcmlvciB0byBsb2dpbiBzaG91bGQgYmUgYXMg
bGltaXRlZCBhcyBwb3NzaWJsZS4NCj4NCj4NCj4gUk1EQToNCj4NCj4+IEluIGEgc2VydmVyIGlt
cGxlbWVudGF0aW9uIEkgd291bGQgcHJvYmFibHkgbWFrZSB0aGlzIGNvbW1hbmQgY29uZmlndXJh
YmxlLCBzbyBhZG1pbmlzdHJhdG9ycyB3b3VsZCBoYXZlIGFuIG9wdGlvbiB0byBkaXNhYmxlIHRo
ZQ0KPj4gZmVhdHVyZS4gIEluIHdoaWNoIGNhc2UgSSB3b3VsZCBwcm9iYWJseSBoaWRlIHRoZSBj
b21tYW5kIGZyb20gYSBGRUFUIHJlc3BvbnNlIHNvIGl0IHdvdWxkIG5vdCBiZSBkaXNjb3ZlcmFi
bGUgYW5kIGhhdmUgdGhlIHNlcnZlcg0KPj4gcmV0dXJuIGEgNTAwIG9yIDUwMiByZXBseSB3aGVu
IFJNREEgaXMgc2VudCBieSB0aGUgY2xpZW50IGFuZCBkaXNhYmxlZCBhdCB0aGUgc2VydmVyLg0K
Pg0KPg0KPiBJIGRvbid0IHRoaW5rIG15IGRvY3VtZW50IHNwZWNpZmllcyB0aGF0IGl0IGlzbid0
IGNvbmZpZ3VyYWJsZS4gIE15IGltcGxlbWVudGF0aW9uIGluIFNlcnYtVSBpcyBjb25maWd1cmFi
bGUgYXMgaXMgYWxtb3N0IGFsbCBvdGhlcg0KPiBGVFAgY29tbWFuZHMuICBJIHRoaW5rIHRoaXMg
Y2FuIGJlIGxlZnQgdXAgdG8gdGhlIHNlcnZlciBpbXBsZW1lbnRhdGlvbi4gIFlvdXIgcG9zc2li
bGUgaW1wbGVtZW50YXRpb24gaXMgZXhhY3RseSBob3cgU2Vydi1VDQo+IGltcGxlbWVudHMgaXQu
ICBJZiB0aGUgZmVhdHVyZSBpcyBkaXNhYmxlZCwgaXQgZG9lc24ndCBhcHBlYXIgaW4gdGhlIEZF
QVQgcmVzcG9uc2UsIG5vciBpcyBpdCBhdmFpbGFibGUgdGhyb3VnaCB0aGUgSEVMUCBjb21tYW5k
Lg0KPg0KPg0KPiBBVkJMOg0KPj4gLi4uDQo+DQo+IFlvdXIgY29tbWVudHMgYWRkcmVzcyB0aGUg
cmVhc29uIGZvciBpdHMgZXhpc3RlbmNlLiAgVGhlIGNsaWVudC1zaWRlIGltcGxlbWVudGF0aW9u
IGluIFNtYXJ0RlRQIHVzZXMgdGhlIGNvbW1hbmQgaW4gdGhpcyBtYW5uZXIuDQo+DQo+IERTSVo6
DQo+PiBUaGlzIGNvdWxkIGNlcnRhaW5seSBiZSB1c2VmdWwsIGFsdGhvdWdoIEkgd291bGQgcHJv
YmFibHkgd2FudCBhIHVzZXIgdG8gYmUgbG9nZ2VkIGluLi4uDQo+DQo+IEFueSBpbmZvcm1hdGlv
biBhYm91dCBwYXRocyBvciBmaWxlcyByZXF1aXJlcyBsb2dpbiBpbiBGVFAuICBJIGFtIHN1cmUg
dGhpcyBpcyB0aGUgY2FzZSBoZXJlIGFzIHdlbGwuICBJZiBhIHNlcnZlciB3b3VsZG4ndCB3YW50
IHRoZQ0KPiAiYW5vbnltb3VzIiB1c2VyIHRvIGhhdmUgYWNjZXNzIHRvIHRoaXMgY29tbWFuZCBp
dCBjb3VsZCBiZSBjb25maWd1cmVkIHRvIGRpc2FsbG93IHRoaXMgY29tbWFuZCBhdCB0aGUgc2Vy
dmVyJ3MgaW1wbGVtZW50YXRpb24gb3INCj4gY29uZmlndXJhdGlvbi4gIFRoaXMgc2hvdWxkIGJl
IGxlZnQgdXAgdG8gdGhlIGltcGxlbWVudGF0aW9uIG9mIHRoZSBzZXJ2ZXIgb3IgYWRtaW5pc3Ry
YXRvciBvZiB0aGUgc2VydmVyLg0KPg0KPj4gSSdkIHByb2JhYmx5IG1ha2UgaXQgY29uZmlndXJh
YmxlIHNvIGFzIG5vdCB0byB0aWUgdXAgdG9vIG1hbnkgc2VydmVyIHJlc291cmNlcyBmb3IgbGFy
Z2UgZGlyZWN0b3J5IHN0cnVjdHVyZXM7Li4uDQo+DQo+IEFncmVlZCwgdGhlIHRpbWUtY29uc3Vt
aW5nIG5hdHVyZSBvZiB0aGUgaW1wbGVtZW50YXRpb24gaXMgZGlzY3Vzc2VkIGJ1dCBjb25maWd1
cmF0aW9uIGJ5IGFuIGFkbWluaXN0cmF0b3Igb3Igc2VydmVyLWltcGxlbWVudGF0aW9uDQo+IGlz
IG5vdC4gICBEbyB5b3UgdGhpbmsgc3VjaCB2ZXJiaWFnZSBpcyByZXF1aXJlZD8NCj4NCj4NCj4g
VEhNQjoNCj4NCj4+IEknbSBub3QgYSBiaWcgZmFuIG9mIGNvbXB1dGluZyB0aGUgdGh1bWJuYWls
IGR5bmFtaWNhbGx5LCBub3IgYW0gSSBmb25kIG9mIGFsbG93aW5nIHRoZSBjbGllbnQgdG8gc3Bl
Y2lmeSB0aGUgdGh1bWJuYWlsIGZvcm1hdCBhbmQNCj4+IHNpemUuDQo+DQo+DQo+IFRoYXQncyB0
aGUgcG9pbnQgb2YgdGhlIGNvbW1hbmQsIHRob3VnaC4gIEl0J3MgdG8gcmVkdWNlIHRoZSBhbW91
bnQgb2YgZGF0YSB0aGF0IGlzIHJlcXVpcmVkIHRvIHRyYXZlbCBvdmVyIHRoZSB3aXJlLiAgVGhl
IGlkZWEgaXMNCj4gdG8gc2hvcnRlbiBkZWxpdmVyeSB0aW1lIHRvIHRoZSBjbGllbnQsIGxldHRp
bmcgdGhlIGNsaWVudCBkZWNpZGUgd2hhdCBpcyBiZXN0IGZvciB0aGUgY2xpZW50LCBub3QgdGhl
IHNlcnZlci4gIFNvbWUgY2xpZW50cyBtYXkNCj4gd2FudCB2ZXJ5IHNtYWxsIGltYWdlcywgc2F5
IGZvciBhIFdpbmRvd3MgRXhwbG9yZXIgc3R5bGUgbGlzdGluZywgb3RoZXJzIG1heSB3YW50IGxh
cmdlciBpbWFnZXMgKDY0MHg0ODAgZm9yIGV4YW1wbGUpIHRvIHNob3cgYQ0KPiBzbGlkZSBzaG93
LiAgSSB0aGluayB0aGUgY2xpZW50IG5lZWRzIHRvIG1ha2UgdGhhdCBkZXRlcm1pbmF0aW9uLiAg
SWYgdGhlIHNlcnZlciBkZWNpZGVzIHRvIGNhY2hlIHRoZXNlIGdlbmVyYXRlZCBpbWFnZXMgaXQg
Y2FuLg0KPg0KPg0KPj4gSSB0aGluayB0aGF0IGl0IHdvdWxkIGJlIGJldHRlciBpZiB0aGUgc2Vy
dmVyIGNvdWxkIHByZS1jYWNoZSB0aHVtYm5haWxzIGZvciBhbnkgZmlsZSB0eXBlIGluIGEgc2Vy
dmVyLWRldGVybWluZWQgc2l6ZSBhbmQgaW1hZ2UNCj4+IGZvcm1hdCwgYW5kIHRoZW4gcmV0dXJu
IHRoZSBiaW5hcnkgZGF0YSBhbmQgaW1hZ2UgZm9ybWF0IGluZm9ybWF0aW9uIHRvIHRoZSBjbGll
bnQuDQo+DQo+DQo+IFRoaXMgY291bGQgd2FzdGUgc2VydmVyLXNpZGUgcmVzb3VyY2VzLCB0aGUg
Y2xpZW50IG1pZ2h0IG5vdCBldmVuIG1ha2UgYSByZXF1ZXN0IGZvciB0aHVtYm5haWwgaW1hZ2Vz
Lg0KPg0KPg0KPj4gRm9yIGV4YW1wbGUsIG1vc3QgZ3JhcGhpY2FsbHktYmFzZWQgb3BlcmF0aW5n
IHN5c3RlbXMgaGF2ZSBzb21lIG1ldGhvZCBmb3IgZGlzcGxheWluZyBmaWxlIGljb25zIHRvIGEg
dXNlciB0aGF0IGlzIHNlYXRlZCBhdCBhDQo+PiBjb21wdXRlciB0ZXJtaW5hbCwgc28gYW4gRlRQ
IHNlcnZlciBpbXBsZW1lbnRhdGlvbiBjb3VsZCBzaW1wbHkgcmV0dXJuIHRoYXQgc2FtZSBpY29u
IHRvIGEgY2xpZW50IGluIHJlc3BvbnNlIHRvIGEgVEhNQiByZXF1ZXN0Lg0KPg0KPg0KPiBSaWdo
dCwgYnV0IHRoaXMgaXNuJ3QgcmVhbGx5IHRoZSBwdXJwb3NlIG9mIHRoaXMgY29tbWFuZC4gIFRo
ZSBwdXJwb3NlIGlzIHRvIHRha2UgYW4gb3JpZ2luYWwgaW1hZ2UgZmlsZSBhbmQgcmVkdWNlIGl0
IHRvIGENCj4gc3BlY2lmaWVkIHNpemUsIG5vdCB0byByZXR1cm4gdGhlIE9TJ3MgaWNvbiByZXBy
ZXNlbnRhdGlvbiBmb3IgdGhhdCBwYXJ0aWN1bGFyIGZpbGUgdHlwZSAoaS5lLiwgbm90IFNIR2V0
RmlsZUluZm8oKSBpbiBXaW5kb3dzKS4NCj4NCj4gTXkgcHJvcG9zZWQgaW1wbGVtZW50YXRpb24g
aXMgZmFpcmx5IHN0cmFpZ2h0Zm9yd2FyZC4gIElmIHN1cHBvcnRlZCB0aGUgRkVBVCBjb21tYW5k
IHJlcGxpZXMgd2l0aCBUSE1CIGFuZCB0aGUgc3VwcG9ydGVkIGZpbGUgdHlwZXMuDQo+IFdoZW4g
dGhlIGNsaWVudCB3YW50cyBhIHRodW1ibmFpbCBpdCBhc2tzIGZvciBpdCB3aXRoIGEgc2luZ2xl
IGNvbW1hbmQuICBIZXJlIGlzIGEgc2FtcGxlIHJlc3VsdCBmcm9tIEZUUCBWb3lhZ2VyIGFuZCBT
ZXJ2LVU6DQo+DQo+IFBPUlQgMTkyLDE2OCwwLDMwLDE5OSw1Mw0KPiAyMDAgUE9SVCBjb21tYW5k
IHN1Y2Nlc3NmdWwuDQo+IFRITUIgUE5HIDk4IDg4IFRob21hcy5KUEcNCj4gMTUwIE9wZW5pbmcg
dGh1bWJuYWlsIGltYWdlIHRyYW5zZmVyIEJJTkFSWSBtb2RlIGRhdGEgY29ubmVjdGlvbiAoMTk3
MzggQnl0ZXMpIGZvciBUaG9tYXMuSlBHLg0KPiAyMjYgVHJhbnNmZXIgY29tcGxldGUuIDE5LDcz
OCBieXRlcyAoMTksNzU2IGNvbXByZXNzZWQgdG8gMTAwLjA5JSkgdHJhbnNmZXJyZWQuIDE5LjI5
IGFjdHVhbCBLQi9zZWMsICAxOS4yOCBlZmZlY3RpdmUgS0Ivc2VjLg0KPg0KPiBUaGUgY2xpZW50
IG9wZW5zIGEgZGF0YSBjaGFubmVsIGp1c3QgbGlrZSBhbnkgb3RoZXIgZmlsZSB0cmFuc2Zlciwg
dGhlbiByZXF1ZXN0cyB0aGUgZmlsZSB1c2luZyBUSE1CLCBmb2xsb3dlZCBieSB0aGUgb3V0cHV0
IHR5cGUsDQo+IHdpZHRoLCBoZWlnaHQsIGFuZCB0aGUgZmlsZSBuYW1lLiAgVGhlIHNlcnZlciBy
ZXNwb25kcyBqdXN0IGxpa2UgYSBmaWxlIHRyYW5zZmVyIGJ1dCBhbHNvIGluY2x1ZGVzIHRoZSBy
ZXN1bHRpbmcgc2l6ZSBpbg0KPiBwYXJlbnRoZXNlcy4NCj4NCj4gV2hpbGUgZGVzaWduaW5nIHRo
aXMgY29tbWFuZCB0aGUgaWRlYSB3YXMgdG8gZmlyc3QgbWFrZSBpdCBzaW1wbGUgZm9yIGJvdGgg
c2lkZXMsIHNlY29uZCB0byBtYWtlIGl0IG9wZXJhdGUgYXMgYW55IG90aGVyIGRvd25sb2FkLA0K
PiBhbmQgdGhpcmQgdG8gbWFrZSBpdCBhcyBmbGV4aWJsZSBhcyBwb3NzaWJsZSwgYWxsb3dpbmcg
dGhlIGNsaWVudCB0byBkZWNpZGUgaG93IHRoZSByZXN1bHRpbmcgZGF0YSBpcyB0byBiZSB1c2Vk
IGFuZCB3aGF0IGlzIG5lZWRlZC4NCj4gT2YgY291cnNlIHRoZSBzZXJ2ZXIgY291bGQgYmUgY29u
ZmlndXJlZCBpbiBhbnkgd2F5IG5lZWRlZC4gIEZvciBleGFtcGxlIGlmIHRoZSBzZXJ2ZXIgd2Fu
dGVkIHRvIGxpbWl0IHRoZSBzaXplIG9mIHRoZSB0aHVtYm5haWxzLA0KPiB0aGUgc2VydmVyIGNv
dWxkIGRvIHRoYXQuICBPdXIgaW1wbGVtZW50YXRpb24gbGltaXRzIHRoZSBudW1iZXIgb2Ygc2lt
dWx0YW5lb3VzIHRocmVhZHMgYWxsb3dlZCB0byBjcmVhdGUgdGhlIHRodW1ibmFpbHMgYXQgYW55
DQo+IGdpdmVuIHRpbWUuICBJIHRoaW5rIHRoZXNlIGRldGFpbHMgbmVlZCB0byBiZSBsZWZ0IHRv
IHRoZSBzZXJ2ZXIgaW1wbGVtZW50YXRpb24uDQo+DQo+IEFzIGZvciB1c2luZyBhbiBPUFQgY29t
bWFuZCB0byBjb25maWd1cmUgYW4gdXBjb21pbmcgVEhNQiBjb21tYW5kIGZvciBpdHMgaW1hZ2Ug
dHlwZSBhbmQgdGhlIHRodW1ibmFpbCBzaXplLCB0aGF0IHNlZW1zIHRvDQo+IGNvbXBsaWNhdGUg
dGhlIGNvbW1hbmQuICBJdCdzIHZlcnkgZWFzeSB0byBhZGQgdGhlc2UgcGFyYW1ldGVycyBpbnRv
IGEgc2luZ2xlIGNvbW1hbmQsIGVsaW1pbmF0aW5nIHRoZSByZXF1aXJlZCBoYW5kc2hha2luZyBi
ZXR3ZWVuDQo+IHRoZSBjbGllbnQgYW5kIHNlcnZlci4gIEFuIGFkZGVkIGJlbmVmaXQgaXMgdGhh
dCBuZWl0aGVyIHRoZSBjbGllbnQgbm9yIHRoZSBzZXJ2ZXIgYXJlIHJlcXVpcmVkIHRvIG1haW50
YWluIHRoZXNlICJvcHRpb25zIg0KPiB0aHJvdWdob3V0IGEgc2Vzc2lvbiwgcmF0aGVyIGFsbCBv
ZiB0aGUgaW5mb3JtYXRpb24gcmVxdWlyZWQgaXMgc2VudCBpbiBhIHNpbmdsZSBjb21tYW5kLg0K
Pg0KPiBJZiB5b3UncmUgaW50ZXJlc3RlZCBpbiBzZWVpbmcgaXQgaW4gYWN0aW9uLCBkb3dubG9h
ZCBTZXJ2LVUgYW5kIEZUUCBWb3lhZ2VyIG9yIFNtYXJ0RlRQLiAgTG9naW4gdG8gdGhlIHNlcnZl
ciwgc3dpdGNoIEZUUCBWb3lhZ2VyDQo+IHRvICJUaHVtYm5haWxzIiB2aWV3LiAgV2l0aCBTbWFy
dEZUUCBzaW1wbHkgc2VsZWN0IGFuIGltYWdlIGZpbGUgYW5kIGEgdGh1bWJuYWlsIGltYWdlLCBv
ZiBkeW5hbWljIHNpemUsIHdpbGwgYXBwZWFyIGluIHRoZSBwcmV2aWV3DQo+IHBhbmUuDQo+DQo+
DQo+IFRoYW5rIHlvdSBhZ2FpbiBmb3IgdGFraW5nIHRoZSB0aW1lIHRvIHByb3ZpZGUgeW91ciBm
ZWVkYmFjay4gIEkgbG9vayBmb3J3YXJkIHRvIHlvdXIgY29tbWVudHMgdG8gdGhlIGFib3ZlLg0K
Pg0KPiBNYXJrIFAuIFBldGVyc29uIC0gUHJlc2lkZW50DQo+IGh0dHA6Ly93d3cuUmhpbm9Tb2Z0
LmNvbQ0KPiBWb2ljZTogKzEoMjYyKSA1NjAtOTYyNw0KPiBGQVg6ICsxKDI2MikgNTYwLTk2MjgN
Cj4NCj4NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0NCj4gRnJvbTogIlJvYmVydCBNY011cnJheSIgPHJvYm1jbUBtaWNyb3NvZnQuY29tPg0KPiBT
ZW50OiBNb25kYXksIE5vdmVtYmVyIDIyLCAyMDEwIDU6MDEgUE0NCj4gVG86IDxmdHBleHRAaWV0
Zi5vcmc+OyAiJ0FudGhvbnkgQnJ5YW4nIiA8YW50aG9ueWJyeWFuQGdtYWlsLmNvbT47IDxtYXJr
LnBldGVyc29uQHJoaW5vc29mdC5jb20+DQo+IFN1YmplY3Q6IFtmdHBleHRdIGRyYWZ0LXBldGVy
c29uLXN0cmVhbWxpbmVkLWZ0cC1jb21tYW5kLWV4dGVuc2lvbnMNCj4NCj4NCj4gW05vdGU6IFJl
bmFtaW5nIHRoZSB0aHJlYWQgZnJvbSAnU3VibWl0dGluZyBuZXcgZHJhZnRzJy5dDQo+DQo+PiBB
bnRob255IEJyeWFuIHdyb3RlOg0KPj4NCj4+IEkgZG9uJ3QgbWVhbiB0byBzaW5nbGUgeW91IG91
dCwgYnV0DQo+PiB5b3Ugc2hvd2VkIGludGVyZXN0IGluIGFuIENTSUQvQUdOVA0KPj4gY29tbWFu
ZC4gRG8geW91IGhhdmUgYW55IG9waW5pb24gb24NCj4+IHRoZSBvdGhlciA0IGNvbW1hbmRzIGlu
IHRoZSBkcmFmdD8NCj4NCj4gVGhhbmtzLCBBbnRob255Lg0KPg0KPiBObyB3b3JyaWVzIC0gSSBt
ZWFudCB0byBzZW5kIGEgYmV0dGVyIHJlc3BvbnNlIGluIHRoZSB3YWtlIG9mIG15IHdpdGhkcmF3
biBBR05UIGRyYWZ0IGFuZCBNYXJrJ3MgY3VycmVudCBTdHJlYW1saW5lZCBGVFAgQ29tbWFuZA0K
PiBFeHRlbnNpb25zIGRyYWZ0LCBidXQgSSBoYWQgYmVlbiByZW1pc3MgYXQgdGFraW5nIHRoZSB0
aW1lIHRvIGNvbGxlY3QgbXkgdGhvdWdodHMgaW4gYSBtb3JlIG1lYW5pbmdmdWwgd2F5LiBCdXQg
c2luY2UgeW91IGFza2VkLA0KPiB0aGlzIHNlZW1zIGxpa2UgYXMgZ29vZCBhdCB0aW1lIGFzIGFu
eS4gOy1dDQo+DQo+IENTSUQgLSBBcyBldmlkZW5jZWQgYnkgbXkgc2hvcnQtbGl2ZWQgQUdOVCBw
cm9wb3NhbCwgSSB0aGluayBpdCdzIHZlcnkgdXNlZnVsIHRvIGhhdmUgc29tZSBzb3J0IG9mIGNs
aWVudC9zZXJ2ZXIgZGlzY292ZXJ5IGNvbW1hbmQuDQo+IEZFQVQgZG9lcyBhIGdvb2Qgam9iIG9m
IGFkdmVydGlzaW5nIHRoZSBsaXN0IG9mIGNvbW1hbmRzIHRoYXQgYXJlIHN1cHBvcnRlZCBieSBh
IHNlcnZlciwgYnV0IE1hcmsncyBwcm9wb3NlZCBDU0lEIGNvbW1hbmQgc2VxdWVuY2UNCj4gcHJv
dmlkZXMgYSBtdWNoIGJldHRlciB3YXkgZm9yIHNlcnZlcnMgYW5kIGNsaWVudCB0byBpZGVudGlm
eSB0aGVpciBmZWF0dXJlcyB0byBlYWNoIG90aGVyIGluIGRldGFpbC4gRm9yIHNlY3VyaXR5IHJl
YXNvbnMgSSB3b3VsZA0KPiBwcm9iYWJseSB3YW50IHRoZSBDU0lEIGV4Y2hhbmdlIHRvIG9jY3Vy
IEFGVEVSIHRoZSBjbGllbnQgaGFzIGxvZ2dlZCBpbiwgYnV0IEkgbWlnaHQgYmUgb3ZlcnJlYWN0
aW5nLg0KPg0KPiBSTURBIC0gVGhpcyBjb3VsZCBiZSBhIHZlcnkgdXNlZnVsIGNvbW1hbmQsIGFu
ZCBpdCB3b3VsZCBwYXJhbGxlbCB0aGUgZnVuY3Rpb25hbGl0eSB0aGF0IEknbSBzdXJlIHdlIGFs
bCB0eXBpY2FsbHkgdXNlIGluIGEgbmF0aXZlDQo+IG9wZXJhdGluZyBzeXN0ZW0gZW52aXJvbm1l
bnQuIEluIGEgc2VydmVyIGltcGxlbWVudGF0aW9uIEkgd291bGQgcHJvYmFibHkgbWFrZSB0aGlz
IGNvbW1hbmQgY29uZmlndXJhYmxlLCBzbyBhZG1pbmlzdHJhdG9ycyB3b3VsZA0KPiBoYXZlIGFu
IG9wdGlvbiB0byBkaXNhYmxlIHRoZSBmZWF0dXJlLiBJbiB3aGljaCBjYXNlIEkgd291bGQgcHJv
YmFibHkgaGlkZSB0aGUgY29tbWFuZCBmcm9tIGEgRkVBVCByZXNwb25zZSBzbyBpdCB3b3VsZCBu
b3QgYmUNCj4gZGlzY292ZXJhYmxlIGFuZCBoYXZlIHRoZSBzZXJ2ZXIgcmV0dXJuIGEgNTAwIG9y
IDUwMiByZXBseSB3aGVuIFJNREEgaXMgc2VudCBieSB0aGUgY2xpZW50IGFuZCBkaXNhYmxlZCBh
dCB0aGUgc2VydmVyLg0KPg0KPiAoTm90ZTogSSBtZW50aW9uIG15IHRob3VnaHRzIGFib3V0IHNl
cnZlciBpbXBsZW1lbnRhdGlvbiBkZXRhaWxzIGp1c3QgdG8gb3BlbiB1cCB0aGUgZGlzY3Vzc2lv
biBhcyB0byB3aGV0aGVyIGFueSBpbXBsZW1lbnRhdGlvbg0KPiBkZXRhaWxzIHNob3VsZCBiZSBj
YWxsZWQgb3V0IGluIHRoZSBkcmFmdCwgb3IgaWYgd2Ugc2hvdWxkIGxlYXZlIHRoYXQgdXAgdG8g
dGhlIGltcGxlbWVudGVycyB0byBkZWNpZGUuKQ0KPg0KPiBBVkJMIC0gVGhpcyBjb21tYW5kIGNv
dWxkIGJlIHZlcnkgdXNlZnVsIGluIGEgY2xpZW50L3NlcnZlciB3b3JsZDsgb3VyIEZUUCBzZXJ2
ZXIgaW1wbGVtZW50YXRpb24gY3VycmVudGx5IHJldHVybnMgdGhlIGF2YWlsYWJsZQ0KPiBzaXpl
IGFmdGVyIGEgc3VjY2Vzc2Z1bCBsb2dpbiBzZXF1ZW5jZSwgYW5kIHRoZSBhdmFpbGFibGUgc2l6
ZSBpcyBiYXNlZCBvbiBzZXJ2ZXIgZGlzayBxdW90YXMgYW5kIHN1Y2guIFRoYXQgYmVpbmcgc2Fp
ZCwgbm90IGV2ZXJ5DQo+IEZUUCBjbGllbnQgd2lsbCBidWJibGUgdGhhdCBpbmZvcm1hdGlvbiB1
cCB0byB0aGUgdXNlciBpbnRlcmZhY2UuIEhhdmluZyBhbiBBVkJMIGNvbW1hbmQgd291bGQgbWFr
ZSBpdCBwb3NzaWJsZSBmb3IgYSBjbGllbnQgdG8NCj4gZGV0ZXJtaW5lIHdoZXRoZXIgZW5vdWdo
IHN0b3JhZ2Ugc3BhY2UgaXMgYXZhaWxhYmxlIGF0IHRoZSBzZXJ2ZXIgQkVGT1JFIHNlbmRpbmcg
YSBmaWxlLCB3aGljaCB3b3VsZCBiZSBncmVhdCB3aGVuIHlvdSdyZSBhYm91dCB0bw0KPiBzZW5k
IGEgMTBHQiBmaWxlIGFuZCB5b3Ugb25seSBoYXZlIDkuOTlHQiBvZiBzdG9yYWdlIHNwYWNlIGxl
ZnQuIDstXQ0KPg0KPiBEU0laIC0gVGhpcyBjb3VsZCBjZXJ0YWlubHkgYmUgdXNlZnVsLCBhbHRo
b3VnaCBJIHdvdWxkIHByb2JhYmx5IHdhbnQgYSB1c2VyIHRvIGJlIGxvZ2dlZCBpbiAobm90IGFu
b255bW91cykgYmVmb3JlIEkgc3VwcG9ydGVkIHRoaXMNCj4gY29tbWFuZCBpbiBvcmRlciB0byBy
ZWR1Y2UgdGhlIHJpc2sgb2YgZGVuaWFsLW9mLXNlcnZpY2UuIEknZCBwcm9iYWJseSBtYWtlIGl0
IGNvbmZpZ3VyYWJsZSBzbyBhcyBub3QgdG8gdGllIHVwIHRvbyBtYW55IHNlcnZlcg0KPiByZXNv
dXJjZXMgZm9yIGxhcmdlIGRpcmVjdG9yeSBzdHJ1Y3R1cmVzOyBhbmQgb25jZSBhZ2FpbiwgaWYg
dGhlIGZlYXR1cmUgd2VyZSBkaXNhYmxlZCBJIHdvdWxkIHByb2JhYmx5IGhpZGUgdGhlIGNvbW1h
bmQgZnJvbSBhIEZFQVQNCj4gcmVzcG9uc2Ugc28gaXQgd291bGQgbm90IGJlIGRpc2NvdmVyYWJs
ZSBhbmQgcmV0dXJuIGEgNTAwIG9yIDUwMiByZXBseSB3aGVuIERTSVogaXMgc2VudCBieSB0aGUg
Y2xpZW50IGFuZCBkaXNhYmxlZCBhdCB0aGUgc2VydmVyLg0KPg0KPiBUSE1CIC0gSSBoYXZlIHRv
IGFkbWl0LCBJIGRvbid0IHdvcmsgb24gYSBncmFwaGljYWwgRlRQIGNsaWVudCwgc28gdGhpcyBj
b21tYW5kIGlzIGxlc3MgdXNlZnVsIHRvIG1lIHBlcnNvbmFsbHksIGJ1dCBJIGNhbiBzZWUgdGhl
DQo+IG1lcml0IHRoYXQgaXQgbWlnaHQgaGF2ZSB0byBzb21lb25lIHRoYXQgZGVzaWducyBhIGdy
YXBoaWNhbCBjbGllbnQuIFRoYXQgYmVpbmcgc2FpZCwgSSdtIG5vdCBhIGJpZyBmYW4gb2YgY29t
cHV0aW5nIHRoZSB0aHVtYm5haWwNCj4gZHluYW1pY2FsbHksIG5vciBhbSBJIGZvbmQgb2YgYWxs
b3dpbmcgdGhlIGNsaWVudCB0byBzcGVjaWZ5IHRoZSB0aHVtYm5haWwgZm9ybWF0IGFuZCBzaXpl
LiBJIHRoaW5rIHRoYXQgaXQgd291bGQgYmUgYmV0dGVyIGlmIHRoZQ0KPiBzZXJ2ZXIgY291bGQg
cHJlLWNhY2hlIHRodW1ibmFpbHMgZm9yIGFueSBmaWxlIHR5cGUgaW4gYSBzZXJ2ZXItZGV0ZXJt
aW5lZCBzaXplIGFuZCBpbWFnZSBmb3JtYXQsIGFuZCB0aGVuIHJldHVybiB0aGUgYmluYXJ5IGRh
dGENCj4gYW5kIGltYWdlIGZvcm1hdCBpbmZvcm1hdGlvbiB0byB0aGUgY2xpZW50LiBGb3IgZXhh
bXBsZSwgbW9zdCBncmFwaGljYWxseS1iYXNlZCBvcGVyYXRpbmcgc3lzdGVtcyBoYXZlIHNvbWUg
bWV0aG9kIGZvciBkaXNwbGF5aW5nDQo+IGZpbGUgaWNvbnMgdG8gYSB1c2VyIHRoYXQgaXMgc2Vh
dGVkIGF0IGEgY29tcHV0ZXIgdGVybWluYWwsIHNvIGFuIEZUUCBzZXJ2ZXIgaW1wbGVtZW50YXRp
b24gY291bGQgc2ltcGx5IHJldHVybiB0aGF0IHNhbWUgaWNvbiB0byBhDQo+IGNsaWVudCBpbiBy
ZXNwb25zZSB0byBhIFRITUIgcmVxdWVzdC4NCj4NCj4gUGxlYXNlIGJlYXIgaW4gbWluZCwgSSBo
YXZlbid0IGdpdmVuIGEgbG90IG9mIHRob3VnaHQgYXMgdG8gd2hhdCB0aGUgY2xpZW50L3NlcnZl
ciBpbnRlcmNoYW5nZSBtaWdodCBsb29rIGxpa2UgaWYgdGhlIHNlcnZlciB3ZXJlDQo+IG1vcmUg
aW4gY29udHJvbCBvZiB0aGUgcmVzcG9uc2UgdG8gYSBUSE1CIHJlcXVlc3QsIGJ1dCBpdCB3b3Vs
ZCBwcm9iYWJseSBiZSBzdWZmaWNpZW50IHRvIHNpbXBseSByZXR1cm4gdGhlIGltYWdlIHR5cGUg
YXMgcGFydCBvZg0KPiB0aGUgcmVzcG9uc2UgYW5kIGxldCB0aGUgY2xpZW50IGRldGVybWluZSB0
aGUgaW1hZ2UgZGltZW5zaW9ucyBiYXNlZCBvbiB0aGUgY2xpZW50J3MgY2FwYWJpbGl0aWVzIGZv
ciByZWFkaW5nIHRoZSBpbWFnZSBkYXRhLiAoQXMgYQ0KPiBzZXJ2ZXIgZ3V5IEkgbGlrZSB0byBw
dXNoIGFueSBjbGllbnQtZnJpZW5kbHkgcHJvY2Vzc2luZyBvbiB0aGUgY2xpZW50IHdoZW5ldmVy
IHBvc3NpYmxlLiA7LV0pIFlvdSBjb3VsZCBib3Jyb3cgYW4gaWRlYSBmcm9tIHRoZQ0KPiBIQVNI
IGRpc2N1c3Npb24gdGhhdCB3ZSd2ZSBiZWVuIGhhdmluZyBhbmQgbWFrZSB0aGUgdGh1bWJuYWls
IGltYWdlIHR5cGUgY29uZmlndXJhYmxlIGZvciB0aGUgY2xpZW50IGJ5IHVzaW5nIGFuIE9QVFMg
Y29tbWFuZCwgd2hpY2gNCj4gbWlnaHQgbG9vayBsaWtlIHRoZSBmb2xsb3dpbmcgZXhhbXBsZXMu
DQo+DQo+IEluIHRoaXMgZmlyc3QgZXhhbXBsZSwgdGhlIHNlcnZlciBoYXMgYSBwcmUtY29uZmln
dXJlZCB0aHVtYm5haWwgaW1hZ2UgdHlwZSBvZiBKUEcsIGFuZCBtYXkgaGF2ZSBwcmUtY2FjaGVk
IHRoZSB0aHVtYm5haWxzIGZvcg0KPiBmaWxlczsgYW55IFRITUIgcmVxdWVzdCB3aXRoIG5vIE9Q
VFMgc3BlY2lmaWVkIHdvdWxkIHVzZSB0aGUgc2VydmVyJ3MgcHJlLWNvbmZpZ3VyZWQgdGh1bWJu
YWlsIGltYWdlIHR5cGUgb2YgSlBHIGFuZCBpbWFnZSB0eXBlIGlzDQo+IHNwZWNpZmllZCBpbiB0
aGUgY29tbWFuZCBjaGFubmVsIHJlc3BvbnNlOg0KPg0KPiBDPiBUSE1CIHdpZGdldC5wbmcNCj4g
Uz4gMTUwIEpQRyBTdGFydGluZyB0aHVtYm5haWwgdHJhbnNmZXIgKDEyMzQgQnl0ZXMpIGZvciB3
aWRnZXQucG5nDQo+IFM+IDIyNiBUcmFuc2ZlciBjb21wbGV0ZS4NCj4NCj4gSW4gdGhlc2UgbmV4
dCBleGFtcGxlcyBhIGNsaWVudCBpcyBhc2tpbmcgZm9yIGRpZmZlcmVudCB0aHVtYm5haWwgaW1h
Z2UgdHlwZXMgYnkgdXNpbmcgT1BUUyBjb21tYW5kcywgYW5kIHRoZSB0aHVtYm5haWwgaW1hZ2Ug
dHlwZXMNCj4gd291bGQgc3RpbGwgYmUgc3BlY2lmaWVkIGluIHRoZSBjb21tYW5kIGNoYW5uZWwg
cmVzcG9uc2VzOg0KPg0KPiBDPiBPUFRTIFRITUIgR0lGDQo+IFM+IDIwMCBPUFRTIFRITUIgR0lG
IGNvbW1hbmQgc3VjY2Vzc2Z1bC4NCj4NCj4gQz4gVEhNQiB3aWRnZXQucHNwDQo+IFM+IDE1MCBH
SUYgU3RhcnRpbmcgdGh1bWJuYWlsIHRyYW5zZmVyICgxMjM0IEJ5dGVzKSBmb3Igd2lkZ2V0LnBz
cA0KPiBTPiAyMjYgVHJhbnNmZXIgY29tcGxldGUuDQo+DQo+IEM+IE9QVFMgVEhNQiBQTkcNCj4g
Uz4gMjAwIE9QVFMgVEhNQiBQTkcgY29tbWFuZCBzdWNjZXNzZnVsLg0KPg0KPiBDPiBUSE1CIHdp
ZGdldC5kb2MNCj4gUz4gMTUwIFBORyBTdGFydGluZyB0aHVtYm5haWwgdHJhbnNmZXIgKDEyMzQg
Qnl0ZXMpIGZvciB3aWRnZXQuZG9jDQo+IFM+IDIyNiBUcmFuc2ZlciBjb21wbGV0ZS4NCj4NCj4g
SW4gdGhpcyBuZXh0IGV4YW1wbGUgYSBjbGllbnQgaXMgYXNraW5nIGZvciBhbiB1bnN1cHBvcnRl
ZCBpbWFnZSB0eXBlLCBzbyB0aGUgc2VydmVyIHdvdWxkIHNpbXBseSByZXR1cm4gdGhlIGFwcHJv
cHJpYXRlIGVycm9yDQo+IHJlcGx5Og0KPg0KPiBDPiBPUFRTIFRITUIgRk9PDQo+IFM+IDUwMSBV
bnN1cHBvcnRlZCB0aHVtYm5haWwgZm9ybWF0Lg0KPg0KPiBJbiB0aGlzIG5leHQgZXhhbXBsZSBh
IGNsaWVudCBpcyBhc2tpbmcgZm9yIHRoZSBjdXJyZW50bHktY29uZmlndXJlZCB0aHVtYm5haWwg
aW1hZ2UgdHlwZSwgc28gdGhlIHNlcnZlciB3b3VsZCByZXR1cm4gdGhlDQo+IGFwcHJvcHJpYXRl
IHJlc3BvbnNlOg0KPg0KPiBDPiBPUFRTIFRITUINCj4gUz4gMjAwIEpQRw0KPg0KPiBZb3UgbWln
aHQgdGFrZSB0aGlzIG9uZSBzdGVwIGZ1cnRoZXIgLSB0aGUgc2VydmVyIG1pZ2h0IGNob29zZSB0
byBvbmx5IHN1cHBvcnQgaXRzIHByZS1jb25maWd1cmVkIHRodW1ibmFpbCBpbWFnZSB0eXBlLCB0
aGVyZWJ5DQo+IGFsbG93aW5nIHByZS1jYWNoaW5nIG9mIGFsbCB0aHVtYm5haWxzIGluIG9uZSBz
cGVjaWZpYyBpbWFnZSBmb3JtYXQuIEluIHRoaXMgZXhhbXBsZSBhIGNsaWVudCBpcyBhc2tpbmcg
Zm9yIFBORyB0aHVtYm5haWxzLCB3aGljaA0KPiBTSE9VTEQgYmUgYSBzdXBwb3J0ZWQgaW1hZ2Ug
dHlwZSwgYnV0IHRoZSBzZXJ2ZXIgb25seSBzdXBwb3J0cyBhIHByZS1jb25maWd1cmVkIHRodW1i
bmFpbCBpbWFnZSB0eXBlIGZvciBKUEcgZmlsZXMgYW5kIHJldHVybnMgdGhlDQo+IGFwcHJvcHJp
YXRlIGVycm9yIHJlcGx5ICg1MDQ/KSBhbmQgdGhlIHNlcnZlcidzIHByZS1jb25maWd1cmVkIHRo
dW1ibmFpbCBpbWFnZSB0eXBlIGlzIHNwZWNpZmllZCBpbiB0aGUgc3Vic2VxdWVudCBjb21tYW5k
IGNoYW5uZWwNCj4gcmVzcG9uc2UgdG8gYSBUSE1CIHJlcXVlc3Q6DQo+DQo+IEM+IE9QVFMgVEhN
QiBQTkcNCj4gUz4gNTA0IFNwZWNpZnlpbmcgdGh1bWJuYWlsIGZvcm1hdHMgaXMgdW5zdXBwb3J0
ZWQuDQo+DQo+IEM+IFRITUIgd2lkZ2V0Lnhscw0KPiBTPiAxNTAgSlBHIFN0YXJ0aW5nIHRodW1i
bmFpbCB0cmFuc2ZlciAoMTIzNCBCeXRlcykgZm9yIHdpZGdldC54bHMNCj4gUz4gMjI2IFRyYW5z
ZmVyIGNvbXBsZXRlLg0KPg0KPiBBcyBJIHNhaWQgZWFybGllciwgSSBoYWRuJ3QgZ2l2ZW4gbXVj
aCB0aG91Z2h0IGFzIHRvIHdoYXQgdGhlIGNsaWVudC9zZXJ2ZXIgVEhNQiBpbnRlcmNoYW5nZSBt
aWdodCBsb29rIGxpa2UgaWYgeW91IHB1dCB0aGUgc2VydmVyDQo+IGluIGNvbnRyb2wgaW5zdGVh
ZCBvZiB0aGUgY2xpZW50LCBidXQgYXMgYSBzZXJ2ZXIgZ3V5IEknZCByYXRoZXIgc2VlIFRITUIg
bG9vayBhIGxpdHRsZSBtb3JlIGxpa2UgdGhlIGV4YW1wbGVzIHRoYXQgSSBnYXZlLiA7LV0NCj4N
Cj4gVGhhbmtzIGFnYWluIQ0KPg0KPiBSb2JlcnQgTWNNdXJyYXkNCj4gcm9ibWNtQG1pY3Jvc29m
dC5jb20NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gZnRwZXh0IG1haWxpbmcgbGlzdA0KPiBmdHBleHRAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9mdHBleHQNCj4NCj4NCj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gZnRwZXh0IG1haWxpbmcgbGlz
dA0KPiBmdHBleHRAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9mdHBleHQNCj4NCj4NCj4NCj4NCj4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4gZnRwZXh0IG1haWxpbmcgbGlzdA0KPiBmdHBleHRA
aWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9mdHBleHQN
Cj4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4gZnRwZXh0IG1haWxpbmcgbGlzdA0KPiBmdHBleHRAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9mdHBleHQNCj4NCg0Kd2Ztcw0K

From prvs=19431281bb=mpp@rhinosoft.com  Tue Nov 23 06:39:26 2010
Return-Path: <prvs=19431281bb=mpp@rhinosoft.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 15A533A6976 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 06:39:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.859
X-Spam-Level: 
X-Spam-Status: No, score=-1.859 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
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 RFLdc0dNnDB1 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 06:39:21 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id 297883A6973 for <ftpext@ietf.org>; Tue, 23 Nov 2010 06:39:20 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009935313.msg for <ftpext@ietf.org>; Tue, 23 Nov 2010 08:40:17 -0600
X-Spam-Processed: rhinosoft.com, Tue, 23 Nov 2010 08:40:17 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=19431281bb=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <DF5FFBB09B4142A789B8461B3730024E@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "Mat Berchtold" <mb@smartftp.com>, "William F. Maton" <wmaton@ottix.net>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net><AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com><914CA95DAC22422C825C665E4E76F860@rhinooffice.net> <Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net> <41871DBEA4CB724B93AC2D8CAADADBF41463C77079@mx.smartsoft.local>
In-Reply-To: <41871DBEA4CB724B93AC2D8CAADADBF41463C77079@mx.smartsoft.local>
Date: Tue, 23 Nov 2010 08:40:14 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 14:39:26 -0000

Hi Mat,

>CSID after login
Sounds good to me, I don't have a good reason for allowing it before login.

>Facts
I don't have any problem with this either, except for "ProductVersion".  The problem I have with this is that we would be forcing 
venders into a particular version numbering scheme.  Although both you and I and many other vendors use this format, some do not and 
consequently would be unable to follow the specification.

> The draft proposes that the client must provide the name and version...
Agreed.

I would also like to give credit to Mat, that the CSID command was actually Mat's idea.  Prior to preparing this document we 
discussed other commands that we might like to include in this draft.  CSID came out of that discussion.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "Mat Berchtold" <mb@smartftp.com>
Sent: Tuesday, November 23, 2010 8:13 AM
To: "William F. Maton" <wmaton@ottix.net>; "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: <ftpext@ietf.org>
Subject: RE: [ftpext] draft-peterson-streamlined-ftp-command-extensions

Hello Mark ..

>CSID after login
I also think the CSID command should only be available after login. I cannot think of a good reason where a  client with good 
intentions would need it before. But maybe I'm missing something here?

>Facts
For the facts, I would propose the following facts which would replace the existing Name and Version facts:
VendorName
ProductName
ProductVersion
Where ProductVersion must be in the following format 1*DIGIT "." 1*DIGIT "." 1*DIGIT* "." 1*DIGIT which represents the version as 
following: major.minor.build.patch

An example:
VendorName: SmartSoft Ltd.
ProductName: SmartFTP
ProductVersion: 4.0.1145.0

>Server/Client fact requirement
The draft proposes that the client must provide the name and version fact where for the server these facts are optional. For 
equality both parties involved should have equal requirements/rights. My proposal is that all facts are optional. The reasoning is 
that there is no need for the client to expose its name or version if it only wants to figure out the case sensitivity of the server 
file system.

Regards,
Mat


-----Original Message-----
From: ftpext-bounces@ietf.org [mailto:ftpext-bounces@ietf.org] On Behalf Of William F. Maton
Sent: Tuesday, 23 November, 2010 14:55
To: Mark P. Peterson
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions

On Tue, 23 Nov 2010, Mark P. Peterson wrote:

> Hi All,
>
> Is there anyone else that agrees with Damin about CSID?  He says it SHOULD be available only after login.

Hi Mark,
        I'm certainly and old enough salt at systems administration to think that identification before authentication or 
authorization is not a good thing.  It makes it easier for the scanners to pick-off what servers are running.  I'd like to force 
them into making the extra effort, since it might as well cost them more work and I can monitor the activity better.

        I think standardizing CSID (from the old non-standard CLNT) is a good thing though.  It should be left up to the implementor 
to support it.

        I've also read he rest of that I-D and have more thoughts on it, but that's for another email.


> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
>
> From: Damin
> Sent: Monday, November 22, 2010 10:17 PM
> To: ftpext@ietf.org
> Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> Hi,
>
>
> On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:
>
> Hi Robert,
>
> Thank you for taking the time to review the commands.  If you don't mind I would
> like to respond to your comments:
>
> CSID:
>
>> For security reasons I would probably want the CSID exchange to occur AFTER the client has logged in, but I might be 
>> overreacting.
>
>
> There is a lot of discussion on the Internet about servers providing "too" much information, especially prior to login.  But 
> having
> worked on both sides of the FTP process, it's usually very easy for the client to identify what brand or flavor the server is.
> There are details which usually identify the server such as the completeness of the FEAT response, the welcome message, responses 
> to
> certain messages, etc.  So, I think it's okay to be available prior to login.  I could change the document to read that it should 
> be
> up to the server's implementation whether or not it's available.
>
> I prefer to edge on the side of caution. I donÂīt see any good reason that this SHOULD be available before login. Commands 
> available
> prior to login should be as limited as possible.
>
>
> RMDA:
>
>> In a server implementation I would probably make this command configurable, so administrators would have an option to disable the
>> feature.  In which case I would probably hide the command from a FEAT response so it would not be discoverable and have the 
>> server
>> return a 500 or 502 reply when RMDA is sent by the client and disabled at the server.
>
>
> I don't think my document specifies that it isn't configurable.  My implementation in Serv-U is configurable as is almost all 
> other
> FTP commands.  I think this can be left up to the server implementation.  Your possible implementation is exactly how Serv-U
> implements it.  If the feature is disabled, it doesn't appear in the FEAT response, nor is it available through the HELP command.
>
>
> AVBL:
>> ...
>
> Your comments address the reason for its existence.  The client-side implementation in SmartFTP uses the command in this manner.
>
> DSIZ:
>> This could certainly be useful, although I would probably want a user to be logged in...
>
> Any information about paths or files requires login in FTP.  I am sure this is the case here as well.  If a server wouldn't want 
> the
> "anonymous" user to have access to this command it could be configured to disallow this command at the server's implementation or
> configuration.  This should be left up to the implementation of the server or administrator of the server.
>
>> I'd probably make it configurable so as not to tie up too many server resources for large directory structures;...
>
> Agreed, the time-consuming nature of the implementation is discussed but configuration by an administrator or 
> server-implementation
> is not.   Do you think such verbiage is required?
>
>
> THMB:
>
>> I'm not a big fan of computing the thumbnail dynamically, nor am I fond of allowing the client to specify the thumbnail format 
>> and
>> size.
>
>
> That's the point of the command, though.  It's to reduce the amount of data that is required to travel over the wire.  The idea is
> to shorten delivery time to the client, letting the client decide what is best for the client, not the server.  Some clients may
> want very small images, say for a Windows Explorer style listing, others may want larger images (640x480 for example) to show a
> slide show.  I think the client needs to make that determination.  If the server decides to cache these generated images it can.
>
>
>> I think that it would be better if the server could pre-cache thumbnails for any file type in a server-determined size and image
>> format, and then return the binary data and image format information to the client.
>
>
> This could waste server-side resources, the client might not even make a request for thumbnail images.
>
>
>> For example, most graphically-based operating systems have some method for displaying file icons to a user that is seated at a
>> computer terminal, so an FTP server implementation could simply return that same icon to a client in response to a THMB request.
>
>
> Right, but this isn't really the purpose of this command.  The purpose is to take an original image file and reduce it to a
> specified size, not to return the OS's icon representation for that particular file type (i.e., not SHGetFileInfo() in Windows).
>
> My proposed implementation is fairly straightforward.  If supported the FEAT command replies with THMB and the supported file 
> types.
> When the client wants a thumbnail it asks for it with a single command.  Here is a sample result from FTP Voyager and Serv-U:
>
> PORT 192,168,0,30,199,53
> 200 PORT command successful.
> THMB PNG 98 88 Thomas.JPG
> 150 Opening thumbnail image transfer BINARY mode data connection (19738 Bytes) for Thomas.JPG.
> 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%) transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.
>
> The client opens a data channel just like any other file transfer, then requests the file using THMB, followed by the output type,
> width, height, and the file name.  The server responds just like a file transfer but also includes the resulting size in
> parentheses.
>
> While designing this command the idea was to first make it simple for both sides, second to make it operate as any other download,
> and third to make it as flexible as possible, allowing the client to decide how the resulting data is to be used and what is 
> needed.
> Of course the server could be configured in any way needed.  For example if the server wanted to limit the size of the thumbnails,
> the server could do that.  Our implementation limits the number of simultaneous threads allowed to create the thumbnails at any
> given time.  I think these details need to be left to the server implementation.
>
> As for using an OPT command to configure an upcoming THMB command for its image type and the thumbnail size, that seems to
> complicate the command.  It's very easy to add these parameters into a single command, eliminating the required handshaking 
> between
> the client and server.  An added benefit is that neither the client nor the server are required to maintain these "options"
> throughout a session, rather all of the information required is sent in a single command.
>
> If you're interested in seeing it in action, download Serv-U and FTP Voyager or SmartFTP.  Login to the server, switch FTP Voyager
> to "Thumbnails" view.  With SmartFTP simply select an image file and a thumbnail image, of dynamic size, will appear in the 
> preview
> pane.
>
>
> Thank you again for taking the time to provide your feedback.  I look forward to your comments to the above.
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Robert McMurray" <robmcm@microsoft.com>
> Sent: Monday, November 22, 2010 5:01 PM
> To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>; <mark.peterson@rhinosoft.com>
> Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> [Note: Renaming the thread from 'Submitting new drafts'.]
>
>> Anthony Bryan wrote:
>>
>> I don't mean to single you out, but
>> you showed interest in an CSID/AGNT
>> command. Do you have any opinion on
>> the other 4 commands in the draft?
>
> Thanks, Anthony.
>
> No worries - I meant to send a better response in the wake of my withdrawn AGNT draft and Mark's current Streamlined FTP Command
> Extensions draft, but I had been remiss at taking the time to collect my thoughts in a more meaningful way. But since you asked,
> this seems like as good at time as any. ;-]
>
> CSID - As evidenced by my short-lived AGNT proposal, I think it's very useful to have some sort of client/server discovery 
> command.
> FEAT does a good job of advertising the list of commands that are supported by a server, but Mark's proposed CSID command sequence
> provides a much better way for servers and client to identify their features to each other in detail. For security reasons I would
> probably want the CSID exchange to occur AFTER the client has logged in, but I might be overreacting.
>
> RMDA - This could be a very useful command, and it would parallel the functionality that I'm sure we all typically use in a native
> operating system environment. In a server implementation I would probably make this command configurable, so administrators would
> have an option to disable the feature. In which case I would probably hide the command from a FEAT response so it would not be
> discoverable and have the server return a 500 or 502 reply when RMDA is sent by the client and disabled at the server.
>
> (Note: I mention my thoughts about server implementation details just to open up the discussion as to whether any implementation
> details should be called out in the draft, or if we should leave that up to the implementers to decide.)
>
> AVBL - This command could be very useful in a client/server world; our FTP server implementation currently returns the available
> size after a successful login sequence, and the available size is based on server disk quotas and such. That being said, not every
> FTP client will bubble that information up to the user interface. Having an AVBL command would make it possible for a client to
> determine whether enough storage space is available at the server BEFORE sending a file, which would be great when you're about to
> send a 10GB file and you only have 9.99GB of storage space left. ;-]
>
> DSIZ - This could certainly be useful, although I would probably want a user to be logged in (not anonymous) before I supported 
> this
> command in order to reduce the risk of denial-of-service. I'd probably make it configurable so as not to tie up too many server
> resources for large directory structures; and once again, if the feature were disabled I would probably hide the command from a 
> FEAT
> response so it would not be discoverable and return a 500 or 502 reply when DSIZ is sent by the client and disabled at the server.
>
> THMB - I have to admit, I don't work on a graphical FTP client, so this command is less useful to me personally, but I can see the
> merit that it might have to someone that designs a graphical client. That being said, I'm not a big fan of computing the thumbnail
> dynamically, nor am I fond of allowing the client to specify the thumbnail format and size. I think that it would be better if the
> server could pre-cache thumbnails for any file type in a server-determined size and image format, and then return the binary data
> and image format information to the client. For example, most graphically-based operating systems have some method for displaying
> file icons to a user that is seated at a computer terminal, so an FTP server implementation could simply return that same icon to 
> a
> client in response to a THMB request.
>
> Please bear in mind, I haven't given a lot of thought as to what the client/server interchange might look like if the server were
> more in control of the response to a THMB request, but it would probably be sufficient to simply return the image type as part of
> the response and let the client determine the image dimensions based on the client's capabilities for reading the image data. (As 
> a
> server guy I like to push any client-friendly processing on the client whenever possible. ;-]) You could borrow an idea from the
> HASH discussion that we've been having and make the thumbnail image type configurable for the client by using an OPTS command, 
> which
> might look like the following examples.
>
> In this first example, the server has a pre-configured thumbnail image type of JPG, and may have pre-cached the thumbnails for
> files; any THMB request with no OPTS specified would use the server's pre-configured thumbnail image type of JPG and image type is
> specified in the command channel response:
>
> C> THMB widget.png
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
> S> 226 Transfer complete.
>
> In these next examples a client is asking for different thumbnail image types by using OPTS commands, and the thumbnail image 
> types
> would still be specified in the command channel responses:
>
> C> OPTS THMB GIF
> S> 200 OPTS THMB GIF command successful.
>
> C> THMB widget.psp
> S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
> S> 226 Transfer complete.
>
> C> OPTS THMB PNG
> S> 200 OPTS THMB PNG command successful.
>
> C> THMB widget.doc
> S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
> S> 226 Transfer complete.
>
> In this next example a client is asking for an unsupported image type, so the server would simply return the appropriate error
> reply:
>
> C> OPTS THMB FOO
> S> 501 Unsupported thumbnail format.
>
> In this next example a client is asking for the currently-configured thumbnail image type, so the server would return the
> appropriate response:
>
> C> OPTS THMB
> S> 200 JPG
>
> You might take this one step further - the server might choose to only support its pre-configured thumbnail image type, thereby
> allowing pre-caching of all thumbnails in one specific image format. In this example a client is asking for PNG thumbnails, which
> SHOULD be a supported image type, but the server only supports a pre-configured thumbnail image type for JPG files and returns the
> appropriate error reply (504?) and the server's pre-configured thumbnail image type is specified in the subsequent command channel
> response to a THMB request:
>
> C> OPTS THMB PNG
> S> 504 Specifying thumbnail formats is unsupported.
>
> C> THMB widget.xls
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
> S> 226 Transfer complete.
>
> As I said earlier, I hadn't given much thought as to what the client/server THMB interchange might look like if you put the server
> in control instead of the client, but as a server guy I'd rather see THMB look a little more like the examples that I gave. ;-]
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
>
>
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

wfms 



From prvs=19431281bb=mpp@rhinosoft.com  Tue Nov 23 06:40:43 2010
Return-Path: <prvs=19431281bb=mpp@rhinosoft.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 C7A1228C113 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 06:40:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.882
X-Spam-Level: 
X-Spam-Status: No, score=-1.882 tagged_above=-999 required=5 tests=[AWL=0.117,  BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
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 ZNKtyRO7GTrN for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 06:40:41 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id CF2CF3A6973 for <ftpext@ietf.org>; Tue, 23 Nov 2010 06:40:40 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009935319.msg for <ftpext@ietf.org>; Tue, 23 Nov 2010 08:41:37 -0600
X-Spam-Processed: rhinosoft.com, Tue, 23 Nov 2010 08:41:37 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=19431281bb=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <6C3AA348BF6146F2885B2094B8E8E29C@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "William F. Maton" <wmaton@ottix.net>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net> <AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com> <914CA95DAC22422C825C665E4E76F860@rhinooffice.net> <Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net>
In-Reply-To: <Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net>
Date: Tue, 23 Nov 2010 08:41:36 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 14:40:43 -0000

Hi William,

Thank you for taking the time to respond.  I cannot think
of any real reason why CSID shouldn't only be allowed after login.
I will change the document to reflect this.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "William F. Maton" <wmaton@ottix.net>
Sent: Tuesday, November 23, 2010 7:55 AM
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: "Damin" <damin@emuxperts.net>; <ftpext@ietf.org>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions

On Tue, 23 Nov 2010, Mark P. Peterson wrote:

> Hi All,
>
> Is there anyone else that agrees with Damin about CSID?  He says it SHOULD be available only after login.

Hi Mark,
  I'm certainly and old enough salt at systems administration to
think that identification before authentication or authorization is not a
good thing.  It makes it easier for the scanners to pick-off what servers
are running.  I'd like to force them into making the extra effort, since
it might as well cost them more work and I can monitor the activity
better.

  I think standardizing CSID (from the old non-standard CLNT) is a
good thing though.  It should be left up to the implementor to support it.

  I've also read he rest of that I-D and have more thoughts on it,
but that's for another email.


> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
>
> From: Damin
> Sent: Monday, November 22, 2010 10:17 PM
> To: ftpext@ietf.org
> Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> Hi,
>
>
> On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:
>
> Hi Robert,
>
> Thank you for taking the time to review the commands.  If you don't mind I would
> like to respond to your comments:
>
> CSID:
>
>> For security reasons I would probably want the CSID exchange to occur AFTER the client has logged in, but I might be 
>> overreacting.
>
>
> There is a lot of discussion on the Internet about servers providing "too" much information, especially prior to login.  But 
> having
> worked on both sides of the FTP process, it's usually very easy for the client to identify what brand or flavor the server is.
> There are details which usually identify the server such as the completeness of the FEAT response, the welcome message, responses 
> to
> certain messages, etc.  So, I think it's okay to be available prior to login.  I could change the document to read that it should 
> be
> up to the server's implementation whether or not it's available.
>
> I prefer to edge on the side of caution. I donÂīt see any good reason that this SHOULD be available before login. Commands 
> available
> prior to login should be as limited as possible.
>
>
> RMDA:
>
>> In a server implementation I would probably make this command configurable, so administrators would have an option to disable the
>> feature.  In which case I would probably hide the command from a FEAT response so it would not be discoverable and have the 
>> server
>> return a 500 or 502 reply when RMDA is sent by the client and disabled at the server.
>
>
> I don't think my document specifies that it isn't configurable.  My implementation in Serv-U is configurable as is almost all 
> other
> FTP commands.  I think this can be left up to the server implementation.  Your possible implementation is exactly how Serv-U
> implements it.  If the feature is disabled, it doesn't appear in the FEAT response, nor is it available through the HELP command.
>
>
> AVBL:
>> ...
>
> Your comments address the reason for its existence.  The client-side implementation in SmartFTP uses the command in this manner.
>
> DSIZ:
>> This could certainly be useful, although I would probably want a user to be logged in...
>
> Any information about paths or files requires login in FTP.  I am sure this is the case here as well.  If a server wouldn't want 
> the
> "anonymous" user to have access to this command it could be configured to disallow this command at the server's implementation or
> configuration.  This should be left up to the implementation of the server or administrator of the server.
>
>> I'd probably make it configurable so as not to tie up too many server resources for large directory structures;...
>
> Agreed, the time-consuming nature of the implementation is discussed but configuration by an administrator or 
> server-implementation
> is not.   Do you think such verbiage is required?
>
>
> THMB:
>
>> I'm not a big fan of computing the thumbnail dynamically, nor am I fond of allowing the client to specify the thumbnail format 
>> and
>> size.
>
>
> That's the point of the command, though.  It's to reduce the amount of data that is required to travel over the wire.  The idea is
> to shorten delivery time to the client, letting the client decide what is best for the client, not the server.  Some clients may
> want very small images, say for a Windows Explorer style listing, others may want larger images (640x480 for example) to show a
> slide show.  I think the client needs to make that determination.  If the server decides to cache these generated images it can.
>
>
>> I think that it would be better if the server could pre-cache thumbnails for any file type in a server-determined size and image
>> format, and then return the binary data and image format information to the client.
>
>
> This could waste server-side resources, the client might not even make a request for thumbnail images.
>
>
>> For example, most graphically-based operating systems have some method for displaying file icons to a user that is seated at a
>> computer terminal, so an FTP server implementation could simply return that same icon to a client in response to a THMB request.
>
>
> Right, but this isn't really the purpose of this command.  The purpose is to take an original image file and reduce it to a
> specified size, not to return the OS's icon representation for that particular file type (i.e., not SHGetFileInfo() in Windows).
>
> My proposed implementation is fairly straightforward.  If supported the FEAT command replies with THMB and the supported file 
> types.
> When the client wants a thumbnail it asks for it with a single command.  Here is a sample result from FTP Voyager and Serv-U:
>
> PORT 192,168,0,30,199,53
> 200 PORT command successful.
> THMB PNG 98 88 Thomas.JPG
> 150 Opening thumbnail image transfer BINARY mode data connection (19738 Bytes) for Thomas.JPG.
> 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%) transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.
>
> The client opens a data channel just like any other file transfer, then requests the file using THMB, followed by the output type,
> width, height, and the file name.  The server responds just like a file transfer but also includes the resulting size in
> parentheses.
>
> While designing this command the idea was to first make it simple for both sides, second to make it operate as any other download,
> and third to make it as flexible as possible, allowing the client to decide how the resulting data is to be used and what is 
> needed.
> Of course the server could be configured in any way needed.  For example if the server wanted to limit the size of the thumbnails,
> the server could do that.  Our implementation limits the number of simultaneous threads allowed to create the thumbnails at any
> given time.  I think these details need to be left to the server implementation.
>
> As for using an OPT command to configure an upcoming THMB command for its image type and the thumbnail size, that seems to
> complicate the command.  It's very easy to add these parameters into a single command, eliminating the required handshaking 
> between
> the client and server.  An added benefit is that neither the client nor the server are required to maintain these "options"
> throughout a session, rather all of the information required is sent in a single command.
>
> If you're interested in seeing it in action, download Serv-U and FTP Voyager or SmartFTP.  Login to the server, switch FTP Voyager
> to "Thumbnails" view.  With SmartFTP simply select an image file and a thumbnail image, of dynamic size, will appear in the 
> preview
> pane.
>
>
> Thank you again for taking the time to provide your feedback.  I look forward to your comments to the above.
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Robert McMurray" <robmcm@microsoft.com>
> Sent: Monday, November 22, 2010 5:01 PM
> To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>; <mark.peterson@rhinosoft.com>
> Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> [Note: Renaming the thread from 'Submitting new drafts'.]
>
>> Anthony Bryan wrote:
>>
>> I don't mean to single you out, but
>> you showed interest in an CSID/AGNT
>> command. Do you have any opinion on
>> the other 4 commands in the draft?
>
> Thanks, Anthony.
>
> No worries - I meant to send a better response in the wake of my withdrawn AGNT draft and Mark's current Streamlined FTP Command
> Extensions draft, but I had been remiss at taking the time to collect my thoughts in a more meaningful way. But since you asked,
> this seems like as good at time as any. ;-]
>
> CSID - As evidenced by my short-lived AGNT proposal, I think it's very useful to have some sort of client/server discovery 
> command.
> FEAT does a good job of advertising the list of commands that are supported by a server, but Mark's proposed CSID command sequence
> provides a much better way for servers and client to identify their features to each other in detail. For security reasons I would
> probably want the CSID exchange to occur AFTER the client has logged in, but I might be overreacting.
>
> RMDA - This could be a very useful command, and it would parallel the functionality that I'm sure we all typically use in a native
> operating system environment. In a server implementation I would probably make this command configurable, so administrators would
> have an option to disable the feature. In which case I would probably hide the command from a FEAT response so it would not be
> discoverable and have the server return a 500 or 502 reply when RMDA is sent by the client and disabled at the server.
>
> (Note: I mention my thoughts about server implementation details just to open up the discussion as to whether any implementation
> details should be called out in the draft, or if we should leave that up to the implementers to decide.)
>
> AVBL - This command could be very useful in a client/server world; our FTP server implementation currently returns the available
> size after a successful login sequence, and the available size is based on server disk quotas and such. That being said, not every
> FTP client will bubble that information up to the user interface. Having an AVBL command would make it possible for a client to
> determine whether enough storage space is available at the server BEFORE sending a file, which would be great when you're about to
> send a 10GB file and you only have 9.99GB of storage space left. ;-]
>
> DSIZ - This could certainly be useful, although I would probably want a user to be logged in (not anonymous) before I supported 
> this
> command in order to reduce the risk of denial-of-service. I'd probably make it configurable so as not to tie up too many server
> resources for large directory structures; and once again, if the feature were disabled I would probably hide the command from a 
> FEAT
> response so it would not be discoverable and return a 500 or 502 reply when DSIZ is sent by the client and disabled at the server.
>
> THMB - I have to admit, I don't work on a graphical FTP client, so this command is less useful to me personally, but I can see the
> merit that it might have to someone that designs a graphical client. That being said, I'm not a big fan of computing the thumbnail
> dynamically, nor am I fond of allowing the client to specify the thumbnail format and size. I think that it would be better if the
> server could pre-cache thumbnails for any file type in a server-determined size and image format, and then return the binary data
> and image format information to the client. For example, most graphically-based operating systems have some method for displaying
> file icons to a user that is seated at a computer terminal, so an FTP server implementation could simply return that same icon to 
> a
> client in response to a THMB request.
>
> Please bear in mind, I haven't given a lot of thought as to what the client/server interchange might look like if the server were
> more in control of the response to a THMB request, but it would probably be sufficient to simply return the image type as part of
> the response and let the client determine the image dimensions based on the client's capabilities for reading the image data. (As 
> a
> server guy I like to push any client-friendly processing on the client whenever possible. ;-]) You could borrow an idea from the
> HASH discussion that we've been having and make the thumbnail image type configurable for the client by using an OPTS command, 
> which
> might look like the following examples.
>
> In this first example, the server has a pre-configured thumbnail image type of JPG, and may have pre-cached the thumbnails for
> files; any THMB request with no OPTS specified would use the server's pre-configured thumbnail image type of JPG and image type is
> specified in the command channel response:
>
> C> THMB widget.png
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
> S> 226 Transfer complete.
>
> In these next examples a client is asking for different thumbnail image types by using OPTS commands, and the thumbnail image 
> types
> would still be specified in the command channel responses:
>
> C> OPTS THMB GIF
> S> 200 OPTS THMB GIF command successful.
>
> C> THMB widget.psp
> S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
> S> 226 Transfer complete.
>
> C> OPTS THMB PNG
> S> 200 OPTS THMB PNG command successful.
>
> C> THMB widget.doc
> S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
> S> 226 Transfer complete.
>
> In this next example a client is asking for an unsupported image type, so the server would simply return the appropriate error
> reply:
>
> C> OPTS THMB FOO
> S> 501 Unsupported thumbnail format.
>
> In this next example a client is asking for the currently-configured thumbnail image type, so the server would return the
> appropriate response:
>
> C> OPTS THMB
> S> 200 JPG
>
> You might take this one step further - the server might choose to only support its pre-configured thumbnail image type, thereby
> allowing pre-caching of all thumbnails in one specific image format. In this example a client is asking for PNG thumbnails, which
> SHOULD be a supported image type, but the server only supports a pre-configured thumbnail image type for JPG files and returns the
> appropriate error reply (504?) and the server's pre-configured thumbnail image type is specified in the subsequent command channel
> response to a THMB request:
>
> C> OPTS THMB PNG
> S> 504 Specifying thumbnail formats is unsupported.
>
> C> THMB widget.xls
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
> S> 226 Transfer complete.
>
> As I said earlier, I hadn't given much thought as to what the client/server THMB interchange might look like if you put the server
> in control instead of the client, but as a server guy I'd rather see THMB look a little more like the examples that I gave. ;-]
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
>
>
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

wfms 



From paulfordh@uk.ibm.com  Tue Nov 23 07:13:04 2010
Return-Path: <paulfordh@uk.ibm.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 6375028C0E5 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 07:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_MED=-4]
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 Z3wKdSjNaO1A for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 07:13:00 -0800 (PST)
Received: from mtagate5.uk.ibm.com (mtagate5.uk.ibm.com [194.196.100.165]) by core3.amsl.com (Postfix) with ESMTP id E34803A6961 for <ftpext@ietf.org>; Tue, 23 Nov 2010 07:12:59 -0800 (PST)
Received: from d06nrmr1307.portsmouth.uk.ibm.com (d06nrmr1307.portsmouth.uk.ibm.com [9.149.38.129]) by mtagate5.uk.ibm.com (8.13.1/8.13.1) with ESMTP id oANFDsd4015541 for <ftpext@ietf.org>; Tue, 23 Nov 2010 15:13:54 GMT
Received: from d06av11.portsmouth.uk.ibm.com (d06av11.portsmouth.uk.ibm.com [9.149.37.252]) by d06nrmr1307.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id oANFDlET3592210 for <ftpext@ietf.org>; Tue, 23 Nov 2010 15:13:53 GMT
Received: from d06av11.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av11.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id oANFDm8h002330 for <ftpext@ietf.org>; Tue, 23 Nov 2010 08:13:48 -0700
Received: from d06ml069.portsmouth.uk.ibm.com (d06ml069.portsmouth.uk.ibm.com [9.149.38.218]) by d06av11.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id oANFDlx5002321; Tue, 23 Nov 2010 08:13:47 -0700
In-Reply-To: <6C3AA348BF6146F2885B2094B8E8E29C@rhinooffice.net>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net> <AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com>	<914CA95DAC22422C825C665E4E76F860@rhinooffice.net> <Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net> <6C3AA348BF6146F2885B2094B8E8E29C@rhinooffice.net>
To: "Mark P. Peterson" <mpp@rhinosoft.com>, ftpext@ietf.org
MIME-Version: 1.0
X-KeepSent: 8C6635BE:33D2510D-802577E4:0051C5FE; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1 SHF149 July 17, 2009
From: Paul Ford-Hutchinson <paulfordh@uk.ibm.com>
Message-ID: <OF8C6635BE.33D2510D-ON802577E4.0051C5FE-802577E4.0053A63D@uk.ibm.com>
Date: Tue, 23 Nov 2010 15:16:59 +0000
X-MIMETrack: Serialize by Router on D06ML069/06/M/IBM(Release 8.0.2FP2|June 22, 2009) at 23/11/2010 15:17:01, Serialize complete at 23/11/2010 15:17:01
Content-Type: multipart/alternative; boundary="=_alternative 0053A245802577E4_="
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 15:13:04 -0000

This is a multipart message in MIME format.
--=_alternative 0053A245802577E4_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Two comments about the CSID before login question:

1) RFCs define protocols not implementations, so the discussion should be=20
about what =5Fcan=5F happen and how a client/server should respond.
2) I'd like to be 100% certain what payload CSID can carry before banning=20
it totally prior to authentication.


Point 1 (the protocol vs implementation thing)
=3D=3D=3D=3D=3D=3D

We need to say what is and isn't allowed in the protocol, comments about=20
implementations are interesting but not really the thrust of an RFC.  In=20
this case, we need to state when a client may send CSID; what a server=20
should do if the client sends it at the wrong time - and at the right=20
time; whether the client should expect that a server might refuse to=20
answer a CSID command because it is in a particular state and that it=20
might be sensible for it to try again when in a different state in the=20
protocol (e.g. logged in).

Also, don't forget that users can log out too - so simply stating after a=20
USER command (or some such) isn't really good enough.

Point 2
=3D=3D=3D=3D=3D=3D

HTTPS is broken because of something similar.  Multi-homed http servers=20
cannot operate on HTTPS because the server needs to present the cert to=20
the client before the client tells the server which certificate (i.e.=20
host) it should be.

I don't know if CSID may contain host specific info  (ext=5Fcfactname and=20
local=5Ffact seem to be a bit of a catch all that might get used for=20
"hostname" or some such.) but be very wary of this catching people out. At =

the very least, if CSID should not be used for host identification, then=20
ban such values from being in these fields.



Perhaps CSID could be permitted to pass different information depending on =

the state of the user's session.  (which brings us back to the protocol vs =

implementation issue - should CSID always pass the same information=20
regardless of session state or is the peer allowed to use session context=20
to decide what to include - thus meaning that two calls to CSID might be=20
allowed to pass different values. In fact - is a client allowed to send=20
multiple CSID commands and what should a server do if the information=20
passed in the second command does not match that from the first (and does=20
REIN need to be involved?)?)

Cheers,
Paul

--=20

Paul Ford-Hutchinson CISSP - Tivoli Security Consultant
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU
IBM Certified Deployment Professional - Tivoli Compliance Insight Manager=20
V8.5

Tel +44 (0)7500 078379  (internal: 37269105)



From:
"Mark P. Peterson" <mpp@rhinosoft.com>
To:
"William F. Maton" <wmaton@ottix.net>
Cc:
ftpext@ietf.org
Date:
23/11/2010 14:45
Subject:
Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
Sent by:
ftpext-bounces@ietf.org



Hi William,

Thank you for taking the time to respond.  I cannot think
of any real reason why CSID shouldn't only be allowed after login.
I will change the document to reflect this.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "William F. Maton" <wmaton@ottix.net>
Sent: Tuesday, November 23, 2010 7:55 AM
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: "Damin" <damin@emuxperts.net>; <ftpext@ietf.org>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions

On Tue, 23 Nov 2010, Mark P. Peterson wrote:

> Hi All,
>
> Is there anyone else that agrees with Damin about CSID?  He says it=20
SHOULD be available only after login.

Hi Mark,
  I'm certainly and old enough salt at systems administration to
think that identification before authentication or authorization is not a
good thing.  It makes it easier for the scanners to pick-off what servers
are running.  I'd like to force them into making the extra effort, since
it might as well cost them more work and I can monitor the activity
better.

  I think standardizing CSID (from the old non-standard CLNT) is a
good thing though.  It should be left up to the implementor to support it.

  I've also read he rest of that I-D and have more thoughts on it,
but that's for another email.


> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
>
> From: Damin
> Sent: Monday, November 22, 2010 10:17 PM
> To: ftpext@ietf.org
> Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> Hi,
>
>
> On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:
>
> Hi Robert,
>
> Thank you for taking the time to review the commands.  If you don't mind =

I would
> like to respond to your comments:
>
> CSID:
>
>> For security reasons I would probably want the CSID exchange to occur=20
AFTER the client has logged in, but I might be=20
>> overreacting.
>
>
> There is a lot of discussion on the Internet about servers providing=20
"too" much information, especially prior to login.  But=20
> having
> worked on both sides of the FTP process, it's usually very easy for the=20
client to identify what brand or flavor the server is.
> There are details which usually identify the server such as the=20
completeness of the FEAT response, the welcome message, responses=20
> to
> certain messages, etc.  So, I think it's okay to be available prior to=20
login.  I could change the document to read that it should=20
> be
> up to the server's implementation whether or not it's available.
>
> I prefer to edge on the side of caution. I don=B4t see any good reason=20
that this SHOULD be available before login. Commands=20
> available
> prior to login should be as limited as possible.
>
>
> RMDA:
>
>> In a server implementation I would probably make this command=20
configurable, so administrators would have an option to disable the
>> feature.  In which case I would probably hide the command from a FEAT=20
response so it would not be discoverable and have the=20
>> server
>> return a 500 or 502 reply when RMDA is sent by the client and disabled=20
at the server.
>
>
> I don't think my document specifies that it isn't configurable.  My=20
implementation in Serv-U is configurable as is almost all=20
> other
> FTP commands.  I think this can be left up to the server implementation. =

 Your possible implementation is exactly how Serv-U
> implements it.  If the feature is disabled, it doesn't appear in the=20
FEAT response, nor is it available through the HELP command.
>
>
> AVBL:
>> ...
>
> Your comments address the reason for its existence.  The client-side=20
implementation in SmartFTP uses the command in this manner.
>
> DSIZ:
>> This could certainly be useful, although I would probably want a user=20
to be logged in...
>
> Any information about paths or files requires login in FTP.  I am sure=20
this is the case here as well.  If a server wouldn't want=20
> the
> "anonymous" user to have access to this command it could be configured=20
to disallow this command at the server's implementation or
> configuration.  This should be left up to the implementation of the=20
server or administrator of the server.
>
>> I'd probably make it configurable so as not to tie up too many server=20
resources for large directory structures;...
>
> Agreed, the time-consuming nature of the implementation is discussed but =

configuration by an administrator or=20
> server-implementation
> is not.   Do you think such verbiage is required?
>
>
> THMB:
>
>> I'm not a big fan of computing the thumbnail dynamically, nor am I fond =

of allowing the client to specify the thumbnail format=20
>> and
>> size.
>
>
> That's the point of the command, though.  It's to reduce the amount of=20
data that is required to travel over the wire.  The idea is
> to shorten delivery time to the client, letting the client decide what=20
is best for the client, not the server.  Some clients may
> want very small images, say for a Windows Explorer style listing, others =

may want larger images (640x480 for example) to show a
> slide show.  I think the client needs to make that determination.  If=20
the server decides to cache these generated images it can.
>
>
>> I think that it would be better if the server could pre-cache=20
thumbnails for any file type in a server-determined size and image
>> format, and then return the binary data and image format information to =

the client.
>
>
> This could waste server-side resources, the client might not even make a =

request for thumbnail images.
>
>
>> For example, most graphically-based operating systems have some method=20
for displaying file icons to a user that is seated at a
>> computer terminal, so an FTP server implementation could simply return=20
that same icon to a client in response to a THMB request.
>
>
> Right, but this isn't really the purpose of this command.  The purpose=20
is to take an original image file and reduce it to a
> specified size, not to return the OS's icon representation for that=20
particular file type (i.e., not SHGetFileInfo() in Windows).
>
> My proposed implementation is fairly straightforward.  If supported the=20
FEAT command replies with THMB and the supported file=20
> types.
> When the client wants a thumbnail it asks for it with a single command.=20
Here is a sample result from FTP Voyager and Serv-U:
>
> PORT 192,168,0,30,199,53
> 200 PORT command successful.
> THMB PNG 98 88 Thomas.JPG
> 150 Opening thumbnail image transfer BINARY mode data connection (19738=20
Bytes) for Thomas.JPG.
> 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%)=20
transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.
>
> The client opens a data channel just like any other file transfer, then=20
requests the file using THMB, followed by the output type,
> width, height, and the file name.  The server responds just like a file=20
transfer but also includes the resulting size in
> parentheses.
>
> While designing this command the idea was to first make it simple for=20
both sides, second to make it operate as any other download,
> and third to make it as flexible as possible, allowing the client to=20
decide how the resulting data is to be used and what is=20
> needed.
> Of course the server could be configured in any way needed.  For example =

if the server wanted to limit the size of the thumbnails,
> the server could do that.  Our implementation limits the number of=20
simultaneous threads allowed to create the thumbnails at any
> given time.  I think these details need to be left to the server=20
implementation.
>
> As for using an OPT command to configure an upcoming THMB command for=20
its image type and the thumbnail size, that seems to
> complicate the command.  It's very easy to add these parameters into a=20
single command, eliminating the required handshaking=20
> between
> the client and server.  An added benefit is that neither the client nor=20
the server are required to maintain these "options"
> throughout a session, rather all of the information required is sent in=20
a single command.
>
> If you're interested in seeing it in action, download Serv-U and FTP=20
Voyager or SmartFTP.  Login to the server, switch FTP Voyager
> to "Thumbnails" view.  With SmartFTP simply select an image file and a=20
thumbnail image, of dynamic size, will appear in the=20
> preview
> pane.
>
>
> Thank you again for taking the time to provide your feedback.  I look=20
forward to your comments to the above.
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Robert McMurray" <robmcm@microsoft.com>
> Sent: Monday, November 22, 2010 5:01 PM
> To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>;=20
<mark.peterson@rhinosoft.com>
> Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> [Note: Renaming the thread from 'Submitting new drafts'.]
>
>> Anthony Bryan wrote:
>>
>> I don't mean to single you out, but
>> you showed interest in an CSID/AGNT
>> command. Do you have any opinion on
>> the other 4 commands in the draft?
>
> Thanks, Anthony.
>
> No worries - I meant to send a better response in the wake of my=20
withdrawn AGNT draft and Mark's current Streamlined FTP Command
> Extensions draft, but I had been remiss at taking the time to collect my =

thoughts in a more meaningful way. But since you asked,
> this seems like as good at time as any. ;-]
>
> CSID - As evidenced by my short-lived AGNT proposal, I think it's very=20
useful to have some sort of client/server discovery=20
> command.
> FEAT does a good job of advertising the list of commands that are=20
supported by a server, but Mark's proposed CSID command sequence
> provides a much better way for servers and client to identify their=20
features to each other in detail. For security reasons I would
> probably want the CSID exchange to occur AFTER the client has logged in, =

but I might be overreacting.
>
> RMDA - This could be a very useful command, and it would parallel the=20
functionality that I'm sure we all typically use in a native
> operating system environment. In a server implementation I would=20
probably make this command configurable, so administrators would
> have an option to disable the feature. In which case I would probably=20
hide the command from a FEAT response so it would not be
> discoverable and have the server return a 500 or 502 reply when RMDA is=20
sent by the client and disabled at the server.
>
> (Note: I mention my thoughts about server implementation details just to =

open up the discussion as to whether any implementation
> details should be called out in the draft, or if we should leave that up =

to the implementers to decide.)
>
> AVBL - This command could be very useful in a client/server world; our=20
FTP server implementation currently returns the available
> size after a successful login sequence, and the available size is based=20
on server disk quotas and such. That being said, not every
> FTP client will bubble that information up to the user interface. Having =

an AVBL command would make it possible for a client to
> determine whether enough storage space is available at the server BEFORE =

sending a file, which would be great when you're about to
> send a 10GB file and you only have 9.99GB of storage space left. ;-]
>
> DSIZ - This could certainly be useful, although I would probably want a=20
user to be logged in (not anonymous) before I supported=20
> this
> command in order to reduce the risk of denial-of-service. I'd probably=20
make it configurable so as not to tie up too many server
> resources for large directory structures; and once again, if the feature =

were disabled I would probably hide the command from a=20
> FEAT
> response so it would not be discoverable and return a 500 or 502 reply=20
when DSIZ is sent by the client and disabled at the server.
>
> THMB - I have to admit, I don't work on a graphical FTP client, so this=20
command is less useful to me personally, but I can see the
> merit that it might have to someone that designs a graphical client.=20
That being said, I'm not a big fan of computing the thumbnail
> dynamically, nor am I fond of allowing the client to specify the=20
thumbnail format and size. I think that it would be better if the
> server could pre-cache thumbnails for any file type in a=20
server-determined size and image format, and then return the binary data
> and image format information to the client. For example, most=20
graphically-based operating systems have some method for displaying
> file icons to a user that is seated at a computer terminal, so an FTP=20
server implementation could simply return that same icon to=20
> a
> client in response to a THMB request.
>
> Please bear in mind, I haven't given a lot of thought as to what the=20
client/server interchange might look like if the server were
> more in control of the response to a THMB request, but it would probably =

be sufficient to simply return the image type as part of
> the response and let the client determine the image dimensions based on=20
the client's capabilities for reading the image data. (As=20
> a
> server guy I like to push any client-friendly processing on the client=20
whenever possible. ;-]) You could borrow an idea from the
> HASH discussion that we've been having and make the thumbnail image type =

configurable for the client by using an OPTS command,=20
> which
> might look like the following examples.
>
> In this first example, the server has a pre-configured thumbnail image=20
type of JPG, and may have pre-cached the thumbnails for
> files; any THMB request with no OPTS specified would use the server's=20
pre-configured thumbnail image type of JPG and image type is
> specified in the command channel response:
>
> C> THMB widget.png
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
> S> 226 Transfer complete.
>
> In these next examples a client is asking for different thumbnail image=20
types by using OPTS commands, and the thumbnail image=20
> types
> would still be specified in the command channel responses:
>
> C> OPTS THMB GIF
> S> 200 OPTS THMB GIF command successful.
>
> C> THMB widget.psp
> S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
> S> 226 Transfer complete.
>
> C> OPTS THMB PNG
> S> 200 OPTS THMB PNG command successful.
>
> C> THMB widget.doc
> S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
> S> 226 Transfer complete.
>
> In this next example a client is asking for an unsupported image type,=20
so the server would simply return the appropriate error
> reply:
>
> C> OPTS THMB FOO
> S> 501 Unsupported thumbnail format.
>
> In this next example a client is asking for the currently-configured=20
thumbnail image type, so the server would return the
> appropriate response:
>
> C> OPTS THMB
> S> 200 JPG
>
> You might take this one step further - the server might choose to only=20
support its pre-configured thumbnail image type, thereby
> allowing pre-caching of all thumbnails in one specific image format. In=20
this example a client is asking for PNG thumbnails, which
> SHOULD be a supported image type, but the server only supports a=20
pre-configured thumbnail image type for JPG files and returns the
> appropriate error reply (504?) and the server's pre-configured thumbnail =

image type is specified in the subsequent command channel
> response to a THMB request:
>
> C> OPTS THMB PNG
> S> 504 Specifying thumbnail formats is unsupported.
>
> C> THMB widget.xls
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
> S> 226 Transfer complete.
>
> As I said earlier, I hadn't given much thought as to what the=20
client/server THMB interchange might look like if you put the server
> in control instead of the client, but as a server guy I'd rather see=20
THMB look a little more like the examples that I gave. ;-]
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
>
>
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

wfms=20


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext



--=_alternative 0053A245802577E4_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"sans-serif">Two comments about the CSID before l=
ogin
question:</font>
<br>
<br><font size=3D2 face=3D"sans-serif">1) RFCs define protocols not impleme=
ntations,
so the discussion should be about what =5Fcan=5F happen and how a client/se=
rver
should respond.</font>
<br><font size=3D2 face=3D"sans-serif">2) I'd like to be 100% certain what
payload CSID can carry before banning it totally prior to authentication.</=
font>
<br>
<br>
<br><font size=3D2 face=3D"sans-serif">Point 1 (the protocol vs implementat=
ion
thing)</font>
<br><font size=3D2 face=3D"sans-serif">=3D=3D=3D=3D=3D=3D</font>
<br>
<br><font size=3D2 face=3D"sans-serif">We need to say what is and isn't all=
owed
in the protocol, comments about implementations are interesting but not
really the thrust of an RFC. &nbsp;In this case, we need to state when
a client may send CSID; what a server should do if the client sends it
at the wrong time - and at the right time; whether the client should expect
that a server might refuse to answer a CSID command because it is in a
particular state and that it might be sensible for it to try again when
in a different state in the protocol (e.g. logged in).</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Also, don't forget that users can log
out too - so simply stating after a USER command (or some such) isn't really
good enough.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Point 2</font>
<br><font size=3D2 face=3D"sans-serif">=3D=3D=3D=3D=3D=3D</font>
<br>
<br><font size=3D2 face=3D"sans-serif">HTTPS is broken because of something
similar. &nbsp;Multi-homed http servers cannot operate on HTTPS because
the server needs to present the cert to the client before the client tells
the server which certificate (i.e. host) it should be.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">I don't know if CSID may contain host
specific info &nbsp;(ext=5Fcfactname and local=5Ffact seem to be a bit of a
catch all that might get used for &quot;hostname&quot; or some such.) but
be very wary of this catching people out. &nbsp;At the very least, if CSID
should not be used for host identification, then ban such values from being
in these fields.</font>
<br>
<br>
<br>
<br><font size=3D2 face=3D"sans-serif">Perhaps CSID could be permitted to p=
ass
different information depending on the state of the user's session. &nbsp;(=
which
brings us back to the protocol vs implementation issue - should CSID always
pass the same information regardless of session state or is the peer allowed
to use session context to decide what to include - thus meaning that two
calls to CSID might be allowed to pass different values. In fact - is a
client allowed to send multiple CSID commands and what should a server
do if the information passed in the second command does not match that
from the first (and does REIN need to be involved?)?)</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Cheers,</font>
<br><font size=3D2 face=3D"sans-serif">Paul</font>
<br>
<br><font size=3D2 face=3D"sans-serif">-- <br>
<br>
Paul Ford-Hutchinson CISSP - Tivoli Security Consultant<br>
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU<br>
IBM Certified Deployment Professional - Tivoli Compliance Insight Manager
V8.5<br>
<br>
Tel +44 (0)7500 078379 &nbsp;(internal: 37269105)</font>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">From:</font>
<td><font size=3D1 face=3D"sans-serif">&quot;Mark P. Peterson&quot; &lt;mpp=
@rhinosoft.com&gt;</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">To:</font>
<td><font size=3D1 face=3D"sans-serif">&quot;William F. Maton&quot; &lt;wma=
ton@ottix.net&gt;</font>
<tr>
<td valign=3Dtop><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Cc:</fo=
nt>
<td><font size=3D1 face=3D"sans-serif">ftpext@ietf.org</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Date:</font>
<td><font size=3D1 face=3D"sans-serif">23/11/2010 14:45</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Subject:</font>
<td><font size=3D1 face=3D"sans-serif">Re: [ftpext] draft-peterson-streamli=
ned-ftp-command-extensions</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Sent by:</font>
<td><font size=3D1 face=3D"sans-serif">ftpext-bounces@ietf.org</font></tabl=
e>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=3D2>Hi William,<br>
<br>
Thank you for taking the time to respond. &nbsp;I cannot think<br>
of any real reason why CSID shouldn't only be allowed after login.<br>
I will change the document to reflect this.<br>
<br>
Mark P. Peterson - President<br>
</font></tt><a href=3Dhttp://www.rhinosoft.com/><tt><font size=3D2>http://w=
ww.RhinoSoft.com</font></tt></a><tt><font size=3D2><br>
Voice: +1(262) 560-9627<br>
FAX: +1(262) 560-9628<br>
<br>
<br>
--------------------------------------------------<br>
From: &quot;William F. Maton&quot; &lt;wmaton@ottix.net&gt;<br>
Sent: Tuesday, November 23, 2010 7:55 AM<br>
To: &quot;Mark P. Peterson&quot; &lt;mpp@rhinosoft.com&gt;<br>
Cc: &quot;Damin&quot; &lt;damin@emuxperts.net&gt;; &lt;ftpext@ietf.org&gt;<=
br>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions<br>
<br>
On Tue, 23 Nov 2010, Mark P. Peterson wrote:<br>
<br>
&gt; Hi All,<br>
&gt;<br>
&gt; Is there anyone else that agrees with Damin about CSID? &nbsp;He says
it SHOULD be available only after login.<br>
<br>
Hi Mark,<br>
 &nbsp;I'm certainly and old enough salt at systems administration to<br>
think that identification before authentication or authorization is not
a<br>
good thing. &nbsp;It makes it easier for the scanners to pick-off what
servers<br>
are running. &nbsp;I'd like to force them into making the extra effort,
since<br>
it might as well cost them more work and I can monitor the activity<br>
better.<br>
<br>
 &nbsp;I think standardizing CSID (from the old non-standard CLNT) is a<br>
good thing though. &nbsp;It should be left up to the implementor to support
it.<br>
<br>
 &nbsp;I've also read he rest of that I-D and have more thoughts on it,<br>
but that's for another email.<br>
<br>
<br>
&gt; Mark P. Peterson - President<br>
&gt; </font></tt><a href=3Dhttp://www.rhinosoft.com/><tt><font size=3D2>htt=
p://www.RhinoSoft.com</font></tt></a><tt><font size=3D2><br>
&gt; Voice: +1(262) 560-9627<br>
&gt; FAX: +1(262) 560-9628<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: Damin<br>
&gt; Sent: Monday, November 22, 2010 10:17 PM<br>
&gt; To: ftpext@ietf.org<br>
&gt; Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extension=
s<br>
&gt;<br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt;<br>
&gt; On 22 November 2010 19:32, Mark P. Peterson &lt;mpp@rhinosoft.com&gt;
wrote:<br>
&gt;<br>
&gt; Hi Robert,<br>
&gt;<br>
&gt; Thank you for taking the time to review the commands. &nbsp;If you
don't mind I would<br>
&gt; like to respond to your comments:<br>
&gt;<br>
&gt; CSID:<br>
&gt;<br>
&gt;&gt; For security reasons I would probably want the CSID exchange to
occur AFTER the client has logged in, but I might be <br>
&gt;&gt; overreacting.<br>
&gt;<br>
&gt;<br>
&gt; There is a lot of discussion on the Internet about servers providing
&quot;too&quot; much information, especially prior to login. &nbsp;But
<br>
&gt; having<br>
&gt; worked on both sides of the FTP process, it's usually very easy for
the client to identify what brand or flavor the server is.<br>
&gt; There are details which usually identify the server such as the comple=
teness
of the FEAT response, the welcome message, responses <br>
&gt; to<br>
&gt; certain messages, etc. &nbsp;So, I think it's okay to be available
prior to login. &nbsp;I could change the document to read that it should
<br>
&gt; be<br>
&gt; up to the server's implementation whether or not it's available.<br>
&gt;<br>
&gt; I prefer to edge on the side of caution. I don=B4t see any good reason
that this SHOULD be available before login. Commands <br>
&gt; available<br>
&gt; prior to login should be as limited as possible.<br>
&gt;<br>
&gt;<br>
&gt; RMDA:<br>
&gt;<br>
&gt;&gt; In a server implementation I would probably make this command
configurable, so administrators would have an option to disable the<br>
&gt;&gt; feature. &nbsp;In which case I would probably hide the command
from a FEAT response so it would not be discoverable and have the <br>
&gt;&gt; server<br>
&gt;&gt; return a 500 or 502 reply when RMDA is sent by the client and
disabled at the server.<br>
&gt;<br>
&gt;<br>
&gt; I don't think my document specifies that it isn't configurable. &nbsp;=
My
implementation in Serv-U is configurable as is almost all <br>
&gt; other<br>
&gt; FTP commands. &nbsp;I think this can be left up to the server implemen=
tation.
&nbsp;Your possible implementation is exactly how Serv-U<br>
&gt; implements it. &nbsp;If the feature is disabled, it doesn't appear
in the FEAT response, nor is it available through the HELP command.<br>
&gt;<br>
&gt;<br>
&gt; AVBL:<br>
&gt;&gt; ...<br>
&gt;<br>
&gt; Your comments address the reason for its existence. &nbsp;The client-s=
ide
implementation in SmartFTP uses the command in this manner.<br>
&gt;<br>
&gt; DSIZ:<br>
&gt;&gt; This could certainly be useful, although I would probably want
a user to be logged in...<br>
&gt;<br>
&gt; Any information about paths or files requires login in FTP. &nbsp;I
am sure this is the case here as well. &nbsp;If a server wouldn't want
<br>
&gt; the<br>
&gt; &quot;anonymous&quot; user to have access to this command it could
be configured to disallow this command at the server's implementation or<br>
&gt; configuration. &nbsp;This should be left up to the implementation
of the server or administrator of the server.<br>
&gt;<br>
&gt;&gt; I'd probably make it configurable so as not to tie up too many
server resources for large directory structures;...<br>
&gt;<br>
&gt; Agreed, the time-consuming nature of the implementation is discussed
but configuration by an administrator or <br>
&gt; server-implementation<br>
&gt; is not. &nbsp; Do you think such verbiage is required?<br>
&gt;<br>
&gt;<br>
&gt; THMB:<br>
&gt;<br>
&gt;&gt; I'm not a big fan of computing the thumbnail dynamically, nor
am I fond of allowing the client to specify the thumbnail format <br>
&gt;&gt; and<br>
&gt;&gt; size.<br>
&gt;<br>
&gt;<br>
&gt; That's the point of the command, though. &nbsp;It's to reduce the
amount of data that is required to travel over the wire. &nbsp;The idea
is<br>
&gt; to shorten delivery time to the client, letting the client decide
what is best for the client, not the server. &nbsp;Some clients may<br>
&gt; want very small images, say for a Windows Explorer style listing,
others may want larger images (640x480 for example) to show a<br>
&gt; slide show. &nbsp;I think the client needs to make that determination.
&nbsp;If the server decides to cache these generated images it can.<br>
&gt;<br>
&gt;<br>
&gt;&gt; I think that it would be better if the server could pre-cache
thumbnails for any file type in a server-determined size and image<br>
&gt;&gt; format, and then return the binary data and image format informati=
on
to the client.<br>
&gt;<br>
&gt;<br>
&gt; This could waste server-side resources, the client might not even
make a request for thumbnail images.<br>
&gt;<br>
&gt;<br>
&gt;&gt; For example, most graphically-based operating systems have some
method for displaying file icons to a user that is seated at a<br>
&gt;&gt; computer terminal, so an FTP server implementation could simply
return that same icon to a client in response to a THMB request.<br>
&gt;<br>
&gt;<br>
&gt; Right, but this isn't really the purpose of this command. &nbsp;The
purpose is to take an original image file and reduce it to a<br>
&gt; specified size, not to return the OS's icon representation for that
particular file type (i.e., not SHGetFileInfo() in Windows).<br>
&gt;<br>
&gt; My proposed implementation is fairly straightforward. &nbsp;If support=
ed
the FEAT command replies with THMB and the supported file <br>
&gt; types.<br>
&gt; When the client wants a thumbnail it asks for it with a single command.
&nbsp;Here is a sample result from FTP Voyager and Serv-U:<br>
&gt;<br>
&gt; PORT 192,168,0,30,199,53<br>
&gt; 200 PORT command successful.<br>
&gt; THMB PNG 98 88 Thomas.JPG<br>
&gt; 150 Opening thumbnail image transfer BINARY mode data connection (19738
Bytes) for Thomas.JPG.<br>
&gt; 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%)
transferred. 19.29 actual KB/sec, &nbsp;19.28 effective KB/sec.<br>
&gt;<br>
&gt; The client opens a data channel just like any other file transfer,
then requests the file using THMB, followed by the output type,<br>
&gt; width, height, and the file name. &nbsp;The server responds just like
a file transfer but also includes the resulting size in<br>
&gt; parentheses.<br>
&gt;<br>
&gt; While designing this command the idea was to first make it simple
for both sides, second to make it operate as any other download,<br>
&gt; and third to make it as flexible as possible, allowing the client
to decide how the resulting data is to be used and what is <br>
&gt; needed.<br>
&gt; Of course the server could be configured in any way needed. &nbsp;For
example if the server wanted to limit the size of the thumbnails,<br>
&gt; the server could do that. &nbsp;Our implementation limits the number
of simultaneous threads allowed to create the thumbnails at any<br>
&gt; given time. &nbsp;I think these details need to be left to the server
implementation.<br>
&gt;<br>
&gt; As for using an OPT command to configure an upcoming THMB command
for its image type and the thumbnail size, that seems to<br>
&gt; complicate the command. &nbsp;It's very easy to add these parameters
into a single command, eliminating the required handshaking <br>
&gt; between<br>
&gt; the client and server. &nbsp;An added benefit is that neither the
client nor the server are required to maintain these &quot;options&quot;<br>
&gt; throughout a session, rather all of the information required is sent
in a single command.<br>
&gt;<br>
&gt; If you're interested in seeing it in action, download Serv-U and FTP
Voyager or SmartFTP. &nbsp;Login to the server, switch FTP Voyager<br>
&gt; to &quot;Thumbnails&quot; view. &nbsp;With SmartFTP simply select
an image file and a thumbnail image, of dynamic size, will appear in the
<br>
&gt; preview<br>
&gt; pane.<br>
&gt;<br>
&gt;<br>
&gt; Thank you again for taking the time to provide your feedback. &nbsp;I
look forward to your comments to the above.<br>
&gt;<br>
&gt; Mark P. Peterson - President<br>
&gt; </font></tt><a href=3Dhttp://www.rhinosoft.com/><tt><font size=3D2>htt=
p://www.RhinoSoft.com</font></tt></a><tt><font size=3D2><br>
&gt; Voice: +1(262) 560-9627<br>
&gt; FAX: +1(262) 560-9628<br>
&gt;<br>
&gt;<br>
&gt; --------------------------------------------------<br>
&gt; From: &quot;Robert McMurray&quot; &lt;robmcm@microsoft.com&gt;<br>
&gt; Sent: Monday, November 22, 2010 5:01 PM<br>
&gt; To: &lt;ftpext@ietf.org&gt;; &quot;'Anthony Bryan'&quot; &lt;anthonybr=
yan@gmail.com&gt;;
&lt;mark.peterson@rhinosoft.com&gt;<br>
&gt; Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions<br>
&gt;<br>
&gt;<br>
&gt; [Note: Renaming the thread from 'Submitting new drafts'.]<br>
&gt;<br>
&gt;&gt; Anthony Bryan wrote:<br>
&gt;&gt;<br>
&gt;&gt; I don't mean to single you out, but<br>
&gt;&gt; you showed interest in an CSID/AGNT<br>
&gt;&gt; command. Do you have any opinion on<br>
&gt;&gt; the other 4 commands in the draft?<br>
&gt;<br>
&gt; Thanks, Anthony.<br>
&gt;<br>
&gt; No worries - I meant to send a better response in the wake of my withd=
rawn
AGNT draft and Mark's current Streamlined FTP Command<br>
&gt; Extensions draft, but I had been remiss at taking the time to collect
my thoughts in a more meaningful way. But since you asked,<br>
&gt; this seems like as good at time as any. ;-]<br>
&gt;<br>
&gt; CSID - As evidenced by my short-lived AGNT proposal, I think it's
very useful to have some sort of client/server discovery <br>
&gt; command.<br>
&gt; FEAT does a good job of advertising the list of commands that are
supported by a server, but Mark's proposed CSID command sequence<br>
&gt; provides a much better way for servers and client to identify their
features to each other in detail. For security reasons I would<br>
&gt; probably want the CSID exchange to occur AFTER the client has logged
in, but I might be overreacting.<br>
&gt;<br>
&gt; RMDA - This could be a very useful command, and it would parallel
the functionality that I'm sure we all typically use in a native<br>
&gt; operating system environment. In a server implementation I would proba=
bly
make this command configurable, so administrators would<br>
&gt; have an option to disable the feature. In which case I would probably
hide the command from a FEAT response so it would not be<br>
&gt; discoverable and have the server return a 500 or 502 reply when RMDA
is sent by the client and disabled at the server.<br>
&gt;<br>
&gt; (Note: I mention my thoughts about server implementation details just
to open up the discussion as to whether any implementation<br>
&gt; details should be called out in the draft, or if we should leave that
up to the implementers to decide.)<br>
&gt;<br>
&gt; AVBL - This command could be very useful in a client/server world;
our FTP server implementation currently returns the available<br>
&gt; size after a successful login sequence, and the available size is
based on server disk quotas and such. That being said, not every<br>
&gt; FTP client will bubble that information up to the user interface.
Having an AVBL command would make it possible for a client to<br>
&gt; determine whether enough storage space is available at the server
BEFORE sending a file, which would be great when you're about to<br>
&gt; send a 10GB file and you only have 9.99GB of storage space left. ;-]<b=
r>
&gt;<br>
&gt; DSIZ - This could certainly be useful, although I would probably want
a user to be logged in (not anonymous) before I supported <br>
&gt; this<br>
&gt; command in order to reduce the risk of denial-of-service. I'd probably
make it configurable so as not to tie up too many server<br>
&gt; resources for large directory structures; and once again, if the featu=
re
were disabled I would probably hide the command from a <br>
&gt; FEAT<br>
&gt; response so it would not be discoverable and return a 500 or 502 reply
when DSIZ is sent by the client and disabled at the server.<br>
&gt;<br>
&gt; THMB - I have to admit, I don't work on a graphical FTP client, so
this command is less useful to me personally, but I can see the<br>
&gt; merit that it might have to someone that designs a graphical client.
That being said, I'm not a big fan of computing the thumbnail<br>
&gt; dynamically, nor am I fond of allowing the client to specify the thumb=
nail
format and size. I think that it would be better if the<br>
&gt; server could pre-cache thumbnails for any file type in a server-determ=
ined
size and image format, and then return the binary data<br>
&gt; and image format information to the client. For example, most graphica=
lly-based
operating systems have some method for displaying<br>
&gt; file icons to a user that is seated at a computer terminal, so an
FTP server implementation could simply return that same icon to <br>
&gt; a<br>
&gt; client in response to a THMB request.<br>
&gt;<br>
&gt; Please bear in mind, I haven't given a lot of thought as to what the
client/server interchange might look like if the server were<br>
&gt; more in control of the response to a THMB request, but it would probab=
ly
be sufficient to simply return the image type as part of<br>
&gt; the response and let the client determine the image dimensions based
on the client's capabilities for reading the image data. (As <br>
&gt; a<br>
&gt; server guy I like to push any client-friendly processing on the client
whenever possible. ;-]) You could borrow an idea from the<br>
&gt; HASH discussion that we've been having and make the thumbnail image
type configurable for the client by using an OPTS command, <br>
&gt; which<br>
&gt; might look like the following examples.<br>
&gt;<br>
&gt; In this first example, the server has a pre-configured thumbnail image
type of JPG, and may have pre-cached the thumbnails for<br>
&gt; files; any THMB request with no OPTS specified would use the server's
pre-configured thumbnail image type of JPG and image type is<br>
&gt; specified in the command channel response:<br>
&gt;<br>
&gt; C&gt; THMB widget.png<br>
&gt; S&gt; 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png<=
br>
&gt; S&gt; 226 Transfer complete.<br>
&gt;<br>
&gt; In these next examples a client is asking for different thumbnail
image types by using OPTS commands, and the thumbnail image <br>
&gt; types<br>
&gt; would still be specified in the command channel responses:<br>
&gt;<br>
&gt; C&gt; OPTS THMB GIF<br>
&gt; S&gt; 200 OPTS THMB GIF command successful.<br>
&gt;<br>
&gt; C&gt; THMB widget.psp<br>
&gt; S&gt; 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp<=
br>
&gt; S&gt; 226 Transfer complete.<br>
&gt;<br>
&gt; C&gt; OPTS THMB PNG<br>
&gt; S&gt; 200 OPTS THMB PNG command successful.<br>
&gt;<br>
&gt; C&gt; THMB widget.doc<br>
&gt; S&gt; 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc<=
br>
&gt; S&gt; 226 Transfer complete.<br>
&gt;<br>
&gt; In this next example a client is asking for an unsupported image type,
so the server would simply return the appropriate error<br>
&gt; reply:<br>
&gt;<br>
&gt; C&gt; OPTS THMB FOO<br>
&gt; S&gt; 501 Unsupported thumbnail format.<br>
&gt;<br>
&gt; In this next example a client is asking for the currently-configured
thumbnail image type, so the server would return the<br>
&gt; appropriate response:<br>
&gt;<br>
&gt; C&gt; OPTS THMB<br>
&gt; S&gt; 200 JPG<br>
&gt;<br>
&gt; You might take this one step further - the server might choose to
only support its pre-configured thumbnail image type, thereby<br>
&gt; allowing pre-caching of all thumbnails in one specific image format.
In this example a client is asking for PNG thumbnails, which<br>
&gt; SHOULD be a supported image type, but the server only supports a pre-c=
onfigured
thumbnail image type for JPG files and returns the<br>
&gt; appropriate error reply (504?) and the server's pre-configured thumbna=
il
image type is specified in the subsequent command channel<br>
&gt; response to a THMB request:<br>
&gt;<br>
&gt; C&gt; OPTS THMB PNG<br>
&gt; S&gt; 504 Specifying thumbnail formats is unsupported.<br>
&gt;<br>
&gt; C&gt; THMB widget.xls<br>
&gt; S&gt; 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls<=
br>
&gt; S&gt; 226 Transfer complete.<br>
&gt;<br>
&gt; As I said earlier, I hadn't given much thought as to what the client/s=
erver
THMB interchange might look like if you put the server<br>
&gt; in control instead of the client, but as a server guy I'd rather see
THMB look a little more like the examples that I gave. ;-]<br>
&gt;<br>
&gt; Thanks again!<br>
&gt;<br>
&gt; Robert McMurray<br>
&gt; robmcm@microsoft.com<br>
&gt;<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ftpext mailing list<br>
&gt; ftpext@ietf.org<br>
&gt; </font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt=
><font size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</font></tt></a=
><tt><font size=3D2><br>
&gt;<br>
&gt;<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ftpext mailing list<br>
&gt; ftpext@ietf.org<br>
&gt; </font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt=
><font size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</font></tt></a=
><tt><font size=3D2><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ftpext mailing list<br>
&gt; ftpext@ietf.org<br>
&gt; </font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt=
><font size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</font></tt></a=
><tt><font size=3D2><br>
&gt;<br>
&gt;<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ftpext mailing list<br>
&gt; ftpext@ietf.org<br>
&gt; </font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt=
><font size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</font></tt></a=
><tt><font size=3D2><br>
&gt;<br>
<br>
wfms <br>
<br>
<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
ftpext mailing list<br>
ftpext@ietf.org<br>
</font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt><fon=
t size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</font></tt></a><tt>=
<font size=3D2><br>
</font></tt>
<br>
<br>
--=_alternative 0053A245802577E4_=--

From wwwrun@core3.amsl.com  Tue Nov 23 10:48:35 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ftpext@ietf.org
Delivered-To: ftpext@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id AFC433A69A1; Tue, 23 Nov 2010 10:48:35 -0800 (PST)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20101123184835.AFC433A69A1@core3.amsl.com>
Date: Tue, 23 Nov 2010 10:48:35 -0800 (PST)
Cc: ftpext@ietf.org
Subject: [ftpext] WG Action: FTP Extensions, 2nd edition (ftpext2)
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: Tue, 23 Nov 2010 18:48:35 -0000

A new IETF working group has been formed in the Applications Area.  For
additional information, please contact the Area Directors or the WG
Chairs.

FTP Extensions, 2nd edition (ftpext2)
---------------------------------------------------
Current Status: Active Working Group

Chair(s): 
 Anthony Bryan <anthonybryan@gmail.com>
 Tony Hansen <tony@att.com>

Applications Area Directors:
 Alexey Melnikov <alexey.melnikov@isode.com>
 Peter Saint-Andre <stpeter@stpeter.im>

Applications Area Advisor:
 Alexey Melnikov <alexey.melnikov@isode.com>

Mailing Lists:
 General Discussion: ftpext@ietf.org
 To subscribe: https://www.ietf.org/mailman/listinfo/ftpext
 Archive: http://www.ietf.org/mail-archive/web/ftpext/

Description of Working Group:

The Standard File Transfer Protocol specification in RFC 959
has been updated several times with command extensions of one
sort or another, including those based on the extension
mechanism of RFC 2389 (a complete list appears in RFC 5797 and
the corresponding IANA registry at
http://www.iana.org/assignments/ftp-commands-extensions).

The following are active FTP related drafts:

  draft-bryan-ftp-hash
  draft-hethmon-mcmurray-ftp-hosts
  FTP extensions to support IPv4/IPv6 translation scenario
  draft-klensin-ftp-typeu-00 - FTP Extension for Internationalized Text

The Working Group will:
* Review and finalize drafts listed above.
* Review and confirm or reject errata of current FTP RFCs.
* Investigate the differences between FTP in theory
 (current RFCs) and practice, and recommend future work to align them.
 Any future work would require rechartering of the WG.

The Working Group's specification deliverables are:
* A document that specifies the HOST command (Proposed Standard).
* A document that specifies the HASH command (Proposed Standard).
* A document that specifies FTP extensions to support IPv4/IPv6
translation scenario.
* A document that specifies FTP extensions for Internationalized Text.

The Working Group must not introduce a new version of FTP, e.g.
an incompatible FTP 2.0.

Goals and Milestones:

Nov 2010  Submit 'File Transfer Protocol HOST Command for Virtual
         Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts 
         will be used as a starting point)
Nov 2010  Submit 'File Transfer Protocol HASH Command for
         Cryptographic Hashes' as working group item (draft-bryan-ftp-
         hash will be used as a starting point)
Nov 2010  Submit 'FTP extensions to support IPv4/IPv6 translation'
         as working group item (draft-liu-ftp64-extension will be used 
         as a starting point)
Dec 2010  Working group Last Call of HOST document
Jan 2011  Submit 'File Transfer Protocol HOST Command for Virtual
         Hosts' to the IESG for consideration as a Proposed Standard
Jan 2011  Working group Last Call of HASH document
Feb 2011  Submit 'File Transfer Protocol HASH Command for
         Cryptographic Hashes' to the IESG for consideration as a 
         Proposed Standard
Mar 2011  Working group Last Call of 'FTP extensions to support
         IPv4/IPv6 translation' document
Apr 2011  Submit 'FTP Extension for Internationalized Text'
         as working group item
May 2011  Submit 'FTP extensions to support IPv4/IPv6 translation'
         to the IESG for consideration as Proposed Standard
Jul 2011  Working group Last Call of 'FTP Extension for 
         Internationalized Text'
Aug 2011  Submit 'FTP Extension for Internationalized Text'
         to the IESG for consideration as Proposed Standard
Sep 2011  Close or recharter

From prvs=19431281bb=mpp@rhinosoft.com  Tue Nov 23 11:51:27 2010
Return-Path: <prvs=19431281bb=mpp@rhinosoft.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 9A06028C0E8 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 11:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6]
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 HNUu9FYw7we0 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 11:51:24 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id B69483A6987 for <ftpext@ietf.org>; Tue, 23 Nov 2010 11:51:23 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009935668.msg for <ftpext@ietf.org>; Tue, 23 Nov 2010 13:52:20 -0600
X-Spam-Processed: rhinosoft.com, Tue, 23 Nov 2010 13:52:20 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=19431281bb=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <1145F0D0D8974C2A8DB587DD6F4E72C8@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: <ftpext@ietf.org>, "Paul Ford-Hutchinson" <paulfordh@uk.ibm.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net><AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com>	<914CA95DAC22422C825C665E4E76F860@rhinooffice.net><Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net> <6C3AA348BF6146F2885B2094B8E8E29C@rhinooffice.net> <OF8C6635BE.33D2510D-ON802577E4.0051C5FE-802577E4.0053A63D@uk.ibm.com>
In-Reply-To: <OF8C6635BE.33D2510D-ON802577E4.0051C5FE-802577E4.0053A63D@uk.ibm.com>
Date: Tue, 23 Nov 2010 13:52:17 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009B_01CB8B15.A410F560"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 19:51:27 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_009B_01CB8B15.A410F560
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Paul,

Thank you for taking the time to respond.

Point 1
=3D=3D=3D=3D=3D=3D=20
I agree with your points.  I will clarify the document.

Point 2=20
=3D=3D=3D=3D=3D=3D=20
CSID doesn't contain any host specific information, the intent is only =
to exchange information about the software between server and client.  =
As for HOST this is being proposed in a different draft for FTP.  I =
believe the information passed between the client and server should only =
apply to the actual software and platform and is independent from the =
login information.  In other words it should always return the same =
information.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628 =20



From: Paul Ford-Hutchinson=20
Sent: Tuesday, November 23, 2010 9:16 AM
To: Mark P. Peterson ; ftpext@ietf.org=20
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions



Two comments about the CSID before login question:=20

1) RFCs define protocols not implementations, so the discussion should =
be about what _can_ happen and how a client/server should respond.=20
2) I'd like to be 100% certain what payload CSID can carry before =
banning it totally prior to authentication.=20


Point 1 (the protocol vs implementation thing)=20
=3D=3D=3D=3D=3D=3D=20

We need to say what is and isn't allowed in the protocol, comments about =
implementations are interesting but not really the thrust of an RFC.  In =
this case, we need to state when a client may send CSID; what a server =
should do if the client sends it at the wrong time - and at the right =
time; whether the client should expect that a server might refuse to =
answer a CSID command because it is in a particular state and that it =
might be sensible for it to try again when in a different state in the =
protocol (e.g. logged in).=20

Also, don't forget that users can log out too - so simply stating after =
a USER command (or some such) isn't really good enough.=20

Point 2=20
=3D=3D=3D=3D=3D=3D=20

HTTPS is broken because of something similar.  Multi-homed http servers =
cannot operate on HTTPS because the server needs to present the cert to =
the client before the client tells the server which certificate (i.e. =
host) it should be.=20

I don't know if CSID may contain host specific info  (ext_cfactname and =
local_fact seem to be a bit of a catch all that might get used for =
"hostname" or some such.) but be very wary of this catching people out.  =
At the very least, if CSID should not be used for host identification, =
then ban such values from being in these fields.=20



Perhaps CSID could be permitted to pass different information depending =
on the state of the user's session.  (which brings us back to the =
protocol vs implementation issue - should CSID always pass the same =
information regardless of session state or is the peer allowed to use =
session context to decide what to include - thus meaning that two calls =
to CSID might be allowed to pass different values. In fact - is a client =
allowed to send multiple CSID commands and what should a server do if =
the information passed in the second command does not match that from =
the first (and does REIN need to be involved?)?)=20

Cheers,=20
Paul=20

--=20

Paul Ford-Hutchinson CISSP - Tivoli Security Consultant
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU
IBM Certified Deployment Professional - Tivoli Compliance Insight =
Manager V8.5

Tel +44 (0)7500 078379  (internal: 37269105)=20


      From:  "Mark P. Peterson" <mpp@rhinosoft.com> =20
      To:  "William F. Maton" <wmaton@ottix.net> =20
      Cc:  ftpext@ietf.org =20
      Date:  23/11/2010 14:45 =20
      Subject:  Re: [ftpext] =
draft-peterson-streamlined-ftp-command-extensions =20
      Sent by:  ftpext-bounces@ietf.org=20


-------------------------------------------------------------------------=
-------



Hi William,

Thank you for taking the time to respond.  I cannot think
of any real reason why CSID shouldn't only be allowed after login.
I will change the document to reflect this.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "William F. Maton" <wmaton@ottix.net>
Sent: Tuesday, November 23, 2010 7:55 AM
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: "Damin" <damin@emuxperts.net>; <ftpext@ietf.org>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions

On Tue, 23 Nov 2010, Mark P. Peterson wrote:

> Hi All,
>
> Is there anyone else that agrees with Damin about CSID?  He says it =
SHOULD be available only after login.

Hi Mark,
 I'm certainly and old enough salt at systems administration to
think that identification before authentication or authorization is not =
a
good thing.  It makes it easier for the scanners to pick-off what =
servers
are running.  I'd like to force them into making the extra effort, since
it might as well cost them more work and I can monitor the activity
better.

 I think standardizing CSID (from the old non-standard CLNT) is a
good thing though.  It should be left up to the implementor to support =
it.

 I've also read he rest of that I-D and have more thoughts on it,
but that's for another email.


> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
>
> From: Damin
> Sent: Monday, November 22, 2010 10:17 PM
> To: ftpext@ietf.org
> Subject: Re: [ftpext] =
draft-peterson-streamlined-ftp-command-extensions
>
>
> Hi,
>
>
> On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:
>
> Hi Robert,
>
> Thank you for taking the time to review the commands.  If you don't =
mind I would
> like to respond to your comments:
>
> CSID:
>
>> For security reasons I would probably want the CSID exchange to occur =
AFTER the client has logged in, but I might be=20
>> overreacting.
>
>
> There is a lot of discussion on the Internet about servers providing =
"too" much information, especially prior to login.  But=20
> having
> worked on both sides of the FTP process, it's usually very easy for =
the client to identify what brand or flavor the server is.
> There are details which usually identify the server such as the =
completeness of the FEAT response, the welcome message, responses=20
> to
> certain messages, etc.  So, I think it's okay to be available prior to =
login.  I could change the document to read that it should=20
> be
> up to the server's implementation whether or not it's available.
>
> I prefer to edge on the side of caution. I don=B4t see any good reason =
that this SHOULD be available before login. Commands=20
> available
> prior to login should be as limited as possible.
>
>
> RMDA:
>
>> In a server implementation I would probably make this command =
configurable, so administrators would have an option to disable the
>> feature.  In which case I would probably hide the command from a FEAT =
response so it would not be discoverable and have the=20
>> server
>> return a 500 or 502 reply when RMDA is sent by the client and =
disabled at the server.
>
>
> I don't think my document specifies that it isn't configurable.  My =
implementation in Serv-U is configurable as is almost all=20
> other
> FTP commands.  I think this can be left up to the server =
implementation.  Your possible implementation is exactly how Serv-U
> implements it.  If the feature is disabled, it doesn't appear in the =
FEAT response, nor is it available through the HELP command.
>
>
> AVBL:
>> ...
>
> Your comments address the reason for its existence.  The client-side =
implementation in SmartFTP uses the command in this manner.
>
> DSIZ:
>> This could certainly be useful, although I would probably want a user =
to be logged in...
>
> Any information about paths or files requires login in FTP.  I am sure =
this is the case here as well.  If a server wouldn't want=20
> the
> "anonymous" user to have access to this command it could be configured =
to disallow this command at the server's implementation or
> configuration.  This should be left up to the implementation of the =
server or administrator of the server.
>
>> I'd probably make it configurable so as not to tie up too many server =
resources for large directory structures;...
>
> Agreed, the time-consuming nature of the implementation is discussed =
but configuration by an administrator or=20
> server-implementation
> is not.   Do you think such verbiage is required?
>
>
> THMB:
>
>> I'm not a big fan of computing the thumbnail dynamically, nor am I =
fond of allowing the client to specify the thumbnail format=20
>> and
>> size.
>
>
> That's the point of the command, though.  It's to reduce the amount of =
data that is required to travel over the wire.  The idea is
> to shorten delivery time to the client, letting the client decide what =
is best for the client, not the server.  Some clients may
> want very small images, say for a Windows Explorer style listing, =
others may want larger images (640x480 for example) to show a
> slide show.  I think the client needs to make that determination.  If =
the server decides to cache these generated images it can.
>
>
>> I think that it would be better if the server could pre-cache =
thumbnails for any file type in a server-determined size and image
>> format, and then return the binary data and image format information =
to the client.
>
>
> This could waste server-side resources, the client might not even make =
a request for thumbnail images.
>
>
>> For example, most graphically-based operating systems have some =
method for displaying file icons to a user that is seated at a
>> computer terminal, so an FTP server implementation could simply =
return that same icon to a client in response to a THMB request.
>
>
> Right, but this isn't really the purpose of this command.  The purpose =
is to take an original image file and reduce it to a
> specified size, not to return the OS's icon representation for that =
particular file type (i.e., not SHGetFileInfo() in Windows).
>
> My proposed implementation is fairly straightforward.  If supported =
the FEAT command replies with THMB and the supported file=20
> types.
> When the client wants a thumbnail it asks for it with a single =
command.  Here is a sample result from FTP Voyager and Serv-U:
>
> PORT 192,168,0,30,199,53
> 200 PORT command successful.
> THMB PNG 98 88 Thomas.JPG
> 150 Opening thumbnail image transfer BINARY mode data connection =
(19738 Bytes) for Thomas.JPG.
> 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%) =
transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.
>
> The client opens a data channel just like any other file transfer, =
then requests the file using THMB, followed by the output type,
> width, height, and the file name.  The server responds just like a =
file transfer but also includes the resulting size in
> parentheses.
>
> While designing this command the idea was to first make it simple for =
both sides, second to make it operate as any other download,
> and third to make it as flexible as possible, allowing the client to =
decide how the resulting data is to be used and what is=20
> needed.
> Of course the server could be configured in any way needed.  For =
example if the server wanted to limit the size of the thumbnails,
> the server could do that.  Our implementation limits the number of =
simultaneous threads allowed to create the thumbnails at any
> given time.  I think these details need to be left to the server =
implementation.
>
> As for using an OPT command to configure an upcoming THMB command for =
its image type and the thumbnail size, that seems to
> complicate the command.  It's very easy to add these parameters into a =
single command, eliminating the required handshaking=20
> between
> the client and server.  An added benefit is that neither the client =
nor the server are required to maintain these "options"
> throughout a session, rather all of the information required is sent =
in a single command.
>
> If you're interested in seeing it in action, download Serv-U and FTP =
Voyager or SmartFTP.  Login to the server, switch FTP Voyager
> to "Thumbnails" view.  With SmartFTP simply select an image file and a =
thumbnail image, of dynamic size, will appear in the=20
> preview
> pane.
>
>
> Thank you again for taking the time to provide your feedback.  I look =
forward to your comments to the above.
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Robert McMurray" <robmcm@microsoft.com>
> Sent: Monday, November 22, 2010 5:01 PM
> To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>; =
<mark.peterson@rhinosoft.com>
> Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> [Note: Renaming the thread from 'Submitting new drafts'.]
>
>> Anthony Bryan wrote:
>>
>> I don't mean to single you out, but
>> you showed interest in an CSID/AGNT
>> command. Do you have any opinion on
>> the other 4 commands in the draft?
>
> Thanks, Anthony.
>
> No worries - I meant to send a better response in the wake of my =
withdrawn AGNT draft and Mark's current Streamlined FTP Command
> Extensions draft, but I had been remiss at taking the time to collect =
my thoughts in a more meaningful way. But since you asked,
> this seems like as good at time as any. ;-]
>
> CSID - As evidenced by my short-lived AGNT proposal, I think it's very =
useful to have some sort of client/server discovery=20
> command.
> FEAT does a good job of advertising the list of commands that are =
supported by a server, but Mark's proposed CSID command sequence
> provides a much better way for servers and client to identify their =
features to each other in detail. For security reasons I would
> probably want the CSID exchange to occur AFTER the client has logged =
in, but I might be overreacting.
>
> RMDA - This could be a very useful command, and it would parallel the =
functionality that I'm sure we all typically use in a native
> operating system environment. In a server implementation I would =
probably make this command configurable, so administrators would
> have an option to disable the feature. In which case I would probably =
hide the command from a FEAT response so it would not be
> discoverable and have the server return a 500 or 502 reply when RMDA =
is sent by the client and disabled at the server.
>
> (Note: I mention my thoughts about server implementation details just =
to open up the discussion as to whether any implementation
> details should be called out in the draft, or if we should leave that =
up to the implementers to decide.)
>
> AVBL - This command could be very useful in a client/server world; our =
FTP server implementation currently returns the available
> size after a successful login sequence, and the available size is =
based on server disk quotas and such. That being said, not every
> FTP client will bubble that information up to the user interface. =
Having an AVBL command would make it possible for a client to
> determine whether enough storage space is available at the server =
BEFORE sending a file, which would be great when you're about to
> send a 10GB file and you only have 9.99GB of storage space left. ;-]
>
> DSIZ - This could certainly be useful, although I would probably want =
a user to be logged in (not anonymous) before I supported=20
> this
> command in order to reduce the risk of denial-of-service. I'd probably =
make it configurable so as not to tie up too many server
> resources for large directory structures; and once again, if the =
feature were disabled I would probably hide the command from a=20
> FEAT
> response so it would not be discoverable and return a 500 or 502 reply =
when DSIZ is sent by the client and disabled at the server.
>
> THMB - I have to admit, I don't work on a graphical FTP client, so =
this command is less useful to me personally, but I can see the
> merit that it might have to someone that designs a graphical client. =
That being said, I'm not a big fan of computing the thumbnail
> dynamically, nor am I fond of allowing the client to specify the =
thumbnail format and size. I think that it would be better if the
> server could pre-cache thumbnails for any file type in a =
server-determined size and image format, and then return the binary data
> and image format information to the client. For example, most =
graphically-based operating systems have some method for displaying
> file icons to a user that is seated at a computer terminal, so an FTP =
server implementation could simply return that same icon to=20
> a
> client in response to a THMB request.
>
> Please bear in mind, I haven't given a lot of thought as to what the =
client/server interchange might look like if the server were
> more in control of the response to a THMB request, but it would =
probably be sufficient to simply return the image type as part of
> the response and let the client determine the image dimensions based =
on the client's capabilities for reading the image data. (As=20
> a
> server guy I like to push any client-friendly processing on the client =
whenever possible. ;-]) You could borrow an idea from the
> HASH discussion that we've been having and make the thumbnail image =
type configurable for the client by using an OPTS command,=20
> which
> might look like the following examples.
>
> In this first example, the server has a pre-configured thumbnail image =
type of JPG, and may have pre-cached the thumbnails for
> files; any THMB request with no OPTS specified would use the server's =
pre-configured thumbnail image type of JPG and image type is
> specified in the command channel response:
>
> C> THMB widget.png
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
> S> 226 Transfer complete.
>
> In these next examples a client is asking for different thumbnail =
image types by using OPTS commands, and the thumbnail image=20
> types
> would still be specified in the command channel responses:
>
> C> OPTS THMB GIF
> S> 200 OPTS THMB GIF command successful.
>
> C> THMB widget.psp
> S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
> S> 226 Transfer complete.
>
> C> OPTS THMB PNG
> S> 200 OPTS THMB PNG command successful.
>
> C> THMB widget.doc
> S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
> S> 226 Transfer complete.
>
> In this next example a client is asking for an unsupported image type, =
so the server would simply return the appropriate error
> reply:
>
> C> OPTS THMB FOO
> S> 501 Unsupported thumbnail format.
>
> In this next example a client is asking for the currently-configured =
thumbnail image type, so the server would return the
> appropriate response:
>
> C> OPTS THMB
> S> 200 JPG
>
> You might take this one step further - the server might choose to only =
support its pre-configured thumbnail image type, thereby
> allowing pre-caching of all thumbnails in one specific image format. =
In this example a client is asking for PNG thumbnails, which
> SHOULD be a supported image type, but the server only supports a =
pre-configured thumbnail image type for JPG files and returns the
> appropriate error reply (504?) and the server's pre-configured =
thumbnail image type is specified in the subsequent command channel
> response to a THMB request:
>
> C> OPTS THMB PNG
> S> 504 Specifying thumbnail formats is unsupported.
>
> C> THMB widget.xls
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
> S> 226 Transfer complete.
>
> As I said earlier, I hadn't given much thought as to what the =
client/server THMB interchange might look like if you put the server
> in control instead of the client, but as a server guy I'd rather see =
THMB look a little more like the examples that I gave. ;-]
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
>
>
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

wfms=20


_______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext



------=_NextPart_000_009B_01CB8B15.A410F560
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16671"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT size=3D2>Hi Paul,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thank you for taking the time to =
respond.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Point 1</FONT></DIV>
<DIV><FONT size=3D2><FONT size=3D2 =
face=3Dsans-serif>=3D=3D=3D=3D=3D=3D</FONT><FONT size=3D3>=20
</FONT><BR>I agree with your points.&nbsp; I will clarify the=20
document.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Point 2<FONT size=3D3> <BR></FONT><FONT size=3D2=20
face=3Dsans-serif>=3D=3D=3D=3D=3D=3D</FONT><FONT size=3D3> =
</FONT><BR>CSID doesn't contain any=20
host specific information, the intent is only to exchange information =
about the=20
software between server and client.&nbsp; As for HOST this is being =
proposed in=20
a different draft for FTP.&nbsp; I believe the information passed =
between the=20
client and server should only apply to the actual software and platform =
and is=20
independent from the login information.&nbsp; In other words it should =
always=20
return the same information.</FONT></DIV>
<DIV><FONT size=3D2><BR>Mark P. Peterson - President<BR><A=20
title=3D"http://www.RhinoSoft.com&#10;CTRL + Click to follow link"=20
href=3D"http://www.RhinoSoft.com">http://www.RhinoSoft.com</A><BR>Voice: =
+1(262)=20
560-9627<BR>FAX: +1(262) 560-9628&nbsp; <BR></FONT></DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><FONT face=3DArial></FONT><FONT face=3DArial></FONT><FONT=20
face=3DArial></FONT><FONT face=3DArial></FONT><FONT =
face=3DArial></FONT><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A=20
title=3D"mailto:paulfordh@uk.ibm.com&#10;CTRL + Click to follow link"=20
href=3D"mailto:paulfordh@uk.ibm.com">Paul Ford-Hutchinson</A> </DIV>
<DIV><B>Sent:</B> Tuesday, November 23, 2010 9:16 AM</DIV>
<DIV><B>To:</B> <A title=3Dmpp@rhinosoft.com =
href=3D"mailto:mpp@rhinosoft.com">Mark=20
P. Peterson</A> ; <A=20
title=3D"mailto:ftpext@ietf.org&#10;CTRL + Click to follow link"=20
href=3D"mailto:ftpext@ietf.org">ftpext@ietf.org</A> </DIV>
<DIV><B>Subject:</B> Re: [ftpext]=20
draft-peterson-streamlined-ftp-command-extensions</DIV></DIV></DIV>
<DIV><FONT size=3D2></FONT><FONT size=3D2></FONT><FONT =
size=3D2></FONT><FONT=20
size=3D2></FONT><FONT size=3D2></FONT><FONT =
size=3D2></FONT><BR></DIV><BR><FONT size=3D2=20
face=3Dsans-serif>Two comments about the CSID before login =
question:</FONT>=20
<BR><BR><FONT size=3D2 face=3Dsans-serif>1) RFCs define protocols not=20
implementations, so the discussion should be about what _can_ happen and =
how a=20
client/server should respond.</FONT> <BR><FONT size=3D2 =
face=3Dsans-serif>2) I'd=20
like to be 100% certain what payload CSID can carry before banning it =
totally=20
prior to authentication.</FONT> <BR><BR><BR><FONT size=3D2 =
face=3Dsans-serif>Point 1=20
(the protocol vs implementation thing)</FONT> <BR><FONT size=3D2=20
face=3Dsans-serif>=3D=3D=3D=3D=3D=3D</FONT> <BR><BR><FONT size=3D2 =
face=3Dsans-serif>We need to=20
say what is and isn't allowed in the protocol, comments about =
implementations=20
are interesting but not really the thrust of an RFC. &nbsp;In this case, =
we need=20
to state when a client may send CSID; what a server should do if the =
client=20
sends it at the wrong time - and at the right time; whether the client =
should=20
expect that a server might refuse to answer a CSID command because it is =
in a=20
particular state and that it might be sensible for it to try again when =
in a=20
different state in the protocol (e.g. logged in).</FONT> <BR><BR><FONT =
size=3D2=20
face=3Dsans-serif>Also, don't forget that users can log out too - so =
simply=20
stating after a USER command (or some such) isn't really good =
enough.</FONT>=20
<BR><BR><FONT size=3D2 face=3Dsans-serif>Point 2</FONT> <BR><FONT =
size=3D2=20
face=3Dsans-serif>=3D=3D=3D=3D=3D=3D</FONT> <BR><BR><FONT size=3D2 =
face=3Dsans-serif>HTTPS is=20
broken because of something similar. &nbsp;Multi-homed http servers =
cannot=20
operate on HTTPS because the server needs to present the cert to the =
client=20
before the client tells the server which certificate (i.e. host) it =
should=20
be.</FONT> <BR><BR><FONT size=3D2 face=3Dsans-serif>I don't know if CSID =
may contain=20
host specific info &nbsp;(ext_cfactname and local_fact seem to be a bit =
of a=20
catch all that might get used for "hostname" or some such.) but be very =
wary of=20
this catching people out. &nbsp;At the very least, if CSID should not be =
used=20
for host identification, then ban such values from being in these =
fields.</FONT>=20
<BR><BR><BR><BR><FONT size=3D2 face=3Dsans-serif>Perhaps CSID could be =
permitted to=20
pass different information depending on the state of the user's session. =

&nbsp;(which brings us back to the protocol vs implementation issue - =
should=20
CSID always pass the same information regardless of session state or is =
the peer=20
allowed to use session context to decide what to include - thus meaning =
that two=20
calls to CSID might be allowed to pass different values. In fact - is a =
client=20
allowed to send multiple CSID commands and what should a server do if =
the=20
information passed in the second command does not match that from the =
first (and=20
does REIN need to be involved?)?)</FONT> <BR><BR><FONT size=3D2=20
face=3Dsans-serif>Cheers,</FONT> <BR><FONT size=3D2 =
face=3Dsans-serif>Paul</FONT>=20
<BR><BR><FONT size=3D2 face=3Dsans-serif>-- <BR><BR>Paul Ford-Hutchinson =
CISSP -=20
Tivoli Security Consultant<BR>IBM UK Ltd. - NHBR - 1PH - North Harbour - =

Portsmouth - PO6 3AU<BR>IBM Certified Deployment Professional - Tivoli=20
Compliance Insight Manager V8.5<BR><BR>Tel +44 (0)7500 078379 =
&nbsp;(internal:=20
37269105)</FONT> <BR><BR><BR>
<TABLE width=3D"100%">
  <TBODY>
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>From:</FONT>=20
    <TD><FONT size=3D1 face=3Dsans-serif>"Mark P. Peterson"=20
      &lt;mpp@rhinosoft.com&gt;</FONT>=20
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>To:</FONT>=20
    <TD><FONT size=3D1 face=3Dsans-serif>"William F. Maton"=20
      &lt;wmaton@ottix.net&gt;</FONT>=20
  <TR>
    <TD vAlign=3Dtop><FONT color=3D#5f5f5f size=3D1 =
face=3Dsans-serif>Cc:</FONT>=20
    <TD><FONT size=3D1 face=3Dsans-serif>ftpext@ietf.org</FONT>=20
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>Date:</FONT>=20
    <TD><FONT size=3D1 face=3Dsans-serif>23/11/2010 14:45</FONT>=20
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>Subject:</FONT> =

    <TD><FONT size=3D1 face=3Dsans-serif>Re: [ftpext]=20
      draft-peterson-streamlined-ftp-command-extensions</FONT>=20
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>Sent by:</FONT> =

    <TD><FONT size=3D1=20
  =
face=3Dsans-serif>ftpext-bounces@ietf.org</FONT></TD></TR></TBODY></TABLE=
><BR>
<HR noShade>
<BR><BR><BR><TT><FONT size=3D2>Hi William,<BR><BR>Thank you for taking =
the time to=20
respond. &nbsp;I cannot think<BR>of any real reason why CSID shouldn't =
only be=20
allowed after login.<BR>I will change the document to reflect =
this.<BR><BR>Mark=20
P. Peterson - President<BR></FONT></TT><A=20
href=3D"http://www.rhinosoft.com/"><TT><FONT=20
size=3D2>http://www.RhinoSoft.com</FONT></TT></A><TT><FONT =
size=3D2><BR>Voice:=20
+1(262) 560-9627<BR>FAX: +1(262)=20
560-9628<BR><BR><BR>--------------------------------------------------<BR=
>From:=20
"William F. Maton" &lt;wmaton@ottix.net&gt;<BR>Sent: Tuesday, November =
23, 2010=20
7:55 AM<BR>To: "Mark P. Peterson" &lt;mpp@rhinosoft.com&gt;<BR>Cc: =
"Damin"=20
&lt;damin@emuxperts.net&gt;; &lt;ftpext@ietf.org&gt;<BR>Subject: Re: =
[ftpext]=20
draft-peterson-streamlined-ftp-command-extensions<BR><BR>On Tue, 23 Nov =
2010,=20
Mark P. Peterson wrote:<BR><BR>&gt; Hi All,<BR>&gt;<BR>&gt; Is there =
anyone else=20
that agrees with Damin about CSID? &nbsp;He says it SHOULD be available =
only=20
after login.<BR><BR>Hi Mark,<BR>&nbsp;I'm certainly and old enough salt =
at=20
systems administration to<BR>think that identification before =
authentication or=20
authorization is not a<BR>good thing. &nbsp;It makes it easier for the =
scanners=20
to pick-off what servers<BR>are running. &nbsp;I'd like to force them =
into=20
making the extra effort, since<BR>it might as well cost them more work =
and I can=20
monitor the activity<BR>better.<BR><BR>&nbsp;I think standardizing CSID =
(from=20
the old non-standard CLNT) is a<BR>good thing though. &nbsp;It should be =
left up=20
to the implementor to support it.<BR><BR>&nbsp;I've also read he rest of =
that=20
I-D and have more thoughts on it,<BR>but that's for another=20
email.<BR><BR><BR>&gt; Mark P. Peterson - President<BR>&gt; =
</FONT></TT><A=20
href=3D"http://www.rhinosoft.com/"><TT><FONT=20
size=3D2>http://www.RhinoSoft.com</FONT></TT></A><TT><FONT =
size=3D2><BR>&gt; Voice:=20
+1(262) 560-9627<BR>&gt; FAX: +1(262) =
560-9628<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
From: Damin<BR>&gt; Sent: Monday, November 22, 2010 10:17 PM<BR>&gt; To: =

ftpext@ietf.org<BR>&gt; Subject: Re: [ftpext]=20
draft-peterson-streamlined-ftp-command-extensions<BR>&gt;<BR>&gt;<BR>&gt;=
=20
Hi,<BR>&gt;<BR>&gt;<BR>&gt; On 22 November 2010 19:32, Mark P. Peterson=20
&lt;mpp@rhinosoft.com&gt; wrote:<BR>&gt;<BR>&gt; Hi =
Robert,<BR>&gt;<BR>&gt;=20
Thank you for taking the time to review the commands. &nbsp;If you don't =
mind I=20
would<BR>&gt; like to respond to your comments:<BR>&gt;<BR>&gt;=20
CSID:<BR>&gt;<BR>&gt;&gt; For security reasons I would probably want the =
CSID=20
exchange to occur AFTER the client has logged in, but I might be =
<BR>&gt;&gt;=20
overreacting.<BR>&gt;<BR>&gt;<BR>&gt; There is a lot of discussion on =
the=20
Internet about servers providing "too" much information, especially =
prior to=20
login. &nbsp;But <BR>&gt; having<BR>&gt; worked on both sides of the FTP =

process, it's usually very easy for the client to identify what brand or =
flavor=20
the server is.<BR>&gt; There are details which usually identify the =
server such=20
as the completeness of the FEAT response, the welcome message, responses =

<BR>&gt; to<BR>&gt; certain messages, etc. &nbsp;So, I think it's okay =
to be=20
available prior to login. &nbsp;I could change the document to read that =
it=20
should <BR>&gt; be<BR>&gt; up to the server's implementation whether or =
not it's=20
available.<BR>&gt;<BR>&gt; I prefer to edge on the side of caution. I =
don=B4t see=20
any good reason that this SHOULD be available before login. Commands =
<BR>&gt;=20
available<BR>&gt; prior to login should be as limited as=20
possible.<BR>&gt;<BR>&gt;<BR>&gt; RMDA:<BR>&gt;<BR>&gt;&gt; In a server=20
implementation I would probably make this command configurable, so=20
administrators would have an option to disable the<BR>&gt;&gt; feature. =
&nbsp;In=20
which case I would probably hide the command from a FEAT response so it =
would=20
not be discoverable and have the <BR>&gt;&gt; server<BR>&gt;&gt; return =
a 500 or=20
502 reply when RMDA is sent by the client and disabled at the=20
server.<BR>&gt;<BR>&gt;<BR>&gt; I don't think my document specifies that =
it=20
isn't configurable. &nbsp;My implementation in Serv-U is configurable as =
is=20
almost all <BR>&gt; other<BR>&gt; FTP commands. &nbsp;I think this can =
be left=20
up to the server implementation. &nbsp;Your possible implementation is =
exactly=20
how Serv-U<BR>&gt; implements it. &nbsp;If the feature is disabled, it =
doesn't=20
appear in the FEAT response, nor is it available through the HELP=20
command.<BR>&gt;<BR>&gt;<BR>&gt; AVBL:<BR>&gt;&gt; ...<BR>&gt;<BR>&gt; =
Your=20
comments address the reason for its existence. &nbsp;The client-side=20
implementation in SmartFTP uses the command in this =
manner.<BR>&gt;<BR>&gt;=20
DSIZ:<BR>&gt;&gt; This could certainly be useful, although I would =
probably want=20
a user to be logged in...<BR>&gt;<BR>&gt; Any information about paths or =
files=20
requires login in FTP. &nbsp;I am sure this is the case here as well. =
&nbsp;If a=20
server wouldn't want <BR>&gt; the<BR>&gt; "anonymous" user to have =
access to=20
this command it could be configured to disallow this command at the =
server's=20
implementation or<BR>&gt; configuration. &nbsp;This should be left up to =
the=20
implementation of the server or administrator of the =
server.<BR>&gt;<BR>&gt;&gt;=20
I'd probably make it configurable so as not to tie up too many server =
resources=20
for large directory structures;...<BR>&gt;<BR>&gt; Agreed, the =
time-consuming=20
nature of the implementation is discussed but configuration by an =
administrator=20
or <BR>&gt; server-implementation<BR>&gt; is not. &nbsp; Do you think =
such=20
verbiage is required?<BR>&gt;<BR>&gt;<BR>&gt; THMB:<BR>&gt;<BR>&gt;&gt; =
I'm not=20
a big fan of computing the thumbnail dynamically, nor am I fond of =
allowing the=20
client to specify the thumbnail format <BR>&gt;&gt; and<BR>&gt;&gt;=20
size.<BR>&gt;<BR>&gt;<BR>&gt; That's the point of the command, though.=20
&nbsp;It's to reduce the amount of data that is required to travel over =
the=20
wire. &nbsp;The idea is<BR>&gt; to shorten delivery time to the client, =
letting=20
the client decide what is best for the client, not the server. =
&nbsp;Some=20
clients may<BR>&gt; want very small images, say for a Windows Explorer =
style=20
listing, others may want larger images (640x480 for example) to show =
a<BR>&gt;=20
slide show. &nbsp;I think the client needs to make that determination. =
&nbsp;If=20
the server decides to cache these generated images it=20
can.<BR>&gt;<BR>&gt;<BR>&gt;&gt; I think that it would be better if the =
server=20
could pre-cache thumbnails for any file type in a server-determined size =
and=20
image<BR>&gt;&gt; format, and then return the binary data and image =
format=20
information to the client.<BR>&gt;<BR>&gt;<BR>&gt; This could waste =
server-side=20
resources, the client might not even make a request for thumbnail=20
images.<BR>&gt;<BR>&gt;<BR>&gt;&gt; For example, most graphically-based=20
operating systems have some method for displaying file icons to a user =
that is=20
seated at a<BR>&gt;&gt; computer terminal, so an FTP server =
implementation could=20
simply return that same icon to a client in response to a THMB=20
request.<BR>&gt;<BR>&gt;<BR>&gt; Right, but this isn't really the =
purpose of=20
this command. &nbsp;The purpose is to take an original image file and =
reduce it=20
to a<BR>&gt; specified size, not to return the OS's icon representation =
for that=20
particular file type (i.e., not SHGetFileInfo() in =
Windows).<BR>&gt;<BR>&gt; My=20
proposed implementation is fairly straightforward. &nbsp;If supported =
the FEAT=20
command replies with THMB and the supported file <BR>&gt; types.<BR>&gt; =
When=20
the client wants a thumbnail it asks for it with a single command. =
&nbsp;Here is=20
a sample result from FTP Voyager and Serv-U:<BR>&gt;<BR>&gt; PORT=20
192,168,0,30,199,53<BR>&gt; 200 PORT command successful.<BR>&gt; THMB =
PNG 98 88=20
Thomas.JPG<BR>&gt; 150 Opening thumbnail image transfer BINARY mode data =

connection (19738 Bytes) for Thomas.JPG.<BR>&gt; 226 Transfer complete. =
19,738=20
bytes (19,756 compressed to 100.09%) transferred. 19.29 actual KB/sec,=20
&nbsp;19.28 effective KB/sec.<BR>&gt;<BR>&gt; The client opens a data =
channel=20
just like any other file transfer, then requests the file using THMB, =
followed=20
by the output type,<BR>&gt; width, height, and the file name. &nbsp;The =
server=20
responds just like a file transfer but also includes the resulting size=20
in<BR>&gt; parentheses.<BR>&gt;<BR>&gt; While designing this command the =
idea=20
was to first make it simple for both sides, second to make it operate as =
any=20
other download,<BR>&gt; and third to make it as flexible as possible, =
allowing=20
the client to decide how the resulting data is to be used and what is =
<BR>&gt;=20
needed.<BR>&gt; Of course the server could be configured in any way =
needed.=20
&nbsp;For example if the server wanted to limit the size of the=20
thumbnails,<BR>&gt; the server could do that. &nbsp;Our implementation =
limits=20
the number of simultaneous threads allowed to create the thumbnails at=20
any<BR>&gt; given time. &nbsp;I think these details need to be left to =
the=20
server implementation.<BR>&gt;<BR>&gt; As for using an OPT command to =
configure=20
an upcoming THMB command for its image type and the thumbnail size, that =
seems=20
to<BR>&gt; complicate the command. &nbsp;It's very easy to add these =
parameters=20
into a single command, eliminating the required handshaking <BR>&gt;=20
between<BR>&gt; the client and server. &nbsp;An added benefit is that =
neither=20
the client nor the server are required to maintain these =
"options"<BR>&gt;=20
throughout a session, rather all of the information required is sent in =
a single=20
command.<BR>&gt;<BR>&gt; If you're interested in seeing it in action, =
download=20
Serv-U and FTP Voyager or SmartFTP. &nbsp;Login to the server, switch =
FTP=20
Voyager<BR>&gt; to "Thumbnails" view. &nbsp;With SmartFTP simply select =
an image=20
file and a thumbnail image, of dynamic size, will appear in the <BR>&gt; =

preview<BR>&gt; pane.<BR>&gt;<BR>&gt;<BR>&gt; Thank you again for taking =
the=20
time to provide your feedback. &nbsp;I look forward to your comments to =
the=20
above.<BR>&gt;<BR>&gt; Mark P. Peterson - President<BR>&gt; =
</FONT></TT><A=20
href=3D"http://www.rhinosoft.com/"><TT><FONT=20
size=3D2>http://www.RhinoSoft.com</FONT></TT></A><TT><FONT =
size=3D2><BR>&gt; Voice:=20
+1(262) 560-9627<BR>&gt; FAX: +1(262) 560-9628<BR>&gt;<BR>&gt;<BR>&gt;=20
--------------------------------------------------<BR>&gt; From: "Robert =

McMurray" &lt;robmcm@microsoft.com&gt;<BR>&gt; Sent: Monday, November =
22, 2010=20
5:01 PM<BR>&gt; To: &lt;ftpext@ietf.org&gt;; "'Anthony Bryan'"=20
&lt;anthonybryan@gmail.com&gt;; =
&lt;mark.peterson@rhinosoft.com&gt;<BR>&gt;=20
Subject: [ftpext]=20
draft-peterson-streamlined-ftp-command-extensions<BR>&gt;<BR>&gt;<BR>&gt;=
 [Note:=20
Renaming the thread from 'Submitting new drafts'.]<BR>&gt;<BR>&gt;&gt; =
Anthony=20
Bryan wrote:<BR>&gt;&gt;<BR>&gt;&gt; I don't mean to single you out,=20
but<BR>&gt;&gt; you showed interest in an CSID/AGNT<BR>&gt;&gt; command. =
Do you=20
have any opinion on<BR>&gt;&gt; the other 4 commands in the=20
draft?<BR>&gt;<BR>&gt; Thanks, Anthony.<BR>&gt;<BR>&gt; No worries - I =
meant to=20
send a better response in the wake of my withdrawn AGNT draft and Mark's =
current=20
Streamlined FTP Command<BR>&gt; Extensions draft, but I had been remiss =
at=20
taking the time to collect my thoughts in a more meaningful way. But =
since you=20
asked,<BR>&gt; this seems like as good at time as any. =
;-]<BR>&gt;<BR>&gt; CSID=20
- As evidenced by my short-lived AGNT proposal, I think it's very useful =
to have=20
some sort of client/server discovery <BR>&gt; command.<BR>&gt; FEAT does =
a good=20
job of advertising the list of commands that are supported by a server, =
but=20
Mark's proposed CSID command sequence<BR>&gt; provides a much better way =
for=20
servers and client to identify their features to each other in detail. =
For=20
security reasons I would<BR>&gt; probably want the CSID exchange to =
occur AFTER=20
the client has logged in, but I might be overreacting.<BR>&gt;<BR>&gt; =
RMDA -=20
This could be a very useful command, and it would parallel the =
functionality=20
that I'm sure we all typically use in a native<BR>&gt; operating system=20
environment. In a server implementation I would probably make this =
command=20
configurable, so administrators would<BR>&gt; have an option to disable =
the=20
feature. In which case I would probably hide the command from a FEAT =
response so=20
it would not be<BR>&gt; discoverable and have the server return a 500 or =
502=20
reply when RMDA is sent by the client and disabled at the=20
server.<BR>&gt;<BR>&gt; (Note: I mention my thoughts about server =
implementation=20
details just to open up the discussion as to whether any =
implementation<BR>&gt;=20
details should be called out in the draft, or if we should leave that up =
to the=20
implementers to decide.)<BR>&gt;<BR>&gt; AVBL - This command could be =
very=20
useful in a client/server world; our FTP server implementation currently =
returns=20
the available<BR>&gt; size after a successful login sequence, and the =
available=20
size is based on server disk quotas and such. That being said, not =
every<BR>&gt;=20
FTP client will bubble that information up to the user interface. Having =
an AVBL=20
command would make it possible for a client to<BR>&gt; determine whether =
enough=20
storage space is available at the server BEFORE sending a file, which =
would be=20
great when you're about to<BR>&gt; send a 10GB file and you only have =
9.99GB of=20
storage space left. ;-]<BR>&gt;<BR>&gt; DSIZ - This could certainly be =
useful,=20
although I would probably want a user to be logged in (not anonymous) =
before I=20
supported <BR>&gt; this<BR>&gt; command in order to reduce the risk of=20
denial-of-service. I'd probably make it configurable so as not to tie up =
too=20
many server<BR>&gt; resources for large directory structures; and once =
again, if=20
the feature were disabled I would probably hide the command from a =
<BR>&gt;=20
FEAT<BR>&gt; response so it would not be discoverable and return a 500 =
or 502=20
reply when DSIZ is sent by the client and disabled at the=20
server.<BR>&gt;<BR>&gt; THMB - I have to admit, I don't work on a =
graphical FTP=20
client, so this command is less useful to me personally, but I can see=20
the<BR>&gt; merit that it might have to someone that designs a graphical =
client.=20
That being said, I'm not a big fan of computing the thumbnail<BR>&gt;=20
dynamically, nor am I fond of allowing the client to specify the =
thumbnail=20
format and size. I think that it would be better if the<BR>&gt; server =
could=20
pre-cache thumbnails for any file type in a server-determined size and =
image=20
format, and then return the binary data<BR>&gt; and image format =
information to=20
the client. For example, most graphically-based operating systems have =
some=20
method for displaying<BR>&gt; file icons to a user that is seated at a =
computer=20
terminal, so an FTP server implementation could simply return that same =
icon to=20
<BR>&gt; a<BR>&gt; client in response to a THMB request.<BR>&gt;<BR>&gt; =
Please=20
bear in mind, I haven't given a lot of thought as to what the =
client/server=20
interchange might look like if the server were<BR>&gt; more in control =
of the=20
response to a THMB request, but it would probably be sufficient to =
simply return=20
the image type as part of<BR>&gt; the response and let the client =
determine the=20
image dimensions based on the client's capabilities for reading the =
image data.=20
(As <BR>&gt; a<BR>&gt; server guy I like to push any client-friendly =
processing=20
on the client whenever possible. ;-]) You could borrow an idea from =
the<BR>&gt;=20
HASH discussion that we've been having and make the thumbnail image type =

configurable for the client by using an OPTS command, <BR>&gt; =
which<BR>&gt;=20
might look like the following examples.<BR>&gt;<BR>&gt; In this first =
example,=20
the server has a pre-configured thumbnail image type of JPG, and may =
have=20
pre-cached the thumbnails for<BR>&gt; files; any THMB request with no =
OPTS=20
specified would use the server's pre-configured thumbnail image type of =
JPG and=20
image type is<BR>&gt; specified in the command channel =
response:<BR>&gt;<BR>&gt;=20
C&gt; THMB widget.png<BR>&gt; S&gt; 150 JPG Starting thumbnail transfer =
(1234=20
Bytes) for widget.png<BR>&gt; S&gt; 226 Transfer =
complete.<BR>&gt;<BR>&gt; In=20
these next examples a client is asking for different thumbnail image =
types by=20
using OPTS commands, and the thumbnail image <BR>&gt; types<BR>&gt; =
would still=20
be specified in the command channel responses:<BR>&gt;<BR>&gt; C&gt; =
OPTS THMB=20
GIF<BR>&gt; S&gt; 200 OPTS THMB GIF command successful.<BR>&gt;<BR>&gt; =
C&gt;=20
THMB widget.psp<BR>&gt; S&gt; 150 GIF Starting thumbnail transfer (1234 =
Bytes)=20
for widget.psp<BR>&gt; S&gt; 226 Transfer complete.<BR>&gt;<BR>&gt; =
C&gt; OPTS=20
THMB PNG<BR>&gt; S&gt; 200 OPTS THMB PNG command =
successful.<BR>&gt;<BR>&gt;=20
C&gt; THMB widget.doc<BR>&gt; S&gt; 150 PNG Starting thumbnail transfer =
(1234=20
Bytes) for widget.doc<BR>&gt; S&gt; 226 Transfer =
complete.<BR>&gt;<BR>&gt; In=20
this next example a client is asking for an unsupported image type, so =
the=20
server would simply return the appropriate error<BR>&gt; =
reply:<BR>&gt;<BR>&gt;=20
C&gt; OPTS THMB FOO<BR>&gt; S&gt; 501 Unsupported thumbnail=20
format.<BR>&gt;<BR>&gt; In this next example a client is asking for the=20
currently-configured thumbnail image type, so the server would return=20
the<BR>&gt; appropriate response:<BR>&gt;<BR>&gt; C&gt; OPTS =
THMB<BR>&gt; S&gt;=20
200 JPG<BR>&gt;<BR>&gt; You might take this one step further - the =
server might=20
choose to only support its pre-configured thumbnail image type, =
thereby<BR>&gt;=20
allowing pre-caching of all thumbnails in one specific image format. In =
this=20
example a client is asking for PNG thumbnails, which<BR>&gt; SHOULD be a =

supported image type, but the server only supports a pre-configured =
thumbnail=20
image type for JPG files and returns the<BR>&gt; appropriate error reply =
(504?)=20
and the server's pre-configured thumbnail image type is specified in the =

subsequent command channel<BR>&gt; response to a THMB =
request:<BR>&gt;<BR>&gt;=20
C&gt; OPTS THMB PNG<BR>&gt; S&gt; 504 Specifying thumbnail formats is=20
unsupported.<BR>&gt;<BR>&gt; C&gt; THMB widget.xls<BR>&gt; S&gt; 150 JPG =

Starting thumbnail transfer (1234 Bytes) for widget.xls<BR>&gt; S&gt; =
226=20
Transfer complete.<BR>&gt;<BR>&gt; As I said earlier, I hadn't given =
much=20
thought as to what the client/server THMB interchange might look like if =
you put=20
the server<BR>&gt; in control instead of the client, but as a server guy =
I'd=20
rather see THMB look a little more like the examples that I gave.=20
;-]<BR>&gt;<BR>&gt; Thanks again!<BR>&gt;<BR>&gt; Robert =
McMurray<BR>&gt;=20
robmcm@microsoft.com<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; ftpext mailing=20
list<BR>&gt; ftpext@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</FONT></TT></A><TT>=
<FONT=20
size=3D2><BR>&gt;<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; ftpext mailing=20
list<BR>&gt; ftpext@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</FONT></TT></A><TT>=
<FONT=20
size=3D2><BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; ftpext mailing=20
list<BR>&gt; ftpext@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</FONT></TT></A><TT>=
<FONT=20
size=3D2><BR>&gt;<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; ftpext mailing=20
list<BR>&gt; ftpext@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</FONT></TT></A><TT>=
<FONT=20
size=3D2><BR>&gt;<BR><BR>wfms=20
<BR><BR><BR>_______________________________________________<BR>ftpext =
mailing=20
list<BR>ftpext@ietf.org<BR></FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/ftpext</FONT></TT></A><TT>=
<FONT=20
size=3D2><BR></FONT></TT><BR><BR></BODY></HTML>

------=_NextPart_000_009B_01CB8B15.A410F560--



From anthonybryan@gmail.com  Tue Nov 23 13:16:29 2010
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 0670728C0DB for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 13:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.817
X-Spam-Level: 
X-Spam-Status: No, score=-2.817 tagged_above=-999 required=5 tests=[AWL=-0.218, 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 ilGuBLQW9iiF for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 13:16:27 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 34C1128C15D for <ftpext@ietf.org>; Tue, 23 Nov 2010 13:16:27 -0800 (PST)
Received: by ewy8 with SMTP id 8so4693406ewy.31 for <ftpext@ietf.org>; Tue, 23 Nov 2010 13:17:24 -0800 (PST)
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:content-type :content-transfer-encoding; bh=YlS2FDpTO6bF3PcaD9k4UFOIHMjiCBXJ5b1R6tlMedg=; b=HPVP7OuAwhu4vJBexi72J1QHh6VZMJL5u96i5202uNiKBusbeiLQs5FfvrDXh6rHK9 SQvU8L/aAGs3Ap/oazaMh+FkrBu5Icjih0bgIZcUYloeeLCV741EQurALSgrvA5rJh0P mtGcUesYMu1yKyvCFZmA0mHD8K50iQ0Qkx2aM=
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 :content-type:content-transfer-encoding; b=sUlLWV2NBWPym3FZDiYOXjgZvXrfdVkwbumo1QiJBeThk8DbwdhpcDFUNuaBhVLHJs Pfezr80gP4eSCUdJsKUcUtP8oLSDe+HlNw4Nb8blbvDmzHsA2GW0N7XbayV9JB1JbynQ CtXLjdimRTtKHVC5J+RXqhd/u37BIv9WuHVzw=
MIME-Version: 1.0
Received: by 10.213.15.209 with SMTP id l17mr7576720eba.63.1290547044577; Tue, 23 Nov 2010 13:17:24 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Tue, 23 Nov 2010 13:17:24 -0800 (PST)
In-Reply-To: <20101123184835.AFC433A69A1@core3.amsl.com>
References: <20101123184835.AFC433A69A1@core3.amsl.com>
Date: Tue, 23 Nov 2010 16:17:24 -0500
Message-ID: <AANLkTinYUc1G-syqicN31Rc+yV6UvKurB-O1nQba2Y9=@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [ftpext] WG Action: FTP Extensions, 2nd edition (ftpext2)
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: Tue, 23 Nov 2010 21:16:29 -0000

so, wow, looks like things are rolling along! :)

as you can see, our WG got approved last Thursday.

I'm very happy to see comments on
draft-peterson-streamlined-ftp-command-extensions still coming in.
please chime in if you haven't already.

I'm new to this, so I wonder what the first order of business is?

here are some ideas:

1) we have 4 drafts on the charter, 3 of which are "active" (John
hasn't updated draft-klensin-ftp-typeu yet). once these are submitted
with the string '-ftpext2-' in the
draft name, they will show up at http://tools.ietf.org/wg/ftpext2/

I think our ID draft-bryan-ftp-hash becomes ietf-ftpext2-hash then? (&
the others follow in a similar fashion).

should this be done now? we should change the WG at the top of our
drafts I guess. how is this done in xml2rfc? is there anything else
that needs to be changed?

2) making sure everyone who would be interested in this WG knows about
it's existence.

now that it's official, I hope more people will hear about it.

Alun mentioned inviting members of the old WG. I think think we can
get a subscriber list, but the archives are at
http://www.ietf.org/mail-archive/text/ftpext/ if anyone could go
through & invite them...

is there anyone else that should be invited?

thanks for being here & helping us to improve FTP!

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


On Tue, Nov 23, 2010 at 1:48 PM, IESG Secretary <iesg-secretary@ietf.org> w=
rote:
> A new IETF working group has been formed in the Applications Area. =A0For
> additional information, please contact the Area Directors or the WG
> Chairs.
>
> FTP Extensions, 2nd edition (ftpext2)
> ---------------------------------------------------
> Current Status: Active Working Group
>
> Chair(s):
> =A0Anthony Bryan <anthonybryan@gmail.com>
> =A0Tony Hansen <tony@att.com>
>
> Applications Area Directors:
> =A0Alexey Melnikov <alexey.melnikov@isode.com>
> =A0Peter Saint-Andre <stpeter@stpeter.im>
>
> Applications Area Advisor:
> =A0Alexey Melnikov <alexey.melnikov@isode.com>
>
> Mailing Lists:
> =A0General Discussion: ftpext@ietf.org
> =A0To subscribe: https://www.ietf.org/mailman/listinfo/ftpext
> =A0Archive: http://www.ietf.org/mail-archive/web/ftpext/
>
> Description of Working Group:
>
> The Standard File Transfer Protocol specification in RFC 959
> has been updated several times with command extensions of one
> sort or another, including those based on the extension
> mechanism of RFC 2389 (a complete list appears in RFC 5797 and
> the corresponding IANA registry at
> http://www.iana.org/assignments/ftp-commands-extensions).
>
> The following are active FTP related drafts:
>
> =A0draft-bryan-ftp-hash
> =A0draft-hethmon-mcmurray-ftp-hosts
> =A0FTP extensions to support IPv4/IPv6 translation scenario
> =A0draft-klensin-ftp-typeu-00 - FTP Extension for Internationalized Text
>
> The Working Group will:
> * Review and finalize drafts listed above.
> * Review and confirm or reject errata of current FTP RFCs.
> * Investigate the differences between FTP in theory
> =A0(current RFCs) and practice, and recommend future work to align them.
> =A0Any future work would require rechartering of the WG.
>
> The Working Group's specification deliverables are:
> * A document that specifies the HOST command (Proposed Standard).
> * A document that specifies the HASH command (Proposed Standard).
> * A document that specifies FTP extensions to support IPv4/IPv6
> translation scenario.
> * A document that specifies FTP extensions for Internationalized Text.
>
> The Working Group must not introduce a new version of FTP, e.g.
> an incompatible FTP 2.0.
>
> Goals and Milestones:
>
> Nov 2010 =A0Submit 'File Transfer Protocol HOST Command for Virtual
> =A0 =A0 =A0 =A0 Hosts' as working group item (draft-hethmon-mcmurray-ftp-=
hosts
> =A0 =A0 =A0 =A0 will be used as a starting point)
> Nov 2010 =A0Submit 'File Transfer Protocol HASH Command for
> =A0 =A0 =A0 =A0 Cryptographic Hashes' as working group item (draft-bryan-=
ftp-
> =A0 =A0 =A0 =A0 hash will be used as a starting point)
> Nov 2010 =A0Submit 'FTP extensions to support IPv4/IPv6 translation'
> =A0 =A0 =A0 =A0 as working group item (draft-liu-ftp64-extension will be =
used
> =A0 =A0 =A0 =A0 as a starting point)
> Dec 2010 =A0Working group Last Call of HOST document
> Jan 2011 =A0Submit 'File Transfer Protocol HOST Command for Virtual
> =A0 =A0 =A0 =A0 Hosts' to the IESG for consideration as a Proposed Standa=
rd
> Jan 2011 =A0Working group Last Call of HASH document
> Feb 2011 =A0Submit 'File Transfer Protocol HASH Command for
> =A0 =A0 =A0 =A0 Cryptographic Hashes' to the IESG for consideration as a
> =A0 =A0 =A0 =A0 Proposed Standard
> Mar 2011 =A0Working group Last Call of 'FTP extensions to support
> =A0 =A0 =A0 =A0 IPv4/IPv6 translation' document
> Apr 2011 =A0Submit 'FTP Extension for Internationalized Text'
> =A0 =A0 =A0 =A0 as working group item
> May 2011 =A0Submit 'FTP extensions to support IPv4/IPv6 translation'
> =A0 =A0 =A0 =A0 to the IESG for consideration as Proposed Standard
> Jul 2011 =A0Working group Last Call of 'FTP Extension for
> =A0 =A0 =A0 =A0 Internationalized Text'
> Aug 2011 =A0Submit 'FTP Extension for Internationalized Text'
> =A0 =A0 =A0 =A0 to the IESG for consideration as Proposed Standard
> Sep 2011 =A0Close or recharter
>

From paulfordh@uk.ibm.com  Tue Nov 23 14:35:56 2010
Return-Path: <paulfordh@uk.ibm.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 DB5F028C11F for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 14:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_MED=-4]
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 oKxCAryfc-fR for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 14:35:53 -0800 (PST)
Received: from mtagate4.uk.ibm.com (mtagate4.uk.ibm.com [194.196.100.164]) by core3.amsl.com (Postfix) with ESMTP id 29C2B3A6997 for <ftpext@ietf.org>; Tue, 23 Nov 2010 14:35:52 -0800 (PST)
Received: from d06nrmr1307.portsmouth.uk.ibm.com (d06nrmr1307.portsmouth.uk.ibm.com [9.149.38.129]) by mtagate4.uk.ibm.com (8.13.1/8.13.1) with ESMTP id oANMannK026387 for <ftpext@ietf.org>; Tue, 23 Nov 2010 22:36:49 GMT
Received: from d06av07.portsmouth.uk.ibm.com (d06av07.portsmouth.uk.ibm.com [9.149.37.248]) by d06nrmr1307.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id oANMamg43608592 for <ftpext@ietf.org>; Tue, 23 Nov 2010 22:36:48 GMT
Received: from d06av07.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av07.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id oANMamhP015513 for <ftpext@ietf.org>; Tue, 23 Nov 2010 15:36:48 -0700
Received: from d06ml069.portsmouth.uk.ibm.com (d06ml069.portsmouth.uk.ibm.com [9.149.38.218]) by d06av07.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id oANMam0j015510; Tue, 23 Nov 2010 15:36:48 -0700
In-Reply-To: <1145F0D0D8974C2A8DB587DD6F4E72C8@rhinooffice.net>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net><AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com> <914CA95DAC22422C825C665E4E76F860@rhinooffice.net><Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net> <6C3AA348BF6146F2885B2094B8E8E29C@rhinooffice.net> <OF8C6635BE.33D2510D-ON802577E4.0051C5FE-802577E4.0053A63D@uk.ibm.com> <1145F0D0D8974C2A8DB587DD6F4E72C8@rhinooffice.net>
To: "Mark P. Peterson" <mpp@rhinosoft.com>
MIME-Version: 1.0
X-KeepSent: ECAD328D:14EBDD49-802577E4:007A3769; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1 SHF149 July 17, 2009
From: Paul Ford-Hutchinson <paulfordh@uk.ibm.com>
Message-ID: <OFECAD328D.14EBDD49-ON802577E4.007A3769-802577E4.007C3599@uk.ibm.com>
Date: Tue, 23 Nov 2010 22:40:02 +0000
X-MIMETrack: Serialize by Router on D06ML069/06/M/IBM(Release 8.0.2FP2|June 22, 2009) at 23/11/2010 22:40:03, Serialize complete at 23/11/2010 22:40:03
Content-Type: multipart/alternative; boundary="=_alternative 007AD0DC802577E4_="
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 22:35:57 -0000

This is a multipart message in MIME format.
--=_alternative 007AD0DC802577E4_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

I understand that HOST is designed to do the job, but extensible crannies=20
in protocols tend to get used for all sorts of things they aren't intended =

for.

In fact, it wouldn't surprise me if the review process ends up kicking the =

'extensible' bits of this command into the long grass.  (i.e. the argument =

that it's actually creating interoperability issues rather than preventing =

them - if there's a need for a value - it should be defined syntactically=20
and semantically - otherwise it doesn't belong in a protocol spec.)

I suggest that there should be some discussion about what kind of=20
information is valid in the CSID command/response and when a client/server =

might expect it to alter (or not).  And if it turns out it is tied to a=20
"session" - point out that a "session" can mean a number of things in FTP, =

so that will need to be specified too.

Cheers,
Paul
--=20

Paul Ford-Hutchinson CISSP - Tivoli Security Consultant
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU
IBM Certified Deployment Professional - Tivoli Compliance Insight Manager=20
V8.5

Tel +44 (0)7500 078379  (internal: 37269105)



From:
"Mark P. Peterson" <mpp@rhinosoft.com>
To:
<ftpext@ietf.org>, Paul Ford-Hutchinson/UK/IBM@IBMGB
Date:
23/11/2010 19:55
Subject:
Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions



Hi Paul,
=20
Thank you for taking the time to respond.
=20
Point 1
=3D=3D=3D=3D=3D=3D=20
I agree with your points.  I will clarify the document.
=20
Point 2=20
=3D=3D=3D=3D=3D=3D=20
CSID doesn't contain any host specific information, the intent is only to=20
exchange information about the software between server and client.  As for =

HOST this is being proposed in a different draft for FTP.  I believe the=20
information passed between the client and server should only apply to the=20
actual software and platform and is independent from the login=20
information.  In other words it should always return the same information.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628=20

From: Paul Ford-Hutchinson=20
Sent: Tuesday, November 23, 2010 9:16 AM
To: Mark P. Peterson ; ftpext@ietf.org=20
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions


Two comments about the CSID before login question:=20

1) RFCs define protocols not implementations, so the discussion should be=20
about what =5Fcan=5F happen and how a client/server should respond.=20
2) I'd like to be 100% certain what payload CSID can carry before banning=20
it totally prior to authentication.=20


Point 1 (the protocol vs implementation thing)=20
=3D=3D=3D=3D=3D=3D=20

We need to say what is and isn't allowed in the protocol, comments about=20
implementations are interesting but not really the thrust of an RFC.  In=20
this case, we need to state when a client may send CSID; what a server=20
should do if the client sends it at the wrong time - and at the right=20
time; whether the client should expect that a server might refuse to=20
answer a CSID command because it is in a particular state and that it=20
might be sensible for it to try again when in a different state in the=20
protocol (e.g. logged in).=20

Also, don't forget that users can log out too - so simply stating after a=20
USER command (or some such) isn't really good enough.=20

Point 2=20
=3D=3D=3D=3D=3D=3D=20

HTTPS is broken because of something similar.  Multi-homed http servers=20
cannot operate on HTTPS because the server needs to present the cert to=20
the client before the client tells the server which certificate (i.e.=20
host) it should be.=20

I don't know if CSID may contain host specific info  (ext=5Fcfactname and=20
local=5Ffact seem to be a bit of a catch all that might get used for=20
"hostname" or some such.) but be very wary of this catching people out. At =

the very least, if CSID should not be used for host identification, then=20
ban such values from being in these fields.=20



Perhaps CSID could be permitted to pass different information depending on =

the state of the user's session.  (which brings us back to the protocol vs =

implementation issue - should CSID always pass the same information=20
regardless of session state or is the peer allowed to use session context=20
to decide what to include - thus meaning that two calls to CSID might be=20
allowed to pass different values. In fact - is a client allowed to send=20
multiple CSID commands and what should a server do if the information=20
passed in the second command does not match that from the first (and does=20
REIN need to be involved?)?)=20

Cheers,=20
Paul=20

--=20

Paul Ford-Hutchinson CISSP - Tivoli Security Consultant
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU
IBM Certified Deployment Professional - Tivoli Compliance Insight Manager=20
V8.5

Tel +44 (0)7500 078379  (internal: 37269105)=20


From:=20
"Mark P. Peterson" <mpp@rhinosoft.com>=20
To:=20
"William F. Maton" <wmaton@ottix.net>=20
Cc:=20
ftpext@ietf.org=20
Date:=20
23/11/2010 14:45=20
Subject:=20
Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions=20
Sent by:=20
ftpext-bounces@ietf.org




Hi William,

Thank you for taking the time to respond.  I cannot think
of any real reason why CSID shouldn't only be allowed after login.
I will change the document to reflect this.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "William F. Maton" <wmaton@ottix.net>
Sent: Tuesday, November 23, 2010 7:55 AM
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: "Damin" <damin@emuxperts.net>; <ftpext@ietf.org>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions

On Tue, 23 Nov 2010, Mark P. Peterson wrote:

> Hi All,
>
> Is there anyone else that agrees with Damin about CSID?  He says it=20
SHOULD be available only after login.

Hi Mark,
 I'm certainly and old enough salt at systems administration to
think that identification before authentication or authorization is not a
good thing.  It makes it easier for the scanners to pick-off what servers
are running.  I'd like to force them into making the extra effort, since
it might as well cost them more work and I can monitor the activity
better.

 I think standardizing CSID (from the old non-standard CLNT) is a
good thing though.  It should be left up to the implementor to support it.

 I've also read he rest of that I-D and have more thoughts on it,
but that's for another email.


> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
>
> From: Damin
> Sent: Monday, November 22, 2010 10:17 PM
> To: ftpext@ietf.org
> Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> Hi,
>
>
> On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:
>
> Hi Robert,
>
> Thank you for taking the time to review the commands.  If you don't mind =

I would
> like to respond to your comments:
>
> CSID:
>
>> For security reasons I would probably want the CSID exchange to occur=20
AFTER the client has logged in, but I might be=20
>> overreacting.
>
>
> There is a lot of discussion on the Internet about servers providing=20
"too" much information, especially prior to login.  But=20
> having
> worked on both sides of the FTP process, it's usually very easy for the=20
client to identify what brand or flavor the server is.
> There are details which usually identify the server such as the=20
completeness of the FEAT response, the welcome message, responses=20
> to
> certain messages, etc.  So, I think it's okay to be available prior to=20
login.  I could change the document to read that it should=20
> be
> up to the server's implementation whether or not it's available.
>
> I prefer to edge on the side of caution. I don=B4t see any good reason=20
that this SHOULD be available before login. Commands=20
> available
> prior to login should be as limited as possible.
>
>
> RMDA:
>
>> In a server implementation I would probably make this command=20
configurable, so administrators would have an option to disable the
>> feature.  In which case I would probably hide the command from a FEAT=20
response so it would not be discoverable and have the=20
>> server
>> return a 500 or 502 reply when RMDA is sent by the client and disabled=20
at the server.
>
>
> I don't think my document specifies that it isn't configurable.  My=20
implementation in Serv-U is configurable as is almost all=20
> other
> FTP commands.  I think this can be left up to the server implementation. =

 Your possible implementation is exactly how Serv-U
> implements it.  If the feature is disabled, it doesn't appear in the=20
FEAT response, nor is it available through the HELP command.
>
>
> AVBL:
>> ...
>
> Your comments address the reason for its existence.  The client-side=20
implementation in SmartFTP uses the command in this manner.
>
> DSIZ:
>> This could certainly be useful, although I would probably want a user=20
to be logged in...
>
> Any information about paths or files requires login in FTP.  I am sure=20
this is the case here as well.  If a server wouldn't want=20
> the
> "anonymous" user to have access to this command it could be configured=20
to disallow this command at the server's implementation or
> configuration.  This should be left up to the implementation of the=20
server or administrator of the server.
>
>> I'd probably make it configurable so as not to tie up too many server=20
resources for large directory structures;...
>
> Agreed, the time-consuming nature of the implementation is discussed but =

configuration by an administrator or=20
> server-implementation
> is not.   Do you think such verbiage is required?
>
>
> THMB:
>
>> I'm not a big fan of computing the thumbnail dynamically, nor am I fond =

of allowing the client to specify the thumbnail format=20
>> and
>> size.
>
>
> That's the point of the command, though.  It's to reduce the amount of=20
data that is required to travel over the wire.  The idea is
> to shorten delivery time to the client, letting the client decide what=20
is best for the client, not the server.  Some clients may
> want very small images, say for a Windows Explorer style listing, others =

may want larger images (640x480 for example) to show a
> slide show.  I think the client needs to make that determination.  If=20
the server decides to cache these generated images it can.
>
>
>> I think that it would be better if the server could pre-cache=20
thumbnails for any file type in a server-determined size and image
>> format, and then return the binary data and image format information to =

the client.
>
>
> This could waste server-side resources, the client might not even make a =

request for thumbnail images.
>
>
>> For example, most graphically-based operating systems have some method=20
for displaying file icons to a user that is seated at a
>> computer terminal, so an FTP server implementation could simply return=20
that same icon to a client in response to a THMB request.
>
>
> Right, but this isn't really the purpose of this command.  The purpose=20
is to take an original image file and reduce it to a
> specified size, not to return the OS's icon representation for that=20
particular file type (i.e., not SHGetFileInfo() in Windows).
>
> My proposed implementation is fairly straightforward.  If supported the=20
FEAT command replies with THMB and the supported file=20
> types.
> When the client wants a thumbnail it asks for it with a single command.=20
Here is a sample result from FTP Voyager and Serv-U:
>
> PORT 192,168,0,30,199,53
> 200 PORT command successful.
> THMB PNG 98 88 Thomas.JPG
> 150 Opening thumbnail image transfer BINARY mode data connection (19738=20
Bytes) for Thomas.JPG.
> 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%)=20
transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.
>
> The client opens a data channel just like any other file transfer, then=20
requests the file using THMB, followed by the output type,
> width, height, and the file name.  The server responds just like a file=20
transfer but also includes the resulting size in
> parentheses.
>
> While designing this command the idea was to first make it simple for=20
both sides, second to make it operate as any other download,
> and third to make it as flexible as possible, allowing the client to=20
decide how the resulting data is to be used and what is=20
> needed.
> Of course the server could be configured in any way needed.  For example =

if the server wanted to limit the size of the thumbnails,
> the server could do that.  Our implementation limits the number of=20
simultaneous threads allowed to create the thumbnails at any
> given time.  I think these details need to be left to the server=20
implementation.
>
> As for using an OPT command to configure an upcoming THMB command for=20
its image type and the thumbnail size, that seems to
> complicate the command.  It's very easy to add these parameters into a=20
single command, eliminating the required handshaking=20
> between
> the client and server.  An added benefit is that neither the client nor=20
the server are required to maintain these "options"
> throughout a session, rather all of the information required is sent in=20
a single command.
>
> If you're interested in seeing it in action, download Serv-U and FTP=20
Voyager or SmartFTP.  Login to the server, switch FTP Voyager
> to "Thumbnails" view.  With SmartFTP simply select an image file and a=20
thumbnail image, of dynamic size, will appear in the=20
> preview
> pane.
>
>
> Thank you again for taking the time to provide your feedback.  I look=20
forward to your comments to the above.
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Robert McMurray" <robmcm@microsoft.com>
> Sent: Monday, November 22, 2010 5:01 PM
> To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>;=20
<mark.peterson@rhinosoft.com>
> Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> [Note: Renaming the thread from 'Submitting new drafts'.]
>
>> Anthony Bryan wrote:
>>
>> I don't mean to single you out, but
>> you showed interest in an CSID/AGNT
>> command. Do you have any opinion on
>> the other 4 commands in the draft?
>
> Thanks, Anthony.
>
> No worries - I meant to send a better response in the wake of my=20
withdrawn AGNT draft and Mark's current Streamlined FTP Command
> Extensions draft, but I had been remiss at taking the time to collect my =

thoughts in a more meaningful way. But since you asked,
> this seems like as good at time as any. ;-]
>
> CSID - As evidenced by my short-lived AGNT proposal, I think it's very=20
useful to have some sort of client/server discovery=20
> command.
> FEAT does a good job of advertising the list of commands that are=20
supported by a server, but Mark's proposed CSID command sequence
> provides a much better way for servers and client to identify their=20
features to each other in detail. For security reasons I would
> probably want the CSID exchange to occur AFTER the client has logged in, =

but I might be overreacting.
>
> RMDA - This could be a very useful command, and it would parallel the=20
functionality that I'm sure we all typically use in a native
> operating system environment. In a server implementation I would=20
probably make this command configurable, so administrators would
> have an option to disable the feature. In which case I would probably=20
hide the command from a FEAT response so it would not be
> discoverable and have the server return a 500 or 502 reply when RMDA is=20
sent by the client and disabled at the server.
>
> (Note: I mention my thoughts about server implementation details just to =

open up the discussion as to whether any implementation
> details should be called out in the draft, or if we should leave that up =

to the implementers to decide.)
>
> AVBL - This command could be very useful in a client/server world; our=20
FTP server implementation currently returns the available
> size after a successful login sequence, and the available size is based=20
on server disk quotas and such. That being said, not every
> FTP client will bubble that information up to the user interface. Having =

an AVBL command would make it possible for a client to
> determine whether enough storage space is available at the server BEFORE =

sending a file, which would be great when you're about to
> send a 10GB file and you only have 9.99GB of storage space left. ;-]
>
> DSIZ - This could certainly be useful, although I would probably want a=20
user to be logged in (not anonymous) before I supported=20
> this
> command in order to reduce the risk of denial-of-service. I'd probably=20
make it configurable so as not to tie up too many server
> resources for large directory structures; and once again, if the feature =

were disabled I would probably hide the command from a=20
> FEAT
> response so it would not be discoverable and return a 500 or 502 reply=20
when DSIZ is sent by the client and disabled at the server.
>
> THMB - I have to admit, I don't work on a graphical FTP client, so this=20
command is less useful to me personally, but I can see the
> merit that it might have to someone that designs a graphical client.=20
That being said, I'm not a big fan of computing the thumbnail
> dynamically, nor am I fond of allowing the client to specify the=20
thumbnail format and size. I think that it would be better if the
> server could pre-cache thumbnails for any file type in a=20
server-determined size and image format, and then return the binary data
> and image format information to the client. For example, most=20
graphically-based operating systems have some method for displaying
> file icons to a user that is seated at a computer terminal, so an FTP=20
server implementation could simply return that same icon to=20
> a
> client in response to a THMB request.
>
> Please bear in mind, I haven't given a lot of thought as to what the=20
client/server interchange might look like if the server were
> more in control of the response to a THMB request, but it would probably =

be sufficient to simply return the image type as part of
> the response and let the client determine the image dimensions based on=20
the client's capabilities for reading the image data. (As=20
> a
> server guy I like to push any client-friendly processing on the client=20
whenever possible. ;-]) You could borrow an idea from the
> HASH discussion that we've been having and make the thumbnail image type =

configurable for the client by using an OPTS command,=20
> which
> might look like the following examples.
>
> In this first example, the server has a pre-configured thumbnail image=20
type of JPG, and may have pre-cached the thumbnails for
> files; any THMB request with no OPTS specified would use the server's=20
pre-configured thumbnail image type of JPG and image type is
> specified in the command channel response:
>
> C> THMB widget.png
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
> S> 226 Transfer complete.
>
> In these next examples a client is asking for different thumbnail image=20
types by using OPTS commands, and the thumbnail image=20
> types
> would still be specified in the command channel responses:
>
> C> OPTS THMB GIF
> S> 200 OPTS THMB GIF command successful.
>
> C> THMB widget.psp
> S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
> S> 226 Transfer complete.
>
> C> OPTS THMB PNG
> S> 200 OPTS THMB PNG command successful.
>
> C> THMB widget.doc
> S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
> S> 226 Transfer complete.
>
> In this next example a client is asking for an unsupported image type,=20
so the server would simply return the appropriate error
> reply:
>
> C> OPTS THMB FOO
> S> 501 Unsupported thumbnail format.
>
> In this next example a client is asking for the currently-configured=20
thumbnail image type, so the server would return the
> appropriate response:
>
> C> OPTS THMB
> S> 200 JPG
>
> You might take this one step further - the server might choose to only=20
support its pre-configured thumbnail image type, thereby
> allowing pre-caching of all thumbnails in one specific image format. In=20
this example a client is asking for PNG thumbnails, which
> SHOULD be a supported image type, but the server only supports a=20
pre-configured thumbnail image type for JPG files and returns the
> appropriate error reply (504?) and the server's pre-configured thumbnail =

image type is specified in the subsequent command channel
> response to a THMB request:
>
> C> OPTS THMB PNG
> S> 504 Specifying thumbnail formats is unsupported.
>
> C> THMB widget.xls
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
> S> 226 Transfer complete.
>
> As I said earlier, I hadn't given much thought as to what the=20
client/server THMB interchange might look like if you put the server
> in control instead of the client, but as a server guy I'd rather see=20
THMB look a little more like the examples that I gave. ;-]
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
>
>
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

wfms=20


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext




--=_alternative 007AD0DC802577E4_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"sans-serif">I understand that HOST is designed to
do the job, but extensible crannies in protocols tend to get used for all
sorts of things they aren't intended for.</font>
<br>
<br><font size=3D2 face=3D"sans-serif">In fact, it wouldn't surprise me if
the review process ends up kicking the 'extensible' bits of this command
into the long grass. &nbsp;(i.e. the argument that it's actually creating
interoperability issues rather than preventing them - if there's a need
for a value - it should be defined syntactically and semantically - otherwi=
se
it doesn't belong in a protocol spec.)</font>
<br>
<br><font size=3D2 face=3D"sans-serif">I suggest that there should be some
discussion about what kind of information is valid in the CSID command/resp=
onse
and when a client/server might expect it to alter (or not). &nbsp;And if
it turns out it is tied to a &quot;session&quot; - point out that a &quot;s=
ession&quot;
can mean a number of things in FTP, so that will need to be specified too.<=
/font>
<br>
<br><font size=3D2 face=3D"sans-serif">Cheers,</font>
<br><font size=3D2 face=3D"sans-serif">Paul</font>
<br><font size=3D2 face=3D"sans-serif">-- <br>
<br>
Paul Ford-Hutchinson CISSP - Tivoli Security Consultant<br>
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU<br>
IBM Certified Deployment Professional - Tivoli Compliance Insight Manager
V8.5<br>
<br>
Tel +44 (0)7500 078379 &nbsp;(internal: 37269105)</font>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">From:</font>
<td><font size=3D1 face=3D"sans-serif">&quot;Mark P. Peterson&quot; &lt;mpp=
@rhinosoft.com&gt;</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">To:</font>
<td><font size=3D1 face=3D"sans-serif">&lt;ftpext@ietf.org&gt;, Paul Ford-H=
utchinson/UK/IBM@IBMGB</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Date:</font>
<td><font size=3D1 face=3D"sans-serif">23/11/2010 19:55</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Subject:</font>
<td><font size=3D1 face=3D"sans-serif">Re: [ftpext] draft-peterson-streamli=
ned-ftp-command-extensions</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=3D2>Hi Paul,</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D2>Thank you for taking the time to respond.</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D2>Point 1</font>
<br><font size=3D2 face=3D"sans-serif">=3D=3D=3D=3D=3D=3D</font><font size=
=3D3> </font><font size=3D2><br>
I agree with your points. &nbsp;I will clarify the document.</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D2>Point 2</font><font size=3D3> </font><font size=3D2 face=
=3D"sans-serif"><br>
=3D=3D=3D=3D=3D=3D</font><font size=3D3> </font><font size=3D2><br>
CSID doesn't contain any host specific information, the intent is only
to exchange information about the software between server and client. &nbsp=
;As
for HOST this is being proposed in a different draft for FTP. &nbsp;I belie=
ve
the information passed between the client and server should only apply
to the actual software and platform and is independent from the login infor=
mation.
&nbsp;In other words it should always return the same information.</font>
<br><font size=3D2><br>
Mark P. Peterson - President</font><font size=3D2 color=3Dblue><u><br>
</u></font><a href=3Dhttp://www.rhinosoft.com/><font size=3D2 color=3Dblue>=
<u>http://www.RhinoSoft.com</u></font></a><font size=3D2><br>
Voice: +1(262) 560-9627<br>
FAX: +1(262) 560-9628 &nbsp;</font>
<br>
<br><font size=3D3><b>From:</b> </font><a href=3Dmailto:paulfordh@uk.ibm.co=
m><font size=3D3 color=3Dblue><u>Paul
Ford-Hutchinson</u></font></a><font size=3D3> </font>
<br><font size=3D3><b>Sent:</b> Tuesday, November 23, 2010 9:16 AM</font>
<br><font size=3D3><b>To:</b> </font><a href=3Dmailto:mpp@rhinosoft.com><fo=
nt size=3D3 color=3Dblue><u>Mark
P. Peterson</u></font></a><font size=3D3> ; </font><a href=3Dmailto:ftpext@=
ietf.org><font size=3D3 color=3Dblue><u>ftpext@ietf.org</u></font></a><font=
 size=3D3>
</font>
<br><font size=3D3><b>Subject:</b> Re: [ftpext] draft-peterson-streamlined-=
ftp-command-extensions</font>
<br>
<br><font size=3D2 face=3D"sans-serif"><br>
Two comments about the CSID before login question:</font><font size=3D3>
<br>
</font><font size=3D2 face=3D"sans-serif"><br>
1) RFCs define protocols not implementations, so the discussion should
be about what =5Fcan=5F happen and how a client/server should respond.</fon=
t><font size=3D3>
</font><font size=3D2 face=3D"sans-serif"><br>
2) I'd like to be 100% certain what payload CSID can carry before banning
it totally prior to authentication.</font><font size=3D3> <br>
<br>
</font><font size=3D2 face=3D"sans-serif"><br>
Point 1 (the protocol vs implementation thing)</font><font size=3D3> </font=
><font size=3D2 face=3D"sans-serif"><br>
=3D=3D=3D=3D=3D=3D</font><font size=3D3> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
We need to say what is and isn't allowed in the protocol, comments about
implementations are interesting but not really the thrust of an RFC. &nbsp;=
In
this case, we need to state when a client may send CSID; what a server
should do if the client sends it at the wrong time - and at the right time;
whether the client should expect that a server might refuse to answer a
CSID command because it is in a particular state and that it might be sensi=
ble
for it to try again when in a different state in the protocol (e.g. logged
in).</font><font size=3D3> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
Also, don't forget that users can log out too - so simply stating after
a USER command (or some such) isn't really good enough.</font><font size=3D=
3>
<br>
</font><font size=3D2 face=3D"sans-serif"><br>
Point 2</font><font size=3D3> </font><font size=3D2 face=3D"sans-serif"><br>
=3D=3D=3D=3D=3D=3D</font><font size=3D3> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
HTTPS is broken because of something similar. &nbsp;Multi-homed http servers
cannot operate on HTTPS because the server needs to present the cert to
the client before the client tells the server which certificate (i.e. host)
it should be.</font><font size=3D3> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
I don't know if CSID may contain host specific info &nbsp;(ext=5Fcfactname
and local=5Ffact seem to be a bit of a catch all that might get used for
&quot;hostname&quot; or some such.) but be very wary of this catching people
out. &nbsp;At the very least, if CSID should not be used for host identific=
ation,
then ban such values from being in these fields.</font><font size=3D3> <br>
<br>
<br>
</font><font size=3D2 face=3D"sans-serif"><br>
Perhaps CSID could be permitted to pass different information depending
on the state of the user's session. &nbsp;(which brings us back to the
protocol vs implementation issue - should CSID always pass the same informa=
tion
regardless of session state or is the peer allowed to use session context
to decide what to include - thus meaning that two calls to CSID might be
allowed to pass different values. In fact - is a client allowed to send
multiple CSID commands and what should a server do if the information passed
in the second command does not match that from the first (and does REIN
need to be involved?)?)</font><font size=3D3> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
Cheers,</font><font size=3D3> </font><font size=3D2 face=3D"sans-serif"><br>
Paul</font><font size=3D3> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
-- <br>
<br>
Paul Ford-Hutchinson CISSP - Tivoli Security Consultant<br>
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU<br>
IBM Certified Deployment Professional - Tivoli Compliance Insight Manager
V8.5<br>
<br>
Tel +44 (0)7500 078379 &nbsp;(internal: 37269105)</font><font size=3D3> <br>
<br>
</font>
<table width=3D100%>
<tr valign=3Dtop>
<td width=3D13%><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">From:</f=
ont><font size=3D3>
</font>
<td width=3D86%><font size=3D1 face=3D"sans-serif">&quot;Mark P. Peterson&q=
uot;
&lt;mpp@rhinosoft.com&gt;</font><font size=3D3> </font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">To:</font><font size=
=3D3>
</font>
<td><font size=3D1 face=3D"sans-serif">&quot;William F. Maton&quot; &lt;wma=
ton@ottix.net&gt;</font><font size=3D3>
</font>
<tr>
<td valign=3Dtop><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Cc:</fo=
nt><font size=3D3>
</font>
<td><font size=3D1 face=3D"sans-serif">ftpext@ietf.org</font><font size=3D3>
</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Date:</font><font si=
ze=3D3>
</font>
<td><font size=3D1 face=3D"sans-serif">23/11/2010 14:45</font><font size=3D=
3>
</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Subject:</font><font=
 size=3D3>
</font>
<td><font size=3D1 face=3D"sans-serif">Re: [ftpext] draft-peterson-streamli=
ned-ftp-command-extensions</font><font size=3D3>
</font>
<tr valign=3Dtop>
<td><font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Sent by:</font><font=
 size=3D3>
</font>
<td><font size=3D1 face=3D"sans-serif">ftpext-bounces@ietf.org</font></tabl=
e>
<br><font size=3D3><br>
</font>
<hr noshade><font size=3D3><br>
<br>
</font><tt><font size=3D2><br>
Hi William,<br>
<br>
Thank you for taking the time to respond. &nbsp;I cannot think<br>
of any real reason why CSID shouldn't only be allowed after login.<br>
I will change the document to reflect this.<br>
<br>
Mark P. Peterson - President</font></tt><font size=3D3 color=3Dblue><u><br>
</u></font><a href=3Dhttp://www.rhinosoft.com/><tt><font size=3D2 color=3Db=
lue><u>http://www.RhinoSoft.com</u></font></tt></a><tt><font size=3D2><br>
Voice: +1(262) 560-9627<br>
FAX: +1(262) 560-9628<br>
<br>
<br>
--------------------------------------------------<br>
From: &quot;William F. Maton&quot; &lt;wmaton@ottix.net&gt;<br>
Sent: Tuesday, November 23, 2010 7:55 AM<br>
To: &quot;Mark P. Peterson&quot; &lt;mpp@rhinosoft.com&gt;<br>
Cc: &quot;Damin&quot; &lt;damin@emuxperts.net&gt;; &lt;ftpext@ietf.org&gt;<=
br>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions<br>
<br>
On Tue, 23 Nov 2010, Mark P. Peterson wrote:<br>
<br>
&gt; Hi All,<br>
&gt;<br>
&gt; Is there anyone else that agrees with Damin about CSID? &nbsp;He says
it SHOULD be available only after login.<br>
<br>
Hi Mark,<br>
 I'm certainly and old enough salt at systems administration to<br>
think that identification before authentication or authorization is not
a<br>
good thing. &nbsp;It makes it easier for the scanners to pick-off what
servers<br>
are running. &nbsp;I'd like to force them into making the extra effort,
since<br>
it might as well cost them more work and I can monitor the activity<br>
better.<br>
<br>
 I think standardizing CSID (from the old non-standard CLNT) is a<br>
good thing though. &nbsp;It should be left up to the implementor to support
it.<br>
<br>
 I've also read he rest of that I-D and have more thoughts on it,<br>
but that's for another email.<br>
<br>
<br>
&gt; Mark P. Peterson - President<br>
&gt; </font></tt><a href=3Dhttp://www.rhinosoft.com/><tt><font size=3D2 col=
or=3Dblue><u>http://www.RhinoSoft.com</u></font></tt></a><tt><font size=3D2=
><br>
&gt; Voice: +1(262) 560-9627<br>
&gt; FAX: +1(262) 560-9628<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: Damin<br>
&gt; Sent: Monday, November 22, 2010 10:17 PM<br>
&gt; To: ftpext@ietf.org<br>
&gt; Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extension=
s<br>
&gt;<br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt;<br>
&gt; On 22 November 2010 19:32, Mark P. Peterson &lt;mpp@rhinosoft.com&gt;
wrote:<br>
&gt;<br>
&gt; Hi Robert,<br>
&gt;<br>
&gt; Thank you for taking the time to review the commands. &nbsp;If you
don't mind I would<br>
&gt; like to respond to your comments:<br>
&gt;<br>
&gt; CSID:<br>
&gt;<br>
&gt;&gt; For security reasons I would probably want the CSID exchange to
occur AFTER the client has logged in, but I might be <br>
&gt;&gt; overreacting.<br>
&gt;<br>
&gt;<br>
&gt; There is a lot of discussion on the Internet about servers providing
&quot;too&quot; much information, especially prior to login. &nbsp;But
<br>
&gt; having<br>
&gt; worked on both sides of the FTP process, it's usually very easy for
the client to identify what brand or flavor the server is.<br>
&gt; There are details which usually identify the server such as the comple=
teness
of the FEAT response, the welcome message, responses <br>
&gt; to<br>
&gt; certain messages, etc. &nbsp;So, I think it's okay to be available
prior to login. &nbsp;I could change the document to read that it should
<br>
&gt; be<br>
&gt; up to the server's implementation whether or not it's available.<br>
&gt;<br>
&gt; I prefer to edge on the side of caution. I don=B4t see any good reason
that this SHOULD be available before login. Commands <br>
&gt; available<br>
&gt; prior to login should be as limited as possible.<br>
&gt;<br>
&gt;<br>
&gt; RMDA:<br>
&gt;<br>
&gt;&gt; In a server implementation I would probably make this command
configurable, so administrators would have an option to disable the<br>
&gt;&gt; feature. &nbsp;In which case I would probably hide the command
from a FEAT response so it would not be discoverable and have the <br>
&gt;&gt; server<br>
&gt;&gt; return a 500 or 502 reply when RMDA is sent by the client and
disabled at the server.<br>
&gt;<br>
&gt;<br>
&gt; I don't think my document specifies that it isn't configurable. &nbsp;=
My
implementation in Serv-U is configurable as is almost all <br>
&gt; other<br>
&gt; FTP commands. &nbsp;I think this can be left up to the server implemen=
tation.
&nbsp;Your possible implementation is exactly how Serv-U<br>
&gt; implements it. &nbsp;If the feature is disabled, it doesn't appear
in the FEAT response, nor is it available through the HELP command.<br>
&gt;<br>
&gt;<br>
&gt; AVBL:<br>
&gt;&gt; ...<br>
&gt;<br>
&gt; Your comments address the reason for its existence. &nbsp;The client-s=
ide
implementation in SmartFTP uses the command in this manner.<br>
&gt;<br>
&gt; DSIZ:<br>
&gt;&gt; This could certainly be useful, although I would probably want
a user to be logged in...<br>
&gt;<br>
&gt; Any information about paths or files requires login in FTP. &nbsp;I
am sure this is the case here as well. &nbsp;If a server wouldn't want
<br>
&gt; the<br>
&gt; &quot;anonymous&quot; user to have access to this command it could
be configured to disallow this command at the server's implementation or<br>
&gt; configuration. &nbsp;This should be left up to the implementation
of the server or administrator of the server.<br>
&gt;<br>
&gt;&gt; I'd probably make it configurable so as not to tie up too many
server resources for large directory structures;...<br>
&gt;<br>
&gt; Agreed, the time-consuming nature of the implementation is discussed
but configuration by an administrator or <br>
&gt; server-implementation<br>
&gt; is not. &nbsp; Do you think such verbiage is required?<br>
&gt;<br>
&gt;<br>
&gt; THMB:<br>
&gt;<br>
&gt;&gt; I'm not a big fan of computing the thumbnail dynamically, nor
am I fond of allowing the client to specify the thumbnail format <br>
&gt;&gt; and<br>
&gt;&gt; size.<br>
&gt;<br>
&gt;<br>
&gt; That's the point of the command, though. &nbsp;It's to reduce the
amount of data that is required to travel over the wire. &nbsp;The idea
is<br>
&gt; to shorten delivery time to the client, letting the client decide
what is best for the client, not the server. &nbsp;Some clients may<br>
&gt; want very small images, say for a Windows Explorer style listing,
others may want larger images (640x480 for example) to show a<br>
&gt; slide show. &nbsp;I think the client needs to make that determination.
&nbsp;If the server decides to cache these generated images it can.<br>
&gt;<br>
&gt;<br>
&gt;&gt; I think that it would be better if the server could pre-cache
thumbnails for any file type in a server-determined size and image<br>
&gt;&gt; format, and then return the binary data and image format informati=
on
to the client.<br>
&gt;<br>
&gt;<br>
&gt; This could waste server-side resources, the client might not even
make a request for thumbnail images.<br>
&gt;<br>
&gt;<br>
&gt;&gt; For example, most graphically-based operating systems have some
method for displaying file icons to a user that is seated at a<br>
&gt;&gt; computer terminal, so an FTP server implementation could simply
return that same icon to a client in response to a THMB request.<br>
&gt;<br>
&gt;<br>
&gt; Right, but this isn't really the purpose of this command. &nbsp;The
purpose is to take an original image file and reduce it to a<br>
&gt; specified size, not to return the OS's icon representation for that
particular file type (i.e., not SHGetFileInfo() in Windows).<br>
&gt;<br>
&gt; My proposed implementation is fairly straightforward. &nbsp;If support=
ed
the FEAT command replies with THMB and the supported file <br>
&gt; types.<br>
&gt; When the client wants a thumbnail it asks for it with a single command.
&nbsp;Here is a sample result from FTP Voyager and Serv-U:<br>
&gt;<br>
&gt; PORT 192,168,0,30,199,53<br>
&gt; 200 PORT command successful.<br>
&gt; THMB PNG 98 88 Thomas.JPG<br>
&gt; 150 Opening thumbnail image transfer BINARY mode data connection (19738
Bytes) for Thomas.JPG.<br>
&gt; 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%)
transferred. 19.29 actual KB/sec, &nbsp;19.28 effective KB/sec.<br>
&gt;<br>
&gt; The client opens a data channel just like any other file transfer,
then requests the file using THMB, followed by the output type,<br>
&gt; width, height, and the file name. &nbsp;The server responds just like
a file transfer but also includes the resulting size in<br>
&gt; parentheses.<br>
&gt;<br>
&gt; While designing this command the idea was to first make it simple
for both sides, second to make it operate as any other download,<br>
&gt; and third to make it as flexible as possible, allowing the client
to decide how the resulting data is to be used and what is <br>
&gt; needed.<br>
&gt; Of course the server could be configured in any way needed. &nbsp;For
example if the server wanted to limit the size of the thumbnails,<br>
&gt; the server could do that. &nbsp;Our implementation limits the number
of simultaneous threads allowed to create the thumbnails at any<br>
&gt; given time. &nbsp;I think these details need to be left to the server
implementation.<br>
&gt;<br>
&gt; As for using an OPT command to configure an upcoming THMB command
for its image type and the thumbnail size, that seems to<br>
&gt; complicate the command. &nbsp;It's very easy to add these parameters
into a single command, eliminating the required handshaking <br>
&gt; between<br>
&gt; the client and server. &nbsp;An added benefit is that neither the
client nor the server are required to maintain these &quot;options&quot;<br>
&gt; throughout a session, rather all of the information required is sent
in a single command.<br>
&gt;<br>
&gt; If you're interested in seeing it in action, download Serv-U and FTP
Voyager or SmartFTP. &nbsp;Login to the server, switch FTP Voyager<br>
&gt; to &quot;Thumbnails&quot; view. &nbsp;With SmartFTP simply select
an image file and a thumbnail image, of dynamic size, will appear in the
<br>
&gt; preview<br>
&gt; pane.<br>
&gt;<br>
&gt;<br>
&gt; Thank you again for taking the time to provide your feedback. &nbsp;I
look forward to your comments to the above.<br>
&gt;<br>
&gt; Mark P. Peterson - President<br>
&gt; </font></tt><a href=3Dhttp://www.rhinosoft.com/><tt><font size=3D2 col=
or=3Dblue><u>http://www.RhinoSoft.com</u></font></tt></a><tt><font size=3D2=
><br>
&gt; Voice: +1(262) 560-9627<br>
&gt; FAX: +1(262) 560-9628<br>
&gt;<br>
&gt;<br>
&gt; --------------------------------------------------<br>
&gt; From: &quot;Robert McMurray&quot; &lt;robmcm@microsoft.com&gt;<br>
&gt; Sent: Monday, November 22, 2010 5:01 PM<br>
&gt; To: &lt;ftpext@ietf.org&gt;; &quot;'Anthony Bryan'&quot; &lt;anthonybr=
yan@gmail.com&gt;;
&lt;mark.peterson@rhinosoft.com&gt;<br>
&gt; Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions<br>
&gt;<br>
&gt;<br>
&gt; [Note: Renaming the thread from 'Submitting new drafts'.]<br>
&gt;<br>
&gt;&gt; Anthony Bryan wrote:<br>
&gt;&gt;<br>
&gt;&gt; I don't mean to single you out, but<br>
&gt;&gt; you showed interest in an CSID/AGNT<br>
&gt;&gt; command. Do you have any opinion on<br>
&gt;&gt; the other 4 commands in the draft?<br>
&gt;<br>
&gt; Thanks, Anthony.<br>
&gt;<br>
&gt; No worries - I meant to send a better response in the wake of my withd=
rawn
AGNT draft and Mark's current Streamlined FTP Command<br>
&gt; Extensions draft, but I had been remiss at taking the time to collect
my thoughts in a more meaningful way. But since you asked,<br>
&gt; this seems like as good at time as any. ;-]<br>
&gt;<br>
&gt; CSID - As evidenced by my short-lived AGNT proposal, I think it's
very useful to have some sort of client/server discovery <br>
&gt; command.<br>
&gt; FEAT does a good job of advertising the list of commands that are
supported by a server, but Mark's proposed CSID command sequence<br>
&gt; provides a much better way for servers and client to identify their
features to each other in detail. For security reasons I would<br>
&gt; probably want the CSID exchange to occur AFTER the client has logged
in, but I might be overreacting.<br>
&gt;<br>
&gt; RMDA - This could be a very useful command, and it would parallel
the functionality that I'm sure we all typically use in a native<br>
&gt; operating system environment. In a server implementation I would proba=
bly
make this command configurable, so administrators would<br>
&gt; have an option to disable the feature. In which case I would probably
hide the command from a FEAT response so it would not be<br>
&gt; discoverable and have the server return a 500 or 502 reply when RMDA
is sent by the client and disabled at the server.<br>
&gt;<br>
&gt; (Note: I mention my thoughts about server implementation details just
to open up the discussion as to whether any implementation<br>
&gt; details should be called out in the draft, or if we should leave that
up to the implementers to decide.)<br>
&gt;<br>
&gt; AVBL - This command could be very useful in a client/server world;
our FTP server implementation currently returns the available<br>
&gt; size after a successful login sequence, and the available size is
based on server disk quotas and such. That being said, not every<br>
&gt; FTP client will bubble that information up to the user interface.
Having an AVBL command would make it possible for a client to<br>
&gt; determine whether enough storage space is available at the server
BEFORE sending a file, which would be great when you're about to<br>
&gt; send a 10GB file and you only have 9.99GB of storage space left. ;-]<b=
r>
&gt;<br>
&gt; DSIZ - This could certainly be useful, although I would probably want
a user to be logged in (not anonymous) before I supported <br>
&gt; this<br>
&gt; command in order to reduce the risk of denial-of-service. I'd probably
make it configurable so as not to tie up too many server<br>
&gt; resources for large directory structures; and once again, if the featu=
re
were disabled I would probably hide the command from a <br>
&gt; FEAT<br>
&gt; response so it would not be discoverable and return a 500 or 502 reply
when DSIZ is sent by the client and disabled at the server.<br>
&gt;<br>
&gt; THMB - I have to admit, I don't work on a graphical FTP client, so
this command is less useful to me personally, but I can see the<br>
&gt; merit that it might have to someone that designs a graphical client.
That being said, I'm not a big fan of computing the thumbnail<br>
&gt; dynamically, nor am I fond of allowing the client to specify the thumb=
nail
format and size. I think that it would be better if the<br>
&gt; server could pre-cache thumbnails for any file type in a server-determ=
ined
size and image format, and then return the binary data<br>
&gt; and image format information to the client. For example, most graphica=
lly-based
operating systems have some method for displaying<br>
&gt; file icons to a user that is seated at a computer terminal, so an
FTP server implementation could simply return that same icon to <br>
&gt; a<br>
&gt; client in response to a THMB request.<br>
&gt;<br>
&gt; Please bear in mind, I haven't given a lot of thought as to what the
client/server interchange might look like if the server were<br>
&gt; more in control of the response to a THMB request, but it would probab=
ly
be sufficient to simply return the image type as part of<br>
&gt; the response and let the client determine the image dimensions based
on the client's capabilities for reading the image data. (As <br>
&gt; a<br>
&gt; server guy I like to push any client-friendly processing on the client
whenever possible. ;-]) You could borrow an idea from the<br>
&gt; HASH discussion that we've been having and make the thumbnail image
type configurable for the client by using an OPTS command, <br>
&gt; which<br>
&gt; might look like the following examples.<br>
&gt;<br>
&gt; In this first example, the server has a pre-configured thumbnail image
type of JPG, and may have pre-cached the thumbnails for<br>
&gt; files; any THMB request with no OPTS specified would use the server's
pre-configured thumbnail image type of JPG and image type is<br>
&gt; specified in the command channel response:<br>
&gt;<br>
&gt; C&gt; THMB widget.png<br>
&gt; S&gt; 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png<=
br>
&gt; S&gt; 226 Transfer complete.<br>
&gt;<br>
&gt; In these next examples a client is asking for different thumbnail
image types by using OPTS commands, and the thumbnail image <br>
&gt; types<br>
&gt; would still be specified in the command channel responses:<br>
&gt;<br>
&gt; C&gt; OPTS THMB GIF<br>
&gt; S&gt; 200 OPTS THMB GIF command successful.<br>
&gt;<br>
&gt; C&gt; THMB widget.psp<br>
&gt; S&gt; 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp<=
br>
&gt; S&gt; 226 Transfer complete.<br>
&gt;<br>
&gt; C&gt; OPTS THMB PNG<br>
&gt; S&gt; 200 OPTS THMB PNG command successful.<br>
&gt;<br>
&gt; C&gt; THMB widget.doc<br>
&gt; S&gt; 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc<=
br>
&gt; S&gt; 226 Transfer complete.<br>
&gt;<br>
&gt; In this next example a client is asking for an unsupported image type,
so the server would simply return the appropriate error<br>
&gt; reply:<br>
&gt;<br>
&gt; C&gt; OPTS THMB FOO<br>
&gt; S&gt; 501 Unsupported thumbnail format.<br>
&gt;<br>
&gt; In this next example a client is asking for the currently-configured
thumbnail image type, so the server would return the<br>
&gt; appropriate response:<br>
&gt;<br>
&gt; C&gt; OPTS THMB<br>
&gt; S&gt; 200 JPG<br>
&gt;<br>
&gt; You might take this one step further - the server might choose to
only support its pre-configured thumbnail image type, thereby<br>
&gt; allowing pre-caching of all thumbnails in one specific image format.
In this example a client is asking for PNG thumbnails, which<br>
&gt; SHOULD be a supported image type, but the server only supports a pre-c=
onfigured
thumbnail image type for JPG files and returns the<br>
&gt; appropriate error reply (504?) and the server's pre-configured thumbna=
il
image type is specified in the subsequent command channel<br>
&gt; response to a THMB request:<br>
&gt;<br>
&gt; C&gt; OPTS THMB PNG<br>
&gt; S&gt; 504 Specifying thumbnail formats is unsupported.<br>
&gt;<br>
&gt; C&gt; THMB widget.xls<br>
&gt; S&gt; 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls<=
br>
&gt; S&gt; 226 Transfer complete.<br>
&gt;<br>
&gt; As I said earlier, I hadn't given much thought as to what the client/s=
erver
THMB interchange might look like if you put the server<br>
&gt; in control instead of the client, but as a server guy I'd rather see
THMB look a little more like the examples that I gave. ;-]<br>
&gt;<br>
&gt; Thanks again!<br>
&gt;<br>
&gt; Robert McMurray<br>
&gt; robmcm@microsoft.com<br>
&gt;<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ftpext mailing list<br>
&gt; ftpext@ietf.org<br>
&gt; </font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt=
><font size=3D2 color=3Dblue><u>https://www.ietf.org/mailman/listinfo/ftpex=
t</u></font></tt></a><tt><font size=3D2><br>
&gt;<br>
&gt;<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ftpext mailing list<br>
&gt; ftpext@ietf.org<br>
&gt; </font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt=
><font size=3D2 color=3Dblue><u>https://www.ietf.org/mailman/listinfo/ftpex=
t</u></font></tt></a><tt><font size=3D2><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ftpext mailing list<br>
&gt; ftpext@ietf.org<br>
&gt; </font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt=
><font size=3D2 color=3Dblue><u>https://www.ietf.org/mailman/listinfo/ftpex=
t</u></font></tt></a><tt><font size=3D2><br>
&gt;<br>
&gt;<br>
&gt; =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
&gt; ftpext mailing list<br>
&gt; ftpext@ietf.org<br>
&gt; </font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt=
><font size=3D2 color=3Dblue><u>https://www.ietf.org/mailman/listinfo/ftpex=
t</u></font></tt></a><tt><font size=3D2><br>
&gt;<br>
<br>
wfms <br>
<br>
<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
ftpext mailing list<br>
ftpext@ietf.org</font></tt><font size=3D3 color=3Dblue><u><br>
</u></font><a href=3Dhttps://www.ietf.org/mailman/listinfo/ftpext><tt><font=
 size=3D2 color=3Dblue><u>https://www.ietf.org/mailman/listinfo/ftpext</u><=
/font></tt></a><font size=3D3><br>
<br>
</font>
<br>
<br>
--=_alternative 007AD0DC802577E4_=--

From keisial@gmail.com  Tue Nov 23 15:53:14 2010
Return-Path: <keisial@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 06F443A6987 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 15:53:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 Hy+AikuTerRF for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 15:53:13 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id CC03A3A68F5 for <ftpext@ietf.org>; Tue, 23 Nov 2010 15:53:12 -0800 (PST)
Received: by eyd10 with SMTP id 10so5169942eyd.31 for <ftpext@ietf.org>; Tue, 23 Nov 2010 15:54:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=mY0Q+bTRCZ6xlld0fLwXaRHsya1hSvcS3NwqyvMQp3U=; b=u6dGYntqqsgOOke5EmaToRW0W7q5qHycOZzCZq5pD3524vuYgdiDF9HDgbF7D2E/e+ ItlBSxH06ZKKFGWvvu2DlCJe7kOoUCwREf4B1i4T1u3BqZBd4q4bXKavNa8m6WkFa00m 5IE6QExMS1Fn8kaaEdtaiGqP+KExU2SKtCgjE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=j4kH1V+V/d+sz+3JwBzIbjZWHm1m5FVlrqmb1nRJleUcS5in3Ls2hjB0AvugL9L9Xl AMaxy0EDK+A0xLXadzEme8JIH8Q1tqtFxf57Kw56/Jkjx464rU83mt/j1OAjiNqjZNwU ugwkxBFMgght7KuoQRH9N8zjITK2ckDUoiHEo=
Received: by 10.216.161.130 with SMTP id w2mr2275524wek.17.1290556444208; Tue, 23 Nov 2010 15:54:04 -0800 (PST)
Received: from [192.168.1.26] ([83.35.126.127]) by mx.google.com with ESMTPS id y15sm3171213weq.6.2010.11.23.15.53.59 (version=SSLv3 cipher=RC4-MD5); Tue, 23 Nov 2010 15:54:02 -0800 (PST)
Message-ID: <4CEC5427.1070605@gmail.com>
Date: Wed, 24 Nov 2010 00:54:15 +0100
From: "=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=" <keisial@gmail.com>
User-Agent: Thunderbird
MIME-Version: 1.0
To: ftpext@ietf.org
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com>
In-Reply-To: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mark.peterson@rhinosoft.com, Robert McMurray <robmcm@microsoft.com>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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: Tue, 23 Nov 2010 23:53:14 -0000

Hello all,

Robert McMurray wrote:
> RMDA - This could be a very useful command, and it would parallel the
> functionality that I'm sure we all typically use in a native operating
> system environment. In a server implementation I would probably make
> this command configurable, so administrators would have an option to
> disable the feature. In which case I would probably hide the command
> from a FEAT response so it would not be discoverable and have the
> server return a 500 or 502 reply when RMDA is sent by the client and
> disabled at the server.

I don't think a server should do that or be encouraged to. If a server
rejects a RMDA the client SHOULD fall back to a recursive listing and
removing.
As currently defined, on receiving a RMDA the server MUST delete
everything in the subpath the user is allowed to. I think that changing
it to also allow a not remove anything would solve the issue.
If the folder being RMDAed is not deletable by the logged in user, the
server MAY -based both on its configuration and user credentials-
directly reject the command. On the other hand, if it deletes one file
(and can not rollback the operation), it must continue the whole subtree.


About THMB:
The format is restricted to registered image subtypes. It should allow
full MIME types, so an application/x-better-image-format could be used.
And giving that step, always using the full mime for images would seem
more clear.

I also prefer the OPTS syntax, since that would allow larger options and
extensions, such as:

  C> OPTS THMB image/png 60 60 page=2
  S> 200 OPTS THMB PNG command successful.

  C> THMB document.doc
  S> 150 PNG Starting thumbnail transfer
  S> 226 Transfer complete.

for requesting a thumbnail for the second page of the document.

Since the OPTS would be given once at the beginning and then used for many files, it's also important for reducing its continuous repetition.


Robert McMurray wrote:
> That being said, I'm not a big fan of computing the thumbnail dynamically, nor am I fond of allowing the client to specify the thumbnail format and size. I think that it would be better if the server could pre-cache thumbnails for any file type in a server-determined size and image format, and then return the binary data and image format information to the client. For example, most graphically-based operating systems have some method for displaying file icons to a user that is seated at a computer terminal, so an FTP server implementation could simply return that same icon to a client in response to a THMB request.
Note that the server can compute it the first time, then cache the
thumbnails you have requested on previous sessions. Moreover, it could
get heuristics as 'Start prethumbnailing with the current options if it
has requested in order the thumbnails of the first three files in the
folder'.


There should be a note about the potential security issues of the THMB
command. Vulnerabilities processing images are common.



Mat Berchtold wrote:
> Server/Client fact requirement
> The draft proposes that the client must provide the name and version fact where for the server these facts are optional. For equality both parties involved should have equal requirements/rights. My proposal is that all facts are optional. The reasoning is that there is no need for the client to expose its name or version if it only wants to figure out the case sensitivity of the server file system.
Sad as it is, it may be useful for implementing client-specific
workarounds in the server.




From tony@att.com  Tue Nov 23 15:55:01 2010
Return-Path: <tony@att.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 309B728C110 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 15:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.434
X-Spam-Level: 
X-Spam-Status: No, score=-106.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 e2jpiG9nI3LQ for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 15:55:00 -0800 (PST)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 18BBD3A68F5 for <ftpext@ietf.org>; Tue, 23 Nov 2010 15:54:59 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-5.tower-161.messagelabs.com!1290556556!19924708!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 21688 invoked from network); 23 Nov 2010 23:55:57 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-5.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Nov 2010 23:55:57 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oANNuF3p012767 for <ftpext@ietf.org>; Tue, 23 Nov 2010 18:56:15 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oANNu8fJ012698 for <ftpext@ietf.org>; Tue, 23 Nov 2010 18:56:08 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oANNtn41023202 for <ftpext@ietf.org>; Tue, 23 Nov 2010 18:55:49 -0500
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oANNtk01023107 for <ftpext@ietf.org>; Tue, 23 Nov 2010 18:55:46 -0500
Received: from [135.70.10.203] (vpn-135-70-10-203.vpn.west.att.com[135.70.10.203]) by maillennium.att.com (mailgw1) with ESMTP id <20101123235545gw1004lku4e> (Authid: tony); Tue, 23 Nov 2010 23:55:46 +0000
X-Originating-IP: [135.70.10.203]
Message-ID: <4CEC5480.8040801@att.com>
Date: Tue, 23 Nov 2010 18:55:44 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: ftpext@ietf.org
References: <20101123184835.AFC433A69A1@core3.amsl.com> <AANLkTinYUc1G-syqicN31Rc+yV6UvKurB-O1nQba2Y9=@mail.gmail.com>
In-Reply-To: <AANLkTinYUc1G-syqicN31Rc+yV6UvKurB-O1nQba2Y9=@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ftpext] WG Action: FTP Extensions, 2nd edition (ftpext2)
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: Tue, 23 Nov 2010 23:55:01 -0000

On 11/23/2010 4:17 PM, Anthony Bryan wrote:
> so, wow, looks like things are rolling along! :)
>
> as you can see, our WG got approved last Thursday.
>
> I'm very happy to see comments on
> draft-peterson-streamlined-ftp-command-extensions still coming in.
> please chime in if you haven't already.
>
> I'm new to this, so I wonder what the first order of business is?
>
> here are some ideas:
>
> 1) we have 4 drafts on the charter, 3 of which are "active" (John
> hasn't updated draft-klensin-ftp-typeu yet). once these are submitted
> with the string '-ftpext2-' in the
> draft name, they will show up at http://tools.ietf.org/wg/ftpext2/
>
> I think our ID draft-bryan-ftp-hash becomes ietf-ftpext2-hash then? (&
> the others follow in a similar fashion).

When the next update is ready for each draft, each author should upload 
the draft under the WG name. Bryan's naming suggestion is apropos:

draft-bryan-ftp-hash => draft-ietf-ftpext2-hash
draft-hethmon-mcmurray-ftp-hosts => draft-ietf-ftpext2-hosts
draft-klensin-ftp-typeu => draft-ietf-ftpext2-typeu

John, since yours is long expired, it would be useful if you just upload 
it under the new name so people can start commenting on it.

> should this be done now? we should change the WG at the top of our
> drafts I guess. how is this done in xml2rfc? is there anything else
> that needs to be changed?
This is optional: it is done by using the <workgroup> element in the 
<front> matter.

     Tony Hansen
     tony@att.com

From robmcm@microsoft.com  Tue Nov 23 20:25:14 2010
Return-Path: <robmcm@microsoft.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 73E2528C105 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 20:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 iqREiCOcvWtJ for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 20:25:12 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id C643D28C100 for <ftpext@ietf.org>; Tue, 23 Nov 2010 20:25:12 -0800 (PST)
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 23 Nov 2010 20:26:11 -0800
Received: from TK5EX14MBXC127.redmond.corp.microsoft.com ([169.254.6.27]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.01.0255.003; Tue, 23 Nov 2010 20:26:11 -0800
From: Robert McMurray <robmcm@microsoft.com>
To: "'Mark P. Peterson'" <mpp@rhinosoft.com>, "ftpext@ietf.org" <ftpext@ietf.org>
Thread-Topic: [ftpext] draft-peterson-streamlined-ftp-command-extensions
Thread-Index: AcuKmTvkbDnCespiQ8mhziICo1jv5gAT8D+AACiZCZA=
Date: Wed, 24 Nov 2010 04:26:11 +0000
Message-ID: <A5FC996C3C37DC4DA5076F1046B5674C442E8816@TK5EX14MBXC127.redmond.corp.microsoft.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com> <D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net>
In-Reply-To: <D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 24 Nov 2010 04:25:14 -0000

Thanks, Mark.

> Mark wrote:
>=20
> That's the point of the command,
> though.  It's to reduce the amount of
> data that is required to travel over
> the wire.  The idea is to shorten
> delivery time to the client, letting
> the client decide what is best for
> the client, not the server.

I understood that to be the case, but looking back to Anthony's original qu=
estion - he had asked which commands were more valuable to me than others. =
With that in mind, when I considered the THMB command from a server impleme=
ntation point-of-view as it appears in the current draft, I thought that th=
e current proposal was a little impractical, which would make me lean away =
from implementing it.

Here's a real-world scenario that illustrates why I think that the current =
THMB proposal breaks down quickly in a normal use scenario:

Let's say that I have a friend who works in astrophotography, and let's say=
 that he's doing his doctoral work on the Crab Nebula. He books some time a=
t one of the national observatories and takes several series of images of t=
he Crab Nebula that are stitched together into 50 large composite images. (=
These have very large dimensions, 100K by 100K pixels, and each is over 100=
MB in size, which are the perfect candidates for thumbnails.) When he publi=
shes his thesis for peer review, he drops the full-sized images in a direct=
ory on an FTP site that I manage where his colleagues can access them. Let'=
s say that his thesis garners a modicum of interest on the day of its publi=
cation for review - perhaps just 10 users. Each of these users has an FTP c=
lient that supports the THMB command as it is currently designed, and each =
FTP client can use varying thumbnail dimensions. So here's what happens:

Client 1 has the following transaction:

Client01> THMB JPG 100 100 Crab_Nebula_01.jpg
Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
-         //Note: 5K bytes are transferred over the data channel//
Server00> 226 Transfer complete.

Since the thumbnail was generated dynamically based on the client's input, =
one of my server's CPUs spikes while it loads the 100MB image into RAM, ren=
ders the thumbnail in the user-requested image format and dimensions, and d=
umps the image on the wire. (Because a client can request any image dimensi=
ons and format, my server implementation would probably not cache the thumb=
nail in memory, but I'll come back to that.) Still, transferring only 5K ov=
er the wire is a lot better than transferring 100MB, so we're in agreement =
that reducing the bandwidth is a good thing.

But I have 9 other clients that are hitting my FTP site and they issue FTP =
thumbnail requests like the following examples:

Client02> THMB PNG 100 100 Crab_Nebula_01.jpg
Client03> THMB GIF 100 100 Crab_Nebula_01.jpg
Client04> THMB JPG 200 200 Crab_Nebula_01.jpg
Client05> THMB PNG 200 200 Crab_Nebula_01.jpg
Client06> THMB GIF 150 150 Crab_Nebula_01.jpg
Client07> THMB PNG 640 480 Crab_Nebula_01.jpg
Client08> THMB GIF 320 240 Crab_Nebula_01.jpg
Client09> THMB JPG 150 150 Crab_Nebula_01.jpg
Client10> THMB JPG 320 240 Crab_Nebula_01.jpg

So my server has received 10 completely dissimilar thumbnail requests, and =
all of those requests are just for the first physical image. If each FTP cl=
ient attempts to download just 20 thumbnails in order to show the first set=
 of thumbnails in each graphical FTP client, I have to dynamically generate=
 200 different thumbnails. Since these are all 100MB images, I am reducing =
my bandwidth at the expense of the CPU and RAM resources that are required =
to process the THMB requests.=20

I mentioned earlier that I would probably not cache the thumbnails in RAM b=
ecause the client can request any thumbnail dimensions, so let's say that m=
y server implementation at least caches thumbnails to disk so I don't have =
to generate them dynamically for every request. Since each FTP client can r=
equest multiple image formats and any image dimensions, I may have to keep =
track of hundreds of thumbnails for each single physical image. That will q=
uickly start to eat up disk space, so now I have to implement some form of =
garbage collection to clean up stale thumbnails. But even then, since my fr=
iend has 50 physical images and I configure my FTP server implementation to=
 only keep the 10 most-recent thumbnails around, I'm still managing 500 thu=
mbnails for his original 50 physical images.

All in all I find the approach for letting only the client have full contro=
l very impractical, and that would prevent me from wanting to implement the=
 THMB command as it is currently documented in the draft. But that being sa=
id, I like the idea of having a thumbnail command, just not the way that it=
's currently proposed. That's why I was suggesting some alternatives, and I=
'll expound a little on that.

In my last email I had suggested letting the server be a little more in con=
trol, and I had suggested that the server could optionally tell an FTP clie=
nt that the client can't specify the image format. If I use the astrophotog=
raphy scenario that I just gave, that means that I could have my friend pre=
-create the 50 thumbnails for the 50 physical images in some fashion where =
the FTP server implementation would pick them up. (I could use shadow folde=
rs, unique thumbnail naming, etc.) This means that there is no spike in CPU=
 or RAM when the 10 FTP clients issue their THMB requests; it also means th=
at I'm only managing 50 static thumbnails. So now the requests could be as =
simple as the following:

Client01> THMB Crab_Nebula_01.jpg
Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
Server00> 226 Transfer complete.
Client02> THMB Crab_Nebula_01.jpg
Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
Server00> 226 Transfer complete.
... etc ...

The reason why I had proposed using the OPTS command was to give the client=
 the level of control that you mentioned in your reply, e.g. "letting the c=
lient decide what is best for the client, not the server." If you were to c=
ombine your client request concepts with elements of my OPTS-based suggesti=
on, you could create a hybrid of the two approaches that might address all =
concerns. Here are some examples:

In this example, the client simply asks for the server's current thumbnail =
configuration:
C> OPTS THMB
S> 200 JPG 100 100

In this example, the client specifies a new thumbnail format:
C> OPTS THMB PNG
S> 200 PNG 100 100

In this example, the client specifies a new thumbnail format and dimensions=
:
C> OPTS THMB GIF 150 150
S> 200 GIF 150 150

I think that something more of a hybrid approach works better - the client =
can ask for a file format and dimensions, but the server can still say "no"=
 to a client-specified file format and dimensions when it wants to, but sti=
ll return a thumbnail when the client asks for it.

C> OPTS THMB PNG 100 100
S> 504 Specifying thumbnail properties is unsupported.

C> THMB widget.png
S> 150 JPG Starting thumbnail transfer for widget.png
S> 226 Transfer complete.

This makes it easier for the server implementation to have a pre-cached col=
lection of thumbnails, especially when given the realistic scenario that I =
listed above. But if you omit using OPTS command and stick with using a sin=
gle THMB command, when an FTP client sends a request that your server doesn=
't want to fulfill for some reason, your only recourse is to fail the whole=
 request. Whereas, if break the process into separate OPTS and THMB command=
s, you can fulfill a THMB request even if you reject the custom parameters =
that the client had requested with an OPTS command.

> Mark wrote:
>=20
> This could waste server-side
> resources, the client might not even
> make a request for thumbnail images.

This is true, but using the astrophotography scenario once again, I'd rathe=
r have 50 5K thumbnail files eating up a tiny fraction of disk space (which=
 is a dirt cheap resource) rather than trying to generate dynamic thumbnail=
s for 50 100MB images and eating CPU and RAM (which are expensive resources=
).

If my server implementation didn't pre-cache thumbnails, and I configured m=
y server to only allow JPG format thumbnails at 100x100 pixels, it would st=
ill be possible to implement some form of in-memory or dynamic to disk cach=
ing for subsequent requests, because now the list of variables has been red=
uced. For example:

Client01> THMB Crab_Nebula_01.jpg
-        //Note: the thumbnail was not//
-        //pre-cached, so the server  //
-        //creates it dynamically and //
-        //caches it to disk after it //
-        //sends the thumbnail to the //
-        //client                     //
Client02> THMB Crab_Nebula_01.jpg
-        //Note: the thumbnail was    //
-        //cached during the previous //
-        //request, so the server can //
-        //send the thumbnail to the  //
-        //client with no additional  //
-        //processing required        //
Client03> THMB Crab_Nebula_01.jpg
... etc ...
Client10> THMB Crab_Nebula_01.jpg

> Mark wrote:
>=20
> This isn't really the purpose of this
> command.  The purpose is to take an
> original image file and reduce it to
> a specified size, not to return the
> OS's icon representation for that
> particular file type.

Perhaps that was not the originally-intended purpose for this command, but =
then I think that you're limiting the usefulness of the command. My suggest=
ion to return an icon may not have been the best example, but limiting the =
THMB command to just image files is not very useful, since there are other =
files that would yield beneficial results. For example, video files are typ=
ically much larger than images, so why shouldn't video files be able to hav=
e unique thumbnails? What about thumbnails for new image types that are int=
roduced later, like SVG files? I would say that it's certainly possible tha=
t any server implementation could refuse to send a thumbnail for any file t=
hat it chooses, but why shouldn't a server implementation be able to return=
 a thumbnail for any file? I am simply suggesting that limiting the functio=
nality of the THMB command to just images reduces the overall value of the =
command.

All that being said, as I stated earlier, I like the idea of a THMB command=
, but at the moment I'm not fond of the current proposal. When I consider t=
hat implementers of FTP clients might read about the THMB command in an RFC=
 and start creating FTP clients that can issue requests for thumbnails in a=
ny number of image formats and pixel dimensions, I start to back away from =
this command pretty quickly.

I admit that it would be different if I implemented my own graphical FTP cl=
ient and my own FTP server, because I could control the THMB interoperabili=
ty in a way of my choosing - for example, I could define a specific set of =
thumbnail dimensions and only use JPG format. But since I would only be imp=
lementing an FTP server, I don't like the way the odds are stacked. (In som=
e ways this is like writing a function to strip whitespace from text files =
- if you generate all of your own text files, then you only have to anticip=
ate what you've defined as whitespace. But when you're stripping whitespace=
 from someone else's text files, you have to anticipate 0x20, 0x09, 0xA0, m=
ultiple character sets, what to do when you get character codes that you do=
n't recognize, etc.)

Just the same, I'd like to see some form of thumbnail functionality if poss=
ible, because the scenario about astrophotography wasn't hypothetical - I a=
ctually have a friend that works with astrophotography who generates those =
types of huge image files; having an effective method to retrieve thumbnail=
s for those large images would be great. But I don't think that the current=
 draft offers an example of an effective method when I consider having to c=
reate dynamically-generated thumbnails for a near-infinite number of possib=
le client request parameters.

Thanks again!

Robert McMurray
robmcm@microsoft.com

From damin@emuxperts.net  Tue Nov 23 21:20:23 2010
Return-Path: <damin@emuxperts.net>
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 6585628C1DD for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 21:20:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.826
X-Spam-Level: 
X-Spam-Status: No, score=-1.826 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 Bk9+wNM79I+a for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 21:20:20 -0800 (PST)
Received: from ca0.emuxperts.net (ca0.emuxperts.net [96.45.180.106]) by core3.amsl.com (Postfix) with ESMTP id 640F128C1DB for <ftpext@ietf.org>; Tue, 23 Nov 2010 21:20:20 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ca0.emuxperts.net (Postfix) with ESMTPSA id 6B6D11FC074 for <ftpext@ietf.org>; Wed, 24 Nov 2010 05:21:18 +0000 (GMT)
Received: by ewy8 with SMTP id 8so4888647ewy.31 for <ftpext@ietf.org>; Tue, 23 Nov 2010 21:21:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.213.105.147 with SMTP id t19mr86160ebo.5.1290576076733; Tue, 23 Nov 2010 21:21:16 -0800 (PST)
Received: by 10.213.114.139 with HTTP; Tue, 23 Nov 2010 21:21:16 -0800 (PST)
In-Reply-To: <AANLkTi=Mm9U2ghmnNkD62AF=JZPB75fzwhUjykb2p+=0@mail.gmail.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com> <D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net> <A5FC996C3C37DC4DA5076F1046B5674C442E8816@TK5EX14MBXC127.redmond.corp.microsoft.com> <AANLkTi=Mm9U2ghmnNkD62AF=JZPB75fzwhUjykb2p+=0@mail.gmail.com>
Date: Wed, 24 Nov 2010 00:21:16 -0500
Message-ID: <AANLkTi=q1tFsjOHKZruoJF_0mjFTg8XemD6i9dOjJv6d@mail.gmail.com>
From: Damin <damin@emuxperts.net>
To: ftpext@ietf.org
Content-Type: multipart/alternative; boundary=0015174c40189c031e0495c5a847
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 24 Nov 2010 05:20:23 -0000

--0015174c40189c031e0495c5a847
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,
I knew this THMB command would be a pain as soon as a saw it.

I think the real problem we=C2=B4re having with it is that it=C2=B4s TOO ve=
rsatile. Do
we really need to let the client specify whatever option they want?
Obvious ways to abuse this would be to exec THMB PNG 100 100, then THMB PNG
100 101, THMB PNG 101,100, and so on...

Perhaps it would be better to simply limit the versatility, the server can
provide certain valid sizes, formats. (somehow...)

In the practical world, we don=C2=B4t really care that the client gets exac=
tly
the size they want! The point is to give a preview of an image. Say, we
configure a server ONLY to support 500x500 in JPG format. Such an image is
fairly small, easy to transfer, and easy to render. If need-be, the client
can (very quickly, and in their own resources) resize their image for actua=
l
view.
This is a win-win for both the client, and the server. The client gets a
speedy preview, and the server can minimise abuse.

I might also point out that there could be a big problem with this command.
How do we know the aspect ratio of the original image? We can=C2=B4t really
specify an appropriate thumb size without knowing that information (stretch=
y
images, anyone?). I think this can be solved with some appropriate commands=
.

On 23 November 2010 23:26, Robert McMurray <robmcm@microsoft.com> wrote:

> Thanks, Mark.
>
> > Mark wrote:
> >
> > That's the point of the command,
> > though.  It's to reduce the amount of
> > data that is required to travel over
> > the wire.  The idea is to shorten
> > delivery time to the client, letting
> > the client decide what is best for
> > the client, not the server.
>
> I understood that to be the case, but looking back to Anthony's original
> question - he had asked which commands were more valuable to me than othe=
rs.
> With that in mind, when I considered the THMB command from a server
> implementation point-of-view as it appears in the current draft, I though=
t
> that the current proposal was a little impractical, which would make me l=
ean
> away from implementing it.
>
> Here's a real-world scenario that illustrates why I think that the curren=
t
> THMB proposal breaks down quickly in a normal use scenario:
>
> Let's say that I have a friend who works in astrophotography, and let's s=
ay
> that he's doing his doctoral work on the Crab Nebula. He books some time =
at
> one of the national observatories and takes several series of images of t=
he
> Crab Nebula that are stitched together into 50 large composite images.
> (These have very large dimensions, 100K by 100K pixels, and each is over
> 100MB in size, which are the perfect candidates for thumbnails.) When he
> publishes his thesis for peer review, he drops the full-sized images in a
> directory on an FTP site that I manage where his colleagues can access th=
em.
> Let's say that his thesis garners a modicum of interest on the day of its
> publication for review - perhaps just 10 users. Each of these users has a=
n
> FTP client that supports the THMB command as it is currently designed, an=
d
> each FTP client can use varying thumbnail dimensions. So here's what
> happens:
>
> Client 1 has the following transaction:
>
> Client01> THMB JPG 100 100 Crab_Nebula_01.jpg
> Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
> -         //Note: 5K bytes are transferred over the data channel//
> Server00> 226 Transfer complete.
>
> Since the thumbnail was generated dynamically based on the client's input=
,
> one of my server's CPUs spikes while it loads the 100MB image into RAM,
> renders the thumbnail in the user-requested image format and dimensions, =
and
> dumps the image on the wire. (Because a client can request any image
> dimensions and format, my server implementation would probably not cache =
the
> thumbnail in memory, but I'll come back to that.) Still, transferring onl=
y
> 5K over the wire is a lot better than transferring 100MB, so we're in
> agreement that reducing the bandwidth is a good thing.
>
> But I have 9 other clients that are hitting my FTP site and they issue FT=
P
> thumbnail requests like the following examples:
>
> Client02> THMB PNG 100 100 Crab_Nebula_01.jpg
> Client03> THMB GIF 100 100 Crab_Nebula_01.jpg
> Client04> THMB JPG 200 200 Crab_Nebula_01.jpg
> Client05> THMB PNG 200 200 Crab_Nebula_01.jpg
> Client06> THMB GIF 150 150 Crab_Nebula_01.jpg
> Client07> THMB PNG 640 480 Crab_Nebula_01.jpg
> Client08> THMB GIF 320 240 Crab_Nebula_01.jpg
> Client09> THMB JPG 150 150 Crab_Nebula_01.jpg
> Client10> THMB JPG 320 240 Crab_Nebula_01.jpg
>
> So my server has received 10 completely dissimilar thumbnail requests, an=
d
> all of those requests are just for the first physical image. If each FTP
> client attempts to download just 20 thumbnails in order to show the first
> set of thumbnails in each graphical FTP client, I have to dynamically
> generate 200 different thumbnails. Since these are all 100MB images, I am
> reducing my bandwidth at the expense of the CPU and RAM resources that ar=
e
> required to process the THMB requests.
>
> I mentioned earlier that I would probably not cache the thumbnails in RAM
> because the client can request any thumbnail dimensions, so let's say tha=
t
> my server implementation at least caches thumbnails to disk so I don't ha=
ve
> to generate them dynamically for every request. Since each FTP client can
> request multiple image formats and any image dimensions, I may have to ke=
ep
> track of hundreds of thumbnails for each single physical image. That will
> quickly start to eat up disk space, so now I have to implement some form =
of
> garbage collection to clean up stale thumbnails. But even then, since my
> friend has 50 physical images and I configure my FTP server implementatio=
n
> to only keep the 10 most-recent thumbnails around, I'm still managing 500
> thumbnails for his original 50 physical images.
>
> All in all I find the approach for letting only the client have full
> control very impractical, and that would prevent me from wanting to
> implement the THMB command as it is currently documented in the draft. Bu=
t
> that being said, I like the idea of having a thumbnail command, just not =
the
> way that it's currently proposed. That's why I was suggesting some
> alternatives, and I'll expound a little on that.
>
> In my last email I had suggested letting the server be a little more in
> control, and I had suggested that the server could optionally tell an FTP
> client that the client can't specify the image format. If I use the
> astrophotography scenario that I just gave, that means that I could have =
my
> friend pre-create the 50 thumbnails for the 50 physical images in some
> fashion where the FTP server implementation would pick them up. (I could =
use
> shadow folders, unique thumbnail naming, etc.) This means that there is n=
o
> spike in CPU or RAM when the 10 FTP clients issue their THMB requests; it
> also means that I'm only managing 50 static thumbnails. So now the reques=
ts
> could be as simple as the following:
>
> Client01> THMB Crab_Nebula_01.jpg
> Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
> Server00> 226 Transfer complete.
> Client02> THMB Crab_Nebula_01.jpg
> Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
> Server00> 226 Transfer complete.
> ... etc ...
>
> The reason why I had proposed using the OPTS command was to give the clie=
nt
> the level of control that you mentioned in your reply, e.g. "letting the
> client decide what is best for the client, not the server." If you were t=
o
> combine your client request concepts with elements of my OPTS-based
> suggestion, you could create a hybrid of the two approaches that might
> address all concerns. Here are some examples:
>
> In this example, the client simply asks for the server's current thumbnai=
l
> configuration:
> C> OPTS THMB
> S> 200 JPG 100 100
>
> In this example, the client specifies a new thumbnail format:
> C> OPTS THMB PNG
> S> 200 PNG 100 100
>
> In this example, the client specifies a new thumbnail format and
> dimensions:
> C> OPTS THMB GIF 150 150
> S> 200 GIF 150 150
>
> I think that something more of a hybrid approach works better - the clien=
t
> can ask for a file format and dimensions, but the server can still say "n=
o"
> to a client-specified file format and dimensions when it wants to, but st=
ill
> return a thumbnail when the client asks for it.
>
> C> OPTS THMB PNG 100 100
> S> 504 Specifying thumbnail properties is unsupported.
>
> C> THMB widget.png
> S> 150 JPG Starting thumbnail transfer for widget.png
> S> 226 Transfer complete.
>
> This makes it easier for the server implementation to have a pre-cached
> collection of thumbnails, especially when given the realistic scenario th=
at
> I listed above. But if you omit using OPTS command and stick with using a
> single THMB command, when an FTP client sends a request that your server
> doesn't want to fulfill for some reason, your only recourse is to fail th=
e
> whole request. Whereas, if break the process into separate OPTS and THMB
> commands, you can fulfill a THMB request even if you reject the custom
> parameters that the client had requested with an OPTS command.
>
> > Mark wrote:
> >
> > This could waste server-side
> > resources, the client might not even
> > make a request for thumbnail images.
>
> This is true, but using the astrophotography scenario once again, I'd
> rather have 50 5K thumbnail files eating up a tiny fraction of disk space
> (which is a dirt cheap resource) rather than trying to generate dynamic
> thumbnails for 50 100MB images and eating CPU and RAM (which are expensiv=
e
> resources).
>
> If my server implementation didn't pre-cache thumbnails, and I configured
> my server to only allow JPG format thumbnails at 100x100 pixels, it would
> still be possible to implement some form of in-memory or dynamic to disk
> caching for subsequent requests, because now the list of variables has be=
en
> reduced. For example:
>
> Client01> THMB Crab_Nebula_01.jpg
> -        //Note: the thumbnail was not//
> -        //pre-cached, so the server  //
> -        //creates it dynamically and //
> -        //caches it to disk after it //
> -        //sends the thumbnail to the //
> -        //client                     //
> Client02> THMB Crab_Nebula_01.jpg
> -        //Note: the thumbnail was    //
> -        //cached during the previous //
> -        //request, so the server can //
> -        //send the thumbnail to the  //
> -        //client with no additional  //
> -        //processing required        //
> Client03> THMB Crab_Nebula_01.jpg
> ... etc ...
> Client10> THMB Crab_Nebula_01.jpg
>
> > Mark wrote:
> >
> > This isn't really the purpose of this
> > command.  The purpose is to take an
> > original image file and reduce it to
> > a specified size, not to return the
> > OS's icon representation for that
> > particular file type.
>
> Perhaps that was not the originally-intended purpose for this command, bu=
t
> then I think that you're limiting the usefulness of the command. My
> suggestion to return an icon may not have been the best example, but
> limiting the THMB command to just image files is not very useful, since
> there are other files that would yield beneficial results. For example,
> video files are typically much larger than images, so why shouldn't video
> files be able to have unique thumbnails? What about thumbnails for new im=
age
> types that are introduced later, like SVG files? I would say that it's
> certainly possible that any server implementation could refuse to send a
> thumbnail for any file that it chooses, but why shouldn't a server
> implementation be able to return a thumbnail for any file? I am simply
> suggesting that limiting the functionality of the THMB command to just
> images reduces the overall value of the command.
>
> All that being said, as I stated earlier, I like the idea of a THMB
> command, but at the moment I'm not fond of the current proposal. When I
> consider that implementers of FTP clients might read about the THMB comma=
nd
> in an RFC and start creating FTP clients that can issue requests for
> thumbnails in any number of image formats and pixel dimensions, I start t=
o
> back away from this command pretty quickly.
>
> I admit that it would be different if I implemented my own graphical FTP
> client and my own FTP server, because I could control the THMB
> interoperability in a way of my choosing - for example, I could define a
> specific set of thumbnail dimensions and only use JPG format. But since I
> would only be implementing an FTP server, I don't like the way the odds a=
re
> stacked. (In some ways this is like writing a function to strip whitespac=
e
> from text files - if you generate all of your own text files, then you on=
ly
> have to anticipate what you've defined as whitespace. But when you're
> stripping whitespace from someone else's text files, you have to anticipa=
te
> 0x20, 0x09, 0xA0, multiple character sets, what to do when you get charac=
ter
> codes that you don't recognize, etc.)
>
> Just the same, I'd like to see some form of thumbnail functionality if
> possible, because the scenario about astrophotography wasn't hypothetical=
 -
> I actually have a friend that works with astrophotography who generates
> those types of huge image files; having an effective method to retrieve
> thumbnails for those large images would be great. But I don't think that =
the
> current draft offers an example of an effective method when I consider
> having to create dynamically-generated thumbnails for a near-infinite num=
ber
> of possible client request parameters.
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

--0015174c40189c031e0495c5a847
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">Hi,<br>I knew this THMB command would be a pain =
as soon as a saw it.<br><br>I think the real problem we=C2=B4re having with=
 it is that it=C2=B4s TOO versatile. Do we really need to let the client sp=
ecify whatever option they want?<br>

Obvious ways to abuse this would be to exec THMB PNG 100 100, then THMB PNG=
 100 101, THMB PNG 101,100, and so on...<br><br>Perhaps it would be better =
to simply limit the versatility, the server can provide certain valid sizes=
, formats. (somehow...)<br>

<br>In the practical world, we don=C2=B4t really care that the client gets =
exactly the size they want! The point is to give a preview of an image. Say=
, we configure a server ONLY to support 500x500 in JPG format. Such an imag=
e is fairly small, easy to transfer, and easy to render. If need-be, the cl=
ient can (very quickly, and in their own resources) resize their image for =
actual view.<br>

This is a win-win for both the client, and the server. The client gets a sp=
eedy preview, and the server can minimise abuse.<br><br>I might also point =
out that there could be a big problem with this command. How do we know the=
 aspect ratio of the original image? We can=C2=B4t really specify an approp=
riate thumb size without knowing that information (stretchy images, anyone?=
). I think this can be solved with some appropriate commands.<br>
<div><div class=3D"h5">
<br><div class=3D"gmail_quote">On 23 November 2010 23:26, Robert McMurray <=
span dir=3D"ltr">&lt;<a href=3D"mailto:robmcm@microsoft.com" target=3D"_bla=
nk">robmcm@microsoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204=
, 204, 204); padding-left: 1ex;">

Thanks, Mark.<br>
<div><br>
&gt; Mark wrote:<br>
&gt;<br>
&gt; That&#39;s the point of the command,<br>
&gt; though. =C2=A0It&#39;s to reduce the amount of<br>
&gt; data that is required to travel over<br>
&gt; the wire. =C2=A0The idea is to shorten<br>
&gt; delivery time to the client, letting<br>
&gt; the client decide what is best for<br>
&gt; the client, not the server.<br>
<br>
</div>I understood that to be the case, but looking back to Anthony&#39;s o=
riginal question - he had asked which commands were more valuable to me tha=
n others. With that in mind, when I considered the THMB command from a serv=
er implementation point-of-view as it appears in the current draft, I thoug=
ht that the current proposal was a little impractical, which would make me =
lean away from implementing it.<br>


<br>
Here&#39;s a real-world scenario that illustrates why I think that the curr=
ent THMB proposal breaks down quickly in a normal use scenario:<br>
<br>
Let&#39;s say that I have a friend who works in astrophotography, and let&#=
39;s say that he&#39;s doing his doctoral work on the Crab Nebula. He books=
 some time at one of the national observatories and takes several series of=
 images of the Crab Nebula that are stitched together into 50 large composi=
te images. (These have very large dimensions, 100K by 100K pixels, and each=
 is over 100MB in size, which are the perfect candidates for thumbnails.) W=
hen he publishes his thesis for peer review, he drops the full-sized images=
 in a directory on an FTP site that I manage where his colleagues can acces=
s them. Let&#39;s say that his thesis garners a modicum of interest on the =
day of its publication for review - perhaps just 10 users. Each of these us=
ers has an FTP client that supports the THMB command as it is currently des=
igned, and each FTP client can use varying thumbnail dimensions. So here&#3=
9;s what happens:<br>


<br>
Client 1 has the following transaction:<br>
<br>
Client01&gt; THMB JPG 100 100 Crab_Nebula_01.jpg<br>
Server00&gt; 150 Starting thumbnail transfer for Crab_Nebula_01.jpg<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0 //Note: 5K bytes are transferred over the dat=
a channel//<br>
Server00&gt; 226 Transfer complete.<br>
<br>
Since the thumbnail was generated dynamically based on the client&#39;s inp=
ut, one of my server&#39;s CPUs spikes while it loads the 100MB image into =
RAM, renders the thumbnail in the user-requested image format and dimension=
s, and dumps the image on the wire. (Because a client can request any image=
 dimensions and format, my server implementation would probably not cache t=
he thumbnail in memory, but I&#39;ll come back to that.) Still, transferrin=
g only 5K over the wire is a lot better than transferring 100MB, so we&#39;=
re in agreement that reducing the bandwidth is a good thing.<br>


<br>
But I have 9 other clients that are hitting my FTP site and they issue FTP =
thumbnail requests like the following examples:<br>
<br>
Client02&gt; THMB PNG 100 100 Crab_Nebula_01.jpg<br>
Client03&gt; THMB GIF 100 100 Crab_Nebula_01.jpg<br>
Client04&gt; THMB JPG 200 200 Crab_Nebula_01.jpg<br>
Client05&gt; THMB PNG 200 200 Crab_Nebula_01.jpg<br>
Client06&gt; THMB GIF 150 150 Crab_Nebula_01.jpg<br>
Client07&gt; THMB PNG 640 480 Crab_Nebula_01.jpg<br>
Client08&gt; THMB GIF 320 240 Crab_Nebula_01.jpg<br>
Client09&gt; THMB JPG 150 150 Crab_Nebula_01.jpg<br>
Client10&gt; THMB JPG 320 240 Crab_Nebula_01.jpg<br>
<br>
So my server has received 10 completely dissimilar thumbnail requests, and =
all of those requests are just for the first physical image. If each FTP cl=
ient attempts to download just 20 thumbnails in order to show the first set=
 of thumbnails in each graphical FTP client, I have to dynamically generate=
 200 different thumbnails. Since these are all 100MB images, I am reducing =
my bandwidth at the expense of the CPU and RAM resources that are required =
to process the THMB requests.<br>


<br>
I mentioned earlier that I would probably not cache the thumbnails in RAM b=
ecause the client can request any thumbnail dimensions, so let&#39;s say th=
at my server implementation at least caches thumbnails to disk so I don&#39=
;t have to generate them dynamically for every request. Since each FTP clie=
nt can request multiple image formats and any image dimensions, I may have =
to keep track of hundreds of thumbnails for each single physical image. Tha=
t will quickly start to eat up disk space, so now I have to implement some =
form of garbage collection to clean up stale thumbnails. But even then, sin=
ce my friend has 50 physical images and I configure my FTP server implement=
ation to only keep the 10 most-recent thumbnails around, I&#39;m still mana=
ging 500 thumbnails for his original 50 physical images.<br>


<br>
All in all I find the approach for letting only the client have full contro=
l very impractical, and that would prevent me from wanting to implement the=
 THMB command as it is currently documented in the draft. But that being sa=
id, I like the idea of having a thumbnail command, just not the way that it=
&#39;s currently proposed. That&#39;s why I was suggesting some alternative=
s, and I&#39;ll expound a little on that.<br>


<br>
In my last email I had suggested letting the server be a little more in con=
trol, and I had suggested that the server could optionally tell an FTP clie=
nt that the client can&#39;t specify the image format. If I use the astroph=
otography scenario that I just gave, that means that I could have my friend=
 pre-create the 50 thumbnails for the 50 physical images in some fashion wh=
ere the FTP server implementation would pick them up. (I could use shadow f=
olders, unique thumbnail naming, etc.) This means that there is no spike in=
 CPU or RAM when the 10 FTP clients issue their THMB requests; it also mean=
s that I&#39;m only managing 50 static thumbnails. So now the requests coul=
d be as simple as the following:<br>


<br>
Client01&gt; THMB Crab_Nebula_01.jpg<br>
Server00&gt; 150 Starting thumbnail transfer for Crab_Nebula_01.jpg<br>
Server00&gt; 226 Transfer complete.<br>
Client02&gt; THMB Crab_Nebula_01.jpg<br>
Server00&gt; 150 Starting thumbnail transfer for Crab_Nebula_01.jpg<br>
Server00&gt; 226 Transfer complete.<br>
... etc ...<br>
<br>
The reason why I had proposed using the OPTS command was to give the client=
 the level of control that you mentioned in your reply, e.g. &quot;letting =
the client decide what is best for the client, not the server.&quot; If you=
 were to combine your client request concepts with elements of my OPTS-base=
d suggestion, you could create a hybrid of the two approaches that might ad=
dress all concerns. Here are some examples:<br>


<br>
In this example, the client simply asks for the server&#39;s current thumbn=
ail configuration:<br>
C&gt; OPTS THMB<br>
S&gt; 200 JPG 100 100<br>
<br>
In this example, the client specifies a new thumbnail format:<br>
C&gt; OPTS THMB PNG<br>
S&gt; 200 PNG 100 100<br>
<br>
In this example, the client specifies a new thumbnail format and dimensions=
:<br>
C&gt; OPTS THMB GIF 150 150<br>
S&gt; 200 GIF 150 150<br>
<br>
I think that something more of a hybrid approach works better - the client =
can ask for a file format and dimensions, but the server can still say &quo=
t;no&quot; to a client-specified file format and dimensions when it wants t=
o, but still return a thumbnail when the client asks for it.<br>


<br>
C&gt; OPTS THMB PNG 100 100<br>
S&gt; 504 Specifying thumbnail properties is unsupported.<br>
<br>
C&gt; THMB widget.png<br>
S&gt; 150 JPG Starting thumbnail transfer for widget.png<br>
S&gt; 226 Transfer complete.<br>
<br>
This makes it easier for the server implementation to have a pre-cached col=
lection of thumbnails, especially when given the realistic scenario that I =
listed above. But if you omit using OPTS command and stick with using a sin=
gle THMB command, when an FTP client sends a request that your server doesn=
&#39;t want to fulfill for some reason, your only recourse is to fail the w=
hole request. Whereas, if break the process into separate OPTS and THMB com=
mands, you can fulfill a THMB request even if you reject the custom paramet=
ers that the client had requested with an OPTS command.<br>


<div><br>
&gt; Mark wrote:<br>
&gt;<br>
&gt; This could waste server-side<br>
&gt; resources, the client might not even<br>
&gt; make a request for thumbnail images.<br>
<br>
</div>This is true, but using the astrophotography scenario once again, I&#=
39;d rather have 50 5K thumbnail files eating up a tiny fraction of disk sp=
ace (which is a dirt cheap resource) rather than trying to generate dynamic=
 thumbnails for 50 100MB images and eating CPU and RAM (which are expensive=
 resources).<br>


<br>
If my server implementation didn&#39;t pre-cache thumbnails, and I configur=
ed my server to only allow JPG format thumbnails at 100x100 pixels, it woul=
d still be possible to implement some form of in-memory or dynamic to disk =
caching for subsequent requests, because now the list of variables has been=
 reduced. For example:<br>


<br>
Client01&gt; THMB Crab_Nebula_01.jpg<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//Note: the thumbnail was not//<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//pre-cached, so the server =C2=A0//<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//creates it dynamically and //<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//caches it to disk after it //<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//sends the thumbnail to the //<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//client =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 //<br>
Client02&gt; THMB Crab_Nebula_01.jpg<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//Note: the thumbnail was =C2=A0 =C2=A0//<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//cached during the previous //<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//request, so the server can //<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//send the thumbnail to the =C2=A0//<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//client with no additional =C2=A0//<br>
- =C2=A0 =C2=A0 =C2=A0 =C2=A0//processing required =C2=A0 =C2=A0 =C2=A0 =C2=
=A0//<br>
Client03&gt; THMB Crab_Nebula_01.jpg<br>
... etc ...<br>
Client10&gt; THMB Crab_Nebula_01.jpg<br>
<div><br>
&gt; Mark wrote:<br>
&gt;<br>
&gt; This isn&#39;t really the purpose of this<br>
&gt; command. =C2=A0The purpose is to take an<br>
&gt; original image file and reduce it to<br>
&gt; a specified size, not to return the<br>
&gt; OS&#39;s icon representation for that<br>
</div>&gt; particular file type.<br>
<br>
Perhaps that was not the originally-intended purpose for this command, but =
then I think that you&#39;re limiting the usefulness of the command. My sug=
gestion to return an icon may not have been the best example, but limiting =
the THMB command to just image files is not very useful, since there are ot=
her files that would yield beneficial results. For example, video files are=
 typically much larger than images, so why shouldn&#39;t video files be abl=
e to have unique thumbnails? What about thumbnails for new image types that=
 are introduced later, like SVG files? I would say that it&#39;s certainly =
possible that any server implementation could refuse to send a thumbnail fo=
r any file that it chooses, but why shouldn&#39;t a server implementation b=
e able to return a thumbnail for any file? I am simply suggesting that limi=
ting the functionality of the THMB command to just images reduces the overa=
ll value of the command.<br>


<br>
All that being said, as I stated earlier, I like the idea of a THMB command=
, but at the moment I&#39;m not fond of the current proposal. When I consid=
er that implementers of FTP clients might read about the THMB command in an=
 RFC and start creating FTP clients that can issue requests for thumbnails =
in any number of image formats and pixel dimensions, I start to back away f=
rom this command pretty quickly.<br>


<br>
I admit that it would be different if I implemented my own graphical FTP cl=
ient and my own FTP server, because I could control the THMB interoperabili=
ty in a way of my choosing - for example, I could define a specific set of =
thumbnail dimensions and only use JPG format. But since I would only be imp=
lementing an FTP server, I don&#39;t like the way the odds are stacked. (In=
 some ways this is like writing a function to strip whitespace from text fi=
les - if you generate all of your own text files, then you only have to ant=
icipate what you&#39;ve defined as whitespace. But when you&#39;re strippin=
g whitespace from someone else&#39;s text files, you have to anticipate 0x2=
0, 0x09, 0xA0, multiple character sets, what to do when you get character c=
odes that you don&#39;t recognize, etc.)<br>


<br>
Just the same, I&#39;d like to see some form of thumbnail functionality if =
possible, because the scenario about astrophotography wasn&#39;t hypothetic=
al - I actually have a friend that works with astrophotography who generate=
s those types of huge image files; having an effective method to retrieve t=
humbnails for those large images would be great. But I don&#39;t think that=
 the current draft offers an example of an effective method when I consider=
 having to create dynamically-generated thumbnails for a near-infinite numb=
er of possible client request parameters.<br>


<div><div></div><div><br>
Thanks again!<br>
<br>
Robert McMurray<br>
<a href=3D"mailto:robmcm@microsoft.com" target=3D"_blank">robmcm@microsoft.=
com</a><br>
_______________________________________________<br>
ftpext mailing list<br>
<a href=3D"mailto:ftpext@ietf.org" target=3D"_blank">ftpext@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/ftpext" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/ftpext</a><br>
</div></div></blockquote></div><br>
</div></div></div><br>

--0015174c40189c031e0495c5a847--

From anthonybryan@gmail.com  Tue Nov 23 23:21:14 2010
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 752BE3A68D3 for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 23:21:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level: 
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[AWL=-0.198, 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 ngC09ytWL8Hn for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 23:21:13 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 000503A68DE for <ftpext@ietf.org>; Tue, 23 Nov 2010 23:21:12 -0800 (PST)
Received: by iwn40 with SMTP id 40so10991231iwn.31 for <ftpext@ietf.org>; Tue, 23 Nov 2010 23:22:11 -0800 (PST)
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:content-type :content-transfer-encoding; bh=vlp2UyU7NTiMkwJ/7SO87pgSaSuvNHwht49PJd2TKNQ=; b=i+q4vx/rt8Y2470HBayw8LfmOgjUgNXlbXQD6lixA3cWKPJRsbEah7kv4wnq+BbsDI FkihgFdMC0b8vtJxH/4/MXgV0L5DnA0u8R5sLJ1QTXRA8I8M555Iq6MSyDJL49fc4aeJ L3cieMv/HmD1L9yJ/XO1nutgBrMhbRIpzuzLg=
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 :content-type:content-transfer-encoding; b=ixDgkaMWvZyk3Ez73Cm7Qp/Ym5yh5I6ZAPw5V/XXgFBTSl5Pp9jGAKSSKvniIzVX7d 01lrhKNt2M4HsrKZBc1tFF+nRmpv3+LCCrVRWjXM2gk9Y6egkgopdEgWOhH5+L+O9R0N 1VfgEMxpZiKFV/BY7JUiYjbx7r/NNSlMMw+Mo=
MIME-Version: 1.0
Received: by 10.231.168.70 with SMTP id t6mr9266129iby.145.1290583331301; Tue, 23 Nov 2010 23:22:11 -0800 (PST)
Received: by 10.231.16.196 with HTTP; Tue, 23 Nov 2010 23:22:11 -0800 (PST)
In-Reply-To: <AANLkTi=kP7j1Q4JmWSeG-qsuCwGdWoAAGbujbpCjOERE@mail.gmail.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C3D2B58B3@TK5EX14MBXC127.redmond.corp.microsoft.com> <AANLkTikG8XVKQ7pLq+bcGhAk=UrJiS05vbkib7jQde_Y@mail.gmail.com> <AANLkTi=kP7j1Q4JmWSeG-qsuCwGdWoAAGbujbpCjOERE@mail.gmail.com>
Date: Wed, 24 Nov 2010 02:22:11 -0500
Message-ID: <AANLkTik+_gyQ1-DQp67NVQ94ndSFEx-AQk=gdyTYkbWp@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Wed, 24 Nov 2010 07:21:14 -0000

On Wed, Nov 3, 2010 at 8:28 PM, Anthony Bryan <anthonybryan@gmail.com> wrot=
e:
> On Thu, Sep 16, 2010 at 1:28 AM, Anthony Bryan <anthonybryan@gmail.com> w=
rote:
>> On Fri, Aug 20, 2010 at 6:01 PM, Robert McMurray <robmcm@microsoft.com> =
wrote:
>>> With that in mind, I've been thinking through implementation scenarios =
in the wake of the denial-of-service discussion that took place before IETF=
 78. More specifically, I've thinking about a scenario where the maximum fi=
le size could be configured at the server, so HASH commands could be preven=
ted from stealing too many server resources when larger files are involved.=
 This is purely a server implementation detail that has nothing to do with =
the draft with the exception of considering which reply code to return.
>>>
>>> Looking at section "3.4. HASH Command Errors" in the draft it would see=
m that none of the 5yz errors that are listed would apply, but returning a =
504 reply might seem to make sense in this scenario. If so, would it be wor=
thwhile to add a statement like the following to the draft?
>>>
>>> =A0 The server-PI SHOULD reply with a 504 reply if the HASH command is
>>> =A0 used on a file that cannot be processed for policy reasons. (For
>>> =A0 example, the file size exceeds the server's hashing policy.)
>>>
>>> Or would a 4yz reply be better since this is a configurable option at t=
he server? Perhaps a 452 reply?
>>
>> revisiting this, Mathias Berchtold is an implementer (ProFTPD module
>> mod_digest, http://www.smartftp.com/oss/proftpd/mod_digest.html ) of
>> the alternate non-standard commands (XCRC, XMD5, XSHA1, SHA256) that
>> HASH is trying to standardize.
>>
>> mod_digest uses 550 reply code for the case that Robert mentioned of a
>> file not being allowed to be hashed because of a policy.
>>
>> "The DigestMaxSize directive configures the maximum number of bytes a
>> single hash command is allowed to read from a file. If the number of
>> bytes to be read from the file is greater than the configured limit
>> the server will return an error. If no DigestMaxSize directive is
>> configured, then there is no limit. It is stronly recommended to set
>> an upper limit."
>>
>> R_550, "%s: Length (%zu) greater than " CONFIG_DIGEST_MAXSIZE " (%zu)
>> config value", cmd->arg, lLength, lMaxSize);
>>
>> Mathias, any suggestions as an implementer?
>>
>> we use 550 already for file not found.
>>
>> =A0 =A0 =A0550 Requested action not taken.
>> =A0 =A0 =A0 =A0 =A0File unavailable (e.g., file not found, no access).
>>
>> we don't seem to have a specific reply code that fits this case currentl=
y.
>> should we mint a new reply code (55z since it's permanent & deals with
>> file system) or use another existing code that isn't an exact fit?
>
> the newest HASH draft uses a new code: 556.
>
> http://tools.ietf.org/html/draft-bryan-ftp-hash
>
> comments? here's the new text.
>
> =A0 =A0 =A0 =A0 =A0 The server-PI SHOULD reply with a 556 reply if the HA=
SH command is
> =A0 =A0 =A0 =A0 =A0 used on a file that cannot be processed for policy re=
asons. =A0(For
> =A0 =A0 =A0 =A0 =A0 example, if the file size exceeds the server's hashin=
g policy.)
>
> later:
>
> =A0 =A0 =A0 =A0 =A0 Server operators might wish to allow the HASH command=
 but restrict
> =A0 =A0 =A0 =A0 =A0 its use to certain files, for example, if the file si=
ze exceeds the
> =A0 =A0 =A0 =A0 =A0 server's hashing policy. =A0A client MUST be able to =
understand that
> =A0 =A0 =A0 =A0 =A0 refusal to process HASH commands may be permanent (if=
 indicated by a
> =A0 =A0 =A0 =A0 =A0 556 response) and will not be honoured later.

now that we have a few more people here, if you could go over this
draft before it becomes draft-ietf-ftpext2-hash...

any comments on using this new 556 code?

http://tools.ietf.org/html/draft-bryan-ftp-hash

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

From anthonybryan@gmail.com  Tue Nov 23 23:37:50 2010
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 EB39C3A695C for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 23:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.78
X-Spam-Level: 
X-Spam-Status: No, score=-2.78 tagged_above=-999 required=5 tests=[AWL=-0.181,  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 Dytd4u4qT-bm for <ftpext@core3.amsl.com>; Tue, 23 Nov 2010 23:37:49 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 9B2D43A68D3 for <ftpext@ietf.org>; Tue, 23 Nov 2010 23:37:49 -0800 (PST)
Received: by eyd10 with SMTP id 10so5306453eyd.31 for <ftpext@ietf.org>; Tue, 23 Nov 2010 23:38:47 -0800 (PST)
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=uKCoHwLMyydTDX+xQHmX4UHqEkfewIFj89V6+DxZkAk=; b=sgFJKcX+SjVkbaRZyoHfWoELaHrl4FpSSHiKF0PWr2AIazNa4AlAH0wIKUZe/rZcCk Ij0QR4knh6xUfStRUw6cfhnsxQ+WJqipRg8LDnZ2FylqFp6GLwsl3evD3EXQL1OjxFdi gyxV3V9IXUpGY+de0smBBmKPaXWQxh6hXF+00=
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=j8oPGcq+C2w8AstZlGx88ZP2aX9qwZcafvO9Sv8m4LCJM89opmgZAOyzFNRxidpxUj KefzwOCzEZ9lALDWCMUywA18I4p3Xqtx+tJkZX1acVSm6jpPdPt+DIZLrUkyjWWKfZRB uwdHkdf/aUht0vWm1S21MyGc7yV9sdVS7lW9U=
MIME-Version: 1.0
Received: by 10.213.34.131 with SMTP id l3mr2817224ebd.63.1290584327083; Tue, 23 Nov 2010 23:38:47 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Tue, 23 Nov 2010 23:38:47 -0800 (PST)
In-Reply-To: <4CEC5480.8040801@att.com>
References: <20101123184835.AFC433A69A1@core3.amsl.com> <AANLkTinYUc1G-syqicN31Rc+yV6UvKurB-O1nQba2Y9=@mail.gmail.com> <4CEC5480.8040801@att.com>
Date: Wed, 24 Nov 2010 02:38:47 -0500
Message-ID: <AANLkTi=hOFDdV5p8YomDmOcQH=jfFC1qt0pHhgR8LYae@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Tony Hansen <tony@att.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] WG Action: FTP Extensions, 2nd edition (ftpext2)
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, 24 Nov 2010 07:37:51 -0000

On Tue, Nov 23, 2010 at 6:55 PM, Tony Hansen <tony@att.com> wrote:
> On 11/23/2010 4:17 PM, Anthony Bryan wrote:
>>
>> so, wow, looks like things are rolling along! :)
>>
>> as you can see, our WG got approved last Thursday.
>>
>> I'm very happy to see comments on
>> draft-peterson-streamlined-ftp-command-extensions still coming in.
>> please chime in if you haven't already.
>>
>> I'm new to this, so I wonder what the first order of business is?
>>
>> here are some ideas:
>>
>> 1) we have 4 drafts on the charter, 3 of which are "active" (John
>> hasn't updated draft-klensin-ftp-typeu yet). once these are submitted
>> with the string '-ftpext2-' in the
>> draft name, they will show up at http://tools.ietf.org/wg/ftpext2/
>>
>> I think our ID draft-bryan-ftp-hash becomes ietf-ftpext2-hash then? (&
>> the others follow in a similar fashion).
>
> When the next update is ready for each draft, each author should upload t=
he
> draft under the WG name. Bryan's naming suggestion is apropos:
>
> draft-bryan-ftp-hash =3D> draft-ietf-ftpext2-hash
> draft-hethmon-mcmurray-ftp-hosts =3D> draft-ietf-ftpext2-hosts
> draft-klensin-ftp-typeu =3D> draft-ietf-ftpext2-typeu

thanks, Tony.

I saw that the websocket draft, when converting from an individual's
to a WG draft, had no changes.
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-thewebsocketprotocol-0=
0.txt

is that how most people do it, or do we wait for substantive changes?

there is also
draft-liu-ftp64-extension =3D> draft-ietf-ftpext2-ftp64 ?

which after discussion during the charter, should be changed to
"Intended status: Standards Track"

>> should this be done now? we should change the WG at the top of our
>> drafts I guess. how is this done in xml2rfc? is there anything else
>> that needs to be changed?
>
> This is optional: it is done by using the <workgroup> element in the <fro=
nt>
> matter.

ahh, I'd been wondering!

I've changed it. we all might as well...now that we've got the WG,
time to flaunt it. :)
--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads

From prvs=1944f83767=mpp@rhinosoft.com  Wed Nov 24 04:52:41 2010
Return-Path: <prvs=1944f83767=mpp@rhinosoft.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 04CBD28C1C4 for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 04:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6]
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 W6BWXsAnHblW for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 04:52:37 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id E3E8E28C1FB for <ftpext@ietf.org>; Wed, 24 Nov 2010 04:52:36 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009936356.msg for <ftpext@ietf.org>; Wed, 24 Nov 2010 06:53:35 -0600
X-Spam-Processed: rhinosoft.com, Wed, 24 Nov 2010 06:53:35 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=1944f83767=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <4FDCE18C80754DF38C2042D7A588E806@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "Paul Ford-Hutchinson" <paulfordh@uk.ibm.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com><D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net><AANLkTi=D8QLkyUxgXt3h+N2nM3qgpKTBDVXLe5-6BM7q@mail.gmail.com><914CA95DAC22422C825C665E4E76F860@rhinooffice.net><Pine.LNX.4.64.1011230851130.6921@iskra.ottix.net> <6C3AA348BF6146F2885B2094B8E8E29C@rhinooffice.net> <OF8C6635BE.33D2510D-ON802577E4.0051C5FE-802577E4.0053A63D@uk.ibm.com> <1145F0D0D8974C2A8DB587DD6F4E72C8@rhinooffice.net> <OFECAD328D.14EBDD49-ON802577E4.007A3769-802577E4.007C3599@uk.ibm.com>
In-Reply-To: <OFECAD328D.14EBDD49-ON802577E4.007A3769-802577E4.007C3599@uk.ibm.com>
Date: Wed, 24 Nov 2010 06:53:32 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BF_01CB8BA4.4EAA6B80"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 24 Nov 2010 12:52:41 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00BF_01CB8BA4.4EAA6B80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Paul,

Thank you for providing your thoughts on CSID.  In response to your =
comments I would like to say that CSID is designed to do nothing more =
than provide information about the server software, version, vendor, and =
platform; and for the client the server software, version, and vendor.  =
The information provided by both sides should not change regardless of =
whether or not a user is logged in, into any particular domain or host.  =
It can be extended if needed, however the idea behind it is that it =
returns these constant values simply used to help identify both sides of =
the connection.

Do you think this needs to be clarified?  If so, where and what verbiage =
would you like to see?

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628 =20



From: Paul Ford-Hutchinson=20
Sent: Tuesday, November 23, 2010 4:40 PM
To: Mark P. Peterson=20
Cc: ftpext@ietf.org=20
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions



I understand that HOST is designed to do the job, but extensible =
crannies in protocols tend to get used for all sorts of things they =
aren't intended for.=20

In fact, it wouldn't surprise me if the review process ends up kicking =
the 'extensible' bits of this command into the long grass.  (i.e. the =
argument that it's actually creating interoperability issues rather than =
preventing them - if there's a need for a value - it should be defined =
syntactically and semantically - otherwise it doesn't belong in a =
protocol spec.)=20

I suggest that there should be some discussion about what kind of =
information is valid in the CSID command/response and when a =
client/server might expect it to alter (or not).  And if it turns out it =
is tied to a "session" - point out that a "session" can mean a number of =
things in FTP, so that will need to be specified too.=20

Cheers,=20
Paul=20
--=20

Paul Ford-Hutchinson CISSP - Tivoli Security Consultant
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU
IBM Certified Deployment Professional - Tivoli Compliance Insight =
Manager V8.5

Tel +44 (0)7500 078379  (internal: 37269105)=20


      From:  "Mark P. Peterson" <mpp@rhinosoft.com> =20
      To:  <ftpext@ietf.org>, Paul Ford-Hutchinson/UK/IBM@IBMGB =20
      Date:  23/11/2010 19:55 =20
      Subject:  Re: [ftpext] =
draft-peterson-streamlined-ftp-command-extensions=20


-------------------------------------------------------------------------=
-------



Hi Paul,=20
 =20
Thank you for taking the time to respond.=20
 =20
Point 1=20
=3D=3D=3D=3D=3D=3D=20
I agree with your points.  I will clarify the document.=20
 =20
Point 2=20
=3D=3D=3D=3D=3D=3D=20
CSID doesn't contain any host specific information, the intent is only =
to exchange information about the software between server and client.  =
As for HOST this is being proposed in a different draft for FTP.  I =
believe the information passed between the client and server should only =
apply to the actual software and platform and is independent from the =
login information.  In other words it should always return the same =
information.=20

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628  =20

From: Paul Ford-Hutchinson=20
Sent: Tuesday, November 23, 2010 9:16 AM=20
To: Mark P. Peterson ; ftpext@ietf.org=20
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions=20


Two comments about the CSID before login question:=20

1) RFCs define protocols not implementations, so the discussion should =
be about what _can_ happen and how a client/server should respond.=20
2) I'd like to be 100% certain what payload CSID can carry before =
banning it totally prior to authentication.=20


Point 1 (the protocol vs implementation thing)=20
=3D=3D=3D=3D=3D=3D=20

We need to say what is and isn't allowed in the protocol, comments about =
implementations are interesting but not really the thrust of an RFC.  In =
this case, we need to state when a client may send CSID; what a server =
should do if the client sends it at the wrong time - and at the right =
time; whether the client should expect that a server might refuse to =
answer a CSID command because it is in a particular state and that it =
might be sensible for it to try again when in a different state in the =
protocol (e.g. logged in).=20

Also, don't forget that users can log out too - so simply stating after =
a USER command (or some such) isn't really good enough.=20

Point 2=20
=3D=3D=3D=3D=3D=3D=20

HTTPS is broken because of something similar.  Multi-homed http servers =
cannot operate on HTTPS because the server needs to present the cert to =
the client before the client tells the server which certificate (i.e. =
host) it should be.=20

I don't know if CSID may contain host specific info  (ext_cfactname and =
local_fact seem to be a bit of a catch all that might get used for =
"hostname" or some such.) but be very wary of this catching people out.  =
At the very least, if CSID should not be used for host identification, =
then ban such values from being in these fields.=20



Perhaps CSID could be permitted to pass different information depending =
on the state of the user's session.  (which brings us back to the =
protocol vs implementation issue - should CSID always pass the same =
information regardless of session state or is the peer allowed to use =
session context to decide what to include - thus meaning that two calls =
to CSID might be allowed to pass different values. In fact - is a client =
allowed to send multiple CSID commands and what should a server do if =
the information passed in the second command does not match that from =
the first (and does REIN need to be involved?)?)=20

Cheers,=20
Paul=20

--=20

Paul Ford-Hutchinson CISSP - Tivoli Security Consultant
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU
IBM Certified Deployment Professional - Tivoli Compliance Insight =
Manager V8.5

Tel +44 (0)7500 078379  (internal: 37269105)=20

      From:  "Mark P. Peterson" <mpp@rhinosoft.com> =20
      To:  "William F. Maton" <wmaton@ottix.net> =20
      Cc:  ftpext@ietf.org =20
      Date:  23/11/2010 14:45 =20
      Subject:  Re: [ftpext] =
draft-peterson-streamlined-ftp-command-extensions =20
      Sent by:  ftpext-bounces@ietf.org=20



-------------------------------------------------------------------------=
-------



Hi William,

Thank you for taking the time to respond.  I cannot think
of any real reason why CSID shouldn't only be allowed after login.
I will change the document to reflect this.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "William F. Maton" <wmaton@ottix.net>
Sent: Tuesday, November 23, 2010 7:55 AM
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: "Damin" <damin@emuxperts.net>; <ftpext@ietf.org>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions

On Tue, 23 Nov 2010, Mark P. Peterson wrote:

> Hi All,
>
> Is there anyone else that agrees with Damin about CSID?  He says it =
SHOULD be available only after login.

Hi Mark,
I'm certainly and old enough salt at systems administration to
think that identification before authentication or authorization is not =
a
good thing.  It makes it easier for the scanners to pick-off what =
servers
are running.  I'd like to force them into making the extra effort, since
it might as well cost them more work and I can monitor the activity
better.

I think standardizing CSID (from the old non-standard CLNT) is a
good thing though.  It should be left up to the implementor to support =
it.

I've also read he rest of that I-D and have more thoughts on it,
but that's for another email.


> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
>
> From: Damin
> Sent: Monday, November 22, 2010 10:17 PM
> To: ftpext@ietf.org
> Subject: Re: [ftpext] =
draft-peterson-streamlined-ftp-command-extensions
>
>
> Hi,
>
>
> On 22 November 2010 19:32, Mark P. Peterson <mpp@rhinosoft.com> wrote:
>
> Hi Robert,
>
> Thank you for taking the time to review the commands.  If you don't =
mind I would
> like to respond to your comments:
>
> CSID:
>
>> For security reasons I would probably want the CSID exchange to occur =
AFTER the client has logged in, but I might be=20
>> overreacting.
>
>
> There is a lot of discussion on the Internet about servers providing =
"too" much information, especially prior to login.  But=20
> having
> worked on both sides of the FTP process, it's usually very easy for =
the client to identify what brand or flavor the server is.
> There are details which usually identify the server such as the =
completeness of the FEAT response, the welcome message, responses=20
> to
> certain messages, etc.  So, I think it's okay to be available prior to =
login.  I could change the document to read that it should=20
> be
> up to the server's implementation whether or not it's available.
>
> I prefer to edge on the side of caution. I don=B4t see any good reason =
that this SHOULD be available before login. Commands=20
> available
> prior to login should be as limited as possible.
>
>
> RMDA:
>
>> In a server implementation I would probably make this command =
configurable, so administrators would have an option to disable the
>> feature.  In which case I would probably hide the command from a FEAT =
response so it would not be discoverable and have the=20
>> server
>> return a 500 or 502 reply when RMDA is sent by the client and =
disabled at the server.
>
>
> I don't think my document specifies that it isn't configurable.  My =
implementation in Serv-U is configurable as is almost all=20
> other
> FTP commands.  I think this can be left up to the server =
implementation.  Your possible implementation is exactly how Serv-U
> implements it.  If the feature is disabled, it doesn't appear in the =
FEAT response, nor is it available through the HELP command.
>
>
> AVBL:
>> ...
>
> Your comments address the reason for its existence.  The client-side =
implementation in SmartFTP uses the command in this manner.
>
> DSIZ:
>> This could certainly be useful, although I would probably want a user =
to be logged in...
>
> Any information about paths or files requires login in FTP.  I am sure =
this is the case here as well.  If a server wouldn't want=20
> the
> "anonymous" user to have access to this command it could be configured =
to disallow this command at the server's implementation or
> configuration.  This should be left up to the implementation of the =
server or administrator of the server.
>
>> I'd probably make it configurable so as not to tie up too many server =
resources for large directory structures;...
>
> Agreed, the time-consuming nature of the implementation is discussed =
but configuration by an administrator or=20
> server-implementation
> is not.   Do you think such verbiage is required?
>
>
> THMB:
>
>> I'm not a big fan of computing the thumbnail dynamically, nor am I =
fond of allowing the client to specify the thumbnail format=20
>> and
>> size.
>
>
> That's the point of the command, though.  It's to reduce the amount of =
data that is required to travel over the wire.  The idea is
> to shorten delivery time to the client, letting the client decide what =
is best for the client, not the server.  Some clients may
> want very small images, say for a Windows Explorer style listing, =
others may want larger images (640x480 for example) to show a
> slide show.  I think the client needs to make that determination.  If =
the server decides to cache these generated images it can.
>
>
>> I think that it would be better if the server could pre-cache =
thumbnails for any file type in a server-determined size and image
>> format, and then return the binary data and image format information =
to the client.
>
>
> This could waste server-side resources, the client might not even make =
a request for thumbnail images.
>
>
>> For example, most graphically-based operating systems have some =
method for displaying file icons to a user that is seated at a
>> computer terminal, so an FTP server implementation could simply =
return that same icon to a client in response to a THMB request.
>
>
> Right, but this isn't really the purpose of this command.  The purpose =
is to take an original image file and reduce it to a
> specified size, not to return the OS's icon representation for that =
particular file type (i.e., not SHGetFileInfo() in Windows).
>
> My proposed implementation is fairly straightforward.  If supported =
the FEAT command replies with THMB and the supported file=20
> types.
> When the client wants a thumbnail it asks for it with a single =
command.  Here is a sample result from FTP Voyager and Serv-U:
>
> PORT 192,168,0,30,199,53
> 200 PORT command successful.
> THMB PNG 98 88 Thomas.JPG
> 150 Opening thumbnail image transfer BINARY mode data connection =
(19738 Bytes) for Thomas.JPG.
> 226 Transfer complete. 19,738 bytes (19,756 compressed to 100.09%) =
transferred. 19.29 actual KB/sec,  19.28 effective KB/sec.
>
> The client opens a data channel just like any other file transfer, =
then requests the file using THMB, followed by the output type,
> width, height, and the file name.  The server responds just like a =
file transfer but also includes the resulting size in
> parentheses.
>
> While designing this command the idea was to first make it simple for =
both sides, second to make it operate as any other download,
> and third to make it as flexible as possible, allowing the client to =
decide how the resulting data is to be used and what is=20
> needed.
> Of course the server could be configured in any way needed.  For =
example if the server wanted to limit the size of the thumbnails,
> the server could do that.  Our implementation limits the number of =
simultaneous threads allowed to create the thumbnails at any
> given time.  I think these details need to be left to the server =
implementation.
>
> As for using an OPT command to configure an upcoming THMB command for =
its image type and the thumbnail size, that seems to
> complicate the command.  It's very easy to add these parameters into a =
single command, eliminating the required handshaking=20
> between
> the client and server.  An added benefit is that neither the client =
nor the server are required to maintain these "options"
> throughout a session, rather all of the information required is sent =
in a single command.
>
> If you're interested in seeing it in action, download Serv-U and FTP =
Voyager or SmartFTP.  Login to the server, switch FTP Voyager
> to "Thumbnails" view.  With SmartFTP simply select an image file and a =
thumbnail image, of dynamic size, will appear in the=20
> preview
> pane.
>
>
> Thank you again for taking the time to provide your feedback.  I look =
forward to your comments to the above.
>
> Mark P. Peterson - President
> http://www.RhinoSoft.com
> Voice: +1(262) 560-9627
> FAX: +1(262) 560-9628
>
>
> --------------------------------------------------
> From: "Robert McMurray" <robmcm@microsoft.com>
> Sent: Monday, November 22, 2010 5:01 PM
> To: <ftpext@ietf.org>; "'Anthony Bryan'" <anthonybryan@gmail.com>; =
<mark.peterson@rhinosoft.com>
> Subject: [ftpext] draft-peterson-streamlined-ftp-command-extensions
>
>
> [Note: Renaming the thread from 'Submitting new drafts'.]
>
>> Anthony Bryan wrote:
>>
>> I don't mean to single you out, but
>> you showed interest in an CSID/AGNT
>> command. Do you have any opinion on
>> the other 4 commands in the draft?
>
> Thanks, Anthony.
>
> No worries - I meant to send a better response in the wake of my =
withdrawn AGNT draft and Mark's current Streamlined FTP Command
> Extensions draft, but I had been remiss at taking the time to collect =
my thoughts in a more meaningful way. But since you asked,
> this seems like as good at time as any. ;-]
>
> CSID - As evidenced by my short-lived AGNT proposal, I think it's very =
useful to have some sort of client/server discovery=20
> command.
> FEAT does a good job of advertising the list of commands that are =
supported by a server, but Mark's proposed CSID command sequence
> provides a much better way for servers and client to identify their =
features to each other in detail. For security reasons I would
> probably want the CSID exchange to occur AFTER the client has logged =
in, but I might be overreacting.
>
> RMDA - This could be a very useful command, and it would parallel the =
functionality that I'm sure we all typically use in a native
> operating system environment. In a server implementation I would =
probably make this command configurable, so administrators would
> have an option to disable the feature. In which case I would probably =
hide the command from a FEAT response so it would not be
> discoverable and have the server return a 500 or 502 reply when RMDA =
is sent by the client and disabled at the server.
>
> (Note: I mention my thoughts about server implementation details just =
to open up the discussion as to whether any implementation
> details should be called out in the draft, or if we should leave that =
up to the implementers to decide.)
>
> AVBL - This command could be very useful in a client/server world; our =
FTP server implementation currently returns the available
> size after a successful login sequence, and the available size is =
based on server disk quotas and such. That being said, not every
> FTP client will bubble that information up to the user interface. =
Having an AVBL command would make it possible for a client to
> determine whether enough storage space is available at the server =
BEFORE sending a file, which would be great when you're about to
> send a 10GB file and you only have 9.99GB of storage space left. ;-]
>
> DSIZ - This could certainly be useful, although I would probably want =
a user to be logged in (not anonymous) before I supported=20
> this
> command in order to reduce the risk of denial-of-service. I'd probably =
make it configurable so as not to tie up too many server
> resources for large directory structures; and once again, if the =
feature were disabled I would probably hide the command from a=20
> FEAT
> response so it would not be discoverable and return a 500 or 502 reply =
when DSIZ is sent by the client and disabled at the server.
>
> THMB - I have to admit, I don't work on a graphical FTP client, so =
this command is less useful to me personally, but I can see the
> merit that it might have to someone that designs a graphical client. =
That being said, I'm not a big fan of computing the thumbnail
> dynamically, nor am I fond of allowing the client to specify the =
thumbnail format and size. I think that it would be better if the
> server could pre-cache thumbnails for any file type in a =
server-determined size and image format, and then return the binary data
> and image format information to the client. For example, most =
graphically-based operating systems have some method for displaying
> file icons to a user that is seated at a computer terminal, so an FTP =
server implementation could simply return that same icon to=20
> a
> client in response to a THMB request.
>
> Please bear in mind, I haven't given a lot of thought as to what the =
client/server interchange might look like if the server were
> more in control of the response to a THMB request, but it would =
probably be sufficient to simply return the image type as part of
> the response and let the client determine the image dimensions based =
on the client's capabilities for reading the image data. (As=20
> a
> server guy I like to push any client-friendly processing on the client =
whenever possible. ;-]) You could borrow an idea from the
> HASH discussion that we've been having and make the thumbnail image =
type configurable for the client by using an OPTS command,=20
> which
> might look like the following examples.
>
> In this first example, the server has a pre-configured thumbnail image =
type of JPG, and may have pre-cached the thumbnails for
> files; any THMB request with no OPTS specified would use the server's =
pre-configured thumbnail image type of JPG and image type is
> specified in the command channel response:
>
> C> THMB widget.png
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.png
> S> 226 Transfer complete.
>
> In these next examples a client is asking for different thumbnail =
image types by using OPTS commands, and the thumbnail image=20
> types
> would still be specified in the command channel responses:
>
> C> OPTS THMB GIF
> S> 200 OPTS THMB GIF command successful.
>
> C> THMB widget.psp
> S> 150 GIF Starting thumbnail transfer (1234 Bytes) for widget.psp
> S> 226 Transfer complete.
>
> C> OPTS THMB PNG
> S> 200 OPTS THMB PNG command successful.
>
> C> THMB widget.doc
> S> 150 PNG Starting thumbnail transfer (1234 Bytes) for widget.doc
> S> 226 Transfer complete.
>
> In this next example a client is asking for an unsupported image type, =
so the server would simply return the appropriate error
> reply:
>
> C> OPTS THMB FOO
> S> 501 Unsupported thumbnail format.
>
> In this next example a client is asking for the currently-configured =
thumbnail image type, so the server would return the
> appropriate response:
>
> C> OPTS THMB
> S> 200 JPG
>
> You might take this one step further - the server might choose to only =
support its pre-configured thumbnail image type, thereby
> allowing pre-caching of all thumbnails in one specific image format. =
In this example a client is asking for PNG thumbnails, which
> SHOULD be a supported image type, but the server only supports a =
pre-configured thumbnail image type for JPG files and returns the
> appropriate error reply (504?) and the server's pre-configured =
thumbnail image type is specified in the subsequent command channel
> response to a THMB request:
>
> C> OPTS THMB PNG
> S> 504 Specifying thumbnail formats is unsupported.
>
> C> THMB widget.xls
> S> 150 JPG Starting thumbnail transfer (1234 Bytes) for widget.xls
> S> 226 Transfer complete.
>
> As I said earlier, I hadn't given much thought as to what the =
client/server THMB interchange might look like if you put the server
> in control instead of the client, but as a server guy I'd rather see =
THMB look a little more like the examples that I gave. ;-]
>
> Thanks again!
>
> Robert McMurray
> robmcm@microsoft.com
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
>
>
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>
>
> _______________________________________________
> ftpext mailing list
> ftpext@ietf.org
> https://www.ietf.org/mailman/listinfo/ftpext
>

wfms=20


_______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext




------=_NextPart_000_00BF_01CB8BA4.4EAA6B80
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16671"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT size=3D2>Hi Paul,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thank you for providing your thoughts on CSID.&nbsp; =
In=20
response to your comments I would like to say that CSID is designed to =
do=20
nothing more than provide information about the server software, =
version,=20
vendor, and platform; and for the client the server software, version, =
and=20
vendor.&nbsp; The information provided by both sides should not change=20
regardless of whether or not a user is logged in, into any particular =
domain or=20
host.&nbsp; It can be extended if needed, however the idea behind it is =
that it=20
returns these constant values simply used to help identify both sides of =
the=20
connection.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Do you think this needs to be clarified?&nbsp; If =
so, where=20
and what verbiage would you like to see?</FONT></DIV>
<DIV><FONT size=3D2><BR>Mark P. Peterson - President<BR><A=20
title=3D"http://www.RhinoSoft.com&#10;CTRL + Click to follow link"=20
href=3D"http://www.RhinoSoft.com">http://www.RhinoSoft.com</A><BR>Voice: =
+1(262)=20
560-9627<BR>FAX: +1(262) 560-9628&nbsp; <BR></FONT></DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A=20
title=3D"mailto:paulfordh@uk.ibm.com&#10;CTRL + Click to follow link"=20
href=3D"mailto:paulfordh@uk.ibm.com">Paul Ford-Hutchinson</A> </DIV>
<DIV><B>Sent:</B> Tuesday, November 23, 2010 4:40 PM</DIV>
<DIV><B>To:</B> <A title=3Dmpp@rhinosoft.com =
href=3D"mailto:mpp@rhinosoft.com">Mark=20
P. Peterson</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dftpext@ietf.org=20
href=3D"mailto:ftpext@ietf.org">ftpext@ietf.org</A> </DIV>
<DIV><B>Subject:</B> Re: [ftpext]=20
draft-peterson-streamlined-ftp-command-extensions</DIV></DIV></DIV>
<DIV><BR></DIV><BR><FONT size=3D2 face=3Dsans-serif>I understand that =
HOST is=20
designed to do the job, but extensible crannies in protocols tend to get =
used=20
for all sorts of things they aren't intended for.</FONT> <BR><BR><FONT =
size=3D2=20
face=3Dsans-serif>In fact, it wouldn't surprise me if the review process =
ends up=20
kicking the 'extensible' bits of this command into the long grass. =
&nbsp;(i.e.=20
the argument that it's actually creating interoperability issues rather =
than=20
preventing them - if there's a need for a value - it should be defined=20
syntactically and semantically - otherwise it doesn't belong in a =
protocol=20
spec.)</FONT> <BR><BR><FONT size=3D2 face=3Dsans-serif>I suggest that =
there should=20
be some discussion about what kind of information is valid in the CSID=20
command/response and when a client/server might expect it to alter (or =
not).=20
&nbsp;And if it turns out it is tied to a "session" - point out that a =
"session"=20
can mean a number of things in FTP, so that will need to be specified=20
too.</FONT> <BR><BR><FONT size=3D2 face=3Dsans-serif>Cheers,</FONT> =
<BR><FONT size=3D2=20
face=3Dsans-serif>Paul</FONT> <BR><FONT size=3D2 face=3Dsans-serif>-- =
<BR><BR>Paul=20
Ford-Hutchinson CISSP - Tivoli Security Consultant<BR>IBM UK Ltd. - NHBR =
- 1PH -=20
North Harbour - Portsmouth - PO6 3AU<BR>IBM Certified Deployment =
Professional -=20
Tivoli Compliance Insight Manager V8.5<BR><BR>Tel +44 (0)7500 078379=20
&nbsp;(internal: 37269105)</FONT> <BR><BR><BR>
<TABLE width=3D"100%">
  <TBODY>
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>From:</FONT>=20
    <TD><FONT size=3D1 face=3Dsans-serif>"Mark P. Peterson"=20
      &lt;mpp@rhinosoft.com&gt;</FONT>=20
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>To:</FONT>=20
    <TD><FONT size=3D1 face=3Dsans-serif>&lt;ftpext@ietf.org&gt;, Paul=20
      Ford-Hutchinson/UK/IBM@IBMGB</FONT>=20
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>Date:</FONT>=20
    <TD><FONT size=3D1 face=3Dsans-serif>23/11/2010 19:55</FONT>=20
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>Subject:</FONT> =

    <TD><FONT size=3D1 face=3Dsans-serif>Re: [ftpext]=20
      =
draft-peterson-streamlined-ftp-command-extensions</FONT></TD></TR></TBODY=
></TABLE><BR>
<HR noShade>
<BR><BR><BR><FONT size=3D2>Hi Paul,</FONT> <BR><FONT =
size=3D3>&nbsp;</FONT>=20
<BR><FONT size=3D2>Thank you for taking the time to respond.</FONT> =
<BR><FONT=20
size=3D3>&nbsp;</FONT> <BR><FONT size=3D2>Point 1</FONT> <BR><FONT =
size=3D2=20
face=3Dsans-serif>=3D=3D=3D=3D=3D=3D</FONT><FONT size=3D3> </FONT><FONT =
size=3D2><BR>I agree with=20
your points. &nbsp;I will clarify the document.</FONT> <BR><FONT=20
size=3D3>&nbsp;</FONT> <BR><FONT size=3D2>Point 2</FONT><FONT size=3D3> =
</FONT><FONT=20
size=3D2 face=3Dsans-serif><BR>=3D=3D=3D=3D=3D=3D</FONT><FONT size=3D3> =
</FONT><FONT=20
size=3D2><BR>CSID doesn't contain any host specific information, the =
intent is=20
only to exchange information about the software between server and =
client.=20
&nbsp;As for HOST this is being proposed in a different draft for FTP. =
&nbsp;I=20
believe the information passed between the client and server should only =
apply=20
to the actual software and platform and is independent from the login=20
information. &nbsp;In other words it should always return the same=20
information.</FONT> <BR><FONT size=3D2><BR>Mark P. Peterson -=20
President</FONT><FONT color=3Dblue size=3D2><U><BR></U></FONT><A=20
href=3D"http://www.rhinosoft.com/"><FONT color=3Dblue=20
size=3D2><U>http://www.RhinoSoft.com</U></FONT></A><FONT =
size=3D2><BR>Voice: +1(262)=20
560-9627<BR>FAX: +1(262) 560-9628 &nbsp;</FONT> <BR><BR><FONT=20
size=3D3><B>From:</B> </FONT><A =
href=3D"mailto:paulfordh@uk.ibm.com"><FONT=20
color=3Dblue size=3D3><U>Paul Ford-Hutchinson</U></FONT></A><FONT =
size=3D3>=20
</FONT><BR><FONT size=3D3><B>Sent:</B> Tuesday, November 23, 2010 9:16 =
AM</FONT>=20
<BR><FONT size=3D3><B>To:</B> </FONT><A =
href=3D"mailto:mpp@rhinosoft.com"><FONT=20
color=3Dblue size=3D3><U>Mark P. Peterson</U></FONT></A><FONT size=3D3> =
; </FONT><A=20
href=3D"mailto:ftpext@ietf.org"><FONT color=3Dblue=20
size=3D3><U>ftpext@ietf.org</U></FONT></A><FONT size=3D3> =
</FONT><BR><FONT=20
size=3D3><B>Subject:</B> Re: [ftpext]=20
draft-peterson-streamlined-ftp-command-extensions</FONT> <BR><BR><FONT =
size=3D2=20
face=3Dsans-serif><BR>Two comments about the CSID before login=20
question:</FONT><FONT size=3D3> <BR></FONT><FONT size=3D2 =
face=3Dsans-serif><BR>1)=20
RFCs define protocols not implementations, so the discussion should be =
about=20
what _can_ happen and how a client/server should respond.</FONT><FONT =
size=3D3>=20
</FONT><FONT size=3D2 face=3Dsans-serif><BR>2) I'd like to be 100% =
certain what=20
payload CSID can carry before banning it totally prior to=20
authentication.</FONT><FONT size=3D3> <BR><BR></FONT><FONT size=3D2=20
face=3Dsans-serif><BR>Point 1 (the protocol vs implementation =
thing)</FONT><FONT=20
size=3D3> </FONT><FONT size=3D2 =
face=3Dsans-serif><BR>=3D=3D=3D=3D=3D=3D</FONT><FONT size=3D3>=20
<BR></FONT><FONT size=3D2 face=3Dsans-serif><BR>We need to say what is =
and isn't=20
allowed in the protocol, comments about implementations are interesting =
but not=20
really the thrust of an RFC. &nbsp;In this case, we need to state when a =
client=20
may send CSID; what a server should do if the client sends it at the =
wrong time=20
- and at the right time; whether the client should expect that a server =
might=20
refuse to answer a CSID command because it is in a particular state and =
that it=20
might be sensible for it to try again when in a different state in the =
protocol=20
(e.g. logged in).</FONT><FONT size=3D3> <BR></FONT><FONT size=3D2=20
face=3Dsans-serif><BR>Also, don't forget that users can log out too - so =
simply=20
stating after a USER command (or some such) isn't really good=20
enough.</FONT><FONT size=3D3> <BR></FONT><FONT size=3D2 =
face=3Dsans-serif><BR>Point=20
2</FONT><FONT size=3D3> </FONT><FONT size=3D2 =
face=3Dsans-serif><BR>=3D=3D=3D=3D=3D=3D</FONT><FONT=20
size=3D3> <BR></FONT><FONT size=3D2 face=3Dsans-serif><BR>HTTPS is =
broken because of=20
something similar. &nbsp;Multi-homed http servers cannot operate on =
HTTPS=20
because the server needs to present the cert to the client before the =
client=20
tells the server which certificate (i.e. host) it should be.</FONT><FONT =
size=3D3>=20
<BR></FONT><FONT size=3D2 face=3Dsans-serif><BR>I don't know if CSID may =
contain=20
host specific info &nbsp;(ext_cfactname and local_fact seem to be a bit =
of a=20
catch all that might get used for "hostname" or some such.) but be very =
wary of=20
this catching people out. &nbsp;At the very least, if CSID should not be =
used=20
for host identification, then ban such values from being in these=20
fields.</FONT><FONT size=3D3> <BR><BR><BR></FONT><FONT size=3D2=20
face=3Dsans-serif><BR>Perhaps CSID could be permitted to pass different=20
information depending on the state of the user's session. &nbsp;(which =
brings us=20
back to the protocol vs implementation issue - should CSID always pass =
the same=20
information regardless of session state or is the peer allowed to use =
session=20
context to decide what to include - thus meaning that two calls to CSID =
might be=20
allowed to pass different values. In fact - is a client allowed to send =
multiple=20
CSID commands and what should a server do if the information passed in =
the=20
second command does not match that from the first (and does REIN need to =
be=20
involved?)?)</FONT><FONT size=3D3> <BR></FONT><FONT size=3D2=20
face=3Dsans-serif><BR>Cheers,</FONT><FONT size=3D3> </FONT><FONT =
size=3D2=20
face=3Dsans-serif><BR>Paul</FONT><FONT size=3D3> <BR></FONT><FONT =
size=3D2=20
face=3Dsans-serif><BR>-- <BR><BR>Paul Ford-Hutchinson CISSP - Tivoli =
Security=20
Consultant<BR>IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - =
PO6=20
3AU<BR>IBM Certified Deployment Professional - Tivoli Compliance Insight =
Manager=20
V8.5<BR><BR>Tel +44 (0)7500 078379 &nbsp;(internal: =
37269105)</FONT><FONT=20
size=3D3> <BR><BR></FONT>
<TABLE width=3D"100%">
  <TBODY>
  <TR vAlign=3Dtop>
    <TD width=3D"13%"><FONT color=3D#5f5f5f size=3D1=20
      face=3Dsans-serif>From:</FONT><FONT size=3D3> </FONT>
    <TD width=3D"86%"><FONT size=3D1 face=3Dsans-serif>"Mark P. =
Peterson"=20
      &lt;mpp@rhinosoft.com&gt;</FONT><FONT size=3D3> </FONT>
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>To:</FONT><FONT =
size=3D3>=20
      </FONT>
    <TD><FONT size=3D1 face=3Dsans-serif>"William F. Maton"=20
      &lt;wmaton@ottix.net&gt;</FONT><FONT size=3D3> </FONT>
  <TR>
    <TD vAlign=3Dtop><FONT color=3D#5f5f5f size=3D1 =
face=3Dsans-serif>Cc:</FONT><FONT=20
      size=3D3> </FONT>
    <TD><FONT size=3D1 face=3Dsans-serif>ftpext@ietf.org</FONT><FONT =
size=3D3>=20
      </FONT>
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 =
face=3Dsans-serif>Date:</FONT><FONT size=3D3>=20
      </FONT>
    <TD><FONT size=3D1 face=3Dsans-serif>23/11/2010 14:45</FONT><FONT =
size=3D3>=20
      </FONT>
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 =
face=3Dsans-serif>Subject:</FONT><FONT=20
      size=3D3> </FONT>
    <TD><FONT size=3D1 face=3Dsans-serif>Re: [ftpext]=20
      draft-peterson-streamlined-ftp-command-extensions</FONT><FONT =
size=3D3>=20
      </FONT>
  <TR vAlign=3Dtop>
    <TD><FONT color=3D#5f5f5f size=3D1 face=3Dsans-serif>Sent =
by:</FONT><FONT=20
      size=3D3> </FONT>
    <TD><FONT size=3D1=20
  =
face=3Dsans-serif>ftpext-bounces@ietf.org</FONT></TD></TR></TBODY></TABLE=
><BR><FONT=20
size=3D3><BR></FONT>
<HR noShade>
<FONT size=3D3><BR><BR></FONT><TT><FONT size=3D2><BR>Hi =
William,<BR><BR>Thank you=20
for taking the time to respond. &nbsp;I cannot think<BR>of any real =
reason why=20
CSID shouldn't only be allowed after login.<BR>I will change the =
document to=20
reflect this.<BR><BR>Mark P. Peterson - President</FONT></TT><FONT =
color=3Dblue=20
size=3D3><U><BR></U></FONT><A =
href=3D"http://www.rhinosoft.com/"><TT><FONT=20
color=3Dblue =
size=3D2><U>http://www.RhinoSoft.com</U></FONT></TT></A><TT><FONT=20
size=3D2><BR>Voice: +1(262) 560-9627<BR>FAX: +1(262)=20
560-9628<BR><BR><BR>--------------------------------------------------<BR=
>From:=20
"William F. Maton" &lt;wmaton@ottix.net&gt;<BR>Sent: Tuesday, November =
23, 2010=20
7:55 AM<BR>To: "Mark P. Peterson" &lt;mpp@rhinosoft.com&gt;<BR>Cc: =
"Damin"=20
&lt;damin@emuxperts.net&gt;; &lt;ftpext@ietf.org&gt;<BR>Subject: Re: =
[ftpext]=20
draft-peterson-streamlined-ftp-command-extensions<BR><BR>On Tue, 23 Nov =
2010,=20
Mark P. Peterson wrote:<BR><BR>&gt; Hi All,<BR>&gt;<BR>&gt; Is there =
anyone else=20
that agrees with Damin about CSID? &nbsp;He says it SHOULD be available =
only=20
after login.<BR><BR>Hi Mark,<BR>I'm certainly and old enough salt at =
systems=20
administration to<BR>think that identification before authentication or=20
authorization is not a<BR>good thing. &nbsp;It makes it easier for the =
scanners=20
to pick-off what servers<BR>are running. &nbsp;I'd like to force them =
into=20
making the extra effort, since<BR>it might as well cost them more work =
and I can=20
monitor the activity<BR>better.<BR><BR>I think standardizing CSID (from =
the old=20
non-standard CLNT) is a<BR>good thing though. &nbsp;It should be left up =
to the=20
implementor to support it.<BR><BR>I've also read he rest of that I-D and =
have=20
more thoughts on it,<BR>but that's for another email.<BR><BR><BR>&gt; =
Mark P.=20
Peterson - President<BR>&gt; </FONT></TT><A=20
href=3D"http://www.rhinosoft.com/"><TT><FONT color=3Dblue=20
size=3D2><U>http://www.RhinoSoft.com</U></FONT></TT></A><TT><FONT =
size=3D2><BR>&gt;=20
Voice: +1(262) 560-9627<BR>&gt; FAX: +1(262)=20
560-9628<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; From: Damin<BR>&gt; Sent: =
Monday,=20
November 22, 2010 10:17 PM<BR>&gt; To: ftpext@ietf.org<BR>&gt; Subject: =
Re:=20
[ftpext]=20
draft-peterson-streamlined-ftp-command-extensions<BR>&gt;<BR>&gt;<BR>&gt;=
=20
Hi,<BR>&gt;<BR>&gt;<BR>&gt; On 22 November 2010 19:32, Mark P. Peterson=20
&lt;mpp@rhinosoft.com&gt; wrote:<BR>&gt;<BR>&gt; Hi =
Robert,<BR>&gt;<BR>&gt;=20
Thank you for taking the time to review the commands. &nbsp;If you don't =
mind I=20
would<BR>&gt; like to respond to your comments:<BR>&gt;<BR>&gt;=20
CSID:<BR>&gt;<BR>&gt;&gt; For security reasons I would probably want the =
CSID=20
exchange to occur AFTER the client has logged in, but I might be =
<BR>&gt;&gt;=20
overreacting.<BR>&gt;<BR>&gt;<BR>&gt; There is a lot of discussion on =
the=20
Internet about servers providing "too" much information, especially =
prior to=20
login. &nbsp;But <BR>&gt; having<BR>&gt; worked on both sides of the FTP =

process, it's usually very easy for the client to identify what brand or =
flavor=20
the server is.<BR>&gt; There are details which usually identify the =
server such=20
as the completeness of the FEAT response, the welcome message, responses =

<BR>&gt; to<BR>&gt; certain messages, etc. &nbsp;So, I think it's okay =
to be=20
available prior to login. &nbsp;I could change the document to read that =
it=20
should <BR>&gt; be<BR>&gt; up to the server's implementation whether or =
not it's=20
available.<BR>&gt;<BR>&gt; I prefer to edge on the side of caution. I =
don=B4t see=20
any good reason that this SHOULD be available before login. Commands =
<BR>&gt;=20
available<BR>&gt; prior to login should be as limited as=20
possible.<BR>&gt;<BR>&gt;<BR>&gt; RMDA:<BR>&gt;<BR>&gt;&gt; In a server=20
implementation I would probably make this command configurable, so=20
administrators would have an option to disable the<BR>&gt;&gt; feature. =
&nbsp;In=20
which case I would probably hide the command from a FEAT response so it =
would=20
not be discoverable and have the <BR>&gt;&gt; server<BR>&gt;&gt; return =
a 500 or=20
502 reply when RMDA is sent by the client and disabled at the=20
server.<BR>&gt;<BR>&gt;<BR>&gt; I don't think my document specifies that =
it=20
isn't configurable. &nbsp;My implementation in Serv-U is configurable as =
is=20
almost all <BR>&gt; other<BR>&gt; FTP commands. &nbsp;I think this can =
be left=20
up to the server implementation. &nbsp;Your possible implementation is =
exactly=20
how Serv-U<BR>&gt; implements it. &nbsp;If the feature is disabled, it =
doesn't=20
appear in the FEAT response, nor is it available through the HELP=20
command.<BR>&gt;<BR>&gt;<BR>&gt; AVBL:<BR>&gt;&gt; ...<BR>&gt;<BR>&gt; =
Your=20
comments address the reason for its existence. &nbsp;The client-side=20
implementation in SmartFTP uses the command in this =
manner.<BR>&gt;<BR>&gt;=20
DSIZ:<BR>&gt;&gt; This could certainly be useful, although I would =
probably want=20
a user to be logged in...<BR>&gt;<BR>&gt; Any information about paths or =
files=20
requires login in FTP. &nbsp;I am sure this is the case here as well. =
&nbsp;If a=20
server wouldn't want <BR>&gt; the<BR>&gt; "anonymous" user to have =
access to=20
this command it could be configured to disallow this command at the =
server's=20
implementation or<BR>&gt; configuration. &nbsp;This should be left up to =
the=20
implementation of the server or administrator of the =
server.<BR>&gt;<BR>&gt;&gt;=20
I'd probably make it configurable so as not to tie up too many server =
resources=20
for large directory structures;...<BR>&gt;<BR>&gt; Agreed, the =
time-consuming=20
nature of the implementation is discussed but configuration by an =
administrator=20
or <BR>&gt; server-implementation<BR>&gt; is not. &nbsp; Do you think =
such=20
verbiage is required?<BR>&gt;<BR>&gt;<BR>&gt; THMB:<BR>&gt;<BR>&gt;&gt; =
I'm not=20
a big fan of computing the thumbnail dynamically, nor am I fond of =
allowing the=20
client to specify the thumbnail format <BR>&gt;&gt; and<BR>&gt;&gt;=20
size.<BR>&gt;<BR>&gt;<BR>&gt; That's the point of the command, though.=20
&nbsp;It's to reduce the amount of data that is required to travel over =
the=20
wire. &nbsp;The idea is<BR>&gt; to shorten delivery time to the client, =
letting=20
the client decide what is best for the client, not the server. =
&nbsp;Some=20
clients may<BR>&gt; want very small images, say for a Windows Explorer =
style=20
listing, others may want larger images (640x480 for example) to show =
a<BR>&gt;=20
slide show. &nbsp;I think the client needs to make that determination. =
&nbsp;If=20
the server decides to cache these generated images it=20
can.<BR>&gt;<BR>&gt;<BR>&gt;&gt; I think that it would be better if the =
server=20
could pre-cache thumbnails for any file type in a server-determined size =
and=20
image<BR>&gt;&gt; format, and then return the binary data and image =
format=20
information to the client.<BR>&gt;<BR>&gt;<BR>&gt; This could waste =
server-side=20
resources, the client might not even make a request for thumbnail=20
images.<BR>&gt;<BR>&gt;<BR>&gt;&gt; For example, most graphically-based=20
operating systems have some method for displaying file icons to a user =
that is=20
seated at a<BR>&gt;&gt; computer terminal, so an FTP server =
implementation could=20
simply return that same icon to a client in response to a THMB=20
request.<BR>&gt;<BR>&gt;<BR>&gt; Right, but this isn't really the =
purpose of=20
this command. &nbsp;The purpose is to take an original image file and =
reduce it=20
to a<BR>&gt; specified size, not to return the OS's icon representation =
for that=20
particular file type (i.e., not SHGetFileInfo() in =
Windows).<BR>&gt;<BR>&gt; My=20
proposed implementation is fairly straightforward. &nbsp;If supported =
the FEAT=20
command replies with THMB and the supported file <BR>&gt; types.<BR>&gt; =
When=20
the client wants a thumbnail it asks for it with a single command. =
&nbsp;Here is=20
a sample result from FTP Voyager and Serv-U:<BR>&gt;<BR>&gt; PORT=20
192,168,0,30,199,53<BR>&gt; 200 PORT command successful.<BR>&gt; THMB =
PNG 98 88=20
Thomas.JPG<BR>&gt; 150 Opening thumbnail image transfer BINARY mode data =

connection (19738 Bytes) for Thomas.JPG.<BR>&gt; 226 Transfer complete. =
19,738=20
bytes (19,756 compressed to 100.09%) transferred. 19.29 actual KB/sec,=20
&nbsp;19.28 effective KB/sec.<BR>&gt;<BR>&gt; The client opens a data =
channel=20
just like any other file transfer, then requests the file using THMB, =
followed=20
by the output type,<BR>&gt; width, height, and the file name. &nbsp;The =
server=20
responds just like a file transfer but also includes the resulting size=20
in<BR>&gt; parentheses.<BR>&gt;<BR>&gt; While designing this command the =
idea=20
was to first make it simple for both sides, second to make it operate as =
any=20
other download,<BR>&gt; and third to make it as flexible as possible, =
allowing=20
the client to decide how the resulting data is to be used and what is =
<BR>&gt;=20
needed.<BR>&gt; Of course the server could be configured in any way =
needed.=20
&nbsp;For example if the server wanted to limit the size of the=20
thumbnails,<BR>&gt; the server could do that. &nbsp;Our implementation =
limits=20
the number of simultaneous threads allowed to create the thumbnails at=20
any<BR>&gt; given time. &nbsp;I think these details need to be left to =
the=20
server implementation.<BR>&gt;<BR>&gt; As for using an OPT command to =
configure=20
an upcoming THMB command for its image type and the thumbnail size, that =
seems=20
to<BR>&gt; complicate the command. &nbsp;It's very easy to add these =
parameters=20
into a single command, eliminating the required handshaking <BR>&gt;=20
between<BR>&gt; the client and server. &nbsp;An added benefit is that =
neither=20
the client nor the server are required to maintain these =
"options"<BR>&gt;=20
throughout a session, rather all of the information required is sent in =
a single=20
command.<BR>&gt;<BR>&gt; If you're interested in seeing it in action, =
download=20
Serv-U and FTP Voyager or SmartFTP. &nbsp;Login to the server, switch =
FTP=20
Voyager<BR>&gt; to "Thumbnails" view. &nbsp;With SmartFTP simply select =
an image=20
file and a thumbnail image, of dynamic size, will appear in the <BR>&gt; =

preview<BR>&gt; pane.<BR>&gt;<BR>&gt;<BR>&gt; Thank you again for taking =
the=20
time to provide your feedback. &nbsp;I look forward to your comments to =
the=20
above.<BR>&gt;<BR>&gt; Mark P. Peterson - President<BR>&gt; =
</FONT></TT><A=20
href=3D"http://www.rhinosoft.com/"><TT><FONT color=3Dblue=20
size=3D2><U>http://www.RhinoSoft.com</U></FONT></TT></A><TT><FONT =
size=3D2><BR>&gt;=20
Voice: +1(262) 560-9627<BR>&gt; FAX: +1(262) =
560-9628<BR>&gt;<BR>&gt;<BR>&gt;=20
--------------------------------------------------<BR>&gt; From: "Robert =

McMurray" &lt;robmcm@microsoft.com&gt;<BR>&gt; Sent: Monday, November =
22, 2010=20
5:01 PM<BR>&gt; To: &lt;ftpext@ietf.org&gt;; "'Anthony Bryan'"=20
&lt;anthonybryan@gmail.com&gt;; =
&lt;mark.peterson@rhinosoft.com&gt;<BR>&gt;=20
Subject: [ftpext]=20
draft-peterson-streamlined-ftp-command-extensions<BR>&gt;<BR>&gt;<BR>&gt;=
 [Note:=20
Renaming the thread from 'Submitting new drafts'.]<BR>&gt;<BR>&gt;&gt; =
Anthony=20
Bryan wrote:<BR>&gt;&gt;<BR>&gt;&gt; I don't mean to single you out,=20
but<BR>&gt;&gt; you showed interest in an CSID/AGNT<BR>&gt;&gt; command. =
Do you=20
have any opinion on<BR>&gt;&gt; the other 4 commands in the=20
draft?<BR>&gt;<BR>&gt; Thanks, Anthony.<BR>&gt;<BR>&gt; No worries - I =
meant to=20
send a better response in the wake of my withdrawn AGNT draft and Mark's =
current=20
Streamlined FTP Command<BR>&gt; Extensions draft, but I had been remiss =
at=20
taking the time to collect my thoughts in a more meaningful way. But =
since you=20
asked,<BR>&gt; this seems like as good at time as any. =
;-]<BR>&gt;<BR>&gt; CSID=20
- As evidenced by my short-lived AGNT proposal, I think it's very useful =
to have=20
some sort of client/server discovery <BR>&gt; command.<BR>&gt; FEAT does =
a good=20
job of advertising the list of commands that are supported by a server, =
but=20
Mark's proposed CSID command sequence<BR>&gt; provides a much better way =
for=20
servers and client to identify their features to each other in detail. =
For=20
security reasons I would<BR>&gt; probably want the CSID exchange to =
occur AFTER=20
the client has logged in, but I might be overreacting.<BR>&gt;<BR>&gt; =
RMDA -=20
This could be a very useful command, and it would parallel the =
functionality=20
that I'm sure we all typically use in a native<BR>&gt; operating system=20
environment. In a server implementation I would probably make this =
command=20
configurable, so administrators would<BR>&gt; have an option to disable =
the=20
feature. In which case I would probably hide the command from a FEAT =
response so=20
it would not be<BR>&gt; discoverable and have the server return a 500 or =
502=20
reply when RMDA is sent by the client and disabled at the=20
server.<BR>&gt;<BR>&gt; (Note: I mention my thoughts about server =
implementation=20
details just to open up the discussion as to whether any =
implementation<BR>&gt;=20
details should be called out in the draft, or if we should leave that up =
to the=20
implementers to decide.)<BR>&gt;<BR>&gt; AVBL - This command could be =
very=20
useful in a client/server world; our FTP server implementation currently =
returns=20
the available<BR>&gt; size after a successful login sequence, and the =
available=20
size is based on server disk quotas and such. That being said, not =
every<BR>&gt;=20
FTP client will bubble that information up to the user interface. Having =
an AVBL=20
command would make it possible for a client to<BR>&gt; determine whether =
enough=20
storage space is available at the server BEFORE sending a file, which =
would be=20
great when you're about to<BR>&gt; send a 10GB file and you only have =
9.99GB of=20
storage space left. ;-]<BR>&gt;<BR>&gt; DSIZ - This could certainly be =
useful,=20
although I would probably want a user to be logged in (not anonymous) =
before I=20
supported <BR>&gt; this<BR>&gt; command in order to reduce the risk of=20
denial-of-service. I'd probably make it configurable so as not to tie up =
too=20
many server<BR>&gt; resources for large directory structures; and once =
again, if=20
the feature were disabled I would probably hide the command from a =
<BR>&gt;=20
FEAT<BR>&gt; response so it would not be discoverable and return a 500 =
or 502=20
reply when DSIZ is sent by the client and disabled at the=20
server.<BR>&gt;<BR>&gt; THMB - I have to admit, I don't work on a =
graphical FTP=20
client, so this command is less useful to me personally, but I can see=20
the<BR>&gt; merit that it might have to someone that designs a graphical =
client.=20
That being said, I'm not a big fan of computing the thumbnail<BR>&gt;=20
dynamically, nor am I fond of allowing the client to specify the =
thumbnail=20
format and size. I think that it would be better if the<BR>&gt; server =
could=20
pre-cache thumbnails for any file type in a server-determined size and =
image=20
format, and then return the binary data<BR>&gt; and image format =
information to=20
the client. For example, most graphically-based operating systems have =
some=20
method for displaying<BR>&gt; file icons to a user that is seated at a =
computer=20
terminal, so an FTP server implementation could simply return that same =
icon to=20
<BR>&gt; a<BR>&gt; client in response to a THMB request.<BR>&gt;<BR>&gt; =
Please=20
bear in mind, I haven't given a lot of thought as to what the =
client/server=20
interchange might look like if the server were<BR>&gt; more in control =
of the=20
response to a THMB request, but it would probably be sufficient to =
simply return=20
the image type as part of<BR>&gt; the response and let the client =
determine the=20
image dimensions based on the client's capabilities for reading the =
image data.=20
(As <BR>&gt; a<BR>&gt; server guy I like to push any client-friendly =
processing=20
on the client whenever possible. ;-]) You could borrow an idea from =
the<BR>&gt;=20
HASH discussion that we've been having and make the thumbnail image type =

configurable for the client by using an OPTS command, <BR>&gt; =
which<BR>&gt;=20
might look like the following examples.<BR>&gt;<BR>&gt; In this first =
example,=20
the server has a pre-configured thumbnail image type of JPG, and may =
have=20
pre-cached the thumbnails for<BR>&gt; files; any THMB request with no =
OPTS=20
specified would use the server's pre-configured thumbnail image type of =
JPG and=20
image type is<BR>&gt; specified in the command channel =
response:<BR>&gt;<BR>&gt;=20
C&gt; THMB widget.png<BR>&gt; S&gt; 150 JPG Starting thumbnail transfer =
(1234=20
Bytes) for widget.png<BR>&gt; S&gt; 226 Transfer =
complete.<BR>&gt;<BR>&gt; In=20
these next examples a client is asking for different thumbnail image =
types by=20
using OPTS commands, and the thumbnail image <BR>&gt; types<BR>&gt; =
would still=20
be specified in the command channel responses:<BR>&gt;<BR>&gt; C&gt; =
OPTS THMB=20
GIF<BR>&gt; S&gt; 200 OPTS THMB GIF command successful.<BR>&gt;<BR>&gt; =
C&gt;=20
THMB widget.psp<BR>&gt; S&gt; 150 GIF Starting thumbnail transfer (1234 =
Bytes)=20
for widget.psp<BR>&gt; S&gt; 226 Transfer complete.<BR>&gt;<BR>&gt; =
C&gt; OPTS=20
THMB PNG<BR>&gt; S&gt; 200 OPTS THMB PNG command =
successful.<BR>&gt;<BR>&gt;=20
C&gt; THMB widget.doc<BR>&gt; S&gt; 150 PNG Starting thumbnail transfer =
(1234=20
Bytes) for widget.doc<BR>&gt; S&gt; 226 Transfer =
complete.<BR>&gt;<BR>&gt; In=20
this next example a client is asking for an unsupported image type, so =
the=20
server would simply return the appropriate error<BR>&gt; =
reply:<BR>&gt;<BR>&gt;=20
C&gt; OPTS THMB FOO<BR>&gt; S&gt; 501 Unsupported thumbnail=20
format.<BR>&gt;<BR>&gt; In this next example a client is asking for the=20
currently-configured thumbnail image type, so the server would return=20
the<BR>&gt; appropriate response:<BR>&gt;<BR>&gt; C&gt; OPTS =
THMB<BR>&gt; S&gt;=20
200 JPG<BR>&gt;<BR>&gt; You might take this one step further - the =
server might=20
choose to only support its pre-configured thumbnail image type, =
thereby<BR>&gt;=20
allowing pre-caching of all thumbnails in one specific image format. In =
this=20
example a client is asking for PNG thumbnails, which<BR>&gt; SHOULD be a =

supported image type, but the server only supports a pre-configured =
thumbnail=20
image type for JPG files and returns the<BR>&gt; appropriate error reply =
(504?)=20
and the server's pre-configured thumbnail image type is specified in the =

subsequent command channel<BR>&gt; response to a THMB =
request:<BR>&gt;<BR>&gt;=20
C&gt; OPTS THMB PNG<BR>&gt; S&gt; 504 Specifying thumbnail formats is=20
unsupported.<BR>&gt;<BR>&gt; C&gt; THMB widget.xls<BR>&gt; S&gt; 150 JPG =

Starting thumbnail transfer (1234 Bytes) for widget.xls<BR>&gt; S&gt; =
226=20
Transfer complete.<BR>&gt;<BR>&gt; As I said earlier, I hadn't given =
much=20
thought as to what the client/server THMB interchange might look like if =
you put=20
the server<BR>&gt; in control instead of the client, but as a server guy =
I'd=20
rather see THMB look a little more like the examples that I gave.=20
;-]<BR>&gt;<BR>&gt; Thanks again!<BR>&gt;<BR>&gt; Robert =
McMurray<BR>&gt;=20
robmcm@microsoft.com<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; ftpext mailing=20
list<BR>&gt; ftpext@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT =
color=3Dblue=20
size=3D2><U>https://www.ietf.org/mailman/listinfo/ftpext</U></FONT></TT><=
/A><TT><FONT=20
size=3D2><BR>&gt;<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; ftpext mailing=20
list<BR>&gt; ftpext@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT =
color=3Dblue=20
size=3D2><U>https://www.ietf.org/mailman/listinfo/ftpext</U></FONT></TT><=
/A><TT><FONT=20
size=3D2><BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; ftpext mailing=20
list<BR>&gt; ftpext@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT =
color=3Dblue=20
size=3D2><U>https://www.ietf.org/mailman/listinfo/ftpext</U></FONT></TT><=
/A><TT><FONT=20
size=3D2><BR>&gt;<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; ftpext mailing=20
list<BR>&gt; ftpext@ietf.org<BR>&gt; </FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT =
color=3Dblue=20
size=3D2><U>https://www.ietf.org/mailman/listinfo/ftpext</U></FONT></TT><=
/A><TT><FONT=20
size=3D2><BR>&gt;<BR><BR>wfms=20
<BR><BR><BR>_______________________________________________<BR>ftpext =
mailing=20
list<BR>ftpext@ietf.org</FONT></TT><FONT color=3Dblue =
size=3D3><U><BR></U></FONT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ftpext"><TT><FONT =
color=3Dblue=20
size=3D2><U>https://www.ietf.org/mailman/listinfo/ftpext</U></FONT></TT><=
/A><FONT=20
size=3D3><BR><BR></FONT><BR><BR></BODY></HTML>

------=_NextPart_000_00BF_01CB8BA4.4EAA6B80--



From prvs=1944f83767=mpp@rhinosoft.com  Wed Nov 24 05:41:26 2010
Return-Path: <prvs=1944f83767=mpp@rhinosoft.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 1766C28C204 for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 05:41:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.221
X-Spam-Level: 
X-Spam-Status: No, score=-2.221 tagged_above=-999 required=5 tests=[AWL=0.378,  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 Xnl9LEJ-1dQi for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 05:41:24 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id A9E0328C1EF for <ftpext@ietf.org>; Wed, 24 Nov 2010 05:41:23 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009936400.msg for <ftpext@ietf.org>; Wed, 24 Nov 2010 07:42:22 -0600
X-Spam-Processed: rhinosoft.com, Wed, 24 Nov 2010 07:42:22 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=1944f83767=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <E02E65C7F82940BCAFDCC2EB7ED5194C@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "Robert McMurray" <robmcm@microsoft.com>, <ftpext@ietf.org>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com> <D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net> <A5FC996C3C37DC4DA5076F1046B5674C442E8816@TK5EX14MBXC127.redmond.corp.microsoft.com>
In-Reply-To: <A5FC996C3C37DC4DA5076F1046B5674C442E8816@TK5EX14MBXC127.redmond.corp.microsoft.com>
Date: Wed, 24 Nov 2010 07:42:16 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 24 Nov 2010 13:41:26 -0000

Hi Robert,

I'm not exactly sure how to reply to your message I will try without quoting, if that makes any sense.  I understand the problem in 
your example, however I think that the problem leads to the implementation of a good FTP server vs. one that isn't so good.  In the 
case of your server I can see a cache implementation that would solve the problem, reduce the amount of required disk space, and 
provide the client with varying sizes of images as I propose with this command.  To solve the real-world problem you've outlined I 
would:

* Add a limit in the server, either hard-coded or user configurable, to identify the maximum dimensions of a thumbnail, let's use 1k 
x 1k for an example.
* Design a thumbnail cache which identifies when an image was placed into the cache, when it was last accessed, the thumbnail 
dimensions, etc.
* When a THMB command arrives for a particular file, first identify if it's in the cache.  If it is in the cache, use the file from 
the cache and create a thumbnail image and provide it to the client.  If not in the cache, create a thumbnail of the maximum allowed 
size, add it to the cache, then return the requested image to the client.
* Maintain the cache.

This simplistic outline does require an additional transformation to get the thumbnail image, however the horsepower required to 
perform this operation is now trivial, for example taking that 1k x 1k image down to 100 x 100.  If another request comes in for 200 
x 200 for that same image, again the CPU usage is very small, yet the amount of data transferred remains low and not limited.

My point to the above example is that we are talking about the implementation.  I realize implementations cannot be ignored but in 
your example an efficient simple solution does exist while not limiting the client to a fixed thumbnail size.  The implementation I 
propose, above, could be extended to support multiple image sizes in addition to a single image size, whatever is needed by the 
server.  For example, if the server received a request for a 256 x 256 thumbnail, the server could decide to create a 512 x 512 
cache image, then create the 256 x 256 sized image to send to the client.  Instead of maintaining a cache of specific sizes it could 
use reasonable stratifications from which thumbnails can be created.

If the server decides it wants to attempt to pre-cache images it could, and it could be triggered by the first thumbnail image 
requested in a directory.  Again, I think this would be an implementation detail that would be at the server author's design.

Regarding thumbnail types.  I agree with you, thumbnails of videos, PDFs, Word documents, text files, and others are all reasonable 
uses for this command.  I don't think my document prevents different file types from being supported, I think it's quite extensible.

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "Robert McMurray" <robmcm@microsoft.com>
Sent: Tuesday, November 23, 2010 10:26 PM
To: "'Mark P. Peterson'" <mpp@rhinosoft.com>; <ftpext@ietf.org>
Subject: RE: [ftpext] draft-peterson-streamlined-ftp-command-extensions

Thanks, Mark.

> Mark wrote:
>
> That's the point of the command,
> though.  It's to reduce the amount of
> data that is required to travel over
> the wire.  The idea is to shorten
> delivery time to the client, letting
> the client decide what is best for
> the client, not the server.

I understood that to be the case, but looking back to Anthony's original question - he had asked which commands were more valuable 
to me than others. With that in mind, when I considered the THMB command from a server implementation point-of-view as it appears in 
the current draft, I thought that the current proposal was a little impractical, which would make me lean away from implementing it.

Here's a real-world scenario that illustrates why I think that the current THMB proposal breaks down quickly in a normal use 
scenario:

Let's say that I have a friend who works in astrophotography, and let's say that he's doing his doctoral work on the Crab Nebula. He 
books some time at one of the national observatories and takes several series of images of the Crab Nebula that are stitched 
together into 50 large composite images. (These have very large dimensions, 100K by 100K pixels, and each is over 100MB in size, 
which are the perfect candidates for thumbnails.) When he publishes his thesis for peer review, he drops the full-sized images in a 
directory on an FTP site that I manage where his colleagues can access them. Let's say that his thesis garners a modicum of interest 
on the day of its publication for review - perhaps just 10 users. Each of these users has an FTP client that supports the THMB 
command as it is currently designed, and each FTP client can use varying thumbnail dimensions. So here's what happens:

Client 1 has the following transaction:

Client01> THMB JPG 100 100 Crab_Nebula_01.jpg
Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
-         //Note: 5K bytes are transferred over the data channel//
Server00> 226 Transfer complete.

Since the thumbnail was generated dynamically based on the client's input, one of my server's CPUs spikes while it loads the 100MB 
image into RAM, renders the thumbnail in the user-requested image format and dimensions, and dumps the image on the wire. (Because a 
client can request any image dimensions and format, my server implementation would probably not cache the thumbnail in memory, but 
I'll come back to that.) Still, transferring only 5K over the wire is a lot better than transferring 100MB, so we're in agreement 
that reducing the bandwidth is a good thing.

But I have 9 other clients that are hitting my FTP site and they issue FTP thumbnail requests like the following examples:

Client02> THMB PNG 100 100 Crab_Nebula_01.jpg
Client03> THMB GIF 100 100 Crab_Nebula_01.jpg
Client04> THMB JPG 200 200 Crab_Nebula_01.jpg
Client05> THMB PNG 200 200 Crab_Nebula_01.jpg
Client06> THMB GIF 150 150 Crab_Nebula_01.jpg
Client07> THMB PNG 640 480 Crab_Nebula_01.jpg
Client08> THMB GIF 320 240 Crab_Nebula_01.jpg
Client09> THMB JPG 150 150 Crab_Nebula_01.jpg
Client10> THMB JPG 320 240 Crab_Nebula_01.jpg

So my server has received 10 completely dissimilar thumbnail requests, and all of those requests are just for the first physical 
image. If each FTP client attempts to download just 20 thumbnails in order to show the first set of thumbnails in each graphical FTP 
client, I have to dynamically generate 200 different thumbnails. Since these are all 100MB images, I am reducing my bandwidth at the 
expense of the CPU and RAM resources that are required to process the THMB requests.

I mentioned earlier that I would probably not cache the thumbnails in RAM because the client can request any thumbnail dimensions, 
so let's say that my server implementation at least caches thumbnails to disk so I don't have to generate them dynamically for every 
request. Since each FTP client can request multiple image formats and any image dimensions, I may have to keep track of hundreds of 
thumbnails for each single physical image. That will quickly start to eat up disk space, so now I have to implement some form of 
garbage collection to clean up stale thumbnails. But even then, since my friend has 50 physical images and I configure my FTP server 
implementation to only keep the 10 most-recent thumbnails around, I'm still managing 500 thumbnails for his original 50 physical 
images.

All in all I find the approach for letting only the client have full control very impractical, and that would prevent me from 
wanting to implement the THMB command as it is currently documented in the draft. But that being said, I like the idea of having a 
thumbnail command, just not the way that it's currently proposed. That's why I was suggesting some alternatives, and I'll expound a 
little on that.

In my last email I had suggested letting the server be a little more in control, and I had suggested that the server could 
optionally tell an FTP client that the client can't specify the image format. If I use the astrophotography scenario that I just 
gave, that means that I could have my friend pre-create the 50 thumbnails for the 50 physical images in some fashion where the FTP 
server implementation would pick them up. (I could use shadow folders, unique thumbnail naming, etc.) This means that there is no 
spike in CPU or RAM when the 10 FTP clients issue their THMB requests; it also means that I'm only managing 50 static thumbnails. So 
now the requests could be as simple as the following:

Client01> THMB Crab_Nebula_01.jpg
Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
Server00> 226 Transfer complete.
Client02> THMB Crab_Nebula_01.jpg
Server00> 150 Starting thumbnail transfer for Crab_Nebula_01.jpg
Server00> 226 Transfer complete.
... etc ...

The reason why I had proposed using the OPTS command was to give the client the level of control that you mentioned in your reply, 
e.g. "letting the client decide what is best for the client, not the server." If you were to combine your client request concepts 
with elements of my OPTS-based suggestion, you could create a hybrid of the two approaches that might address all concerns. Here are 
some examples:

In this example, the client simply asks for the server's current thumbnail configuration:
C> OPTS THMB
S> 200 JPG 100 100

In this example, the client specifies a new thumbnail format:
C> OPTS THMB PNG
S> 200 PNG 100 100

In this example, the client specifies a new thumbnail format and dimensions:
C> OPTS THMB GIF 150 150
S> 200 GIF 150 150

I think that something more of a hybrid approach works better - the client can ask for a file format and dimensions, but the server 
can still say "no" to a client-specified file format and dimensions when it wants to, but still return a thumbnail when the client 
asks for it.

C> OPTS THMB PNG 100 100
S> 504 Specifying thumbnail properties is unsupported.

C> THMB widget.png
S> 150 JPG Starting thumbnail transfer for widget.png
S> 226 Transfer complete.

This makes it easier for the server implementation to have a pre-cached collection of thumbnails, especially when given the 
realistic scenario that I listed above. But if you omit using OPTS command and stick with using a single THMB command, when an FTP 
client sends a request that your server doesn't want to fulfill for some reason, your only recourse is to fail the whole request. 
Whereas, if break the process into separate OPTS and THMB commands, you can fulfill a THMB request even if you reject the custom 
parameters that the client had requested with an OPTS command.

> Mark wrote:
>
> This could waste server-side
> resources, the client might not even
> make a request for thumbnail images.

This is true, but using the astrophotography scenario once again, I'd rather have 50 5K thumbnail files eating up a tiny fraction of 
disk space (which is a dirt cheap resource) rather than trying to generate dynamic thumbnails for 50 100MB images and eating CPU and 
RAM (which are expensive resources).

If my server implementation didn't pre-cache thumbnails, and I configured my server to only allow JPG format thumbnails at 100x100 
pixels, it would still be possible to implement some form of in-memory or dynamic to disk caching for subsequent requests, because 
now the list of variables has been reduced. For example:

Client01> THMB Crab_Nebula_01.jpg
-        //Note: the thumbnail was not//
-        //pre-cached, so the server  //
-        //creates it dynamically and //
-        //caches it to disk after it //
-        //sends the thumbnail to the //
-        //client                     //
Client02> THMB Crab_Nebula_01.jpg
-        //Note: the thumbnail was    //
-        //cached during the previous //
-        //request, so the server can //
-        //send the thumbnail to the  //
-        //client with no additional  //
-        //processing required        //
Client03> THMB Crab_Nebula_01.jpg
... etc ...
Client10> THMB Crab_Nebula_01.jpg

> Mark wrote:
>
> This isn't really the purpose of this
> command.  The purpose is to take an
> original image file and reduce it to
> a specified size, not to return the
> OS's icon representation for that
> particular file type.

Perhaps that was not the originally-intended purpose for this command, but then I think that you're limiting the usefulness of the 
command. My suggestion to return an icon may not have been the best example, but limiting the THMB command to just image files is 
not very useful, since there are other files that would yield beneficial results. For example, video files are typically much larger 
than images, so why shouldn't video files be able to have unique thumbnails? What about thumbnails for new image types that are 
introduced later, like SVG files? I would say that it's certainly possible that any server implementation could refuse to send a 
thumbnail for any file that it chooses, but why shouldn't a server implementation be able to return a thumbnail for any file? I am 
simply suggesting that limiting the functionality of the THMB command to just images reduces the overall value of the command.

All that being said, as I stated earlier, I like the idea of a THMB command, but at the moment I'm not fond of the current proposal. 
When I consider that implementers of FTP clients might read about the THMB command in an RFC and start creating FTP clients that can 
issue requests for thumbnails in any number of image formats and pixel dimensions, I start to back away from this command pretty 
quickly.

I admit that it would be different if I implemented my own graphical FTP client and my own FTP server, because I could control the 
THMB interoperability in a way of my choosing - for example, I could define a specific set of thumbnail dimensions and only use JPG 
format. But since I would only be implementing an FTP server, I don't like the way the odds are stacked. (In some ways this is like 
writing a function to strip whitespace from text files - if you generate all of your own text files, then you only have to 
anticipate what you've defined as whitespace. But when you're stripping whitespace from someone else's text files, you have to 
anticipate 0x20, 0x09, 0xA0, multiple character sets, what to do when you get character codes that you don't recognize, etc.)

Just the same, I'd like to see some form of thumbnail functionality if possible, because the scenario about astrophotography wasn't 
hypothetical - I actually have a friend that works with astrophotography who generates those types of huge image files; having an 
effective method to retrieve thumbnails for those large images would be great. But I don't think that the current draft offers an 
example of an effective method when I consider having to create dynamically-generated thumbnails for a near-infinite number of 
possible client request parameters.

Thanks again!

Robert McMurray
robmcm@microsoft.com 



From prvs=1944f83767=mpp@rhinosoft.com  Wed Nov 24 05:57:15 2010
Return-Path: <prvs=1944f83767=mpp@rhinosoft.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 AED963A6A58 for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 05:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[AWL=0.190,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 i0wRZKk6OXdK for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 05:57:14 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id 49CBE3A6A51 for <ftpext@ietf.org>; Wed, 24 Nov 2010 05:57:13 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009936413.msg for <ftpext@ietf.org>; Wed, 24 Nov 2010 07:58:13 -0600
X-Spam-Processed: rhinosoft.com, Wed, 24 Nov 2010 07:58:13 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=1944f83767=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <24FEC9729BA54CC7B08C13D51785BB1F@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: =?iso-8859-1?Q?=C1ngel_Gonz=E1lez?= <keisial@gmail.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com> <4CEC5427.1070605@gmail.com>
In-Reply-To: <4CEC5427.1070605@gmail.com>
Date: Wed, 24 Nov 2010 07:58:06 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 24 Nov 2010 13:57:15 -0000

Hi Ángel,

RMDA
-------
> If the folder being RMDAed is not deletable by the logged in user, the
server MAY -based both on its configuration and user credentials-
directly reject the command. On the other hand, if it deletes one file
(and can not rollback the operation), it must continue the whole subtree.

I will add this to the document.

THMB
-------
>  It should allow full MIME types, so an application/x-better-image-format could be used.

I cannot find a reason to disagree, so I agree that following a standard for
identifying the thumbnail type should be used.  I could use your help here
clarifying my document.

> I also prefer the OPTS syntax, since that would allow larger options and
extensions, such as:...

I prefer specifying the parameters in the command for two primary reasons.

1) By requiring a client to use OPTS to specify output type and resolution
the client and server must exchange this information in a separate command.
Commands require a handshake and consequently some latency between the
server and client for the exchange.  Depending on many different factors this
latency, even on a fast connection, can be noticeable.  If the client wants different
sized images frequently, let's say for every thumbnail image, it would be
even more noticeable.  The bandwidth required to specify 10 bytes or less as a
parameter to the command is trivial by comparison even on the slowest
connections.

2) By requiring a client to use OPTS to identify the parameters, both the client
and the server must maintain the parameters for this command, more-or-less
as a state.  I'm a big fan of keeping things very simple.

3) End-user support is easier when parameters are specified with the command.
When end-users or customers have problems they'll often provide a portion of a
log to identify what is going on with the communication between the server and
client.  Technicians analyzing the log may not have all of the required information
regarding the THMB command.  With the parameters being issued with the
command analysis is far simpler and accurate.

> There should be a note about the potential security issues of the THMB
command. Vulnerabilities processing images are common.

Could you give me some examples or how you would like to see this worded
and where you would like to see this placed in the document?

Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628


--------------------------------------------------
From: "Ángel González" <keisial@gmail.com>
Sent: Tuesday, November 23, 2010 5:54 PM
To: <ftpext@ietf.org>
Cc: "Robert McMurray" <robmcm@microsoft.com>; <anthonybryan@gmail.com>; <mark.peterson@rhinosoft.com>; <mb@smartftp.com>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions

Hello all,

Robert McMurray wrote:
> RMDA - This could be a very useful command, and it would parallel the
> functionality that I'm sure we all typically use in a native operating
> system environment. In a server implementation I would probably make
> this command configurable, so administrators would have an option to
> disable the feature. In which case I would probably hide the command
> from a FEAT response so it would not be discoverable and have the
> server return a 500 or 502 reply when RMDA is sent by the client and
> disabled at the server.

I don't think a server should do that or be encouraged to. If a server
rejects a RMDA the client SHOULD fall back to a recursive listing and
removing.
As currently defined, on receiving a RMDA the server MUST delete
everything in the subpath the user is allowed to. I think that changing
it to also allow a not remove anything would solve the issue.
If the folder being RMDAed is not deletable by the logged in user, the
server MAY -based both on its configuration and user credentials-
directly reject the command. On the other hand, if it deletes one file
(and can not rollback the operation), it must continue the whole subtree.


About THMB:
The format is restricted to registered image subtypes. It should allow
full MIME types, so an application/x-better-image-format could be used.
And giving that step, always using the full mime for images would seem
more clear.

I also prefer the OPTS syntax, since that would allow larger options and
extensions, such as:

  C> OPTS THMB image/png 60 60 page=2
  S> 200 OPTS THMB PNG command successful.

  C> THMB document.doc
  S> 150 PNG Starting thumbnail transfer
  S> 226 Transfer complete.

for requesting a thumbnail for the second page of the document.

Since the OPTS would be given once at the beginning and then used for many files, it's also important for reducing its continuous 
repetition.


Robert McMurray wrote:
> That being said, I'm not a big fan of computing the thumbnail dynamically, nor am I fond of allowing the client to specify the 
> thumbnail format and size. I think that it would be better if the server could pre-cache thumbnails for any file type in a 
> server-determined size and image format, and then return the binary data and image format information to the client. For example, 
> most graphically-based operating systems have some method for displaying file icons to a user that is seated at a computer 
> terminal, so an FTP server implementation could simply return that same icon to a client in response to a THMB request.
Note that the server can compute it the first time, then cache the
thumbnails you have requested on previous sessions. Moreover, it could
get heuristics as 'Start prethumbnailing with the current options if it
has requested in order the thumbnails of the first three files in the
folder'.


There should be a note about the potential security issues of the THMB
command. Vulnerabilities processing images are common.



Mat Berchtold wrote:
> Server/Client fact requirement
> The draft proposes that the client must provide the name and version fact where for the server these facts are optional. For 
> equality both parties involved should have equal requirements/rights. My proposal is that all facts are optional. The reasoning is 
> that there is no need for the client to expose its name or version if it only wants to figure out the case sensitivity of the 
> server file system.
Sad as it is, it may be useful for implementing client-specific
workarounds in the server. 



From tony@att.com  Wed Nov 24 06:49:36 2010
Return-Path: <tony@att.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 5287628C279 for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 06:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.442
X-Spam-Level: 
X-Spam-Status: No, score=-106.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 XDFS0IAQ6AMt for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 06:49:32 -0800 (PST)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id 0FD2C28C270 for <ftpext@ietf.org>; Wed, 24 Nov 2010 06:49:30 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-15.tower-146.messagelabs.com!1290610227!26834778!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 6712 invoked from network); 24 Nov 2010 14:50:27 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-15.tower-146.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Nov 2010 14:50:27 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oAOEoj7o030668 for <ftpext@ietf.org>; Wed, 24 Nov 2010 09:50:45 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oAOEofA9030569 for <ftpext@ietf.org>; Wed, 24 Nov 2010 09:50:41 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oAOEoMtH020277 for <ftpext@ietf.org>; Wed, 24 Nov 2010 09:50:22 -0500
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oAOEnwO9019019 for <ftpext@ietf.org>; Wed, 24 Nov 2010 09:49:58 -0500
Received: from [135.70.10.203] (vpn-135-70-10-203.vpn.west.att.com[135.70.10.203]) by maillennium.att.com (mailgw1) with ESMTP id <20101124144957gw1004lkure> (Authid: tony); Wed, 24 Nov 2010 14:49:57 +0000
X-Originating-IP: [135.70.10.203]
Message-ID: <4CED2614.8000005@att.com>
Date: Wed, 24 Nov 2010 09:49:56 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Anthony Bryan <anthonybryan@gmail.com>
References: <20101123184835.AFC433A69A1@core3.amsl.com>	<AANLkTinYUc1G-syqicN31Rc+yV6UvKurB-O1nQba2Y9=@mail.gmail.com>	<4CEC5480.8040801@att.com> <AANLkTi=hOFDdV5p8YomDmOcQH=jfFC1qt0pHhgR8LYae@mail.gmail.com>
In-Reply-To: <AANLkTi=hOFDdV5p8YomDmOcQH=jfFC1qt0pHhgR8LYae@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ftpext@ietf.org
Subject: Re: [ftpext] WG Action: FTP Extensions, 2nd edition (ftpext2)
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, 24 Nov 2010 14:49:36 -0000

On 11/24/2010 2:38 AM, Anthony Bryan wrote:
> On Tue, Nov 23, 2010 at 6:55 PM, Tony Hansen<tony@att.com>  wrote:
>> When the next update is ready for each draft, each author should 
>> upload the
>> draft under the WG name. Bryan's naming suggestion is apropos:
>>
>> draft-bryan-ftp-hash =>  draft-ietf-ftpext2-hash
>> draft-hethmon-mcmurray-ftp-hosts =>  draft-ietf-ftpext2-hosts
>> draft-klensin-ftp-typeu =>  draft-ietf-ftpext2-typeu
> thanks, Tony.
>
> I saw that the websocket draft, when converting from an individual's
> to a WG draft, had no changes.
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-hybi-thewebsocketprotocol-00.txt
>
> is that how most people do it, or do we wait for substantive changes?
It can be done either way. If there are changes pending for a draft at 
the same time, then it can be done as part of that update. If there are 
no pending changes, then you can either just do it or wait for changes 
to appear; it's a judgment call. (If an individual draft is in its final 
state and ready for publication, the name change is a formality that can 
be done immediately just as a matter of course.)

> there is also
> draft-liu-ftp64-extension =>  draft-ietf-ftpext2-ftp64 ?
>
> which after discussion during the charter, should be changed to
> "Intended status: Standards Track"

Yes.

     Tony Hansen
     tony@att.com

From keisial@gmail.com  Wed Nov 24 12:35:46 2010
Return-Path: <keisial@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 539E728C13A for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 12:35:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_54=0.6, MIME_8BIT_HEADER=0.3]
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 EaJ71zm5MRnl for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 12:35:45 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 7A17E28C149 for <ftpext@ietf.org>; Wed, 24 Nov 2010 12:35:44 -0800 (PST)
Received: by wwa36 with SMTP id 36so135308wwa.13 for <ftpext@ietf.org>; Wed, 24 Nov 2010 12:36:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=+f2qLN2C2USbUxMVnpK+qsR+S/rDF3eAYO9XcPci5H8=; b=bjb23/kS9xShY4PO8Tw/nBKi1Mmi0KFqrpkuCnNoGGEKyAhN83I90AhvzjuPmfnXge +oBsHAxtRAc80hja//O7cpTnYPNSUeN1uzqT2M6p3nmkIyI4EhO9OsL9B+zkpTWR22aU f3dmHh7B1KfZNDZaULJrXf8T5ck4TCN5EELVM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=FZwnGKp3MUgQY9pVo9sncoIM16+k8n2wVPQiUuRR9aE1/fdxCD4ReuyXw9j5b1U44u KqtPyL5THodzqLUd0/IzC2+uEv/Ci+W4NxCBmTx3FqYFLNhs5NAoNoWiy2V/xKkA/6Kz 2rem2W2CIwfye7KrtAcgcOOk4eugtXedk7jpg=
Received: by 10.216.161.147 with SMTP id w19mr8438765wek.88.1290631003383; Wed, 24 Nov 2010 12:36:43 -0800 (PST)
Received: from [192.168.1.26] (225.red-80-28-70.adsl.dynamic.ccgg.telefonica.net [80.28.70.225]) by mx.google.com with ESMTPS id x59sm3676029weq.14.2010.11.24.12.36.40 (version=SSLv3 cipher=RC4-MD5); Wed, 24 Nov 2010 12:36:41 -0800 (PST)
Message-ID: <4CED776A.5020609@gmail.com>
Date: Wed, 24 Nov 2010 21:36:58 +0100
From: "=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=" <keisial@gmail.com>
User-Agent: Thunderbird
MIME-Version: 1.0
To: "Mark P. Peterson" <mpp@rhinosoft.com>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com> <4CEC5427.1070605@gmail.com> <24FEC9729BA54CC7B08C13D51785BB1F@rhinooffice.net>
In-Reply-To: <24FEC9729BA54CC7B08C13D51785BB1F@rhinooffice.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 24 Nov 2010 20:35:46 -0000

Mark P. Peterson wrote:
> Hi Ángel,
>
> RMDA
> -------
>> If the folder being RMDAed is not deletable by the logged in user, the
> server MAY -based both on its configuration and user credentials-
> directly reject the command. On the other hand, if it deletes one file
> (and can not rollback the operation), it must continue the whole subtree.
>
> I will add this to the document.
>
> THMB
> -------
>>  It should allow full MIME types, so an application/x-better-image-format could be used.
> I cannot find a reason to disagree, so I agree that following a standard for
> identifying the thumbnail type should be used.  I could use your help here
> clarifying my document.
>
>> I also prefer the OPTS syntax, since that would allow larger options and
> extensions, such as:...
>
> I prefer specifying the parameters in the command for two primary reasons.
>
> 1) By requiring a client to use OPTS to specify output type and resolution
> the client and server must exchange this information in a separate command.
> Commands require a handshake and consequently some latency between the
> server and client for the exchange.  Depending on many different factors this
> latency, even on a fast connection, can be noticeable.  If the client wants different
> sized images frequently, let's say for every thumbnail image, it would be
> even more noticeable.  The bandwidth required to specify 10 bytes or less as a
> parameter to the command is trivial by comparison even on the slowest
> connections.
Sure, but why would the client want differently sized images frequently?
I think the client would only need to state it once, perhaps with a
change on
window resize. The number of thumbnails on a typical case would be much
larger.


> 2) By requiring a client to use OPTS to identify the parameters, both the client
> and the server must maintain the parameters for this command, more-or-less
> as a state.  I'm a big fan of keeping things very simple.
There is a trade off here. Although it is tempting to not store anything
at the server
for this, I still consider that using OPTS is a better route.

> 3) End-user support is easier when parameters are specified with the command.
> When end-users or customers have problems they'll often provide a portion of a
> log to identify what is going on with the communication between the server and
> client.  Technicians analyzing the log may not have all of the required information
> regarding the THMB command.  With the parameters being issued with the
> command analysis is far simpler and accurate.
The server could repeat the options in the 150 response if it is deemed
needed for
user support.


>> There should be a note about the potential security issues of the THMB
> command. Vulnerabilities processing images are common.
>
> Could you give me some examples or how you would like to see this worded
> and where you would like to see this placed in the document?

Doing a bit of googling for image vulnerabilities:
http://en.wikipedia.org/wiki/Windows_Metafile_vulnerability
http://blogs.techrepublic.com.com/itdojo/?p=892
http://www.sophos.com/pressoffice/news/articles/2004/09/va_critical16sep04.html
http://www.kb.cert.org/vuls/id/680620
http://www.kb.cert.org/vuls/id/238678
http://www.libpng.org/pub/png/libpng.html
http://secunia.com/advisories/27213/
http://hypersecurity.blogspot.com/2010/03/cve-2010-0188-adobe-reader-tiff.html

Vulnerabilities in image processing are quite bad, because it is easy to
make a client
render an image.THMB adds image rendering to ftp servers, which have a
great
exposure to the public.
These vulnerabilities often allow arbitrary code execution, but even a
DoS would be
bad for a ftp server. Most importantly, an attacker must not be able to
get LocalSystem/root
access on a server by just uploading a malicious image. Not even if the
fault lies on
some OS-provided library used for the thumbnailing.

I suppose the appropiate section is the security one, with a note to it
from THMB.
I don't know if it should be introduced by noting how thumbnailing adds
a significant
amount of code and how image vulnerabilities appear from time to time.

The main piece could be similar to this:
> Server implementations should be prepared in advance to mitigate
> vulnerabilities in
> the libraries used for thumbnailing. Servers are encouraged to perform
> all thumbnailing
> operations in a low-privilege process isolated from the server one.

Best regards


From keisial@gmail.com  Wed Nov 24 12:41:09 2010
Return-Path: <keisial@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 BE78528C13A for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 12:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=0.299,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
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 ALhCfiTepuJ2 for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 12:41:09 -0800 (PST)
Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by core3.amsl.com (Postfix) with ESMTP id 67E1C28C10B for <ftpext@ietf.org>; Wed, 24 Nov 2010 12:41:08 -0800 (PST)
Received: by wwb24 with SMTP id 24so129828wwb.34 for <ftpext@ietf.org>; Wed, 24 Nov 2010 12:42:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=SEaT1gWxhwEdJNTUDzxLnWdQlkGXjNNhorWY6bqiUDo=; b=b4GTNsbhkKXSBrB1/BWN1Tl6Iw8ER7Ns7KYjzSisE9IKCdVEw5eItuGQ6/jWcS0yky EW7YoUMPkkDyEf3FCcws7WDMbmvVNAwyhTqvNNQ3N7XUWzEitLjLY3LPyoFhtJFVlC3b 9adzd3KOeEKyppjLMeveBpNTybF9xNAo+kjQ4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=Lc7t6uNY7pzJViO+s2mJFT8hgmdu/7YZ4UVqV/QSBBrxNL/PgwyhbTfx4Lx5+bwtR7 dBOowHO3YdzNSB36Ef278ALYzRsnyR2MvfpO0qZsAw1wdEc5q9gAnn7rR0QeAaSaiq32 FORqj0vl81dsbD1Zpy3FIq9t/Y3H8r2B/eU0s=
Received: by 10.216.87.20 with SMTP id x20mr3091379wee.52.1290631327567; Wed, 24 Nov 2010 12:42:07 -0800 (PST)
Received: from [192.168.1.26] (225.red-80-28-70.adsl.dynamic.ccgg.telefonica.net [80.28.70.225]) by mx.google.com with ESMTPS id x3sm3679295wes.22.2010.11.24.12.42.05 (version=SSLv3 cipher=RC4-MD5); Wed, 24 Nov 2010 12:42:06 -0800 (PST)
Message-ID: <4CED78AF.8040707@gmail.com>
Date: Wed, 24 Nov 2010 21:42:23 +0100
From: "=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=" <keisial@gmail.com>
User-Agent: Thunderbird
MIME-Version: 1.0
To: Damin <damin@emuxperts.net>
References: <A5FC996C3C37DC4DA5076F1046B5674C442CE618@TK5EX14MBXC125.redmond.corp.microsoft.com>	<D2BD569FC8F4431E85F609B71E61EB79@rhinooffice.net>	<A5FC996C3C37DC4DA5076F1046B5674C442E8816@TK5EX14MBXC127.redmond.corp.microsoft.com>	<AANLkTi=Mm9U2ghmnNkD62AF=JZPB75fzwhUjykb2p+=0@mail.gmail.com> <AANLkTi=q1tFsjOHKZruoJF_0mjFTg8XemD6i9dOjJv6d@mail.gmail.com>
In-Reply-To: <AANLkTi=q1tFsjOHKZruoJF_0mjFTg8XemD6i9dOjJv6d@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040306030603050201050908"
Cc: ftpext@ietf.org
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 24 Nov 2010 20:41:10 -0000

This is a multi-part message in MIME format.
--------------040306030603050201050908
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Damin wrote:
> I might also point out that there could be a big problem with this
> command. How do we know the aspect ratio of the original image? We
> canÂīt really specify an appropriate thumb size without knowing that
> information (stretchy images, anyone?). I think this can be solved
> with some appropriate commands.

Knowing the image size is much easier than knowing how to create a
thumbnail for it. Note that the library used for thumbnailing may
already take that into account.

When given the command "THMB PNG 20 40 foo.gif" a conformant could just
shell out executing "|convert |foo.gif|-resize 20x40 thumb.png|"


--------------040306030603050201050908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Damin wrote:<br>
    <blockquote
      cite="mid:AANLkTi=q1tFsjOHKZruoJF_0mjFTg8XemD6i9dOjJv6d@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">I might also point out that there could
        be a big problem with this command. How do we know the aspect
        ratio of the original image? We canÂīt really specify an
        appropriate thumb size without knowing that information
        (stretchy images, anyone?). I think this can be solved with some
        appropriate commands.<br>
      </div>
    </blockquote>
    <br>
    Knowing the image size is much easier than knowing how to create a
    thumbnail for it. Note that the library used for thumbnailing may
    already take that into account.<br>
    <br>
    When given the command "THMB PNG 20 40 foo.gif" a conformant could
    just shell out executing "<code>convert </code>foo.gif<code>
      -resize 20x40 thumb.png</code>"<br>
    <br>
  </body>
</html>

--------------040306030603050201050908--

From Internet-Drafts@ietf.org  Wed Nov 24 14:45:24 2010
Return-Path: <Internet-Drafts@ietf.org>
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 41DEC3A69D1; Wed, 24 Nov 2010 14:45:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level: 
X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 eaJ8Wm7Vx7h0; Wed, 24 Nov 2010 14:45:12 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE7653A69E3; Wed, 24 Nov 2010 14:45:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101124224501.31531.96663.idtracker@localhost>
Date: Wed, 24 Nov 2010 14:45:01 -0800
Cc: ftpext@ietf.org
Subject: [ftpext] I-D Action:draft-ietf-ftpext2-hash-00.txt
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, 24 Nov 2010 22:45:25 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the FTP Extensions, 2nd edition Working Group of the IETF.


	Title           : File Transfer Protocol HASH Command for Cryptographic Hashes
	Author(s)       : A. Bryan, et al.
	Filename        : draft-ietf-ftpext2-hash-00.txt
	Pages           : 15
	Date            : 2010-11-24

The File Transfer Protocol does not offer any method to verify the
integrity of a transferred file, nor can two files be compared
against each other without actually transferring them first.
Cryptographic hashes are a possible solution to this problem.  In the
past, several attempts have been made to add commands to obtain
checksums and hashes, however none have been formally specified,
leading to non-interoperability and confusion.  To solve these
issues, this document specifies a new FTP command to be used by
clients to request cryptographic hashes of files.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ftpext2-hash-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-ftpext2-hash-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-11-24143702.I-D@ietf.org>


--NextPart--

From lothar@kimmeringer.de  Wed Nov 24 16:14:25 2010
Return-Path: <lothar@kimmeringer.de>
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 1348F3A6A92 for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 16:14:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=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 SCYkBXFfhD-R for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 16:14:24 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by core3.amsl.com (Postfix) with ESMTP id 19F843A69D8 for <ftpext@ietf.org>; Wed, 24 Nov 2010 16:14:23 -0800 (PST)
Received: from [192.168.1.20] (mnch-5d85fe93.pool.mediaWays.net [93.133.254.147]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0M940H-1P8zyA1P3N-00CxLW; Thu, 25 Nov 2010 01:15:23 +0100
Message-ID: <4CEDAA9A.8030303@kimmeringer.de>
Date: Thu, 25 Nov 2010 01:15:22 +0100
From: Lothar Kimmeringer <lothar@kimmeringer.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: ftpext@ietf.org
References: <20101124224501.31531.96663.idtracker@localhost>
In-Reply-To: <20101124224501.31531.96663.idtracker@localhost>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:JzUHeHCwMFmWel5KRMz89gDvz/uLncV/pAxEiifwDRj gS4k883yL2K3AVCpy+ehEIY+SzkiB6/NtgClf8J6SmrTSAW4cL Fqjj8kk8bk0Bo+h++5ZE5gum82zGJEDBsfDK5tmiRmxym2xc8y xN7edGvhXdmYn3/if+NV/g/ZJ7sbgQGbPEo8I13wSA6DwoB8m7 LS56lXrkuR9WAhA72hKKg==
Subject: Re: [ftpext] I-D Action:draft-ietf-ftpext2-hash-00.txt
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: Thu, 25 Nov 2010 00:26:16 -0000

Hello,

just being added to the maillist and already having a first question ;-)

Am 24.11.2010 23:45, schrieb Internet-Drafts@ietf.org:
> The File Transfer Protocol does not offer any method to verify the
> integrity of a transferred file, nor can two files be compared
> against each other without actually transferring them first.

[...]

> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ftpext2-hash-00.txt

I read the draft and tried to find the reason by searching the
archive. Why are startpoint and endpoint (SP and EP) missing?
The options are even mentioned in Appendx B. Adding these
options would e.g. allow to implement distributed downloads where
parts of the same file can be downloaded from different mirror-
servers at the same time checking the hash of each part.

In case you want to add another entry to Appendix B:
Lobster IntegrationServer (supports XCRC, XSHA1, XMD5; all with
SP and EP).


Best regards,

Lothar Kimmeringer
-- 
Lothar Kimmeringer                E-Mail: spamfang@kimmeringer.de
                PGP-encrypted mails preferred (Key-ID: 0x8BC3CD81)

Always remember: The answer is forty-two, there can only be wrong
                  questions!

From anthonybryan@gmail.com  Wed Nov 24 16:41:08 2010
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 A13653A6A9A for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 16:41:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.754
X-Spam-Level: 
X-Spam-Status: No, score=-2.754 tagged_above=-999 required=5 tests=[AWL=-0.155, 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 thbv3eY1cIkQ for <ftpext@core3.amsl.com>; Wed, 24 Nov 2010 16:41:05 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 337DB3A69E1 for <ftpext@ietf.org>; Wed, 24 Nov 2010 16:41:05 -0800 (PST)
Received: by iwn40 with SMTP id 40so399549iwn.31 for <ftpext@ietf.org>; Wed, 24 Nov 2010 16:42:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=B1h6I4Jv8+2Xr656uQs13ir8hkpAsc5v3CRqLvN0XnU=; b=EaO+1jqLjBHJiyoW4MszwPv6mwCrByVsR3qRpOlaGaIpIYu461iSONAhN+BOAwxSGu EapNJiRLHr0f3DrFNszUJymL2rjXlTCNBcw1AKlRfhm2HYchen00Kg6eq1GlYuvV9arD izk6phCND43kOsPq7mTiiibH4x+L6O8R3lcuY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=kclQ9z3PgOwG3ExPlFRB+LZuODzyvR8JMfvuZc7dYYItTbPkLQ58GJfTCPwy6TrEeP vjelOaA+CCIqfR+o+dbfe3kQovTR96mPPArZa4HlBA9PXRC27Umx4wzdVgt+VNnsKwPr ZE5YJ3IDPlyqu96+rqUirpn/7XTW0sQdfK5eU=
MIME-Version: 1.0
Received: by 10.231.19.74 with SMTP id z10mr46072iba.120.1290645724628; Wed, 24 Nov 2010 16:42:04 -0800 (PST)
Received: by 10.231.16.196 with HTTP; Wed, 24 Nov 2010 16:42:04 -0800 (PST)
Date: Wed, 24 Nov 2010 19:42:04 -0500
Message-ID: <AANLkTikWo4nuvVmrLr6CcGxwYCDVFak+7cqpwkSzvanN@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [ftpext] WG priority: draft-hethmon-mcmurray-ftp-hosts
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: Thu, 25 Nov 2010 00:41:08 -0000

HOST is a mature draft, and as you can see from the dates in the
charter, there are only a few months left til we plan to have it
submitted to the IESG.

Nov 2010 - Submit 'File Transfer Protocol HOST Command for Virtual
Hosts' as working group item
Dec 2010 - Working group Last Call of HOST document
Jan 2011 - Submit 'File Transfer Protocol HOST Command for Virtual
Hosts' to the IESG for consideration as a Proposed Standard

please take the time to review and comment on it.

http://tools.ietf.org/html/draft-hethmon-mcmurray-ftp-hosts

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

From anthonybryan@gmail.com  Thu Nov 25 15:51:27 2010
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 528093A6AEE for <ftpext@core3.amsl.com>; Thu, 25 Nov 2010 15:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.744
X-Spam-Level: 
X-Spam-Status: No, score=-2.744 tagged_above=-999 required=5 tests=[AWL=-0.145, 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 Y29TeukdzJ1u for <ftpext@core3.amsl.com>; Thu, 25 Nov 2010 15:51:26 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id E8B1B3A69B5 for <ftpext@ietf.org>; Thu, 25 Nov 2010 15:51:25 -0800 (PST)
Received: by ewy8 with SMTP id 8so761318ewy.31 for <ftpext@ietf.org>; Thu, 25 Nov 2010 15:52:27 -0800 (PST)
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=F1AASEqC7tsegpsTjpWt7jwp+oCIqJ5QpOBNaJVGF6Y=; b=UYIx0X4qir502+SGEWGNLBFLr9mSY6INmVDGgC+iiNHz7uknCSfRNVwuugsy74UsX+ LVKwGCwGS2xWrCKfI+1HoHwLiwsBb8CUgmLO4/T0mD5/3qpQ2NB/D/lc4eHJkbgbfxBt /bV1icQa+/RCK1n0LJyyXljcae54Mjss1mcfQ=
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=c5aGMBLeG41IZSQdu08laQr7y03xMIlUTDeG5Emi+xAiqYL5/urz+i9+yL5AYPBr23 fpsvOZWsULgal+b8OW38sACswhV9RohjxBnyqpWIXFbs7PXa51bcMslqNp9WvUesyIBY vWIfF8MvOnlWGntF1GhrqQN4UWRVnEuR8vfYs=
MIME-Version: 1.0
Received: by 10.213.33.133 with SMTP id h5mr3142841ebd.89.1290729146046; Thu, 25 Nov 2010 15:52:26 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Thu, 25 Nov 2010 15:52:25 -0800 (PST)
In-Reply-To: <4CEDAA9A.8030303@kimmeringer.de>
References: <20101124224501.31531.96663.idtracker@localhost> <4CEDAA9A.8030303@kimmeringer.de>
Date: Thu, 25 Nov 2010 18:52:25 -0500
Message-ID: <AANLkTik8Bv9YKo+uPt0ntk9OS0qQW2T5_RJ56CFZxMnS@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Lothar Kimmeringer <lothar@kimmeringer.de>, mb@smartftp.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] I-D Action:draft-ietf-ftpext2-hash-00.txt
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: Thu, 25 Nov 2010 23:51:27 -0000

On Wed, Nov 24, 2010 at 7:15 PM, Lothar Kimmeringer
<lothar@kimmeringer.de> wrote:
> Hello,
>
> just being added to the maillist and already having a first question ;-)

welcome, thanks for joining us!

> Am 24.11.2010 23:45, schrieb Internet-Drafts@ietf.org:
>>
>> The File Transfer Protocol does not offer any method to verify the
>> integrity of a transferred file, nor can two files be compared
>> against each other without actually transferring them first.
>
> [...]
>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-ftpext2-hash-00.txt
>
> I read the draft and tried to find the reason by searching the
> archive. Why are startpoint and endpoint (SP and EP) missing?

good question!

as you say, some of the other commands (XCRC, XMD5, XSHA1) support
partial file hashing.

I remember this was on our list of known issues, and we authors
brought it up a number of times. we never received any feedback on it
(except for Mat from SmartFTP on his forum who was for it), so it was
dropped.

[for everyone's info, some of the older FTP drafts like HASH that were
around before this mailing list were discussed on apps-discuss (going
back to March for HASH):
http://www.ietf.org/mail-archive/web/apps-discuss/current/maillist.html
]

> The options are even mentioned in Appendx B. Adding these
> options would e.g. allow to implement distributed downloads where
> parts of the same file can be downloaded from different mirror-
> servers at the same time checking the hash of each part.

that's exactly what we're doing in Metalink/XML & Metalink/HTTP (part
of the reason we needed HASH). mirrors, hashes, & signatures, are
offered over HTTP headers:
http://tools.ietf.org/html/draft-bryan-metalinkhttp (see section 7.1)

the Content-MD5 header which does partial hashes for HTTP is being
phased out I believe. we have the partial file hashes in the XML and
different ranges can be downloaded from mirrors...

> In case you want to add another entry to Appendix B:
> Lobster IntegrationServer (supports XCRC, XSHA1, XMD5; all with
> SP and EP).

done! it'll appear in the next version.
--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads

From keisial@gmail.com  Thu Nov 25 16:33:55 2010
Return-Path: <keisial@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 C08723A69B5 for <ftpext@core3.amsl.com>; Thu, 25 Nov 2010 16:33:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 xQBv3-F0O6Ab for <ftpext@core3.amsl.com>; Thu, 25 Nov 2010 16:33:53 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id EA88A3A69A0 for <ftpext@ietf.org>; Thu, 25 Nov 2010 16:33:52 -0800 (PST)
Received: by wwa36 with SMTP id 36so1449619wwa.13 for <ftpext@ietf.org>; Thu, 25 Nov 2010 16:34:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=HHHvw2paYEWmqoBPemFPHftvgVsLp8fli3IL63RxiJI=; b=FcXtg0vfeEd3ACeJEhpEosEYBjHMvM2yKDPzNNpYDPGzln2d8xlHUP1QPcSxrjUuM2 HKtxhCl+RqJ3hscyOOD+Mzt7Kuh1Fx6IBeEr0q912VY1CzaK3NBYaP1CcHRyfqMNQDWB VSZTDBaaT2zoMOFjM/GNqsABvzu6t0r+7vTL0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=Ye9WaUzh8FfU6+IHdCgHBslkopmkjlDreurjNw+sHxyxnrFnP5TS9wo+lNM0AtMJIv rk4gZ3OlmwTCrFroyZkF4/K56wWbxiRQl/wV8kI+u/rN0p6AdMRZGALJZ04m7HuX0+4g 7S94Z5s6ZYQ9FUR9y01jYuPxWfiUkV/hPoSaM=
Received: by 10.216.160.132 with SMTP id u4mr290528wek.11.1290731692876; Thu, 25 Nov 2010 16:34:52 -0800 (PST)
Received: from [192.168.1.26] (98.Red-83-54-100.dynamicIP.rima-tde.net [83.54.100.98]) by mx.google.com with ESMTPS id p4sm643073wej.4.2010.11.25.16.34.50 (version=SSLv3 cipher=RC4-MD5); Thu, 25 Nov 2010 16:34:51 -0800 (PST)
Message-ID: <4CEF00C0.5050200@gmail.com>
Date: Fri, 26 Nov 2010 01:35:12 +0100
From: "=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=" <keisial@gmail.com>
User-Agent: Thunderbird
MIME-Version: 1.0
To: Anthony Bryan <anthonybryan@gmail.com>, ftpext@ietf.org
References: <20101124224501.31531.96663.idtracker@localhost>	<4CEDAA9A.8030303@kimmeringer.de> <AANLkTik8Bv9YKo+uPt0ntk9OS0qQW2T5_RJ56CFZxMnS@mail.gmail.com>
In-Reply-To: <AANLkTik8Bv9YKo+uPt0ntk9OS0qQW2T5_RJ56CFZxMnS@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [ftpext] I-D Action:draft-ietf-ftpext2-hash-00.txt
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: Fri, 26 Nov 2010 00:33:55 -0000

Anthony Bryan wrote:
>> I read the draft and tried to find the reason by searching the
>> archive. Why are startpoint and endpoint (SP and EP) missing?
> good question!
>
> as you say, some of the other commands (XCRC, XMD5, XSHA1) support
> partial file hashing.
>
> I remember this was on our list of known issues, and we authors
> brought it up a number of times. we never received any feedback on it
> (except for Mat from SmartFTP on his forum who was for it), so it was
> dropped.
>
> [for everyone's info, some of the older FTP drafts like HASH that were
> around before this mailing list were discussed on apps-discuss (going
> back to March for HASH):
> http://www.ietf.org/mail-archive/web/apps-discuss/current/maillist.html
> ]

I also think it is interesting to have hashes of partial content.
They key piece is 'partial verification'. You could have distributed
downloads
from several mirrors without being able to separatedly hash each piece.
Hash the file on all the mirrors (so it's the same), download the pieces,
join, hash the final file. If it's good, ok. If not, redownload
*everything* again.
Which is exactly what you would have to do if you did a normal download from
the ftp.
You download a big file (eg. a DVD iso) and it fails verification (the
server hash
command is analogous to the checksums usually provided in the dowload page).
That file is quite worthless now, even if you know that the error will
probably be
just a couple of bytes.
Let's assume now that the ftp server allos a hash range command. Then,
instead
of redownloading everything, your client starts bisecting the file,
finds a 1K block
where your local copy differs, and redownloading it you're done.

A couple of requirements:
* The user should not be required to know the file size in advance.
* The protocol should allow a server allowing full file hashes but
rejecting partial hashes.


From mb@smartftp.com  Fri Nov 26 00:10:51 2010
Return-Path: <mb@smartftp.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 C14E93A6A57 for <ftpext@core3.amsl.com>; Fri, 26 Nov 2010 00:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  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 I5epe8KyZXDF for <ftpext@core3.amsl.com>; Fri, 26 Nov 2010 00:10:47 -0800 (PST)
Received: from mail.smartftp.com (mail.smartftp.com [75.126.59.172]) by core3.amsl.com (Postfix) with ESMTP id 3E5683A6988 for <ftpext@ietf.org>; Fri, 26 Nov 2010 00:10:46 -0800 (PST)
Received: from mx.smartsoft.local ([2002:4b7e:3bac::4b7e:3bac]) by mx.smartsoft.local ([2002:4b7e:3bac::4b7e:3bac]) with mapi; Fri, 26 Nov 2010 02:11:53 -0600
From: Mat Berchtold <mb@smartftp.com>
To: Anthony Bryan <anthonybryan@gmail.com>, Robert McMurray <robmcm@microsoft.com>
Date: Fri, 26 Nov 2010 02:11:42 -0600
Thread-Topic: [ftpext] Question about draft-bryan-ftp-hash-07
Thread-Index: Act7uBgiOrxcUhw5RhKMIKPLx+OxjARiPObg
Message-ID: <41871DBEA4CB724B93AC2D8CAADADBF41463C770CF@mx.smartsoft.local>
References: <A5FC996C3C37DC4DA5076F1046B5674C3D2B58B3@TK5EX14MBXC127.redmond.corp.microsoft.com> <AANLkTikG8XVKQ7pLq+bcGhAk=UrJiS05vbkib7jQde_Y@mail.gmail.com> <AANLkTi=kP7j1Q4JmWSeG-qsuCwGdWoAAGbujbpCjOERE@mail.gmail.com>
In-Reply-To: <AANLkTi=kP7j1Q4JmWSeG-qsuCwGdWoAAGbujbpCjOERE@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Fri, 26 Nov 2010 08:10:51 -0000

> the newest HASH draft uses a new code: 556.
Good idea. I have updated the proftpd mod_digest module to use the same err=
or code as well. I also plan to add support for the HASH command within the=
 next couple of weeks.

Mat

-----Original Message-----
From: Anthony Bryan [mailto:anthonybryan@gmail.com]=20
Sent: Thursday, 04 November, 2010 01:29
To: Robert McMurray; Mat Berchtold
Cc: ftpext@ietf.org
Subject: Re: [ftpext] Question about draft-bryan-ftp-hash-07

On Thu, Sep 16, 2010 at 1:28 AM, Anthony Bryan <anthonybryan@gmail.com> wro=
te:
> On Fri, Aug 20, 2010 at 6:01 PM, Robert McMurray <robmcm@microsoft.com> w=
rote:
>> With that in mind, I've been thinking through implementation scenarios i=
n the wake of the denial-of-service discussion that took place before IETF =
78. More specifically, I've thinking about a scenario where the maximum fil=
e size could be configured at the server, so HASH commands could be prevent=
ed from stealing too many server resources when larger files are involved. =
This is purely a server implementation detail that has nothing to do with t=
he draft with the exception of considering which reply code to return.
>>
>> Looking at section "3.4. HASH Command Errors" in the draft it would seem=
 that none of the 5yz errors that are listed would apply, but returning a 5=
04 reply might seem to make sense in this scenario. If so, would it be wort=
hwhile to add a statement like the following to the draft?
>>
>> =A0 The server-PI SHOULD reply with a 504 reply if the HASH command is
>> =A0 used on a file that cannot be processed for policy reasons. (For
>> =A0 example, the file size exceeds the server's hashing policy.)
>>
>> Or would a 4yz reply be better since this is a configurable option at th=
e server? Perhaps a 452 reply?
>
> revisiting this, Mathias Berchtold is an implementer (ProFTPD module=20
> mod_digest, http://www.smartftp.com/oss/proftpd/mod_digest.html ) of=20
> the alternate non-standard commands (XCRC, XMD5, XSHA1, SHA256) that=20
> HASH is trying to standardize.
>
> mod_digest uses 550 reply code for the case that Robert mentioned of a=20
> file not being allowed to be hashed because of a policy.
>
> "The DigestMaxSize directive configures the maximum number of bytes a=20
> single hash command is allowed to read from a file. If the number of=20
> bytes to be read from the file is greater than the configured limit=20
> the server will return an error. If no DigestMaxSize directive is=20
> configured, then there is no limit. It is stronly recommended to set=20
> an upper limit."
>
> R_550, "%s: Length (%zu) greater than " CONFIG_DIGEST_MAXSIZE " (%zu)=20
> config value", cmd->arg, lLength, lMaxSize);
>
> Mathias, any suggestions as an implementer?
>
> we use 550 already for file not found.
>
> =A0 =A0 =A0550 Requested action not taken.
> =A0 =A0 =A0 =A0 =A0File unavailable (e.g., file not found, no access).
>
> we don't seem to have a specific reply code that fits this case currently=
.
> should we mint a new reply code (55z since it's permanent & deals with=20
> file system) or use another existing code that isn't an exact fit?

the newest HASH draft uses a new code: 556.

http://tools.ietf.org/html/draft-bryan-ftp-hash

comments? here's the new text.

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

later:

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

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

From anthonybryan@gmail.com  Fri Nov 26 00:29:26 2010
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 EEF5E3A6A7D for <ftpext@core3.amsl.com>; Fri, 26 Nov 2010 00:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.735
X-Spam-Level: 
X-Spam-Status: No, score=-2.735 tagged_above=-999 required=5 tests=[AWL=-0.136, 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 1yDn6pQNAkf5 for <ftpext@core3.amsl.com>; Fri, 26 Nov 2010 00:29:25 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 2A8DF3A6A58 for <ftpext@ietf.org>; Fri, 26 Nov 2010 00:29:25 -0800 (PST)
Received: by ewy8 with SMTP id 8so877147ewy.31 for <ftpext@ietf.org>; Fri, 26 Nov 2010 00:30:27 -0800 (PST)
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=aoCWtWGaR2vXl5vyxzQl9D/uQ7uGKHKLsmC2LxphKhs=; b=EnuCkKnNRy7S+OQrxc0qgv/g2UWbOPdRSU996X6D2MObEwgTtqICqED25CoccfmFw4 aZkwgjC3eEX+4FzhYItVCmM/Xo6pnzPQ5Fwah+O3f8aA5XxqIqzKwIPgfLkWVMVBV7in 3qi8/euxC3aTkzkiMV+5gRtkOss9MoS1Ksp8E=
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=x7WSQ7KAUyuv3SYXoDCLgF/IUmEQo6nSHjFXFBQrNT+BSLwBh7mx9ZnqzdTg2KR7Jh x9TEawu6ML44H3LOY4BHcC9/Y3HZ43eUmu8ASsKJQnbg2pAjTkzQDBgoalMmTvpz4ceu 0Nbip7UXHh56psSD/w1FMgf4TtkkUPbCqm8yM=
MIME-Version: 1.0
Received: by 10.213.22.197 with SMTP id o5mr6051738ebb.89.1290760227383; Fri, 26 Nov 2010 00:30:27 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Fri, 26 Nov 2010 00:30:27 -0800 (PST)
In-Reply-To: <41871DBEA4CB724B93AC2D8CAADADBF41463C770CF@mx.smartsoft.local>
References: <A5FC996C3C37DC4DA5076F1046B5674C3D2B58B3@TK5EX14MBXC127.redmond.corp.microsoft.com> <AANLkTikG8XVKQ7pLq+bcGhAk=UrJiS05vbkib7jQde_Y@mail.gmail.com> <AANLkTi=kP7j1Q4JmWSeG-qsuCwGdWoAAGbujbpCjOERE@mail.gmail.com> <41871DBEA4CB724B93AC2D8CAADADBF41463C770CF@mx.smartsoft.local>
Date: Fri, 26 Nov 2010 03:30:27 -0500
Message-ID: <AANLkTikS+exC6fe+oexLbbLMKmS5rbCeXR64f6AGVzpe@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Mat Berchtold <mb@smartftp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ftpext@ietf.org" <ftpext@ietf.org>, Robert McMurray <robmcm@microsoft.com>, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
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: Fri, 26 Nov 2010 08:29:27 -0000

great, Mat, thanks a bunch! obviously there isn't a rush, but it will
be useful to have.

following that, (it was on apps-discuss but not mentioned here) we
have client (aria2) and server (FileZilla) implementations for
testing, albeit for the slightly different -02 draft.

aria2 client http://www.ietf.org/mail-archive/web/apps-discuss/current/msg0=
1497.html
FileZilla server
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01481.html

btw, if you have time Mat, can you reply to the partial file hash
thread (or here)?
I remember you felt strongly about including that feature.

On Fri, Nov 26, 2010 at 3:11 AM, Mat Berchtold <mb@smartftp.com> wrote:
>> the newest HASH draft uses a new code: 556.
> Good idea. I have updated the proftpd mod_digest module to use the same e=
rror code as well. I also plan to add support for the HASH command within t=
he next couple of weeks.
>
> Mat
>
> -----Original Message-----
> From: Anthony Bryan [mailto:anthonybryan@gmail.com]
> Sent: Thursday, 04 November, 2010 01:29
> To: Robert McMurray; Mat Berchtold
> Cc: ftpext@ietf.org
> Subject: Re: [ftpext] Question about draft-bryan-ftp-hash-07
>
> On Thu, Sep 16, 2010 at 1:28 AM, Anthony Bryan <anthonybryan@gmail.com> w=
rote:
>> On Fri, Aug 20, 2010 at 6:01 PM, Robert McMurray <robmcm@microsoft.com> =
wrote:
>>> With that in mind, I've been thinking through implementation scenarios =
in the wake of the denial-of-service discussion that took place before IETF=
 78. More specifically, I've thinking about a scenario where the maximum fi=
le size could be configured at the server, so HASH commands could be preven=
ted from stealing too many server resources when larger files are involved.=
 This is purely a server implementation detail that has nothing to do with =
the draft with the exception of considering which reply code to return.
>>>
>>> Looking at section "3.4. HASH Command Errors" in the draft it would see=
m that none of the 5yz errors that are listed would apply, but returning a =
504 reply might seem to make sense in this scenario. If so, would it be wor=
thwhile to add a statement like the following to the draft?
>>>
>>> =A0 The server-PI SHOULD reply with a 504 reply if the HASH command is
>>> =A0 used on a file that cannot be processed for policy reasons. (For
>>> =A0 example, the file size exceeds the server's hashing policy.)
>>>
>>> Or would a 4yz reply be better since this is a configurable option at t=
he server? Perhaps a 452 reply?
>>
>> revisiting this, Mathias Berchtold is an implementer (ProFTPD module
>> mod_digest, http://www.smartftp.com/oss/proftpd/mod_digest.html ) of
>> the alternate non-standard commands (XCRC, XMD5, XSHA1, SHA256) that
>> HASH is trying to standardize.
>>
>> mod_digest uses 550 reply code for the case that Robert mentioned of a
>> file not being allowed to be hashed because of a policy.
>>
>> "The DigestMaxSize directive configures the maximum number of bytes a
>> single hash command is allowed to read from a file. If the number of
>> bytes to be read from the file is greater than the configured limit
>> the server will return an error. If no DigestMaxSize directive is
>> configured, then there is no limit. It is stronly recommended to set
>> an upper limit."
>>
>> R_550, "%s: Length (%zu) greater than " CONFIG_DIGEST_MAXSIZE " (%zu)
>> config value", cmd->arg, lLength, lMaxSize);
>>
>> Mathias, any suggestions as an implementer?
>>
>> we use 550 already for file not found.
>>
>> =A0 =A0 =A0550 Requested action not taken.
>> =A0 =A0 =A0 =A0 =A0File unavailable (e.g., file not found, no access).
>>
>> we don't seem to have a specific reply code that fits this case currentl=
y.
>> should we mint a new reply code (55z since it's permanent & deals with
>> file system) or use another existing code that isn't an exact fit?
>
> the newest HASH draft uses a new code: 556.
>
> http://tools.ietf.org/html/draft-bryan-ftp-hash
>
> comments? here's the new text.
>
> =A0 =A0 =A0 =A0 =A0 The server-PI SHOULD reply with a 556 reply if the HA=
SH command is
> =A0 =A0 =A0 =A0 =A0 used on a file that cannot be processed for policy re=
asons. =A0(For
> =A0 =A0 =A0 =A0 =A0 example, if the file size exceeds the server's hashin=
g policy.)
>
> later:
>
> =A0 =A0 =A0 =A0 =A0 Server operators might wish to allow the HASH command=
 but restrict
> =A0 =A0 =A0 =A0 =A0 its use to certain files, for example, if the file si=
ze exceeds the
> =A0 =A0 =A0 =A0 =A0 server's hashing policy. =A0A client MUST be able to =
understand that
> =A0 =A0 =A0 =A0 =A0 refusal to process HASH commands may be permanent (if=
 indicated by a
> =A0 =A0 =A0 =A0 =A0 556 response) and will not be honoured later.
>
> --
> (( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
> =A0 )) Easier, More Reliable, Self Healing Downloads
>



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

From anthonybryan@gmail.com  Fri Nov 26 00:46:05 2010
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 54D9B3A6A63 for <ftpext@core3.amsl.com>; Fri, 26 Nov 2010 00:46:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.577
X-Spam-Level: 
X-Spam-Status: No, score=-2.577 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 cOGqRuX3sEeU for <ftpext@core3.amsl.com>; Fri, 26 Nov 2010 00:46:04 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 0A7463A69A6 for <ftpext@ietf.org>; Fri, 26 Nov 2010 00:46:03 -0800 (PST)
Received: by eyd10 with SMTP id 10so875634eyd.31 for <ftpext@ietf.org>; Fri, 26 Nov 2010 00:47:06 -0800 (PST)
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=R+oy6pMVzqKcEKnRkpICdgJwS+lmwOtwv5DU+qEUeO0=; b=Yp+cAW8beFisQaINWdrnO/qCBJkXSzCJ8crYo1p1WF5laZOb/JOBC+1CyA6+vV4Cew fboVBqFXCebGBI5ndY0qtWKkUvqQ2Xc8aJq9dhpWwCYUIggx/A9BF9T0iSVULfFIW3hZ UPr1rxFyi7/h96dO1P2yZhhly1uohlPm9GK2o=
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=DGxlZf8JEU3Y/wKOhJXZ6wU3HTZyu9x8o+F5p9xXF73PLHLzIDVk+XGjmM0+P0vw/r ecHZ95C4Zu3oe5G1cMxj7GIRQnqw3fMNxqzUyqpOeU7FJomQ087mYHMOn16ZYEcaXSBl ZlDO17ByurpH4fFsqBoPl+FpqM9ph9Ctg+LK4=
MIME-Version: 1.0
Received: by 10.213.22.197 with SMTP id o5mr6065859ebb.89.1290761226519; Fri, 26 Nov 2010 00:47:06 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Fri, 26 Nov 2010 00:47:06 -0800 (PST)
In-Reply-To: <4CEF00C0.5050200@gmail.com>
References: <20101124224501.31531.96663.idtracker@localhost> <4CEDAA9A.8030303@kimmeringer.de> <AANLkTik8Bv9YKo+uPt0ntk9OS0qQW2T5_RJ56CFZxMnS@mail.gmail.com> <4CEF00C0.5050200@gmail.com>
Date: Fri, 26 Nov 2010 03:47:06 -0500
Message-ID: <AANLkTimFeub1ynp4UcKAv84GP9f=gcG485jUgT82mB87@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= <keisial@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] I-D Action:draft-ietf-ftpext2-hash-00.txt
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: Fri, 26 Nov 2010 08:46:05 -0000

2010/11/25 =C1ngel Gonz=E1lez <keisial@gmail.com>:
> Anthony Bryan wrote:
>>> I read the draft and tried to find the reason by searching the
>>> archive. Why are startpoint and endpoint (SP and EP) missing?
>> good question!
>>
>> as you say, some of the other commands (XCRC, XMD5, XSHA1) support
>> partial file hashing.
>>
>> I remember this was on our list of known issues, and we authors
>> brought it up a number of times. we never received any feedback on it
>> (except for Mat from SmartFTP on his forum who was for it), so it was
>> dropped.
>>
>> [for everyone's info, some of the older FTP drafts like HASH that were
>> around before this mailing list were discussed on apps-discuss (going
>> back to March for HASH):
>> http://www.ietf.org/mail-archive/web/apps-discuss/current/maillist.html
>> ]
>
> I also think it is interesting to have hashes of partial content.
> They key piece is 'partial verification'. You could have distributed
> downloads
> from several mirrors without being able to separatedly hash each piece.
> Hash the file on all the mirrors (so it's the same), download the pieces,
> join, hash the final file. If it's good, ok. If not, redownload
> *everything* again.
> Which is exactly what you would have to do if you did a normal download f=
rom
> the ftp.
> You download a big file (eg. a DVD iso) and it fails verification (the
> server hash
> command is analogous to the checksums usually provided in the dowload pag=
e).
> That file is quite worthless now, even if you know that the error will
> probably be
> just a couple of bytes.
> Let's assume now that the ftp server allos a hash range command. Then,
> instead
> of redownloading everything, your client starts bisecting the file,
> finds a 1K block
> where your local copy differs, and redownloading it you're done.

yep, the partial file hashes are for download repair.

that's what we use them for in Metalink, but instead of being able to
request the hash for a specific range, the hashes are pre-computed &
stored in XML for (usually 256k but can be whatever size) chunks,
instead of dynamically requested.

as mentioned, Content-MD5 (RFC 1864) requests partial hashes for HTTP,
and Instance Digests (RFC 3230) for full file hashes.

> A couple of requirements:
> * The user should not be required to know the file size in advance.

you mean the client? why? it should just assume from a starting point
to the end of the file?

> * The protocol should allow a server allowing full file hashes but
> rejecting partial hashes.

right, partial file hashing would be OPTIONAL.
--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads

From keisial@gmail.com  Fri Nov 26 08:12:23 2010
Return-Path: <keisial@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 DC02C28C0EA for <ftpext@core3.amsl.com>; Fri, 26 Nov 2010 08:12:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 pgs9al3VVW6b for <ftpext@core3.amsl.com>; Fri, 26 Nov 2010 08:12:22 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id B5E1028C0D7 for <ftpext@ietf.org>; Fri, 26 Nov 2010 08:12:21 -0800 (PST)
Received: by wwa36 with SMTP id 36so2175308wwa.13 for <ftpext@ietf.org>; Fri, 26 Nov 2010 08:13:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=LAPJPryCDJQA/5bDU0VQLyqe1ZpWhZLx3wfrpAHi/Us=; b=jlyM9HlwBebnajn5lrE6YoA1z92g3YKHQb29g4R9q6RdG+V0LIkqKAacmQ67QAXnD2 qIcs4A//NNiJeaBz4wQirnPHIGQBkEZ/3M8hx7+bQde1u7inpBdqkJ+QPKE15/jIQLXZ Fhstqt552AqtkCNShMUVBNDAvd51MhTnku/xo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=p75lzolIOPmGO+JtUdJQwbZNxzfjVw4e+BeWCQ5fCwNDhRdNmeFY7zO7RPbLho1tXc Ee6PE2t6GTIu1dlVr2P6yXSMLqkG4JNEbJ2Sn9iKRQWvvjbmSYLkM+M5TFwMcznweUkV MA9vMVCZTtr/WAnp6Hc5IbsCZWj4M9go0Acc4=
Received: by 10.227.145.68 with SMTP id c4mr2610301wbv.42.1290788004270; Fri, 26 Nov 2010 08:13:24 -0800 (PST)
Received: from [192.168.1.26] (145.Red-83-49-202.dynamicIP.rima-tde.net [83.49.202.145]) by mx.google.com with ESMTPS id x6sm997430weq.37.2010.11.26.08.13.21 (version=SSLv3 cipher=RC4-MD5); Fri, 26 Nov 2010 08:13:23 -0800 (PST)
Message-ID: <4CEFDCB9.6010203@gmail.com>
Date: Fri, 26 Nov 2010 17:13:45 +0100
From: "=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=" <keisial@gmail.com>
User-Agent: Thunderbird
MIME-Version: 1.0
To: Anthony Bryan <anthonybryan@gmail.com>, ftpext@ietf.org
References: <20101124224501.31531.96663.idtracker@localhost>	<4CEDAA9A.8030303@kimmeringer.de>	<AANLkTik8Bv9YKo+uPt0ntk9OS0qQW2T5_RJ56CFZxMnS@mail.gmail.com>	<4CEF00C0.5050200@gmail.com> <AANLkTimFeub1ynp4UcKAv84GP9f=gcG485jUgT82mB87@mail.gmail.com>
In-Reply-To: <AANLkTimFeub1ynp4UcKAv84GP9f=gcG485jUgT82mB87@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [ftpext] I-D Action:draft-ietf-ftpext2-hash-00.txt
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: Fri, 26 Nov 2010 16:12:24 -0000

Anthony Bryan wrote:
>> * The user should not be required to know the file size in advance.
> you mean the client? why? it should just assume from a starting point
> to the end of the file?
Sorry, I wasn't clear here. The client should not be required to know
the file size
for getting *the full hash*. If it is intended to convert the full file
hash case into
'partial hash from 0 to filesize', there should be some magic value for
the end of file.


From tatsuhiro.t@gmail.com  Sun Nov 28 01:40:11 2010
Return-Path: <tatsuhiro.t@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 A95C83A69DD for <ftpext@core3.amsl.com>; Sun, 28 Nov 2010 01:40:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 LRpz8CkIBK2B for <ftpext@core3.amsl.com>; Sun, 28 Nov 2010 01:40:10 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id AAADD3A697E for <ftpext@ietf.org>; Sun, 28 Nov 2010 01:40:09 -0800 (PST)
Received: by fxm9 with SMTP id 9so2690372fxm.31 for <ftpext@ietf.org>; Sun, 28 Nov 2010 01:41:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=nKzEScdqUJ9AqSMmZYJewwxd2MMYBWow/ckjUtzPoTk=; b=mD3Iw30Jmu1MLV7SC0F7YIbJ12tp9KykjHKP/j8+oK1E2ozJYSMfVON0bl/RClztEh VsAyHNXWfh4STxLCVvjj8LXJqBuk5iLoug9v+Ldr0I40h+VY96piS7JJ2qqJhaMfj6dP HacziMUApBIjWhL7VxR+FgawhPqMXWpNiQyso=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=fkvEBEBad7qdFmIP2sScV2zs1FFq5ISpIuXGsrVwmOe5szud4ZxCEQhCoGeWssaNn8 LO1K2zD+SGDeQ8xxD31A8G4tuApQKZdSMDw+BP+sPrjGceM43yp80dkcDoGwvjdMc4jh PLOUPuqkAFjsW81KusQ841V5ti4zxFdfYS2NA=
Received: by 10.223.71.199 with SMTP id i7mr4071688faj.57.1290937276147; Sun, 28 Nov 2010 01:41:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.101.205 with HTTP; Sun, 28 Nov 2010 01:40:55 -0800 (PST)
From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Sun, 28 Nov 2010 18:40:55 +0900
Message-ID: <AANLkTi=pBbGPtyjuU6NF32bRK3nz3i2k3ugDtCjF0SAS@mail.gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [ftpext]  draft-peterson-streamlined-ftp-command-extensions
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: Sun, 28 Nov 2010 09:40:11 -0000

Hi,

> DSIZ command

If a directory specified in DSIZ command contains symbolic links,
does this command calculate linked target file, or just size of a
symbolic link file itself?

Also, if a symbolic link 'foolink' which links to directory foo is
given in DSIZ command,
does server returns 550 error because it is not directory?

>DSIZ command should not consider this in its response, instead
> leaving it up to the underlying file system to determine the number
> of octets occupied by the files.

About phrase "the number of octets occupied by the files":
Some file systems(e.g. ext4) supports sparse file, and
space that those files actually occupy are sometimes much more smaller than
 'ls' shows its file size. For those files, does DSIZ return the octets occupied
by the files? I think if the user use DSIZ instead of recursive SIZE command,
they want file size normally shown by 'ls', not occupied octets in file system.

Sorry if this has been discussed already.

Best regards,

Tatsuhiro Tsujikawa

From tatsuhiro.t@gmail.com  Sun Nov 28 08:20:22 2010
Return-Path: <tatsuhiro.t@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 D8B4228C102 for <ftpext@core3.amsl.com>; Sun, 28 Nov 2010 08:20:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_101=0.6]
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 qlC6xPSCfCjm for <ftpext@core3.amsl.com>; Sun, 28 Nov 2010 08:20:22 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id D460728C0FC for <ftpext@ietf.org>; Sun, 28 Nov 2010 08:20:21 -0800 (PST)
Received: by fxm9 with SMTP id 9so2835288fxm.31 for <ftpext@ietf.org>; Sun, 28 Nov 2010 08:21:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=HqvRnvqfKpEm3JH9kK8CBooDsPGT2HTYa/PLlSes+e8=; b=rRtOoTO+qnPW1JDL7khoJ7jwQRAoMmPMVhmw9pScKOOcFkngt4FPunojLIaXoKeBd6 XXVKkd5XlPvhvLkkgRjm4mdRJOLpRUVicqmRWxeImI/+IRo+ro5RVqVL7gcwGYsvTEs9 bCjROTI2z9Pa+IF2zmNXUziCjB5jV39krvcW4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=fgHrf07QpV/o0puuj8oUyiDfZ1asTQpFxEYgDv/JXPbclEFVTVR7+nzNd1atQIPj8T g1npt8217fKm7cj1bWamNvkDqdDzl8NNxIBm0kqiQqrl8P8ELfFDBUo9YytGOwJgiAJk XbDLsybM+bxreTxIkwmYsE4Ml6AWcVFzxhjx8=
Received: by 10.223.101.131 with SMTP id c3mr4403890fao.95.1290961289102; Sun, 28 Nov 2010 08:21:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.101.205 with HTTP; Sun, 28 Nov 2010 08:21:08 -0800 (PST)
From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Mon, 29 Nov 2010 01:21:08 +0900
Message-ID: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [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: Sun, 28 Nov 2010 16:20:22 -0000

Hi,

In FTP, user can set start byte of transfer by REST command.
But it seems it lacks the feature to set end byte of transfer, like
HTTP's Range request.
Does it really lack this feature? Are there any ftp server/client support this?

Issuing ABOR command is workaround but sometimes it does not stop immediately
and unused bytes are transfered.
Another possible workaround is that just closing data connection and
wait for reply
from control connection(I've not tested this yet).

A example of utilization this feature is Metalink download.
In Metalink, it contains several URIs for one file. So we can download it from
several sources. From each server, client downloads non-overlapping segment.
For example, when downloading 1 file using 2 FTP servers.
We can use REST command for second half of the download and it downloads given
 point to the end of file. This is fine. The control connection can be reused.
For the first half of the download, since we cannot set end byte, we
have to close connection
entirely after first half of file is downloaded. The control
connection cannot be reused this time.
We can use ABOR, but it has drawback as I mentioned earlier.

Best regards,

Tatsuhiro Tsujikawa

From john-ietf@jck.com  Sun Nov 28 15:39:46 2010
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 E00A828B56A for <ftpext@core3.amsl.com>; Sun, 28 Nov 2010 15:39:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 YIKVH-jcyR4G for <ftpext@core3.amsl.com>; Sun, 28 Nov 2010 15:39:43 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 6DF593A69A7 for <ftpext@ietf.org>; Sun, 28 Nov 2010 15:39:43 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PMqrS-000B84-0U; Sun, 28 Nov 2010 18:40:50 -0500
Date: Sun, 28 Nov 2010 18:40:49 -0500
From: John C Klensin <john-ietf@jck.com>
To: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>, ftpext@ietf.org
Message-ID: <8F4BB4C1C1895841414414D0@PST.JCK.COM>
In-Reply-To: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com>
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
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: Sun, 28 Nov 2010 23:39:46 -0000

--On Monday, November 29, 2010 01:21 +0900 Tatsuhiro Tsujikawa
<tatsuhiro.t@gmail.com> wrote:

> Hi,
> 
> In FTP, user can set start byte of transfer by REST command.

This is a misuse of the intent of the command and some
historical FTP implementations won't permit it.  In particular,
REST is defined only for Block and Compressed modes (neither of
which is widely used these days) and starts only from a
server-specified checkpoint marker.   While I can believe that
some implementations might construe REST followed by an integer
in stream mode as a byte offset to be used in a subsequent STOR
or RETR command, that usage is certainly not guaranteed by
anything in RFC 959.

Note that design is quite intentional and necessary to reflect a
wide variety of different file system organizations, including
files that are not organized sequentially on the remote or local
host.

As the most trivial example, FTP doesn't even guarantee that the
bits of a sequential file will be transferred in the order in
which they appear in their original form.

> But it seems it lacks the feature to set end byte of transfer,
> like HTTP's Range request.
> Does it really lack this feature? Are there any ftp
> server/client support this?

It seems to me that you are looking for a remote file management
protocol that supports a much more specific file abstraction
than is the case with FTP, which is purely and simply a file
transfer protocol for entire files, not fragments of them.  HTTP
does assume a particular type of file organization model, which
is one reason byte-oriented fragment identifiers work.  If that
model serves your needs, why not just use HTTP?   If you need
the more general organizational model of FTP, you will need to
either transfer the entire file and then extract whatever you
need (using whatever local access method is appropriate to that
file) or find/ use/ design a file management protocol, rather
than a file transfer one.

> A example of utilization this feature is Metalink download.
> In Metalink, it contains several URIs for one file. So we can
> download it from several sources. From each server, client
> downloads non-overlapping segment. For example, when
> downloading 1 file using 2 FTP servers. We can use REST
> command for second half of the download and it downloads given
>  point to the end of file. This is fine. The control
> connection can be reused. For the first half of the download,
> since we cannot set end byte, we have to close connection
> entirely after first half of file is downloaded. The control
> connection cannot be reused this time.
> We can use ABOR, but it has drawback as I mentioned earlier.

And, again, why not use HTTP?

    john






From Richard.Koenning@ts.fujitsu.com  Mon Nov 29 05:48:29 2010
Return-Path: <Richard.Koenning@ts.fujitsu.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 5042028C11D for <ftpext@core3.amsl.com>; Mon, 29 Nov 2010 05:48:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 rusjVigZTBaw for <ftpext@core3.amsl.com>; Mon, 29 Nov 2010 05:48:28 -0800 (PST)
Received: from dgate10.ts.fujitsu.com (dgate10.ts.fujitsu.com [80.70.172.49]) by core3.amsl.com (Postfix) with ESMTP id C1B9C28C11B for <ftpext@ietf.org>; Mon, 29 Nov 2010 05:48:27 -0800 (PST)
DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Message-ID:Date:From:Reply-To:Organization: User-Agent:X-Accept-Language:MIME-Version:To:Subject: References:In-Reply-To:Content-Type: Content-Transfer-Encoding; b=vCL8lP20w3Qjhf3hKxV7zOQXSUcjM14mJmpACLI0GZ0rVuuLbP27dEg8 rVZbfzOIfFhdHsEiMC1t4OmR5drARVGY4pcc1IrbavGclUMqysqLAfl2a BY99pfnZYGBx0lykDvwB46R/Yoj+Xs+kyS7XaiHdCpHIncGgipE8jTg3g 9XA1DJKI3l59VAv2rYR5PUy9bAIuWLcAt30pkLya5sx61eWbf5lGoQSDP ifgMGV9cuy0nvFepiicXJ9vNVo39S;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=Richard.Koenning@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1291038578; x=1322574578; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; z=Message-ID:=20<4CF3AF6F.6070307@ts.fujitsu.com>|Date:=20 Mon,=2029=20Nov=202010=2014:49:35=20+0100|From:=20Richard =20Koenning=20<Richard.Koenning@ts.fujitsu.com>|Reply-To: =20=20Richard.Koenning@ts.fujitsu.com|MIME-Version:=201.0 |To:=20"ftpext@ietf.org"=20<ftpext@ietf.org>|Subject:=20R e:=20[ftpext]=20End=20byte=20of=20transfer=20in=20FTP |References:=20<AANLkTi=3D_OsGPMsC=3DBHtOyHzTTM5vJ1=3DyW9 fYk_Tp1xm7@mail.gmail.com>=20<8F4BB4C1C1895841414414D0@PS T.JCK.COM>|In-Reply-To:=20<8F4BB4C1C1895841414414D0@PST.J CK.COM>|Content-Transfer-Encoding:=20quoted-printable; bh=1bH1pJkSVq0McJafQqID7Ku5FuWrmTxQCDlC0+KQ96s=; b=SYixy6Q//WMyaAxzFjyH7sVbChC1fVgGH5GtiDma5C7kzCJB28mj2uAf B7JCe/qYPoGYjhOTsKGFo4oc1XzemzjGlhqXPzXEWz5OVgZkd+oQaU2j6 a/tia1kuJ90ZnK4yGsh8vksDppbFvzosctD/rcyJMgkh2LdgGavs5A/QL 0gnnUHOEZ3bBCA4PGeZc3rRhVt9GEgvv+h1hiZNmiFIoT9bfUiH5Pda/3 cBO6VD0yF18pVWxJbSPfo9Ylyrm6J;
X-SBRSScore: None
X-IronPort-AV: E=Sophos;i="4.59,276,1288566000"; d="scan'208";a="61025980"
Received: from abgdgate40u.abg.fsc.net ([172.25.138.90]) by dgate10u.abg.fsc.net with ESMTP; 29 Nov 2010 14:49:35 +0100
X-IronPort-AV: E=Sophos;i="4.59,275,1288566000"; d="scan'208";a="105960756"
Received: from mch8469d.mch.fsc.net (HELO [172.25.52.240]) ([172.25.52.240]) by abgdgate40u.abg.fsc.net with ESMTP; 29 Nov 2010 14:49:35 +0100
Message-ID: <4CF3AF6F.6070307@ts.fujitsu.com>
Date: Mon, 29 Nov 2010 14:49:35 +0100
From: Richard Koenning <Richard.Koenning@ts.fujitsu.com>
Organization: Fujitsu Technology Solutions GmbH
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: de, de-nds, en, en-US, it
MIME-Version: 1.0
To: "ftpext@ietf.org" <ftpext@ietf.org>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <8F4BB4C1C1895841414414D0@PST.JCK.COM>
In-Reply-To: <8F4BB4C1C1895841414414D0@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [ftpext] End byte of transfer in FTP
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Richard.Koenning@ts.fujitsu.com
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, 29 Nov 2010 13:48:29 -0000

John C Klensin wrote:

> --On Monday, November 29, 2010 01:21 +0900 Tatsuhiro Tsujikawa
> <tatsuhiro.t@gmail.com> wrote:
>=20
>=20
>>Hi,
>>
>>In FTP, user can set start byte of transfer by REST command.
>=20
>=20
> This is a misuse of the intent of the command and some
> historical FTP implementations won't permit it.  In particular,
> REST is defined only for Block and Compressed modes (neither of
> which is widely used these days) and starts only from a
> server-specified checkpoint marker.   While I can believe that
> some implementations might construe REST followed by an integer
> in stream mode as a byte offset to be used in a subsequent STOR
> or RETR command, that usage is certainly not guaranteed by
> anything in RFC 959.

REST is defined for STREAM mode, see RFC 3659, p.13.

Best regards,
Richard K=F6nning
--=20
Dr. Richard W. K=F6nning
Fujitsu Technology Solutions GmbH


From prvs=1949d8c605=mpp@rhinosoft.com  Mon Nov 29 07:04:50 2010
Return-Path: <prvs=1949d8c605=mpp@rhinosoft.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 F310528C121 for <ftpext@core3.amsl.com>; Mon, 29 Nov 2010 07:04:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.303
X-Spam-Level: 
X-Spam-Status: No, score=-2.303 tagged_above=-999 required=5 tests=[AWL=0.296,  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 JM8lix04httQ for <ftpext@core3.amsl.com>; Mon, 29 Nov 2010 07:04:48 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id BF01E3A6BD3 for <ftpext@ietf.org>; Mon, 29 Nov 2010 07:04:48 -0800 (PST)
Received: from MPNOTEBOOK ([192.168.1.20]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009940591.msg for <ftpext@ietf.org>; Mon, 29 Nov 2010 09:05:56 -0600
X-Spam-Processed: rhinosoft.com, Mon, 29 Nov 2010 09:05:56 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=1949d8c605=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <19F9469141E34A4D9C8ECDE7FBADB20E@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "Tatsuhiro Tsujikawa" <tatsuhiro.t@gmail.com>, <ftpext@ietf.org>
References: <AANLkTi=pBbGPtyjuU6NF32bRK3nz3i2k3ugDtCjF0SAS@mail.gmail.com>
In-Reply-To: <AANLkTi=pBbGPtyjuU6NF32bRK3nz3i2k3ugDtCjF0SAS@mail.gmail.com>
Date: Mon, 29 Nov 2010 09:05:54 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions
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, 29 Nov 2010 15:04:50 -0000

Hi Tatsuhiro,

Thank you for replying.

> If a directory specified in DSIZ command contains symbolic links,
> does this command calculate linked target file, or just size of a
> symbolic link file itself?

That's an implementation decision for the server.  It can go either way, 
and could be configurable by the server administrator.

> Also, if a symbolic link 'foolink' which links to directory foo is
> given in DSIZ command, does server returns 550 error because
> it is not directory?

This is also an implementation decision that could go either way.

> About phrase "the number of octets occupied by the files":...

It is the actual number of bytes in the files, not the number of
bytes used by the underlying OS.


Mark P. Peterson - President
http://www.RhinoSoft.com
Voice: +1(262) 560-9627
FAX: +1(262) 560-9628  


--------------------------------------------------
From: "Tatsuhiro Tsujikawa" <tatsuhiro.t@gmail.com>
Sent: Sunday, November 28, 2010 3:40 AM
To: <ftpext@ietf.org>
Subject: [ftpext]  draft-peterson-streamlined-ftp-command-extensions

Hi,

> DSIZ command

If a directory specified in DSIZ command contains symbolic links,
does this command calculate linked target file, or just size of a
symbolic link file itself?

Also, if a symbolic link 'foolink' which links to directory foo is
given in DSIZ command,
does server returns 550 error because it is not directory?

>DSIZ command should not consider this in its response, instead
> leaving it up to the underlying file system to determine the number
> of octets occupied by the files.

About phrase "the number of octets occupied by the files":
Some file systems(e.g. ext4) supports sparse file, and
space that those files actually occupy are sometimes much more smaller than
 'ls' shows its file size. For those files, does DSIZ return the octets occupied
by the files? I think if the user use DSIZ instead of recursive SIZE command,
they want file size normally shown by 'ls', not occupied octets in file system.

Sorry if this has been discussed already.

Best regards,

Tatsuhiro Tsujikawa
_______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext 


From anthonybryan@gmail.com  Mon Nov 29 17:15:48 2010
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 9D8C13A6C4F for <ftpext@core3.amsl.com>; Mon, 29 Nov 2010 17:15:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[AWL=-0.113, 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 qlXp1oF8-B4h for <ftpext@core3.amsl.com>; Mon, 29 Nov 2010 17:15:47 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 483603A6C3F for <ftpext@ietf.org>; Mon, 29 Nov 2010 17:15:47 -0800 (PST)
Received: by eyd10 with SMTP id 10so2586339eyd.31 for <ftpext@ietf.org>; Mon, 29 Nov 2010 17:16:57 -0800 (PST)
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=Rk1YDTzm+AFiYlWDA1RqXSnuV05h4QEZxxSp7R4cneA=; b=ia02rN0OtUmAo1ZPz42TSnanTCPXHoUUvb4oHyXJilRQEk95rK6AkEDxIKDi0lJ8CD NmnTjwxC6cH4EXSBnWaqoeFdONB6lUdLoWKj9waHkQSG5jOmFszkJKp0jaf8t/dOH/3i itKyA45IgupkpafP3bOpAteckF0Stsf7UgMD8=
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=q+xbwn8GKziZZi/vEs7tWHFeWL3VzNs1VOYlzxmBVl/uH5yQC0+Y4TjrEzosjbggUY 0RSia6oFGhB93TcHjEmreI2ul1gv1u7w94Q37heul8hIjUKI0csingj3G+6jd2QsxbRB ujK/xmmO3cQ8pyL90Ufk/Y/EZPaPFnWHMqxZQ=
MIME-Version: 1.0
Received: by 10.213.15.135 with SMTP id k7mr7616665eba.76.1291079816565; Mon, 29 Nov 2010 17:16:56 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Mon, 29 Nov 2010 17:16:56 -0800 (PST)
In-Reply-To: <D22AFE44108D486EB4C6F469A61BFB2B@rhinooffice.net>
References: <1791E3B42BE242848B7FFFC7015B4563@rhinooffice.net> <AANLkTimeH+O4E4XEq6cdw0UaM4UpDTo6EKB9kB1x4PJh@mail.gmail.com> <139EAF2195BC496AA3F25288D56BFB43@rhinooffice.net> <AANLkTinriyMy5_thOnx29HbGQ41NcYW+MS27YGDAjoNT@mail.gmail.com> <D22AFE44108D486EB4C6F469A61BFB2B@rhinooffice.net>
Date: Mon, 29 Nov 2010 20:16:56 -0500
Message-ID: <AANLkTikzavFRiegLQXAophNicGamAXXJ9O=2PTELhknw@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] Posted Update to "draft-peterson-streamlined-ftp-command-extensions"
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: Tue, 30 Nov 2010 01:15:48 -0000

On Fri, Nov 19, 2010 at 11:25 AM, Mark P. Peterson <mpp@rhinosoft.com> wrot=
e:
> Hi Anthony,
>
> I submitted a new revision which I believe addresses your comments below.
> It appears I still have some "idnets" issues even though I attempted to m=
ake
> the corrections you mention below. =A0Thank you for your assistance with =
this
> draft.

hi Mark,

your new version has not shown up yet. the latest version I see is -09
from Sept 17. I know discussion is still ongoing, but perhaps the
issues that have reached consensus can be rolled into a new draft. we
can work on everything & the idnits issues gradually :)

http://tools.ietf.org/html/draft-peterson-streamlined-ftp-command-extension=
s

did you follow the usual process?  perhaps it got stuck somewhere.
submit at https://datatracker.ietf.org/idst/upload.cgi , then click
the link in your email.

it's good to see your draft getting discussion.

<chair hat=3D"off">
I feel strongest about CSID (similar to Robert's AGNT or CLNT) & AVBL
(which is similar to
http://tools.ietf.org/html/draft-dilip-ftpext-safe-transfer-00#section-5.1
). like HASH, apparently, these issues keep popping up & people keep
solving them, so maybe it is best to finally offer a standardized
command. RMDA, DSIZ, and THMB also sound useful in some cases, I look
forward to seeing their evolution.

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

From anthonybryan@gmail.com  Mon Nov 29 18:09:13 2010
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 D42F828C154 for <ftpext@core3.amsl.com>; Mon, 29 Nov 2010 18:09:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=-0.257, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 ZoRbutix+US8 for <ftpext@core3.amsl.com>; Mon, 29 Nov 2010 18:09:13 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id A93FB28C0E0 for <ftpext@ietf.org>; Mon, 29 Nov 2010 18:09:12 -0800 (PST)
Received: by eyd10 with SMTP id 10so2603253eyd.31 for <ftpext@ietf.org>; Mon, 29 Nov 2010 18:10:22 -0800 (PST)
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=Lcj4k4nbRsruLcG6L/Do93Mo5e7kBfDPBzANDALdfsQ=; b=FBEu3T3X/Vyqz99DL5MAtnF/Us5M1ZGsB+FrphoQluDt92T1h+ZWzVJrLVdAwXrkS2 vGWG+UW1u5WbLeldwY5R30trCylr/hz7zHrh+ZMbrQQQDM2eT3jOytBRfYY+XTM8Fp5l OB+ML7F9GW5cBow2eggdNsk6kqSdwpH+4bNI8=
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=x7TYqw1Z0e3haF0BCy5LFcfGfm01rpjxBjcGI5YgidhOv/eILzHG6/J8R3rLm4HSwh bh0PSaurOge327+Un8fSpya7ufomMla+WC4dM+ZVOPfomJyMOdVy4IN8R0FVLaacffmb dZFAvpKBf5wh82iUtIONo4kBIkBy+O0Rtv0eY=
MIME-Version: 1.0
Received: by 10.213.15.135 with SMTP id k7mr7644076eba.76.1291083022362; Mon, 29 Nov 2010 18:10:22 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Mon, 29 Nov 2010 18:10:22 -0800 (PST)
In-Reply-To: <4CEFDCB9.6010203@gmail.com>
References: <20101124224501.31531.96663.idtracker@localhost> <4CEDAA9A.8030303@kimmeringer.de> <AANLkTik8Bv9YKo+uPt0ntk9OS0qQW2T5_RJ56CFZxMnS@mail.gmail.com> <4CEF00C0.5050200@gmail.com> <AANLkTimFeub1ynp4UcKAv84GP9f=gcG485jUgT82mB87@mail.gmail.com> <4CEFDCB9.6010203@gmail.com>
Date: Mon, 29 Nov 2010 21:10:22 -0500
Message-ID: <AANLkTi=i5A4RogvHLJuhsRJ0cFOOYGHkAk+aDwEvg_o7@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= <keisial@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] I-D Action:draft-ietf-ftpext2-hash-00.txt
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: Tue, 30 Nov 2010 02:09:13 -0000

2010/11/26 =C1ngel Gonz=E1lez <keisial@gmail.com>:
> Anthony Bryan wrote:
>>> * The user should not be required to know the file size in advance.
>> you mean the client? why? it should just assume from a starting point
>> to the end of the file?
> Sorry, I wasn't clear here. The client should not be required to know
> the file size
> for getting *the full hash*. If it is intended to convert the full file
> hash case into
> 'partial hash from 0 to filesize', there should be some magic value for
> the end of file.

what would be the reason for that? someone could try to HASH a file
that is still being uploaded very slowly.

so, people seem to be interested in partial file hashing. I think it
is worth considering, even though it makes things more complicated and
there are potential security issues.

any suggestions how to add this to the current draft?
--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads

From tatsuhiro.t@gmail.com  Tue Nov 30 06:14:47 2010
Return-Path: <tatsuhiro.t@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 3377A3A6C6F for <ftpext@core3.amsl.com>; Tue, 30 Nov 2010 06:14:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  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 rIrIVQYLIqDF for <ftpext@core3.amsl.com>; Tue, 30 Nov 2010 06:14:46 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 041DB3A6C66 for <ftpext@ietf.org>; Tue, 30 Nov 2010 06:14:45 -0800 (PST)
Received: by fxm9 with SMTP id 9so4618630fxm.31 for <ftpext@ietf.org>; Tue, 30 Nov 2010 06:15:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=xi0rQI1tko0ORQggxjL2ZqgsQzcBKwz1j7uA6xFIVFc=; b=rCzcL8QEbFrcwZMlhN2hFd3EhAddBSVJN9+uafIISjHg+uavefVvvdIur0ZbOAjRAj Hvjk7fHZFCdu+Bwp7CknwrvO9pGoSs9zVTzCxSY3izuMaytmLR9jtVyLNqUflVzvkySA wjdtIQ2JFZu6cxVXZ6bpDIpcRcIUBzF9nllpQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=p+j5N3BzjEXWPxCrH0Wq4BNvLqhT5Cc0/aWx7zqUj7fCWE9Xi8T+rF5xXA1ek5toNr +XlTh6jiG6X0BC9Mm1irGcxbndOGCoAO0aRtS9UDAVMCx5hAi6BWrM8s2Pp30lnea6Lj c5yaowS0T47/+x/e8dnRq3Ae4h5uwprEZF6hE=
Received: by 10.223.86.206 with SMTP id t14mr6839766fal.30.1291126556747; Tue, 30 Nov 2010 06:15:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.83.200 with HTTP; Tue, 30 Nov 2010 06:15:35 -0800 (PST)
In-Reply-To: <8F4BB4C1C1895841414414D0@PST.JCK.COM>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <8F4BB4C1C1895841414414D0@PST.JCK.COM>
From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Tue, 30 Nov 2010 23:15:35 +0900
Message-ID: <AANLkTikegF58eH=ZvjnDhgUT6dyhckPodMGOEwS9H=D5@mail.gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Tue, 30 Nov 2010 14:14:47 -0000

Hi,

Thank you for replying!

2010/11/29 John C Klensin <john-ietf@jck.com>:
>
>
> --On Monday, November 29, 2010 01:21 +0900 Tatsuhiro Tsujikawa
> <tatsuhiro.t@gmail.com> wrote:
>
>> Hi,
>>
>> In FTP, user can set start byte of transfer by REST command.
>
> This is a misuse of the intent of the command and some
> historical FTP implementations won't permit it. =A0In particular,
> REST is defined only for Block and Compressed modes (neither of
> which is widely used these days) and starts only from a
> server-specified checkpoint marker. =A0 While I can believe that
> some implementations might construe REST followed by an integer
> in stream mode as a byte offset to be used in a subsequent STOR
> or RETR command, that usage is certainly not guaranteed by
> anything in RFC 959.
>
> Note that design is quite intentional and necessary to reflect a
> wide variety of different file system organizations, including
> files that are not organized sequentially on the remote or local
> host.
>
> As the most trivial example, FTP doesn't even guarantee that the
> bits of a sequential file will be transferred in the order in
> which they appear in their original form.
>

As Richard suggests, REST was extended to STREAM mode in RFC3695.

>> But it seems it lacks the feature to set end byte of transfer,
>> like HTTP's Range request.
>> Does it really lack this feature? Are there any ftp
>> server/client support this?
>
> It seems to me that you are looking for a remote file management
> protocol that supports a much more specific file abstraction
> than is the case with FTP, which is purely and simply a file
> transfer protocol for entire files, not fragments of them. =A0HTTP
> does assume a particular type of file organization model, which
> is one reason byte-oriented fragment identifiers work. =A0If that
> model serves your needs, why not just use HTTP? =A0 If you need
> the more general organizational model of FTP, you will need to
> either transfer the entire file and then extract whatever you
> need (using whatever local access method is appropriate to that
> file) or find/ use/ design a file management protocol, rather
> than a file transfer one.
>
>> A example of utilization this feature is Metalink download.
>> In Metalink, it contains several URIs for one file. So we can
>> download it from several sources. From each server, client
>> downloads non-overlapping segment. For example, when
>> downloading 1 file using 2 FTP servers. We can use REST
>> command for second half of the download and it downloads given
>> =A0point to the end of file. This is fine. The control
>> connection can be reused. For the first half of the download,
>> since we cannot set end byte, we have to close connection
>> entirely after first half of file is downloaded. The control
>> connection cannot be reused this time.
>> We can use ABOR, but it has drawback as I mentioned earlier.
>
> And, again, why not use HTTP?
>

If we can choose protocol, then, yes, we choose HTTP definitely.
But there are existing FTP servers which we cannot make any changes and
we want to include them in Metalink. Especially if the file is only
served in particular
FTP site.

Tatsuhiro Tsujikawa

From Internet-Drafts@ietf.org  Tue Nov 30 09:00:02 2010
Return-Path: <Internet-Drafts@ietf.org>
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 C60C53A6BD4; Tue, 30 Nov 2010 09:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.424
X-Spam-Level: 
X-Spam-Status: No, score=-102.424 tagged_above=-999 required=5 tests=[AWL=0.175, 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 hqR85QK0r7zP; Tue, 30 Nov 2010 09:00:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E88228C11F; Tue, 30 Nov 2010 09:00:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101130170001.3943.611.idtracker@localhost>
Date: Tue, 30 Nov 2010 09:00:01 -0800
Cc: ftpext@ietf.org
Subject: [ftpext] I-D ACTION:draft-ietf-ftpext2-hosts-00.txt
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: Tue, 30 Nov 2010 17:00:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the FTP Extensions, 2nd edition Working Group of the IETF.

	Title		: File Transfer Protocol HOST Command for Virtual Hosts

	Author(s)	: P. Hethmon, R. McMurray
	Filename	: draft-ietf-ftpext2-hosts-00.txt
	Pages		: 20
	Date		: 2010-11-30
	
   This document defines a new FTP command that provides a mechanism for
   FTP clients and servers to identify individual virtual hosts on an
   FTP server.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ftpext2-hosts-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-ftpext2-hosts-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-11-30085524.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Tue Nov 30 15:31:55 2010
Return-Path: <Internet-Drafts@ietf.org>
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 692143A6CB5; Tue, 30 Nov 2010 15:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.432
X-Spam-Level: 
X-Spam-Status: No, score=-102.432 tagged_above=-999 required=5 tests=[AWL=0.167, 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 aych87aPEp92; Tue, 30 Nov 2010 15:31:53 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 735F83A6CB1; Tue, 30 Nov 2010 15:30:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101130233039.1078.26079.idtracker@localhost>
Date: Tue, 30 Nov 2010 15:30:39 -0800
Cc: ftpext@ietf.org
Subject: [ftpext] I-D Action:draft-ietf-ftpext2-typeu-00.txt
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: Tue, 30 Nov 2010 23:31:55 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the FTP Extensions, 2nd edition Working Group of the IETF.


	Title           : FTP Extension for Internationalized Text
	Author(s)       : J. Klensin
	Filename        : draft-ietf-ftpext2-typeu-00.txt
	Pages           : 8
	Date            : 2010-11-30

The original FTP protocol supported TYPE values for ASCII and EBCDIC
text, plus binary ("IMAGE") transmission.  As the Internet becomes
more international, there is a growing requirement to be able to
transmit textual data, encoded in Unicode, in a way that is
independent of the coding and line representation forms of particular
operating systems.  This memo specifies a new FTP TYPE value for
Unicode data.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ftpext2-typeu-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-ftpext2-typeu-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-11-30152307.I-D@ietf.org>


--NextPart--

From anthonybryan@gmail.com  Tue Nov 30 21:59:20 2010
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 93F483A6CEC for <ftpext@core3.amsl.com>; Tue, 30 Nov 2010 21:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.907
X-Spam-Level: 
X-Spam-Status: No, score=-2.907 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_LOW=-1]
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 EgcEekBDnusv for <ftpext@core3.amsl.com>; Tue, 30 Nov 2010 21:59:19 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id E49F53A6CEA for <ftpext@ietf.org>; Tue, 30 Nov 2010 21:59:18 -0800 (PST)
Received: by ewy8 with SMTP id 8so3454056ewy.31 for <ftpext@ietf.org>; Tue, 30 Nov 2010 22:00:31 -0800 (PST)
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=qmwyZRzwD3HEJCmmBPENHnwTyoXNZcu8+tgze1YxrX0=; b=XBBweoH5TvMmXoWvMhf2go3PZ0dvWwLbEVrhWYFqsb4GHHmF+9T/uuUdpiV7owWrvE gvLk1Y9vb/WoYUKWt/h2/WrLuRiyizJ37e5oYhhhqp6GLi9oxjCg/x/Twgx+f/QCOz3N 7vF3LGu+YtkhitBW06SDmvQnYzpl9HOyCoJvA=
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=jz6m2Uh5ik1Z5/9cyxHXwmiJVpLsd0Eg+G28BW7eyHSwDs2XAMXr+CSesSONxc3Ivq 0bQvLjZXNhYzfLvC0IczIYDV3Zgk+tXAizMtuOwhq0u28sV1z3dRWcqMBE5EKQGAasVl lgjuJ10bTPQnLo7kNa43gGGGgADCcTqJxFsnU=
MIME-Version: 1.0
Received: by 10.213.104.138 with SMTP id p10mr3724071ebo.63.1291183231044; Tue, 30 Nov 2010 22:00:31 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Tue, 30 Nov 2010 22:00:31 -0800 (PST)
In-Reply-To: <AANLkTinriyMy5_thOnx29HbGQ41NcYW+MS27YGDAjoNT@mail.gmail.com>
References: <1791E3B42BE242848B7FFFC7015B4563@rhinooffice.net> <AANLkTimeH+O4E4XEq6cdw0UaM4UpDTo6EKB9kB1x4PJh@mail.gmail.com> <139EAF2195BC496AA3F25288D56BFB43@rhinooffice.net> <AANLkTinriyMy5_thOnx29HbGQ41NcYW+MS27YGDAjoNT@mail.gmail.com>
Date: Wed, 1 Dec 2010 01:00:31 -0500
Message-ID: <AANLkTik9qaJgeVR4j-K+G-VErCCjHA2SL0cnkYq_+_J4@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] Posted Update to "draft-peterson-streamlined-ftp-command-extensions"
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, 01 Dec 2010 05:59:20 -0000

looking good! the new version is up...

On Sat, Sep 18, 2010 at 5:13 AM, Anthony Bryan <anthonybryan@gmail.com> wro=
te:
>
> some other issues...
>
> 3) would it be useful to have more exact error responses like we are
> talking about for HASH? (same for section 4.2).
>
> 3.2. DSIZ Error Responses
>
> =A0 In the event that the pathname is not a directory, the server MUST
> =A0 return a permanent 550 error reply. =A0Where the command cannot be
> =A0 parsed, a 500 or 501 reply SHOULD be sent. =A0The client MUST NOT
> =A0 assume that the presence of a 550 reply indicates that it cannot
> =A0 access the directory or its contents. =A0The server may generate this
> =A0 error for other reasons, for example the overhead required for the
> =A0 operation is too great.
>
> 4c)
>
> =A0 The AVBL
> =A0 command offers an interface for retrieving this value in a way that
> =A0 can be machine parsed.
>
> also mentioned a few lines later in 4.1 (I think once in 4.1 is enough):
>
> =A0 The 213 reply is formatted in such a way that the returned size can
> =A0 be machine parsed.


in 3.1 you have:

   The 213 reply is formatted in such a way that the returned size value
   can be machine parsed; the response MUST simply be the command
   response followed by an integer value with no delimiters.

don't you want the same in 4.1?

> 5) see 4a. don't you want some consistency here?
>
> =A0 A successful response includes a numeric value that may be the number
> =A0 of octets available as dictated by the physical limitations of the
> =A0 underlying storage mechanism. =A0It may also be a limit imposed upon
> =A0 <pathname> or even the user that issued the command. =A0The exact
> =A0 method for calculating this numeric value is up to the specific
> =A0 server-FTP process implementation.

this seems pretty vague and open ended. is it intended to be?

maybe something like this?

   A successful response includes a numeric value that is the number
   of octets available as dictated by the physical limitations of the
   underlying storage mechanism, or a limit imposed upon
   <pathname> or a limit imposed upon the user that issued the command.

> 6) THMB FEAT response is in 5.3
>
> =A0 Image formats supported by the server are listed in the THMB FEAT
> Response [6.3].

still unfixed.

11) as mentioned before, CSID is not in the IANA considerations section.

> On Fri, Sep 17, 2010 at 5:44 PM, Mark P. Peterson <mpp@rhinosoft.com> wro=
te:
>> Hi Anthony,
>>
>> Thank you. =A0I have updated the draft. =A0It can be found here:
>>
>> https://datatracker.ietf.org/doc/draft-peterson-streamlined-ftp-command-=
extensions/
>>
>> Mark P. Peterson - President
>> http://www.RhinoSoft.com
>> Voice: +1(262) 560-9627
>> FAX: +1(262) 560-9628
>>
>>
>> --------------------------------------------------
>> From: "Anthony Bryan" <anthonybryan@gmail.com>
>> Sent: Friday, September 17, 2010 3:08 AM
>> To: "Mark P. Peterson" <mpp@rhinosoft.com>
>> Cc: <ftpext@ietf.org>
>> Subject: Re: [ftpext] Posted Update to "draft-peterson-streamlined-ftp-c=
ommand-extensions"
>>
>> On Wed, Sep 15, 2010 at 8:20 AM, Mark P. Peterson <mpp@rhinosoft.com> wr=
ote:
>>> Hello,
>>>
>>> I have updated "draft-peterson-streamlined-ftp-command-extensions"
>>> as per some suggestions from Anthony Bryan. =A0The IANA Considerations
>>> section has been updated to reflect his suggestions. =A0The draft is
>>> located here:
>>>
>>> https://datatracker.ietf.org/doc/draft-peterson-streamlined-ftp-command=
-extensions/
>>
>> thanks, Mark! I plan to give this a more thorough review soon, & I
>> hope others will too.
>>
>>
>> looking at the last example in each of these, should the last line of ea=
ch be
>>
>> =A0 =A0 =A0 =A0 S> 550 file.fid: Is a file.
>>
>> ?
>>
>> 3.4. DSIZ Examples
>>
>> =A0 Assuming the presence of directory "A" on the server and that the
>> =A0 client has the necessary permissions to access and list it, a typica=
l
>> =A0 DSIZ client-server exchange would be:
>>
>> =A0 =A0 =A0 =A0 C> DSIZ A
>> =A0 =A0 =A0 =A0 S> 213 123456
>>
>> =A0 Where 123456 is the number of octets on the server's file system
>> =A0 occupied by the directory "A" and its contents.
>>
>> =A0 Assuming directory "A" cannot be listed due to client permissions,
>> =A0 the client-server exchange would be:
>>
>> =A0 =A0 =A0 =A0 C> DSIZ A
>> =A0 =A0 =A0 =A0 S> 550 A: Permission denied.
>>
>> =A0 Assuming the client provides the argument "file.fid" where "file.fid=
"
>> =A0 is an existing file, the client-server exchange would be:
>>
>> =A0 =A0 =A0 =A0 C> DSIZ file.fid
>> =A0 =A0 =A0 =A0 S> 550 A: Is a file.
>>
>>
>> 4.4. AVBL Examples
>>
>> =A0 Assuming the client provides the argument "file.fid" where "file.fid=
"
>> =A0 is an existing file, the client-server exchange would be:
>>
>> =A0 =A0 =A0 =A0 C> AVBL file.fid
>> =A0 =A0 =A0 =A0 S> 550 A: Is a file.
>>
>>
>> --
>> (( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
>> =A0)) Easier, More Reliable, Self Healing Downloads
>>
>>
>
>
>
> --
> (( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
> =A0 )) Easier, More Reliable, Self Healing Downloads
>



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