
From daniel@haxx.se  Wed Dec  1 11:01:38 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 57A713A6C29 for <ftpext@core3.amsl.com>; Wed,  1 Dec 2010 11:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.282
X-Spam-Level: 
X-Spam-Status: No, score=-2.282 tagged_above=-999 required=5 tests=[AWL=-0.633, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 o0Zm941Y5dxx for <ftpext@core3.amsl.com>; Wed,  1 Dec 2010 11:01:37 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 343553A6C20 for <ftpext@ietf.org>; Wed,  1 Dec 2010 11:01:35 -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 oB1J2ocF027327; Wed, 1 Dec 2010 20:02:50 +0100
Date: Wed, 1 Dec 2010 20:02:50 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
In-Reply-To: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Wed, 01 Dec 2010 20:02:50 +0100 (CET)
Cc: ftpext@ietf.org
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: Wed, 01 Dec 2010 19:01:38 -0000

On Mon, 29 Nov 2010, Tatsuhiro Tsujikawa wrote:

> 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).

curl does FTP range requests that way. It used to just close the transfer at 
the desired end point, and it even works fine with "most" servers while the 
remaining servers we've found requires an ABOR for the server to notice that 
the transfer was indeed closed. And after an ABOR like that, it really is hard 
to re-use the control connection safely, so this kind of "range" request 
certainly has its limitations.

-- 

  / daniel.haxx.se

From prvs=195177ff02=mpp@rhinosoft.com  Wed Dec  1 11:02:23 2010
Return-Path: <prvs=195177ff02=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 B6D793A6C20 for <ftpext@core3.amsl.com>; Wed,  1 Dec 2010 11:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.045
X-Spam-Level: 
X-Spam-Status: No, score=-2.045 tagged_above=-999 required=5 tests=[AWL=-0.046, 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 c9aYSIIWAruI for <ftpext@core3.amsl.com>; Wed,  1 Dec 2010 11:02:22 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id 348F33A6B46 for <ftpext@ietf.org>; Wed,  1 Dec 2010 11:02:22 -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 md50009943052.msg for <ftpext@ietf.org>; Wed, 01 Dec 2010 13:03:34 -0600
X-Spam-Processed: rhinosoft.com, Wed, 01 Dec 2010 13:03:34 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 192.168.1.20
X-Return-Path: prvs=195177ff02=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <9828C7BDC9A44A57A1CF441BC6007CCC@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> <AANLkTik9qaJgeVR4j-K+G-VErCCjHA2SL0cnkYq_+_J4@mail.gmail.com>
In-Reply-To: <AANLkTik9qaJgeVR4j-K+G-VErCCjHA2SL0cnkYq_+_J4@mail.gmail.com>
Date: Wed, 1 Dec 2010 13:03:32 -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: Wed, 01 Dec 2010 19:02:23 -0000

Hi Anthony,

> 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?

Yes, I modified the document (version 11).

> 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.

I changed it to use your text (version 11).

> still unfixed.

Yes, I was hoping to get a little help here, a suggestion on what the FEAT response
would look like, references, and changes to the samples.

> 11) as mentioned before, CSID is not in the IANA considerations section.

I have added it to the document (version 11).

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: Wednesday, December 01, 2010 12:00 AM
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: <ftpext@ietf.org>
Subject: Re: [ftpext] Posted Update to "draft-peterson-streamlined-ftp-command-extensions"

looking good! the new version is up...

On Sat, Sep 18, 2010 at 5:13 AM, Anthony Bryan <anthonybryan@gmail.com> wrote:
>
> 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
>
>   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.
>
> 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.


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?
>
>   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.

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
>
>   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> 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
>



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


From daniel@haxx.se  Thu Dec  2 03:16:18 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 15D2428B797 for <ftpext@core3.amsl.com>; Thu,  2 Dec 2010 03:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level: 
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=-0.175, 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 AZDJkfUtXETS for <ftpext@core3.amsl.com>; Thu,  2 Dec 2010 03:16:16 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 75D9B3A6915 for <ftpext@ietf.org>; Thu,  2 Dec 2010 03:16:16 -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 oB2BHTDM005381; Thu, 2 Dec 2010 12:17:30 +0100
Date: Thu, 2 Dec 2010 12:17:29 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: "Mark P. Peterson" <mpp@rhinosoft.com>
In-Reply-To: <F1714E4C4C6E44CDAB8FD961B5C5368B@rhinooffice.net>
Message-ID: <alpine.DEB.2.00.1012021203180.15551@tvnag.unkk.fr>
References: <F1714E4C4C6E44CDAB8FD961B5C5368B@rhinooffice.net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1129329158-104651497-1291288650=:15551"
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Thu, 02 Dec 2010 12:17:30 +0100 (CET)
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: Thu, 02 Dec 2010 11:16:18 -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.

--1129329158-104651497-1291288650=:15551
Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8BIT

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

> 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.

Hi Mark,

I've been away, but here are my comments to the draft:

o The name "Streamlined FTP Command Extensions" reads very odd in my mind, as
   they are in fact new/additional commands, I don't see how they streamline
   anything.

o RMDA - I think a 'rm -rf' version is a very good addition to FTP and it is
   in fact a generally requested operation by users in my experience.

o DSIZ - I see very little value for DSIZ in practise. Since the size of a
   given number of files is only true in that very instant, the returned value
   will just be a reason for misunderstandings and misuse. The way the command
   is described is however accurate and functional.

o AVBL - I see very little value for AVBL in practise. First off, this is
   only true the very moment the command is invoked and the next moment
   there may no longer be anything at all left so using the value for any logic
   will almost certainly be done wrongly. Further, disk space availibility
   depends on a lot of other factors as well besides just "available octets",
   så if there us 1000 bytes free you may be able to store a single 1000 byte
   file there, but perhaps not even be able to store 5 100 byte files. Alas,
   the value of such a command is questionable to me.

o THMB - I am firmly against this command. The idea that we would
   promote a command that makes a thumbnail for an image file is an abonimation
   in my mind. That's not the job of FTP, the "File Transfer Protocol". If you
   need thumbnails for whatever file format, then provide them either directly
   as plain files in your file system, or write an FTP server that provides
   "virtual" files that you generate on demand when the client asks for the
   files. I strongly oppose this command.

o CSID - fine with me. I don't see much benefit for many vendors to
   immediately start supporting it, but I don't see any harm in making a
   standard way to get/expose the information.

-- 

  / daniel.haxx.se
--1129329158-104651497-1291288650=:15551--

From prvs=1952273b46=mpp@rhinosoft.com  Thu Dec  2 05:23:26 2010
Return-Path: <prvs=1952273b46=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 EA20228C103 for <ftpext@core3.amsl.com>; Thu,  2 Dec 2010 05:23:25 -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 2wqyOSccN3OV for <ftpext@core3.amsl.com>; Thu,  2 Dec 2010 05:23:23 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id 24BB328C100 for <ftpext@ietf.org>; Thu,  2 Dec 2010 05:22:54 -0800 (PST)
Received: from MPNOTEBOOK ([209.242.229.18]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009943735.msg for <ftpext@ietf.org>; Thu, 02 Dec 2010 07:24:08 -0600
X-Spam-Processed: rhinosoft.com, Thu, 02 Dec 2010 07:24:08 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 209.242.229.18
X-Return-Path: prvs=1952273b46=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <E836DF37E23E4F33BA9FEC420F9B8C2E@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: "Daniel Stenberg" <daniel@haxx.se>
References: <F1714E4C4C6E44CDAB8FD961B5C5368B@rhinooffice.net> <alpine.DEB.2.00.1012021203180.15551@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1012021203180.15551@tvnag.unkk.fr>
Date: Thu, 2 Dec 2010 07:24:02 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"
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: Thu, 02 Dec 2010 13:23:26 -0000

Hi Daniel,

Thank you for your response and your comments.  The reason they're called
"streamlined" is because 4 out of the 5 commands could be performed via
other methods, these allow them to be performed in a single command.

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


--------------------------------------------------
From: "Daniel Stenberg" <daniel@haxx.se>
Sent: Thursday, December 02, 2010 5:17 AM
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Cc: <ftpext@ietf.org>
Subject: Re: [ftpext] draft-peterson-streamlined-ftp-command-extensions

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

> 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.

Hi Mark,

I've been away, but here are my comments to the draft:

o The name "Streamlined FTP Command Extensions" reads very odd in my mind, as
   they are in fact new/additional commands, I don't see how they streamline
   anything.

o RMDA - I think a 'rm -rf' version is a very good addition to FTP and it is
   in fact a generally requested operation by users in my experience.

o DSIZ - I see very little value for DSIZ in practise. Since the size of a
   given number of files is only true in that very instant, the returned value
   will just be a reason for misunderstandings and misuse. The way the command
   is described is however accurate and functional.

o AVBL - I see very little value for AVBL in practise. First off, this is
   only true the very moment the command is invoked and the next moment
   there may no longer be anything at all left so using the value for any logic
   will almost certainly be done wrongly. Further, disk space availibility
   depends on a lot of other factors as well besides just "available octets",
   så if there us 1000 bytes free you may be able to store a single 1000 byte
   file there, but perhaps not even be able to store 5 100 byte files. Alas,
   the value of such a command is questionable to me.

o THMB - I am firmly against this command. The idea that we would
   promote a command that makes a thumbnail for an image file is an abonimation
   in my mind. That's not the job of FTP, the "File Transfer Protocol". If you
   need thumbnails for whatever file format, then provide them either directly
   as plain files in your file system, or write an FTP server that provides
   "virtual" files that you generate on demand when the client asks for the
   files. I strongly oppose this command.

o CSID - fine with me. I don't see much benefit for many vendors to
   immediately start supporting it, but I don't see any harm in making a
   standard way to get/expose the information.

-- 

  / daniel.haxx.se 



From tatsuhiro.t@gmail.com  Sat Dec  4 06:54:48 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 4293128C0ED for <ftpext@core3.amsl.com>; Sat,  4 Dec 2010 06:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_00=-2.599, 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 kuTErEonHzCU for <ftpext@core3.amsl.com>; Sat,  4 Dec 2010 06:54:47 -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 5133A28C0DD for <ftpext@ietf.org>; Sat,  4 Dec 2010 06:54:46 -0800 (PST)
Received: by fxm9 with SMTP id 9so8864833fxm.31 for <ftpext@ietf.org>; Sat, 04 Dec 2010 06:56:05 -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; bh=OpWTlwI3jommLAMs2KyMeOezZSsJqr/QbSkinQYpCsw=; b=rDed0FyLlKeCTdY7KeXZW2939Ai5Tp+gCNcDTS1rZavMLxFtJhqBUWW6DXb9mNBIgJ RDPOWitVVSjXFlVFHEWQXN77MU9oyB3RJLbY1kZ7vB34ONKZxjbBaMiJKTwKENzfn0D9 oTi7kmY8QoJU+spSLXxuZqxNlHONHFfbleQsY=
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; b=gfeN5l4oZbDZ+tQ/9gh+T7piCkWGGG5FEwpotsKDmYGmDZO537ME13Zd0Yktl6ILip ZNgSsINmqX6KWGY3N8RrXaYcYI3UPvuT8uAevkRllAE8DHq7mX/mshC77wigtbBO+xXG SITCbBP+XYoVaamxjoVGM+27qaKJ0elOZGcSc=
Received: by 10.223.120.193 with SMTP id e1mr3435954far.106.1291474563154; Sat, 04 Dec 2010 06:56:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.83.200 with HTTP; Sat, 4 Dec 2010 06:55:43 -0800 (PST)
In-Reply-To: <AANLkTikegF58eH=ZvjnDhgUT6dyhckPodMGOEwS9H=D5@mail.gmail.com>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <8F4BB4C1C1895841414414D0@PST.JCK.COM> <AANLkTikegF58eH=ZvjnDhgUT6dyhckPodMGOEwS9H=D5@mail.gmail.com>
From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Sat, 4 Dec 2010 23:55:43 +0900
Message-ID: <AANLkTinPBahv0xrfDBgw7qK2vdi6PuZzTS4tCMX5HUXR@mail.gmail.com>
To: ftpext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
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: Sat, 04 Dec 2010 14:54:48 -0000

2010/11/30 Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>:
>
> As Richard suggests, REST was extended to STREAM mode in RFC3695.
>

Sorry for typo:
s/RFC3695/RFC3659/

From anthonybryan@gmail.com  Sat Dec  4 14:14:23 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 8768128C0E7 for <ftpext@core3.amsl.com>; Sat,  4 Dec 2010 14:14:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level: 
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, J_CHICKENPOX_101=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 XIx1B3mr7YSm for <ftpext@core3.amsl.com>; Sat,  4 Dec 2010 14:14:22 -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 5433828C0E3 for <ftpext@ietf.org>; Sat,  4 Dec 2010 14:14:22 -0800 (PST)
Received: by eyd10 with SMTP id 10so5914375eyd.31 for <ftpext@ietf.org>; Sat, 04 Dec 2010 14:15:41 -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=sMT/5EpNgLeiPud69AKJLfMsB5qlCtIKN3q7134wKMM=; b=Pi/S4/W81Fe0okZtz7pxRfkWfYFTsoEsElxNLmEUCA5Se9BxEMsYlIuJZ9B9UH8tRh oUsTodjAU8L+QlKh1aFDf9tGeBtnwIwR6/GI5q9WGfRelS4rI2560o8vFyOgdwO+ztVd yO2ct2UdwdNIwSD1V6CZ423EsoqcfudZ8ljOA=
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=MpmtryOtfnK5ulrTsfSpq2KvlQeZ1dVz4M8IRzRtgJDpnvb0JwCeNA+Y03zPxBL8Jr kkkSgBJ5Ccrw96TXwxQRVi/mE5cW3eYi3gD1UWmxeSCmrnNhMWIfevILZKSLmV48Fw7e QMVcmFeoN3BLHBRclEHuACkgqEJk4ZQ/Wkphc=
MIME-Version: 1.0
Received: by 10.213.15.135 with SMTP id k7mr4075686eba.76.1291500941747; Sat, 04 Dec 2010 14:15:41 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Sat, 4 Dec 2010 14:15:41 -0800 (PST)
In-Reply-To: <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr>
Date: Sat, 4 Dec 2010 17:15:41 -0500
Message-ID: <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Daniel Stenberg <daniel@haxx.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
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: Sat, 04 Dec 2010 22:14:23 -0000

On Wed, Dec 1, 2010 at 2:02 PM, Daniel Stenberg <daniel@haxx.se> wrote:
> On Mon, 29 Nov 2010, Tatsuhiro Tsujikawa wrote:
>
>> 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).
>
> curl does FTP range requests that way. It used to just close the transfer=
 at
> the desired end point, and it even works fine with "most" servers while t=
he
> remaining servers we've found requires an ABOR for the server to notice t=
hat
> the transfer was indeed closed. And after an ABOR like that, it really is
> hard to re-use the control connection safely, so this kind of "range"
> request certainly has its limitations.

would it be possible to modify REST so that if the FEAT reply included RANG=
E:

      C> feat
      S> 211- <any descriptive text>
      S>  ...
      S>  REST STREAM RANGE
      S>  ...
      S> 211 end

REST could take a starting point and ending point?

if so, I wonder if servers & clients would want to implement that or
if it's too late in the game.

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

From tatsuhiro.t@gmail.com  Sun Dec  5 01:25: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 2A5D13A6A55 for <ftpext@core3.amsl.com>; Sun,  5 Dec 2010 01:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, J_CHICKENPOX_42=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 T+tZUanlZn+m for <ftpext@core3.amsl.com>; Sun,  5 Dec 2010 01:25: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 2456E3A69B9 for <ftpext@ietf.org>; Sun,  5 Dec 2010 01:25:45 -0800 (PST)
Received: by fxm9 with SMTP id 9so9255044fxm.31 for <ftpext@ietf.org>; Sun, 05 Dec 2010 01:27:06 -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:cc:content-type :content-transfer-encoding; bh=ztCnUb22vg3re8AdVogJyKvk+B+J9BAd/Iyu6u2TB1k=; b=Vx2czZevzA8IeC6lEvPCl9aato4+G17BvyHUs/7sQy6bxfbUp7gqA5eSLwi1UfDIcx lxMgNfd1V/mL7XhS36+UboxErSxnXVdhGV/H3ZNQUnwKqjhRm3vlzG4BOTvmuDP41KC6 n0wfI8GdPyDhYT73KL/U4eivkcsy73eRwdKx0=
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 :cc:content-type:content-transfer-encoding; b=rYRqgT7Yn0T/DLJpC6xXn3Iy5UX4PJGLrdmJvQtPZCgcDfgTxzunfY2PtVgPzcka3i 32mK876ecBucYBhE2QskdCX9xffGlbkM5zEgZo4hE2z1OEHXx9az0xnjVSqCoHf06vup kgdeJXoSxO1LahqlBloLMcrzW8t0V7svYSlrM=
Received: by 10.223.36.220 with SMTP id u28mr3364053fad.11.1291541226684; Sun, 05 Dec 2010 01:27:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.83.200 with HTTP; Sun, 5 Dec 2010 01:26:46 -0800 (PST)
In-Reply-To: <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr> <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>
From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Sun, 5 Dec 2010 18:26:46 +0900
Message-ID: <AANLkTiks7Yx9C3kEzJSHr=0oHjBrg4RhBkFAwZBQn8p7@mail.gmail.com>
To: Anthony Bryan <anthonybryan@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org, Daniel Stenberg <daniel@haxx.se>
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, 05 Dec 2010 09:25:47 -0000

2010/12/5 Anthony Bryan <anthonybryan@gmail.com>:
>
> would it be possible to modify REST so that if the FEAT reply included RA=
NGE:
>
> =A0 =A0 =A0C> feat
> =A0 =A0 =A0S> 211- <any descriptive text>
> =A0 =A0 =A0S> =A0...
> =A0 =A0 =A0S> =A0REST STREAM RANGE
> =A0 =A0 =A0S> =A0...
> =A0 =A0 =A0S> 211 end
>
> REST could take a starting point and ending point?
>

I don't know it is possible to extend existing command to get another argum=
ent.
But if it can, it is reasonable.

If it cannot, then we can make another command, say, RANG(or RNGE?)
which takes starting
and ending point.

> if so, I wonder if servers & clients would want to implement that or
> if it's too late in the game.
>

At least for client, I'd love to implement this extension in aria2;)
I think it is not too late, because there is big difference with or
without standard.
And still FTP is widely used and FTP server code is maintained, so
there is a plenty
of room for this extension.

Best regards,

Tatsuhiro Tsujikawa

From daniel@haxx.se  Sun Dec  5 23:54:32 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 1F56E3A69C6 for <ftpext@core3.amsl.com>; Sun,  5 Dec 2010 23:54:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level: 
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5 tests=[AWL=-0.140, 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 g0G0rmki6iRU for <ftpext@core3.amsl.com>; Sun,  5 Dec 2010 23:54:31 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id A85293A698E for <ftpext@ietf.org>; Sun,  5 Dec 2010 23:54:30 -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 oB67toJ0013670; Mon, 6 Dec 2010 08:55:50 +0100
Date: Mon, 6 Dec 2010 08:55:50 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Anthony Bryan <anthonybryan@gmail.com>
In-Reply-To: <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1012060855010.19637@tvnag.unkk.fr>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr> <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Mon, 06 Dec 2010 08:55:50 +0100 (CET)
Cc: ftpext@ietf.org
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: Mon, 06 Dec 2010 07:54:32 -0000

On Sat, 4 Dec 2010, Anthony Bryan wrote:

> would it be possible to modify REST so that if the FEAT reply included 
> RANGE:

I don't see much point in that. I'd rather see a new range function or 
possibly one that sets the end point in the same style REST sets the start 
point.

-- 

  / daniel.haxx.se

From john-ietf@jck.com  Mon Dec  6 06:56:36 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 DB17A3A67FF for <ftpext@core3.amsl.com>; Mon,  6 Dec 2010 06:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, 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 h2CsLVW6iBE8 for <ftpext@core3.amsl.com>; Mon,  6 Dec 2010 06:56:36 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id ECC513A67B4 for <ftpext@ietf.org>; Mon,  6 Dec 2010 06:56:35 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PPcVk-0008pW-Jp; Mon, 06 Dec 2010 09:57:52 -0500
Date: Mon, 06 Dec 2010 09:57:51 -0500
From: John C Klensin <john-ietf@jck.com>
To: Daniel Stenberg <daniel@haxx.se>, Anthony Bryan <anthonybryan@gmail.com>
Message-ID: <A6BF1C5A1E1A999D1A7D33E3@PST.JCK.COM>
In-Reply-To: <alpine.DEB.2.00.1012060855010.19637@tvnag.unkk.fr>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr> <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com> <alpine.DEB.2.00.1012060855010.19637@tvnag.unkk.fr>
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
Cc: ftpext@ietf.org
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: Mon, 06 Dec 2010 14:56:36 -0000

--On Monday, December 06, 2010 08:55 +0100 Daniel Stenberg
<daniel@haxx.se> wrote:

> On Sat, 4 Dec 2010, Anthony Bryan wrote:
> 
>> would it be possible to modify REST so that if the FEAT reply
>> included  RANGE:
> 
> I don't see much point in that. I'd rather see a new range
> function or possibly one that sets the end point in the same
> style REST sets the start point.

Yes.  I'm still not convinced trying to specify fragments of
stream files is a good idea at all but, if it is to be done,
let's do it with a new command and very clearly-specified
semantics.  Remember that, if transfers are done in TYPE I, 

	-- not only can one have any of the usual
	line-separation characters, but one can have other sorts
	of record markers or length-delimited lines or blocks.
	
	-- if Unicode is being sent consistent with the base
	spec), one gets internal storage forms (often UTF-16LE
	or UTF-16BE) not only UTF-8, and certainly does not get
	one octet per character.

So specifying fragments clearly is not a trivial piece of work
unless the new command also requires a new file STRUcture
variation.

      john


From Richard.Koenning@ts.fujitsu.com  Mon Dec  6 07:33:20 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 B1A243A6811 for <ftpext@core3.amsl.com>; Mon,  6 Dec 2010 07:33:20 -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 27XfxFBXH7eF for <ftpext@core3.amsl.com>; Mon,  6 Dec 2010 07:33:18 -0800 (PST)
Received: from dgate20.ts.fujitsu.com (dgate20.ts.fujitsu.com [80.70.172.51]) by core3.amsl.com (Postfix) with ESMTP id A09193A681D for <ftpext@ietf.org>; Mon,  6 Dec 2010 07:33:17 -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:CC:Subject: References:In-Reply-To:Content-Type: Content-Transfer-Encoding; b=EJQjRILg/F4W4gpZOOWYxfRsFpw2tOwTkRo8e81PtTyz72wJlbsNSLKo VoOntpiMeMjvHtFwzuM1p+p/AiKNtyGUdmFRAKWk1Mj3x2gylc+qiPVAL +FRgGE4zkaSdND2X4xaolcXdSwN+WnPz/88LdT7MnBzdN3B8ZWXfolUOF 8EV52u2jXUaVhm1V2kUyOQ7AIdFFSZoRd5P48x7jgclwpBPXpCn1LXzav +1o8YE0EgDPaNJtCA2/DmI6/0cJ27;
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=1291649682; x=1323185682; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; z=Message-ID:=20<4CFD028C.6050105@ts.fujitsu.com>|Date:=20 Mon,=2006=20Dec=202010=2016:34:36=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>|CC:=20John =20C=20Klensin=20<john-ietf@jck.com>,=20Daniel=20Stenberg =20<daniel@haxx.se>,=20=0D=0A=20Anthony=20Bryan=20<anthon ybryan@gmail.com>|Subject:=20Re:=20[ftpext]=20End=20byte =20of=20transfer=20in=20FTP|References:=20<AANLkTi=3D_OsG PMsC=3DBHtOyHzTTM5vJ1=3DyW9fYk_Tp1xm7@mail.gmail.com>=09< alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr>=09<AAN LkTikGmtyrcpbEabBXZAo3ai=3Dz8082RBSrvKSQrzq6@mail.gmail.c om>=09<alpine.DEB.2.00.1012060855010.19637@tvnag.unkk.fr> =20<A6BF1C5A1E1A999D1A7D33E3@PST.JCK.COM>|In-Reply-To:=20 <A6BF1C5A1E1A999D1A7D33E3@PST.JCK.COM> |Content-Transfer-Encoding:=20quoted-printable; bh=g9e507Bn1NNKnZ4J2B2A156Cz/hxfiRYCgSN6V3DY30=; b=LUIjKqML4Oxv2d5HuNnMQkRrI0AdvuzkfQvZufi14lY8OE5ys8at9R62 /ywnNxkRTcP5xiGJNZ0TV1ab4fS/Gonc4nrFiZvKHIYToQirsaa/4G1iW freBtm2+QWWoiXV7Fg0cgSBXCLgE5JsZZ2HtQDg+0Y/3IbR7jbTONkr6u Lls7il267qCSWIV1sZtLWJKU4hO/83DOd3iEsDOR5dnN9K5JcHqX12OeO VCn3soaepb8taGRx94TrV0ZYkVrlw;
X-SBRSScore: None
X-IronPort-AV: E=Sophos;i="4.59,305,1288566000"; d="scan'208";a="53492218"
Received: from abgdgate40u.abg.fsc.net ([172.25.138.90]) by dgate20u.abg.fsc.net with ESMTP; 06 Dec 2010 16:34:37 +0100
X-IronPort-AV: E=Sophos;i="4.59,305,1288566000"; d="scan'208";a="106491202"
Received: from mch8469d.mch.fsc.net (HELO [172.25.52.240]) ([172.25.52.240]) by abgdgate40u.abg.fsc.net with ESMTP; 06 Dec 2010 16:34:37 +0100
Message-ID: <4CFD028C.6050105@ts.fujitsu.com>
Date: Mon, 06 Dec 2010 16:34:36 +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>	<alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr>	<AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>	<alpine.DEB.2.00.1012060855010.19637@tvnag.unkk.fr> <A6BF1C5A1E1A999D1A7D33E3@PST.JCK.COM>
In-Reply-To: <A6BF1C5A1E1A999D1A7D33E3@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: Daniel Stenberg <daniel@haxx.se>
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, 06 Dec 2010 15:33:20 -0000

John C Klensin wrote:

> Yes.  I'm still not convinced trying to specify fragments of
> stream files is a good idea at all but, if it is to be done,
> let's do it with a new command and very clearly-specified
> semantics.  Remember that, if transfers are done in TYPE I,=20
>=20
> 	-- not only can one have any of the usual
> 	line-separation characters, but one can have other sorts
> 	of record markers or length-delimited lines or blocks.
> =09
> 	-- if Unicode is being sent consistent with the base
> 	spec), one gets internal storage forms (often UTF-16LE
> 	or UTF-16BE) not only UTF-8, and certainly does not get
> 	one octet per character.
>=20
> So specifying fragments clearly is not a trivial piece of work
> unless the new command also requires a new file STRUcture
> variation.

I don't see a problem on FTP protocol level, with TYPE I the transfered=20
data is an unstructured stream of bytes, in which REST currently defines =

a starting point and in which a RANGE specification would additionally=20
define an endpoint.
FTP clients and servers operating on files which are not simply a stream =

of bytes but e.g. have some length-delimited record structure may have=20
hard work to do, but this problem exists already with the current REST=20
command.

--=20
Dr. Richard W. K=F6nning
Fujitsu Technology Solutions GmbH


From anthonybryan@gmail.com  Mon Dec  6 16:11: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 70F0328C0DB for <ftpext@core3.amsl.com>; Mon,  6 Dec 2010 16:11:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.215
X-Spam-Level: 
X-Spam-Status: No, score=-3.215 tagged_above=-999 required=5 tests=[AWL=0.384,  BAYES_00=-2.599, 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 3TeIWZW+aSHN for <ftpext@core3.amsl.com>; Mon,  6 Dec 2010 16:11:07 -0800 (PST)
Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by core3.amsl.com (Postfix) with ESMTP id E328E28C0D7 for <ftpext@ietf.org>; Mon,  6 Dec 2010 16:11:05 -0800 (PST)
Received: by ewy6 with SMTP id 6so21582825ewy.40 for <ftpext@ietf.org>; Mon, 06 Dec 2010 16:12:29 -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=FiohGqqQn9AXlLdovZp37Gr3x18ktDnO3RmsTYBBazM=; b=qePU6H0OLi+Y2m5V+9roIfEIyBpGb5Uu6EVg7CJImY7rnnzaUXteqChK57tVWWLbOp d4e7NLexr8VLpuGPCwkquzXQCBnkbZruZLxghjutfGKqTXG1bI/LiiO/+LOuiIUm25vO 59yUfNwUxHGt2vfiXjOBpM5sA5VgSx5sIsBcQ=
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=A72TyjBBAvcolKEkx8UyFLVdKmefPc4dEILs7KJvtLuT0NXso0XnKgicdoFMKRov2m RInk2g/SfEcfXRZjawYqwviJw4gC7K9qVrV5ZlSXSE6YRZK1/fn4guYTYZPyL/aY6IeY mbPIFbJVyW0FczfNHowOo8eACbgM0lJL1naLY=
MIME-Version: 1.0
Received: by 10.213.19.201 with SMTP id c9mr189580ebb.89.1291680748321; Mon, 06 Dec 2010 16:12:28 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Mon, 6 Dec 2010 16:12:28 -0800 (PST)
In-Reply-To: <20101130170001.3943.611.idtracker@localhost>
References: <20101130170001.3943.611.idtracker@localhost>
Date: Mon, 6 Dec 2010 19:12:28 -0500
Message-ID: <AANLkTinDU5fMow28urk3RQR_MkeuxrrSgCN2CGMTmvb+@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: ftpext@ietf.org, Robert McMurray <robmcm@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [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, 07 Dec 2010 00:11:08 -0000

On Tue, Nov 30, 2010 at 12:00 PM,  <Internet-Drafts@ietf.org> wrote:
> 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 Grou=
p of the IETF.
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : File Transfer Protocol HOST Co=
mmand for Virtual Hosts
>
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : P. Hethmon, R. McMurray
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-ftpext2-hosts-00.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 20
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-11-30
>
> =A0 This document defines a new FTP command that provides a mechanism for
> =A0 FTP clients and servers to identify individual virtual hosts on an
> =A0 FTP server.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ftpext2-hosts-00.txt

Robert, are there any changes from the pre-WG version? for some reason
a diff is not available, even though I requested that this version
updates the pre-WG version in the datatracker.

from reading the prose again, looks good to go! (I didn't go over the
diagrams or ABNF).

typo/spelling nits:

1) Introduction
mutiple -> multiple

2) I'm not sure what this means...should the "of" in the middle be dropped?
3.1
This specification, however, allows only the of names that can be
inferred from the ABNF
   grammar given for the "hostname".

2) 3.3 double "as if"s

      a. Ignore the HOST command and act as if as if a HOST command
      had not been sent.

3) Acknowledgments

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

From tony@att.com  Mon Dec  6 16:54:57 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 65AD53A68E0 for <ftpext@core3.amsl.com>; Mon,  6 Dec 2010 16:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.847
X-Spam-Level: 
X-Spam-Status: No, score=-105.847 tagged_above=-999 required=5 tests=[AWL=-0.540, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 OFKApFZ4emJ6 for <ftpext@core3.amsl.com>; Mon,  6 Dec 2010 16:54:56 -0800 (PST)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 7035F3A68DA for <ftpext@ietf.org>; Mon,  6 Dec 2010 16:54:56 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-5.tower-161.messagelabs.com!1291683379!19139689!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 17828 invoked from network); 7 Dec 2010 00:56:20 -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; 7 Dec 2010 00:56:20 -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 oB70uc62017699 for <ftpext@ietf.org>; Mon, 6 Dec 2010 19:56:39 -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 oB70uYXC017600 for <ftpext@ietf.org>; Mon, 6 Dec 2010 19:56:34 -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 oB70uE3V016282 for <ftpext@ietf.org>; Mon, 6 Dec 2010 19:56:14 -0500
Received: from mailgw1.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id oB70u9Dv016214 for <ftpext@ietf.org>; Mon, 6 Dec 2010 19:56:09 -0500
Received: from [135.70.17.26] (vpn-135-70-17-26.vpn.west.att.com[135.70.17.26]) by maillennium.att.com (mailgw1) with ESMTP id <20101207005608gw1004lknne> (Authid: tony); Tue, 7 Dec 2010 00:56:09 +0000
X-Originating-IP: [135.70.17.26]
Message-ID: <4CFD8627.4030006@att.com>
Date: Mon, 06 Dec 2010 19:56:07 -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
CC: ftpext@ietf.org
References: <20101130170001.3943.611.idtracker@localhost> <AANLkTinDU5fMow28urk3RQR_MkeuxrrSgCN2CGMTmvb+@mail.gmail.com>
In-Reply-To: <AANLkTinDU5fMow28urk3RQR_MkeuxrrSgCN2CGMTmvb+@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [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, 07 Dec 2010 00:54:57 -0000

On 12/6/2010 7:12 PM, Anthony Bryan wrote:
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-ftpext2-hosts-00.txt
> Robert, are there any changes from the pre-WG version? for some reason
> a diff is not available, even though I requested that this version
> updates the pre-WG version in the datatracker.

http://tools.ietf.org/rfcdiff?url1=draft-hethmon-mcmurray-ftp-hosts-15.txt&url2=draft-ietf-ftpext2-hosts-00.txt

     Tony Hansen
     tony@att.com

From robmcm@microsoft.com  Tue Dec  7 19:51:04 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 8BFD73A6862 for <ftpext@core3.amsl.com>; Tue,  7 Dec 2010 19:51:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.419
X-Spam-Level: 
X-Spam-Status: No, score=-10.419 tagged_above=-999 required=5 tests=[AWL=0.180, 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 Vpe17Hs5k7-b for <ftpext@core3.amsl.com>; Tue,  7 Dec 2010 19:51:03 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id CDB903A6834 for <ftpext@ietf.org>; Tue,  7 Dec 2010 19:51:03 -0800 (PST)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 7 Dec 2010 19:52:30 -0800
Received: from TK5EX14MBXC127.redmond.corp.microsoft.com ([169.254.6.27]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.01.0255.003; Tue, 7 Dec 2010 19:52:30 -0800
From: Robert McMurray <robmcm@microsoft.com>
To: Anthony Bryan <anthonybryan@gmail.com>, "ftpext@ietf.org" <ftpext@ietf.org>
Thread-Topic: [ftpext] I-D ACTION:draft-ietf-ftpext2-hosts-00.txt
Thread-Index: AQHLlaOWCgUirq7P9k6zrFqpVH+MlZOV5eFg
Date: Wed, 8 Dec 2010 03:52:30 +0000
Message-ID: <A5FC996C3C37DC4DA5076F1046B5674C4433F1D5@TK5EX14MBXC127.redmond.corp.microsoft.com>
References: <20101130170001.3943.611.idtracker@localhost> <AANLkTinDU5fMow28urk3RQR_MkeuxrrSgCN2CGMTmvb+@mail.gmail.com>
In-Reply-To: <AANLkTinDU5fMow28urk3RQR_MkeuxrrSgCN2CGMTmvb+@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.71]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [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: Wed, 08 Dec 2010 03:51:04 -0000

Thanks, Anthony.

Good catches on the spelling errors. :-)

> Robert, are there any changes from the pre-WG
> version? for some reason a diff is not
> available, even though I requested that this version
> updates the pre-WG version in the datatracker.

I had made very few changes for the 00 draft posting in the new WG, but aft=
er I submitted the 00 draft I had a few nits show up in the IETF datatracke=
r about the license that I was using - the required license verbiage appare=
ntly changed when the draft changed working groups. So I was working on a n=
ew version when I saw your email, and I've submitted a new version that fix=
es everything. (And this new draft references the FTPEXT2 WG in the header =
instead of the Network WG.)

Thanks again!

Robert McMurray
robmcm@microsoft.com


From tatsuhiro.t@gmail.com  Wed Dec  8 04:33:27 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 865DC3A6907 for <ftpext@core3.amsl.com>; Wed,  8 Dec 2010 04:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.179
X-Spam-Level: 
X-Spam-Status: No, score=-3.179 tagged_above=-999 required=5 tests=[AWL=0.420,  BAYES_00=-2.599, 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 EUVLij7q3r2L for <ftpext@core3.amsl.com>; Wed,  8 Dec 2010 04:33:26 -0800 (PST)
Received: from mail-fx0-f43.google.com (mail-fx0-f43.google.com [209.85.161.43]) by core3.amsl.com (Postfix) with ESMTP id 5DD063A690A for <ftpext@ietf.org>; Wed,  8 Dec 2010 04:33:26 -0800 (PST)
Received: by fxm18 with SMTP id 18so994972fxm.16 for <ftpext@ietf.org>; Wed, 08 Dec 2010 04:34:53 -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=52moXN/8jxNPD+mW3BJqJlOfzUnUCPVn4YXjKPFqU4M=; b=DLjoXlC4UqM8oXuPtjzAG8YiKV/iZknDW46P6i9n3f+XQX+7ZEtlre7r7mzuwMZlc0 oR4palrBU1BHiYcfywnwjklqPpyrdMSOq2iEz98WfeW6kaS2sqMXT0EU+zM1bb0nAJgu xuqJQDF4sRHaJIzQTGaXRi3O6ViJQCkKOeaO8=
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=Q0LyYOadMAs8c684EBIXKGc9aDg9+ViPwEYAYbXpyYbioyew59G5mwjewUKB/pOjEG 2uPxoVLNEnkQ7fz5P1RxlAOAX3bY+zARBy6MskZzDEcHqCCV3Ml5qZ4GewqGJRESww3p 4N/U+BBw8NjhalF5kklI/38YX6DClqFogsAZM=
Received: by 10.223.93.142 with SMTP id v14mr2721334fam.49.1291811692963; Wed, 08 Dec 2010 04:34:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.83.200 with HTTP; Wed, 8 Dec 2010 04:34:32 -0800 (PST)
In-Reply-To: <4CFD028C.6050105@ts.fujitsu.com>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr> <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com> <alpine.DEB.2.00.1012060855010.19637@tvnag.unkk.fr> <A6BF1C5A1E1A999D1A7D33E3@PST.JCK.COM> <4CFD028C.6050105@ts.fujitsu.com>
From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Wed, 8 Dec 2010 21:34:32 +0900
Message-ID: <AANLkTinWUwrQ-21qQvXr9P4GG2DB+SzYUCDEuCwP-6Kw@mail.gmail.com>
To: "ftpext@ietf.org" <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: Wed, 08 Dec 2010 12:33:27 -0000

2010/12/7 Richard Koenning <Richard.Koenning@ts.fujitsu.com>:
> John C Klensin wrote:
>
>> Yes. =A0I'm still not convinced trying to specify fragments of
>> stream files is a good idea at all but, if it is to be done,
>> let's do it with a new command and very clearly-specified
>> semantics. =A0Remember that, if transfers are done in TYPE I,
>> =A0 =A0 =A0 =A0-- not only can one have any of the usual
>> =A0 =A0 =A0 =A0line-separation characters, but one can have other sorts
>> =A0 =A0 =A0 =A0of record markers or length-delimited lines or blocks.
>>
>> =A0 =A0 =A0 =A0-- if Unicode is being sent consistent with the base
>> =A0 =A0 =A0 =A0spec), one gets internal storage forms (often UTF-16LE
>> =A0 =A0 =A0 =A0or UTF-16BE) not only UTF-8, and certainly does not get
>> =A0 =A0 =A0 =A0one octet per character.
>>
>> So specifying fragments clearly is not a trivial piece of work
>> unless the new command also requires a new file STRUcture
>> variation.
>
> I don't see a problem on FTP protocol level, with TYPE I the transfered d=
ata
> is an unstructured stream of bytes, in which REST currently defines a
> starting point and in which a RANGE specification would additionally defi=
ne
> an endpoint.

Agree.

> FTP clients and servers operating on files which are not simply a stream =
of
> bytes but e.g. have some length-delimited record structure may have hard
> work to do, but this problem exists already with the current REST command=
.
>

Agree.
RFC3659 5.1 states about this problem:

In other representation types and structures
 more effort will be required, but it remains always possible to
 determine the offset with finite, but perhaps non-negligible, effort.


The transfer modes other than STREAM mode use marker to specify restart poi=
nt
and the marker is sent from sending host.
Then we have no way to know the end point marker because it is not sent.
Because of this, I think it is very hard or impossible to define this
RANGE specification
for other than STREAM mode.
Is it possible to define RANGE specification only in STREAM mode?

Best regards,

Tatsuhiro Tsujikawa

From Internet-Drafts@ietf.org  Wed Dec  8 10:15:06 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 25E643A6849; Wed,  8 Dec 2010 10:15:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 5oUn1eIhk80O; Wed,  8 Dec 2010 10:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 618493A6827; Wed,  8 Dec 2010 10:15:02 -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.10
Message-ID: <20101208181502.13334.10373.idtracker@localhost>
Date: Wed, 08 Dec 2010 10:15:02 -0800
Cc: ftpext@ietf.org
Subject: [ftpext] I-D ACTION:draft-ietf-ftpext2-hosts-01.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, 08 Dec 2010 18:15:06 -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-01.txt
	Pages		: 20
	Date		: 2010-12-8
	
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-01.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-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From Internet-Drafts@ietf.org  Wed Dec  8 10:30:47 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 473BC3A698F; Wed,  8 Dec 2010 10:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.784
X-Spam-Level: 
X-Spam-Status: No, score=-101.784 tagged_above=-999 required=5 tests=[AWL=-0.815, BAYES_00=-2.599, SARE_PROLOSTOCK_SYM3=1.63, 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 0qjU7043zGLx; Wed,  8 Dec 2010 10:30:46 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96C573A6994; Wed,  8 Dec 2010 10:30:03 -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.10
Message-ID: <20101208183003.16873.32193.idtracker@localhost>
Date: Wed, 08 Dec 2010 10:30:03 -0800
Cc: ftpext@ietf.org
Subject: [ftpext] I-D Action:draft-ietf-ftpext2-ftp64-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, 08 Dec 2010 18:30:47 -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 IPv4/IPv6 transition
	Author(s)       : D. Liu, et al.
	Filename        : draft-ietf-ftpext2-ftp64-00.txt
	Pages           : 7
	Date            : 2010-12-08

The File transfer protocol, which is defined by the RFC 959, has a
long history, but still being widely used.  The original version of
FTP specification defines IPv4 version of FTP.  RFC 2428 defines IPv6
extensions of FTP, introducing EPRT and EPSV command.  In the IPv6-
IPv4 translation scenario, considerations should be applied to FTP
client, server and translation box to ensure FTP protocol work
properly.  This document discusses the details for FTP to work in
IPv4-IPv6 transition scenario.  This document proposes to update
IPv6 FTP client's specification to make it easier to work in 6to4
scenario.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ftpext2-ftp64-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-ftp64-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From daniel@haxx.se  Wed Dec  8 14:20:28 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 48B8C3A689E for <ftpext@core3.amsl.com>; Wed,  8 Dec 2010 14:20:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level: 
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[AWL=-0.117, 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 Wg56t4kmUxZK for <ftpext@core3.amsl.com>; Wed,  8 Dec 2010 14:20:27 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id B3D3E3A686B for <ftpext@ietf.org>; Wed,  8 Dec 2010 14:20:26 -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 oB8MLt0P009453 for <ftpext@ietf.org>; Wed, 8 Dec 2010 23:21:55 +0100
Date: Wed, 8 Dec 2010 23:21:55 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: ftpext@ietf.org
In-Reply-To: <20101208181502.13334.10373.idtracker@localhost>
Message-ID: <alpine.DEB.2.00.1012081927080.18372@tvnag.unkk.fr>
References: <20101208181502.13334.10373.idtracker@localhost>
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, 08 Dec 2010 23:21:55 +0100 (CET)
Subject: Re: [ftpext] I-D ACTION:draft-ietf-ftpext2-hosts-01.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, 08 Dec 2010 22:20:28 -0000

On Wed, 8 Dec 2010, Internet-Drafts@ietf.org wrote:

> 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.

This is a very well written document and I really like it. Two 
comments/remarks:


Section 3 (and 3.3) mentions that the server can respond to a late HOST in one 
of two ways (a or b).

Why two? Why not just specify one specific way which will make it easier for 
both client and server authors to behave? (I would personally prefer b but it 
is not a strong preference).


Section 3.1 details that HOST only specify host name or IP address, not port 
number. The HTTP Host: header can (optionally) include a port number. The text 
says that the port number is pointless but I'm not sure that it always is and 
will be. In a time when we use NATs and port forwarders and so on, I can 
imagine a case when you have a front end port (port A) open for clients to 
connect to, but once connected you forward the traffic to an internal site on 
port B (or C or D perhaps when load ballancing for example) and thus the 
internal receiver of the traffic doesn't know which port the client originally 
connected to unless it mentions that.

It's just so easy to also support the port number as I think it would be a 
shame to forbid it since there may actually be usecases for it!

-- 

  / daniel.haxx.se

From anthonybryan@gmail.com  Wed Dec  8 19:48:03 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 881313A694C for <ftpext@core3.amsl.com>; Wed,  8 Dec 2010 19:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.244
X-Spam-Level: 
X-Spam-Status: No, score=-3.244 tagged_above=-999 required=5 tests=[AWL=0.355,  BAYES_00=-2.599, 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 eMvT4-+-ArTj for <ftpext@core3.amsl.com>; Wed,  8 Dec 2010 19:48:02 -0800 (PST)
Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by core3.amsl.com (Postfix) with ESMTP id 210473A682B for <ftpext@ietf.org>; Wed,  8 Dec 2010 19:48:01 -0800 (PST)
Received: by ewy6 with SMTP id 6so1413900ewy.40 for <ftpext@ietf.org>; Wed, 08 Dec 2010 19:49:30 -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=WFH04Gy6YaDnbMlchMfk80uXQmu7qs/DMOx7kaa/7F4=; b=Z5udGkWwBgivgLtWXlwCKIG9e5btQFgxkcLJNU6vfn13LOqpXXxYMo7p7pwMxtTQMB 4cso+c1wZbIfQRWA3N5QRZ4tgmNXbFhUCVtiFSrfO5iyqU1700vzUXQG3m+nSwrRH6Gl dz+T+ibmdrUflrHLlrD8iW4iLNzSNURztztXE=
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=ucTJbdjSEwp/IIIWPAbwqu2rAkgzkWgJZdBa5YbA5nALQJU4C2zDRzXhSOHAf+NnpJ D6jmtu6Xf1NBXxBhPJLTW2fWW7ObHkKfxl9L2O5+HMWlJpvcRZsTY3w6Mb+5M78iNpNd gZgph+EvFcitypb6JRER2UjEdu6W8Py6GOP5o=
MIME-Version: 1.0
Received: by 10.213.3.20 with SMTP id 20mr8761408ebl.89.1291866568190; Wed, 08 Dec 2010 19:49:28 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Wed, 8 Dec 2010 19:49:28 -0800 (PST)
Date: Wed, 8 Dec 2010 22:49:28 -0500
Message-ID: <AANLkTinXcgu+6U+hMVqAVFbQGX9PYSjv5p35sZ1zudEh@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] FTPEXT2 Working Group pages
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, 09 Dec 2010 03:48:03 -0000

I don't know how much other WGs use the wiki, but I put some info up.

we now have all 4 WG drafts & the related ones here:
http://tools.ietf.org/wg/ftpext2/

I put up the charter dates too:
http://trac.tools.ietf.org/wg/ftpext2/trac/roadmap

also, this page listing FTP RFCs and drafts:
http://trac.tools.ietf.org/wg/ftpext2/trac/wiki/FtpSpecs

anything else that might be useful?
--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads

From alun@texis.com  Fri Dec 10 09:35:58 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 DDD1C28C0F6 for <ftpext@core3.amsl.com>; Fri, 10 Dec 2010 09:35:57 -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 vEZ5Q1yIXrkk for <ftpext@core3.amsl.com>; Fri, 10 Dec 2010 09:35:56 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 2D20328C0DC for <ftpext@ietf.org>; Fri, 10 Dec 2010 09:35:56 -0800 (PST)
Received: from Parnassus (c-76-22-69-139.hsd1.wa.comcast.net [76.22.69.139]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0Lu77W-1QRHz51S22-011iv6; Fri, 10 Dec 2010 12:37:26 -0500
From: "Alun Jones" <alun@texis.com>
To: "'Anthony Bryan'" <anthonybryan@gmail.com>, "'Mark P. Peterson'" <mpp@rhinosoft.com>
References: <1791E3B42BE242848B7FFFC7015B4563@rhinooffice.net>	<AANLkTimeH+O4E4XEq6cdw0UaM4UpDTo6EKB9kB1x4PJh@mail.gmail.com>	<139EAF2195BC496AA3F25288D56BFB43@rhinooffice.net>	<AANLkTinriyMy5_thOnx29HbGQ41NcYW+MS27YGDAjoNT@mail.gmail.com>	<D22AFE44108D486EB4C6F469A61BFB2B@rhinooffice.net> <AANLkTikzavFRiegLQXAophNicGamAXXJ9O=2PTELhknw@mail.gmail.com>
In-Reply-To: <AANLkTikzavFRiegLQXAophNicGamAXXJ9O=2PTELhknw@mail.gmail.com>
Date: Fri, 10 Dec 2010 09:37:18 -0800
Organization: Texas Imperial Software
Message-ID: <049101cb9890$e8dde580$ba99b080$@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: AcuQLEpR5TmeaNxJTWKF9M185Gc/cwIYUlkA
Content-Language: en-us
X-Provags-ID: V02:K0:0+j3PfjwvLewl8ddNfSfg9+fYOqgoIAcdHf8BnuEvkL TFW0xxK1xgvf/dIkg9OYUx+xMri7uMZhiuxAjGZm07d/gvYYwt SNffq8KV+u9TO2I0j8YBMElelEy7qLMgw/SZDCbsirhLdYvso6 kmnqlcliNZ5N390/KJ2/QAQ8b0toJZrzCZmoeaSRquOSMz9lBD EtRfkRqcLS4tZ3IxDwwUA==
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
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, 10 Dec 2010 17:35:58 -0000

> From: ftpext-bounces@ietf.org [mailto:ftpext-bounces@ietf.org] On
> 
> <chair hat="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.

I see AVBL as being very similar to the ALLO command - in fact, for many of
the suggested uses of AVBL (checking that space is sufficient before
starting a long upload), it would seem that ALLO is better. Using AVBL to
check if there's room for a 10GB file suffers from the possibility that
there are two users uploading a 10GB file, and each gets to put 5.1GB up
before failing. Using ALLO means that whoever requests the space first, gets
that space (subject to quota requirements), the other guy gets told he can't
upload right now.

ALLO is defined in RFC 959 (and probably earlier).

Alun.
~~~~


From daniel@haxx.se  Mon Dec 20 00:32: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 1A6B53A6A1F for <ftpext@core3.amsl.com>; Mon, 20 Dec 2010 00:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level: 
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=-1.199, 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 dNEZJFLis0p3 for <ftpext@core3.amsl.com>; Mon, 20 Dec 2010 00:32:15 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id AE1143A6A14 for <ftpext@ietf.org>; Mon, 20 Dec 2010 00:32: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 oBK8Y5gm002775 for <ftpext@ietf.org>; Mon, 20 Dec 2010 09:34:05 +0100
Date: Mon, 20 Dec 2010 09:34:05 +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.1012200851550.4567@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]); Mon, 20 Dec 2010 09:34:05 +0100 (CET)
Subject: [ftpext] File Transfer Protocol RANG Command for Byte Ranges
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, 20 Dec 2010 08:32:16 -0000

Hi friends,

Based on our previous discussions in the "End byte of transfer in FTP" thread 
on this list, we[1] have jotted down a draft for how a new "RANG" command for 
FTP could work:

 	http://www.ietf.org/id/draft-bryan-ftp-range-00.txt

As we see existing use-cases for this feature, we think it would be great to 
get it supported using regular means instead of the "hacks" currently in use 
in FTP clients.

We'd love to get some feedback and comments on what we've come up with so far!

1 = We are Tatsuhiro Tsujikawa, Anthony Bryan and myself.

-- 

  / daniel.haxx.se

From Richard.Koenning@ts.fujitsu.com  Mon Dec 20 07:35:47 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 DCF5D3A6A14 for <ftpext@core3.amsl.com>; Mon, 20 Dec 2010 07:35:47 -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 ATTS37l8u-Mx for <ftpext@core3.amsl.com>; Mon, 20 Dec 2010 07:35:46 -0800 (PST)
Received: from dgate10.ts.fujitsu.com (dgate10.ts.fujitsu.com [80.70.172.49]) by core3.amsl.com (Postfix) with ESMTP id 9264F3A66B4 for <ftpext@ietf.org>; Mon, 20 Dec 2010 07:35:46 -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:CC:Subject: References:In-Reply-To:Content-Type: Content-Transfer-Encoding; b=VBCcl/YOk4V+3l9H9zY/37Tj3IKVu9bCsSY+2HTt4JAdCH/dzyM375bE MxMfqHYXZkt0nwB0Kjk9isdAB9orECOYgS1fDe8pN9/gp8mG2CnR3BJAu dvBsqlCBc4NV5pH5n6cd1bYa11oijA2Bj7QTUmT0UDarTO/jTGCaE01vt HsF8xBSwlRvXuEuTdklh3ZFAoL0irWi/fUMEaeiNRUGUinBtEG46ogL1Z ClPQhA0VGYFTwM916rf/JACWVzZqQ;
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=1292859461; x=1324395461; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; z=Message-ID:=20<4D0F7841.2080108@ts.fujitsu.com>|Date:=20 Mon,=2020=20Dec=202010=2016:37:37=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>|CC:=20Daniel =20Stenberg=20<daniel@haxx.se>|Subject:=20Re:=20[ftpext] =20File=20Transfer=20Protocol=20RANG=20Command=20for=20By te=20Ranges|References:=20<alpine.DEB.2.00.1012200851550. 4567@tvnag.unkk.fr>|In-Reply-To:=20<alpine.DEB.2.00.10122 00851550.4567@tvnag.unkk.fr>|Content-Transfer-Encoding: =20quoted-printable; bh=LC/u1+NXupWmTovAHNs1GEBkepRQ0ltwXok22B5+aJE=; b=T6EugPsmlwPI7XFGr1ZcgAXNoCK1YtrdQ4mHbJV+iyWbGcTJsW5ylQ/e hdH8r41YMQG1uNSohhXeVjmLXC2dTiDokzVhuj5x0tcnrTBwaQhJ2o3N7 2PlWtLBICKgWjnRrEt2cdadJNFUqxH+YVMmIFLiEc9c8O7UYojUBrUGfe BgdOsPYa6q7azuvjfR8TCq8Sxdl3gmJ+VKmYTSylyjFqOmOQbYFmhkMzJ CfiY+IKN6yDWLA04l+PdGqShslr9T;
X-SBRSScore: None
X-IronPort-AV: E=Sophos;i="4.60,202,1291590000"; d="scan'208";a="63861852"
Received: from abgdgate30u.abg.fsc.net ([172.25.138.66]) by dgate10u.abg.fsc.net with ESMTP; 20 Dec 2010 16:37:38 +0100
X-IronPort-AV: E=Sophos;i="4.60,202,1291590000"; d="scan'208";a="105821571"
Received: from mch8469d.mch.fsc.net (HELO [172.25.52.240]) ([172.25.52.240]) by abgdgate30u.abg.fsc.net with ESMTP; 20 Dec 2010 16:37:38 +0100
Message-ID: <4D0F7841.2080108@ts.fujitsu.com>
Date: Mon, 20 Dec 2010 16:37:37 +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: <alpine.DEB.2.00.1012200851550.4567@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.00.1012200851550.4567@tvnag.unkk.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: Daniel Stenberg <daniel@haxx.se>
Subject: Re: [ftpext] File Transfer Protocol RANG Command for Byte Ranges
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, 20 Dec 2010 15:35:48 -0000

Hello,

Daniel Stenberg wrote:

> Based on our previous discussions in the "End byte of transfer in FTP" =
thread=20
> on this list, we[1] have jotted down a draft for how a new "RANG" comma=
nd for=20
> FTP could work:
>=20
>  	http://www.ietf.org/id/draft-bryan-ftp-range-00.txt
>=20
> As we see existing use-cases for this feature, we think it would be gre=
at to=20
> get it supported using regular means instead of the "hacks" currently i=
n use=20
> in FTP clients.

iirc some FTP server implementations support the SIZE/REST commands only =

for TYPE I, because supporting it for TYPE A or E would require to read=20
the file completely before giving an answer, which would make the server =

prone to DoS attacks. These implementations will probably confine the=20
RANG command to TYPE I too.
The description of error code 551 gives me the impression that the RANG=20
command is intended only for TYPE I, but from section 3 i got the=20
impression that in principle all representation types shall be=20
supported. If the latter is true, but implementations are allowed to=20
support e.g. only TYPE I, in my opinion there should be an error code=20
for indication of such a partial support besides the all-or-nothing 500/5=
52.
Best regards,
Richard K=F6nning
--=20
Dr. Richard W. K=F6nning
Fujitsu Technology Solutions GmbH


From daniel@haxx.se  Mon Dec 20 13:35:24 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 D135F3A68F7 for <ftpext@core3.amsl.com>; Mon, 20 Dec 2010 13:35:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.385
X-Spam-Level: 
X-Spam-Status: No, score=-3.385 tagged_above=-999 required=5 tests=[AWL=-1.136, 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 s7RE68wMDMds for <ftpext@core3.amsl.com>; Mon, 20 Dec 2010 13:35:23 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id 63BEA3A68EC for <ftpext@ietf.org>; Mon, 20 Dec 2010 13:35:23 -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 oBKLbJGJ014158; Mon, 20 Dec 2010 22:37:19 +0100
Date: Mon, 20 Dec 2010 22:37:19 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Richard Koenning <Richard.Koenning@ts.fujitsu.com>
In-Reply-To: <4D0F7841.2080108@ts.fujitsu.com>
Message-ID: <alpine.DEB.2.00.1012202235110.8006@tvnag.unkk.fr>
References: <alpine.DEB.2.00.1012200851550.4567@tvnag.unkk.fr> <4D0F7841.2080108@ts.fujitsu.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Mon, 20 Dec 2010 22:37:19 +0100 (CET)
Cc: "ftpext@ietf.org" <ftpext@ietf.org>
Subject: Re: [ftpext] File Transfer Protocol RANG Command for Byte Ranges
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, 20 Dec 2010 21:35:24 -0000

On Mon, 20 Dec 2010, Richard Koenning wrote:

>>  	http://www.ietf.org/id/draft-bryan-ftp-range-00.txt
>
> iirc some FTP server implementations support the SIZE/REST commands only for 
> TYPE I, because supporting it for TYPE A or E would require to read the file 
> completely before giving an answer, which would make the server prone to DoS 
> attacks. These implementations will probably confine the RANG command to 
> TYPE I too.

I think it make sense to limit the command to only TYPE I transfers, as long 
as nobody can come up with a plausible way and use case for another type.

-- 

  / daniel.haxx.se

From iljitsch@muada.com  Tue Dec 21 15:02:53 2010
Return-Path: <iljitsch@muada.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 3AEFA3A6ACA for <ftpext@core3.amsl.com>; Tue, 21 Dec 2010 15:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.056
X-Spam-Level: 
X-Spam-Status: No, score=-102.056 tagged_above=-999 required=5 tests=[AWL=0.543, 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 qXLER+i3siG1 for <ftpext@core3.amsl.com>; Tue, 21 Dec 2010 15:02:52 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 112E03A6A6F for <ftpext@ietf.org>; Tue, 21 Dec 2010 15:02:51 -0800 (PST)
Received: from [192.168.0.193] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id oBLN4kqH060535 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ftpext@ietf.org>; Wed, 22 Dec 2010 00:04:47 +0100 (CET) (envelope-from iljitsch@muada.com)
From: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 22 Dec 2010 00:04:42 +0100
Message-Id: <C04E4326-D403-4B8F-B6E2-506B1FECB4FE@muada.com>
To: ftpext@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [ftpext] RFC 2640
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, 21 Dec 2010 23:02:53 -0000

Hi,

We're having a discussion on how the FTP64 ALG should support RFC 2640, =
which allows clients and servers to negotiate a language for the free =
text that the FTP server sends to the client.

My opinion is that it would be ok for the ALG to create text in the =
default language (presumably English) even if the client and server =
negotiate another language. Another solution would be to block such =
negotiations but I don't like this extra complexity and I'm not sure =
that having the server's text in a non-preferred language for =
consistency with the ALG's text helps the user.

My questions:

- are there any RFC 2640-compliant implementations out there?

- anyone have a problem with moving RFC 2640 to historic?

Iljitsch=

From tj@castaglia.org  Tue Dec 21 15:40:45 2010
Return-Path: <tj@castaglia.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 17D003A6910 for <ftpext@core3.amsl.com>; Tue, 21 Dec 2010 15:40:45 -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 DV8Itge-l+eQ for <ftpext@core3.amsl.com>; Tue, 21 Dec 2010 15:40:42 -0800 (PST)
Received: from new1.smtp.messagingengine.com (new1.smtp.messagingengine.com [66.111.4.221]) by core3.amsl.com (Postfix) with ESMTP id BAAED3A67FA for <ftpext@ietf.org>; Tue, 21 Dec 2010 15:40:41 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 23DD5200E1; Tue, 21 Dec 2010 18:42:38 -0500 (EST)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 21 Dec 2010 18:42:38 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:from:to:cc:subject:in-reply-to:message-id:references:mime-version:content-type; s=smtpout; bh=4INnRT1oCkGYzEXlqPyiMMkNchc=; b=R2jclLdmny202ok1XLkZYBHuE3/bUHwUap0Xb3CAu35iqzU0yrMii4SoPjewXnZ4gHXEnAYbuLNDCTS8DMV53xgT3hLqfjFgm9BSB+BmTluciC8xaGmxaPlZ17iKbSALA2sV1YGyaI8BD2muzNw6KvQAMg3Qk68wSvOanjtgjVM=
X-Sasl-enc: 8ERYVHsF15ZW+oinPDgcRKH+yb/YAQHJ22VNXM14uP6c 1292974957
Received: from familiar.netflix.com (lg-nat.corp.netflix.com [208.75.77.65]) by mail.messagingengine.com (Postfix) with ESMTPSA id 84051443F13; Tue, 21 Dec 2010 18:42:37 -0500 (EST)
Date: Tue, 21 Dec 2010 15:42:36 -0800 (PST)
From: "TJ Saunders" <tj@castaglia.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <C04E4326-D403-4B8F-B6E2-506B1FECB4FE@muada.com>
Message-ID: <alpine.DEB.2.00.1012211542050.12930@familiar.castaglia.org>
References: <C04E4326-D403-4B8F-B6E2-506B1FECB4FE@muada.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ftpext@ietf.org
Subject: Re: [ftpext] RFC 2640
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, 21 Dec 2010 23:40:45 -0000

> My questions:
> 
> - are there any RFC 2640-compliant implementations out there?

Yes.  ProFTPD, when built with NLS support, implements RFC 2640.

Cheers,
TJ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Much of your pain is self-chosen.

     -Kahlil Gibran

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

From iljitsch@muada.com  Wed Dec 22 03:40:25 2010
Return-Path: <iljitsch@muada.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 A75B63A6AD9; Wed, 22 Dec 2010 03:40:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, 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 aCt6qzsT4DyX; Wed, 22 Dec 2010 03:39:19 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 64B113A6B14; Wed, 22 Dec 2010 03:39:19 -0800 (PST)
Received: from claw.it.uc3m.es ([163.117.139.69]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id oBMBfDjQ063719 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 Dec 2010 12:41:13 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Date: Wed, 22 Dec 2010 12:40:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com>
References: <0cac01cb58ea$32d19a60$9874cf20$@com> <9B57C850BB53634CACEC56EF4853FF65343005F2@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <B166ACF7-FA96-4954-8411-A86BC7923A76@muada.com> <9B57C850BB53634CACEC56EF4853FF653447D195@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
To: Dave Thaler <dthaler@microsoft.com>
X-Mailer: Apple Mail (2.1082)
Cc: draft-ietf-behave-ftp64@tools.ietf.org, ftpext@ietf.org, Behave WG <behave@ietf.org>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
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, 22 Dec 2010 11:40:25 -0000

[CC to ftpext, please prune as desired when following up]

On 22 dec 2010, at 1:32, Dave Thaler wrote:

> To your later question, Microsoft's IIS does support RFC 2640
> in its FTP server.  Microsoft's current FTP clients, on the other =
hand, do not
> support RFC 2640.

And so does ProFTPD.

I quickly checked maybe a dozen FTP sites. A few of them supported LANG, =
although none any languages other than English, one UTF8 but not LANG, =
one LANG but not FEAT (which is in non-conformance to RFC 2640). So I =
guess a quick deprecation is off the table.

After reading RFC 2640 a bit more closely, it turns out that it actually =
allows CR/LFs in filenames, but those are escaped using a null =
character. This probably warrants a warning in the FTP64 document, as =
ALG implementers may not be aware of this and of course a null character =
has special meaning in languages such as C.

Back to the original problem.

Ideally, the ALG would observe the LANG negotiation and then send text =
in the desired language. However, there is no way to make sure that the =
ALG supports all the languages that clients and servers may support, so =
even if the ALG makes this attempt, there will be cases when it can't =
provide text in the desired language.

When that happens, there are two choices:

1. block the LANG negotiation and use the default language

2. ignore the LANG negotiation and use the default language

The advantage of 1 is consistency. However, this is more complex to =
implement and despite some evidence of LANG support I fear that actual =
use of this feature is too low to see good real-world testing, so there =
is a significant risk of bugs that won't come to light until the ALG is =
widely deployed. Another downside is that the user is now deprived of =
text in the desired language for text sent by the server that isn't =
touched by the ALG. Most notably, this would be the greetings. With =
failed LANG negotiation, users probably also wouldn't be able to use =
UTF-8 user names, passwords or path names.

The advantage of 2 is implementation simplicity and that the majority of =
the text is still in the desired language. However, some server =
responses will be in the ALG's (default) language rather than in the =
negotiated language. (But informed users can still see what's going on =
from the numeric response, the text is merely additional information.)

I propose the following:

- provide some explanation of the issue in the document
- ALGs MUST support UTF-8 and the CR0LF thing
- ALGs MAY monitor the LANG negotiation and adjust their language =
accordingly (with no opinion about what happens when the ALG supports =
the user desired language but the server doesn't)
- if the ALG doesn't monitor the LANG negotiation or doesn't support the =
negotiated language, it uses its default language

Thoughts?=

From dthaler@microsoft.com  Wed Dec 22 08:38:11 2010
Return-Path: <dthaler@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 75F103A6B2A; Wed, 22 Dec 2010 08:38:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.242
X-Spam-Level: 
X-Spam-Status: No, score=-110.242 tagged_above=-999 required=5 tests=[AWL=-0.243, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_HI=-8, 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 95+LUc2Y8d+E; Wed, 22 Dec 2010 08:38:10 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 435F03A6A67; Wed, 22 Dec 2010 08:38:10 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 22 Dec 2010 08:40:08 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.1.255.3; Wed, 22 Dec 2010 08:40:08 -0800
Received: from TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com ([169.254.4.151]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Wed, 22 Dec 2010 08:40:08 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Thread-Topic: [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
Thread-Index: ActY6jKKLqeAf6WHSOikuiNZqgewtAH/d6IwBraFzQAJXXikgAAN1huAACguIwAABqYt8A==
Date: Wed, 22 Dec 2010 16:40:06 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653447F40D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
References: <0cac01cb58ea$32d19a60$9874cf20$@com> <9B57C850BB53634CACEC56EF4853FF65343005F2@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <B166ACF7-FA96-4954-8411-A86BC7923A76@muada.com> <9B57C850BB53634CACEC56EF4853FF653447D195@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com>
In-Reply-To: <8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 22 Dec 2010 08:46:56 -0800
Cc: "draft-ietf-behave-ftp64@tools.ietf.org" <draft-ietf-behave-ftp64@tools.ietf.org>, "ftpext@ietf.org" <ftpext@ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
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, 22 Dec 2010 16:38:11 -0000

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Wednesday, December 22, 2010 3:41 AM
> To: Dave Thaler
> Cc: draft-ietf-behave-ftp64@tools.ietf.org; Behave WG; ftpext@ietf.org
> Subject: Re: [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
>=20
> [CC to ftpext, please prune as desired when following up]
>=20
> On 22 dec 2010, at 1:32, Dave Thaler wrote:
>=20
> > To your later question, Microsoft's IIS does support RFC 2640
> > in its FTP server.  Microsoft's current FTP clients, on the other hand,=
 do not
> > support RFC 2640.
>=20
> And so does ProFTPD.
>=20
> I quickly checked maybe a dozen FTP sites. A few of them supported LANG,
> although none any languages other than English, one UTF8 but not LANG, on=
e
> LANG but not FEAT (which is in non-conformance to RFC 2640). So I guess a
> quick deprecation is off the table.
>=20
> After reading RFC 2640 a bit more closely, it turns out that it actually =
allows
> CR/LFs in filenames, but those are escaped using a null character. This p=
robably
> warrants a warning in the FTP64 document, as ALG implementers may not be
> aware of this and of course a null character has special meaning in langu=
ages
> such as C.
>=20
> Back to the original problem.
>=20
> Ideally, the ALG would observe the LANG negotiation and then send text in=
 the
> desired language. However, there is no way to make sure that the ALG supp=
orts
> all the languages that clients and servers may support, so even if the AL=
G makes
> this attempt, there will be cases when it can't provide text in the desir=
ed
> language.
>=20
> When that happens, there are two choices:
>=20
> 1. block the LANG negotiation and use the default language
>=20
> 2. ignore the LANG negotiation and use the default language

Yes for LANG (as opposed to the FEAT exchange), those are the same as I=20
described in my email.

> The advantage of 1 is consistency. However, this is more complex to imple=
ment
> and despite some evidence of LANG support I fear that actual use of this =
feature
> is too low to see good real-world testing, so there is a significant risk=
 of bugs
> that won't come to light until the ALG is widely deployed. Another downsi=
de is
> that the user is now deprived of text in the desired language for text se=
nt by the
> server that isn't touched by the ALG. Most notably, this would be the gre=
etings.
> With failed LANG negotiation, users probably also wouldn't be able to use=
 UTF-8
> user names, passwords or path names.

The last sentence is not correct.   The LANG command only controls the lang=
uage
of the server's text responses.  It has no effect on the ability for the cl=
ient
(or server) to use UTF-8 user names, passwords, or path names.

But yes, the advantage is consistency, and the disadvantage is that you're
limited to languages supported by both the server and the ALG.

>=20
> The advantage of 2 is implementation simplicity and that the majority of =
the text
> is still in the desired language. However, some server responses will be =
in the
> ALG's (default) language rather than in the negotiated language. (But inf=
ormed
> users can still see what's going on from the numeric response, the text i=
s merely
> additional information.)

To repeat my earlier point, the disadvantages are
1) Text from the ALG may render as garbage (even overwriting the numeric re=
sponse,
   making it impossible for the user to see what's going on... remember som=
e languages
   are bidirectional so this isn't just about the backspace character)
2) Some clients might even crash or have other unexpected behavior, since
    2 appears to violate RFC 2640 and hence could easily have untested beha=
vior.

To me, the above disadvantages are strong arguments against 2.

>=20
> I propose the following:
>=20
> - provide some explanation of the issue in the document
> - ALGs MUST support UTF-8 and the CR0LF thing
> - ALGs MAY monitor the LANG negotiation and adjust their language accordi=
ngly
> (with no opinion about what happens when the ALG supports the user desire=
d
> language but the server doesn't)

Personally, I think the above MAY needs to be a MUST.

> - if the ALG doesn't monitor the LANG negotiation or doesn't support the
> negotiated language, it uses its default language
>=20
> Thoughts?

-Dave

From dthaler@microsoft.com  Wed Dec 22 09:17:12 2010
Return-Path: <dthaler@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 B75B43A67FD; Wed, 22 Dec 2010 09:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level: 
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 hNEFBSKZ-A9w; Wed, 22 Dec 2010 09:17:11 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id D6AC83A6B30; Wed, 22 Dec 2010 09:17:11 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 22 Dec 2010 09:19:10 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.1.255.3; Wed, 22 Dec 2010 09:19:09 -0800
Received: from TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com ([169.254.4.151]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Wed, 22 Dec 2010 09:19:09 -0800
From: Dave Thaler <dthaler@microsoft.com>
To: Dave Thaler <dthaler@microsoft.com>, Iljitsch van Beijnum <iljitsch@muada.com>
Thread-Topic: [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
Thread-Index: ActY6jKKLqeAf6WHSOikuiNZqgewtAH/d6IwBraFzQAJXXikgAAN1huAACguIwAABqYt8AALsh7Q
Date: Wed, 22 Dec 2010 17:19:08 +0000
Message-ID: <9B57C850BB53634CACEC56EF4853FF653447F599@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
References: <0cac01cb58ea$32d19a60$9874cf20$@com> <9B57C850BB53634CACEC56EF4853FF65343005F2@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <B166ACF7-FA96-4954-8411-A86BC7923A76@muada.com> <9B57C850BB53634CACEC56EF4853FF653447D195@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com> <9B57C850BB53634CACEC56EF4853FF653447F40D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF653447F40D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-behave-ftp64@tools.ietf.org" <draft-ietf-behave-ftp64@tools.ietf.org>, "ftpext@ietf.org" <ftpext@ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
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, 22 Dec 2010 17:17:12 -0000

One more comment...

[...]
> > Ideally, the ALG would observe the LANG negotiation and then send text
> > in the desired language. However, there is no way to make sure that
> > the ALG supports all the languages that clients and servers may
> > support, so even if the ALG makes this attempt, there will be cases
> > when it can't provide text in the desired language.
> >
> > When that happens, there are two choices:
> >
> > 1. block the LANG negotiation and use the default language
> >
> > 2. ignore the LANG negotiation and use the default language
>=20
> Yes for LANG (as opposed to the FEAT exchange), those are the same as I
> described in my email.
>=20
> > The advantage of 1 is consistency. However, this is more complex to
> > implement and despite some evidence of LANG support I fear that actual
> > use of this feature is too low to see good real-world testing, so
> > there is a significant risk of bugs that won't come to light until the
> > ALG is widely deployed. Another downside is that the user is now
> > deprived of text in the desired language for text sent by the server th=
at isn't
> touched by the ALG. Most notably, this would be the greetings.
> > With failed LANG negotiation, users probably also wouldn't be able to
> > use UTF-8 user names, passwords or path names.
>=20
> The last sentence is not correct.   The LANG command only controls the
> language
> of the server's text responses.  It has no effect on the ability for the =
client (or
> server) to use UTF-8 user names, passwords, or path names.
>=20
> But yes, the advantage is consistency, and the disadvantage is that you'r=
e
> limited to languages supported by both the server and the ALG.
>=20
> >
> > The advantage of 2 is implementation simplicity and that the majority
> > of the text is still in the desired language. However, some server
> > responses will be in the ALG's (default) language rather than in the
> > negotiated language. (But informed users can still see what's going on
> > from the numeric response, the text is merely additional information.)
>=20
> To repeat my earlier point, the disadvantages are
> 1) Text from the ALG may render as garbage (even overwriting the numeric
> response,
>    making it impossible for the user to see what's going on... remember s=
ome
> languages
>    are bidirectional so this isn't just about the backspace character)
> 2) Some clients might even crash or have other unexpected behavior, since
>     2 appears to violate RFC 2640 and hence could easily have untested be=
havior.
>=20
> To me, the above disadvantages are strong arguments against 2.

Of course, in theory, neither of the above *should* be a problem=20
if implementations deal with text correctly.  I guess the main point
is about RFC compliance and levels of testing.

I wouldn't want to apparently violate RFC 2640 without the=20
FTPEXT group's consent, so that would be the question to the FTPEXT list.

-Dave=20


From dwing@cisco.com  Thu Dec 23 10:04:37 2010
Return-Path: <dwing@cisco.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 5D7063A6856; Thu, 23 Dec 2010 10:04:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.512
X-Spam-Level: 
X-Spam-Status: No, score=-110.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 0tt0sfHNKVxh; Thu, 23 Dec 2010 10:04:35 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 81FDC3A6850; Thu, 23 Dec 2010 10:04:35 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAN8dE02rR7H+/2dsb2JhbACXN4x0c6Vnmy6FSgSEZQ
X-IronPort-AV: E=Sophos;i="4.60,219,1291593600"; d="scan'208";a="640611294"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-6.cisco.com with ESMTP; 23 Dec 2010 18:06:36 +0000
Received: from dwingWS (sjc-vpn2-687.cisco.com [10.21.114.175]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id oBNI6ajr022399; Thu, 23 Dec 2010 18:06:36 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dave Thaler'" <dthaler@microsoft.com>, "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <0cac01cb58ea$32d19a60$9874cf20$@com>	<9B57C850BB53634CACEC56EF4853FF65343005F2@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>	<B166ACF7-FA96-4954-8411-A86BC7923A76@muada.com>	<9B57C850BB53634CACEC56EF4853FF653447D195@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>	<9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>	<8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com>	<9B57C850BB53634CACEC56EF4853FF653447F40D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447F599@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF653447F599@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 23 Dec 2010 10:06:36 -0800
Message-ID: <049901cba2cc$238f67e0$6aae37a0$@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: ActY6jKKLqeAf6WHSOikuiNZqgewtAH/d6IwBraFzQAJXXikgAAN1huAACguIwAABqYt8AALsh7QABxF4tA=
Content-Language: en-us
Cc: draft-ietf-behave-ftp64@tools.ietf.org, ftpext@ietf.org, 'Behave WG' <behave@ietf.org>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
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, 23 Dec 2010 18:04:37 -0000

<soapbox>
This thread underscores why standardizing an ALGs is terribly 
difficult.  In this case, the addition of a new feature (LANG
command) on the client and server requires the ALG to either
break that new feature or to fully support the new feature.
For the ALG to fully support LANG, that means an ALG has 
to support all possible languages that can be expressed by 
LANG.

... and, remember, FTP is a "simple" protocol.
</soapbox>

The best solution I see is the FTP64 ALG has to (MUST) 
remove LANG from the server's FEAT response, and translate
the LANG command to NOOP and return a 5xy response to the
client.


If an FTP client, running on an IPv6-only machine, does not
like LANG being disabled, there are two solutions:

  1. the FTP client has to implement the "ALGS DISABLE64" 
     command, and ensure the IPv4-only FTP server it is 
     using properly supports the EPSV command.  This
     is, effectively, draft-ietf-ftpext2-ftp64-00.
OR
  2. have the FTP server add an AAAA record, and properly
     support the EPSV command.  This causes the FTP traffic
     to not use the NAT64 or FTP64 ALG.

-d




> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Dave Thaler
> Sent: Wednesday, December 22, 2010 9:19 AM
> To: Dave Thaler; Iljitsch van Beijnum
> Cc: draft-ietf-behave-ftp64@tools.ietf.org; ftpext@ietf.org; Behave WG
> Subject: Re: [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
> 
> One more comment...
> 
> [...]
> > > Ideally, the ALG would observe the LANG negotiation and then send
> text
> > > in the desired language. However, there is no way to make sure that
> > > the ALG supports all the languages that clients and servers may
> > > support, so even if the ALG makes this attempt, there will be cases
> > > when it can't provide text in the desired language.
> > >
> > > When that happens, there are two choices:
> > >
> > > 1. block the LANG negotiation and use the default language
> > >
> > > 2. ignore the LANG negotiation and use the default language
> >
> > Yes for LANG (as opposed to the FEAT exchange), those are the same as
> I
> > described in my email.
> >
> > > The advantage of 1 is consistency. However, this is more complex to
> > > implement and despite some evidence of LANG support I fear that
> actual
> > > use of this feature is too low to see good real-world testing, so
> > > there is a significant risk of bugs that won't come to light until
> the
> > > ALG is widely deployed. Another downside is that the user is now
> > > deprived of text in the desired language for text sent by the
> server that isn't
> > touched by the ALG. Most notably, this would be the greetings.
> > > With failed LANG negotiation, users probably also wouldn't be able
> to
> > > use UTF-8 user names, passwords or path names.
> >
> > The last sentence is not correct.   The LANG command only controls
> the
> > language
> > of the server's text responses.  It has no effect on the ability for
> the client (or
> > server) to use UTF-8 user names, passwords, or path names.
> >
> > But yes, the advantage is consistency, and the disadvantage is that
> you're
> > limited to languages supported by both the server and the ALG.
> >
> > >
> > > The advantage of 2 is implementation simplicity and that the
> majority
> > > of the text is still in the desired language. However, some server
> > > responses will be in the ALG's (default) language rather than in
> the
> > > negotiated language. (But informed users can still see what's going
> on
> > > from the numeric response, the text is merely additional
> information.)
> >
> > To repeat my earlier point, the disadvantages are
> > 1) Text from the ALG may render as garbage (even overwriting the
> numeric
> > response,
> >    making it impossible for the user to see what's going on...
> remember some
> > languages
> >    are bidirectional so this isn't just about the backspace
> character)
> > 2) Some clients might even crash or have other unexpected behavior,
> since
> >     2 appears to violate RFC 2640 and hence could easily have
> untested behavior.
> >
> > To me, the above disadvantages are strong arguments against 2.
> 
> Of course, in theory, neither of the above *should* be a problem
> if implementations deal with text correctly.  I guess the main point
> is about RFC compliance and levels of testing.
> 
> I wouldn't want to apparently violate RFC 2640 without the
> FTPEXT group's consent, so that would be the question to the FTPEXT
> list.
> 
> -Dave
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From iljitsch@muada.com  Thu Dec 23 10:11:17 2010
Return-Path: <iljitsch@muada.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 5AFA13A6855; Thu, 23 Dec 2010 10:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 iydbjXllAOlB; Thu, 23 Dec 2010 10:11:07 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 483AD3A685A; Thu, 23 Dec 2010 10:11:03 -0800 (PST)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id oBNICvC3072895 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Dec 2010 19:12:57 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <049901cba2cc$238f67e0$6aae37a0$@com>
Date: Thu, 23 Dec 2010 19:12:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <101F87C4-F714-48C2-852A-67332B712DD1@muada.com>
References: <0cac01cb58ea$32d19a60$9874cf20$@com>	<9B57C850BB53634CACEC56EF4853FF65343005F2@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>	<B166ACF7-FA96-4954-8411-A86BC7923A76@muada.com>	<9B57C850BB53634CACEC56EF4853FF653447D195@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>	<9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>	<8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com>	<9B57C850BB53634CACEC56EF4853FF653447F40D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447F599@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <049901cba2cc$238f67e0$6aae37a0$@com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: draft-ietf-behave-ftp64@tools.ietf.org, ftpext@ietf.org, 'Behave WG' <behave@ietf.org>, 'Dave Thaler' <dthaler@microsoft.com>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
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, 23 Dec 2010 18:11:17 -0000

On 23 dec 2010, at 19:06, Dan Wing wrote:

> The best solution I see is the FTP64 ALG has to (MUST)=20
> remove LANG from the server's FEAT response, and translate
> the LANG command to NOOP and return a 5xy response to the
> client.

But how does making the server use the default language make the user's =
experience any better?=

From dwing@cisco.com  Thu Dec 23 10:25:01 2010
Return-Path: <dwing@cisco.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 43FF53A6858; Thu, 23 Dec 2010 10:25:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.514
X-Spam-Level: 
X-Spam-Status: No, score=-110.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 gy4a6TGCz06L; Thu, 23 Dec 2010 10:25:00 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 726F03A6843; Thu, 23 Dec 2010 10:25:00 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFABciE02rR7Hu/2dsb2JhbACXN4x0c6VcmyuFSgSEZQ
X-IronPort-AV: E=Sophos;i="4.60,219,1291593600"; d="scan'208";a="237095583"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 23 Dec 2010 18:27:01 +0000
Received: from dwingWS (sjc-vpn2-687.cisco.com [10.21.114.175]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id oBNIR1ee012334; Thu, 23 Dec 2010 18:27:01 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Iljitsch van Beijnum'" <iljitsch@muada.com>
References: <0cac01cb58ea$32d19a60$9874cf20$@com>	<9B57C850BB53634CACEC56EF4853FF65343005F2@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>	<B166ACF7-FA96-4954-8411-A86BC7923A76@muada.com>	<9B57C850BB53634CACEC56EF4853FF653447D195@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>	<9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>	<8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com>	<9B57C850BB53634CACEC56EF4853FF653447F40D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447F599@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <049901cba2cc$238f67e0$6aae37a0$@com> <101F87C4-F714-48C2-852A-67332B712DD1@muada.com>
In-Reply-To: <101F87C4-F714-48C2-852A-67332B712DD1@muada.com>
Date: Thu, 23 Dec 2010 10:27:01 -0800
Message-ID: <04a401cba2ce$fdba5180$f92ef480$@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: AcuizQsxEH0fsv7gT0CgDu564FTndQAABOLw
Content-Language: en-us
Cc: draft-ietf-behave-ftp64@tools.ietf.org, ftpext@ietf.org, 'Behave WG' <behave@ietf.org>, 'Dave Thaler' <dthaler@microsoft.com>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
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, 23 Dec 2010 18:25:01 -0000

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Thursday, December 23, 2010 10:13 AM
> To: Dan Wing
> Cc: 'Dave Thaler'; draft-ietf-behave-ftp64@tools.ietf.org;
> ftpext@ietf.org; 'Behave WG'
> Subject: Re: [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
> 
> On 23 dec 2010, at 19:06, Dan Wing wrote:
> 
> > The best solution I see is the FTP64 ALG has to (MUST)
> > remove LANG from the server's FEAT response, and translate
> > the LANG command to NOOP and return a 5xy response to the
> > client.
> 
> But how does making the server use the default language make the user's
> experience any better?

The user might have to read something in the FTP server's default
language, but it will be ASCII.  That's better than the FTP client
potentially throwing an error.

-d



From iljitsch@muada.com  Thu Dec 23 13:41:34 2010
Return-Path: <iljitsch@muada.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 B46DA3A68B7; Thu, 23 Dec 2010 13:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 8OyXFcjZ5mXP; Thu, 23 Dec 2010 13:40:59 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id B17343A6895; Thu, 23 Dec 2010 13:40:58 -0800 (PST)
Received: from [192.168.0.195] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id oBNLgpE5073861 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Dec 2010 22:42:52 +0100 (CET) (envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <04a401cba2ce$fdba5180$f92ef480$@com>
Date: Thu, 23 Dec 2010 22:42:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1535EAD-802E-4EF6-ACA5-7F66BCFED987@muada.com>
References: <0cac01cb58ea$32d19a60$9874cf20$@com>	<9B57C850BB53634CACEC56EF4853FF65343005F2@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>	<B166ACF7-FA96-4954-8411-A86BC7923A76@muada.com>	<9B57C850BB53634CACEC56EF4853FF653447D195@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>	<9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>	<8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com>	<9B57C850BB53634CACEC56EF4853FF653447F40D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447F599@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <049901cba2cc$238f67e0$6aae37a0$@com> <101F87C4-F714-48C2-852A-67332B712DD1@muada.com> <04a401cba2ce$fdba5180$f92ef480$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: draft-ietf-behave-ftp64@tools.ietf.org, ftpext@ietf.org, 'Behave WG' <behave@ietf.org>, 'Dave Thaler' <dthaler@microsoft.com>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
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, 23 Dec 2010 21:41:35 -0000

On 23 dec 2010, at 19:27, Dan Wing wrote:

>> But how does making the server use the default language make the =
user's
>> experience any better?

> The user might have to read something in the FTP server's default
> language, but it will be ASCII.  That's better than the FTP client
> potentially throwing an error.

Dave mentioned the client potentially crashing. I don't buy that. An FTP =
client can obviously handle ASCII if the desired LANG is not supported, =
so then it's going to crash when it sees the same characters when =
another language is negotiated but it otherwise sees the same text. It's =
not like 7-bit ASCII characters never occur in languages that use other =
scripts.

Maybe at this point in the discussion it would be good to hear from =
implementers. There are already tons of NAT44 FTP ALGs out there, I =
wonder how those solve this.=

From alun@texis.com  Thu Dec 23 19:53:16 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 F212E3A68CB for <ftpext@core3.amsl.com>; Thu, 23 Dec 2010 19:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.968
X-Spam-Level: 
X-Spam-Status: No, score=-0.968 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_PROLOSTOCK_SYM3=1.63]
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 odITyK5+BSEW for <ftpext@core3.amsl.com>; Thu, 23 Dec 2010 19:53:07 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 1D87A3A68E1 for <ftpext@ietf.org>; Thu, 23 Dec 2010 19:53:07 -0800 (PST)
Received: from Parnassus (c-67-183-209-87.hsd1.wa.comcast.net [67.183.209.87]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0LoEfR-1Q3MTw0nzF-00fsRz; Thu, 23 Dec 2010 22:55:06 -0500
From: "Alun Jones" <alun@wftpd.com>
Sender: "Alun Jones" <alun@texis.com>
To: <ftpext@ietf.org>
Date: Thu, 23 Dec 2010 19:55:04 -0800
Organization: Texas Imperial Software
Message-ID: <001501cba31e$5a3dd860$0eb98920$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01CBA2DB.4C1A9860"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuZoeFcOCqOYAVqT2imeP5Sg9U8QQ==
Content-Language: en-us
X-Provags-ID: V02:K0:0a4mI4eWgTYMZEDOYmt+nMOyk8nm5gqLc4YVUxzSUGp FEk2PXRJa5Lg/d8ojjZzqxVoRDt7N1XOa6JjtuhLAUATiQ1oxu P9b2SxRRbnSLt45+ai0ifYlX1XYupAjxfyXfM5llgz1EhIgZn/ OjGWLGj3W6yJM34EMzIOhMSsERuYz6g6GxJwzRcNLRcvHbm4Sl B8J8kM/fgFRqh4ydzvuSw==
Subject: [ftpext] Firewalls & FTP over TLS.
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, 24 Dec 2010 03:53:16 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01CBA2DB.4C1A9860
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I frequently find I have a hard time selling my FTP server into environments
that are looking for a secure and standard file transfer server.

 

Not because it's not a good and standard implementation of FTP over TLS -
I've found it to work very well with numerous clients.

 

The failure is twofold - one, because the perceived "standard" for this is
SFTP, and two, because of the headache of getting FTP (and particularly FTP
over TLS) to work through a firewall.

 

The "SFTP is a standard" complaint is galling, because of course, SFTP is
not a documented standard, and pretty much requires reverse engineering in
order to make it work. I've been trying to push this message - that SFTP is
flakey compared to FTP over TLS simply because SFTP essentially relies on
each server / client author making tweaks to have it work with those they
test with, rather than coding to a unified standard like FTP over TLS. Maybe
that's not a problem for those of you with SFTP capabilities in your
servers, but personally, I don't find that I want to implement an
undocumented standard.

 

The "Can't make FTP over TLS work through a NAT / firewall" is irritating
too, partly because it seems to be mostly true. In MODE S, TYPE I transfers,
the PORT command or PASV response have to be filtered and altered to open a
port and/or change the IP address to make the connection work. The
alternative is to open a wide swath of ports at the firewall, which security
teams shy away from, and in many companies, outright prohibit.

 

Again, SFTP wins out here, because it works over one port, and one port only
- although opening up port 22 (SSH) essentially says "allow anything",
because SSH is used as a tunnel for multiple random protocols as well as SSH
and SFTP. It would be really nice if FTP could work over predictable port
numbers, especially if they were already opened by the firewall's usual
operation.

 

Well, I've said it before, and got absolutely no response, so I'm asking
again - why don't we use the default port as defined in RFC 959 and before?

 

An FTP (or FTP over TLS) client connecting from port U to port L and sending
a RETR or STOR command (or equivalent) without a PORT or PASV (or EPRT,
EPSV, etc) command will cause the server to connect from server port L-1 to
client port U, and because of the nature of firewalls, they will generally
have opened a hole (server:any => client:U) already.

 

Great, that works for the first transfer, because in MODE S, you close the
TCP data connection to indicate the end of a transfer, and can't open a new
socket (server:L-1 => client:U) for another two to four minutes.

 

Again, there's already an RFC 959 way of getting around this - instead of
using MODE S, use MODE B. Then, although there's a slight penalty in terms
of the chunk markers and restart markers, there's no issue with closing and
re-opening connections in rapid-fire transfers of small files or directory
listings, and it gets through a firewall and a NAT quite happily without
having to provide external IP address mappings, UPNP, or large firewall
holes.

 

While I've been able to test this with my own crappy test client (WFTPD
Client hasn't had enough work put into it to be really good), it would be
great to see this supported across multiple FTP clients and servers. IIS FTP
server already supports MODE B, but I don't really have any idea as to how
wide-spread support for MODE B is, or what features clients and servers
expect to see, or get confused by. I know that one failing in my own server
is a lack of support for restart markers (although it currently works if you
specify byte counts, as if it was in MODE S).

 

Another thing that needs discussing for MODE B support is how ABOR should
work - that's not exactly clear, either.

 

So, who else supports MODE B for firewall / NAT traversal?

 

Alun.

~~~~


------=_NextPart_000_0016_01CBA2DB.4C1A9860
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;}
span.EmailStyle17
	{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;}
--></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>I =
frequently find I have a hard time selling my FTP server into =
environments that are looking for a secure and standard file transfer =
server.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Not because it&#8217;s not a good and standard =
implementation of FTP over TLS &#8211; I&#8217;ve found it to work very =
well with numerous clients.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The failure =
is twofold &#8211; one, because the perceived &#8220;standard&#8221; for =
this is SFTP, and two, because of the headache of getting FTP (and =
particularly FTP over TLS) to work through a firewall.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The =
&#8220;SFTP is a standard&#8221; complaint is galling, because of =
course, SFTP is not a documented standard, and pretty much requires =
reverse engineering in order to make it work. I&#8217;ve been trying to =
push this message &#8211; that SFTP is flakey compared to FTP over TLS =
simply because SFTP essentially relies on each server / client author =
making tweaks to have it work with those they test with, rather than =
coding to a unified standard like FTP over TLS. Maybe that&#8217;s not a =
problem for those of you with SFTP capabilities in your servers, but =
personally, I don&#8217;t find that I want to implement an undocumented =
standard.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The &#8220;Can&#8217;t make FTP over TLS work through =
a NAT / firewall&#8221; is irritating too, partly because it seems to be =
mostly true. In MODE S, TYPE I transfers, the PORT command or PASV =
response have to be filtered and altered to open a port and/or change =
the IP address to make the connection work. The alternative is to open a =
wide swath of ports at the firewall, which security teams shy away from, =
and in many companies, outright prohibit.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Again, SFTP =
wins out here, because it works over one port, and one port only &#8211; =
although opening up port 22 (SSH) essentially says &#8220;allow =
anything&#8221;, because SSH is used as a tunnel for multiple random =
protocols as well as SSH and SFTP. It would be really nice if FTP could =
work over predictable port numbers, especially if they were already =
opened by the firewall&#8217;s usual operation.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Well, =
I&#8217;ve said it before, and got absolutely no response, so I&#8217;m =
asking again &#8211; why don&#8217;t we use the default port as defined =
in RFC 959 and before?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>An FTP (or =
FTP over TLS) client connecting from port U to port L and sending a RETR =
or STOR command (or equivalent) without a PORT or PASV (or EPRT, EPSV, =
etc) command will cause the server to connect from server port L-1 to =
client port U, and because of the nature of firewalls, they will =
generally have opened a hole (server:any =3D&gt; client:U) =
already.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Great, that works for the first transfer, because in =
MODE S, you close the TCP data connection to indicate the end of a =
transfer, and can&#8217;t open a new socket (server:L-1 =3D&gt; =
client:U) for another two to four minutes.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Again, =
there&#8217;s already an RFC 959 way of getting around this &#8211; =
instead of using MODE S, use MODE B. Then, although there&#8217;s a =
slight penalty in terms of the chunk markers and restart markers, =
there&#8217;s no issue with closing and re-opening connections in =
rapid-fire transfers of small files or directory listings, and it gets =
through a firewall and a NAT quite happily without having to provide =
external IP address mappings, UPNP, or large firewall =
holes.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>While I&#8217;ve been able to test this with my own =
crappy test client (WFTPD Client hasn&#8217;t had enough work put into =
it to be really good), it would be great to see this supported across =
multiple FTP clients and servers. IIS FTP server already supports MODE =
B, but I don&#8217;t really have any idea as to how wide-spread support =
for MODE B is, or what features clients and servers expect to see, or =
get confused by. I know that one failing in my own server is a lack of =
support for restart markers (although it currently works if you specify =
byte counts, as if it was in MODE S).<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Another =
thing that needs discussing for MODE B support is how ABOR should work =
&#8211; that&#8217;s not exactly clear, either.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>So, who else =
supports MODE B for firewall / NAT traversal?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Alun.<o:p></o:p></p><p =
class=3DMsoNormal>~~~~<o:p></o:p></p></div></body></html>
------=_NextPart_000_0016_01CBA2DB.4C1A9860--


From prvs=19744f556a=mpp@rhinosoft.com  Thu Dec 23 21:29:30 2010
Return-Path: <prvs=19744f556a=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 922783A68E1 for <ftpext@core3.amsl.com>; Thu, 23 Dec 2010 21:29:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.784
X-Spam-Level: 
X-Spam-Status: No, score=-2.784 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SARE_PROLOSTOCK_SYM3=1.63]
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 EGPu0XSQZxy3 for <ftpext@core3.amsl.com>; Thu, 23 Dec 2010 21:29:27 -0800 (PST)
Received: from rhinosoft.com (mail1.rhinosoft.com [97.88.242.106]) by core3.amsl.com (Postfix) with ESMTP id 681D13A68E9 for <ftpext@ietf.org>; Thu, 23 Dec 2010 21:29:27 -0800 (PST)
Received: from MPNOTEBOOK ([209.242.229.18]) (authenticated user mpp@rhinosoft.com) by rhinosoft.com (rhinosoft.com [127.0.0.1]) (MDaemon PRO v11.0.3) with ESMTP id md50009962949.msg for <ftpext@ietf.org>; Thu, 23 Dec 2010 23:31:27 -0600
X-Spam-Processed: rhinosoft.com, Thu, 23 Dec 2010 23:31:27 -0600 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: mpp@rhinosoft.com
X-MDRemoteIP: 209.242.229.18
X-Return-Path: prvs=19744f556a=mpp@rhinosoft.com
X-Envelope-From: mpp@rhinosoft.com
X-MDaemon-Deliver-To: ftpext@ietf.org
Message-ID: <7E9CC636C5A247FF9B9DA3E9E967E6FB@rhinooffice.net>
From: "Mark P. Peterson" <mpp@rhinosoft.com>
To: <alun@texis.com>, <ftpext@ietf.org>
References: <001501cba31e$5a3dd860$0eb98920$@com>
In-Reply-To: <001501cba31e$5a3dd860$0eb98920$@com>
Date: Thu, 23 Dec 2010 23:31:21 -0600
Organization: Rhino Software, Inc.
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0047_01CBA2F9.81C4DCF0"
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] Firewalls & FTP over TLS.
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, 24 Dec 2010 05:29:31 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0047_01CBA2F9.81C4DCF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Alun,

I just have a couple comments regarding your SFTP comments.

> The "SFTP is a standard" complaint is galling, because of course, SFTP =
is
> not a documented standard, and pretty much requires reverse =
engineering in
> order to make it work.

What are the drafts drafted by J. Galbraith (VanDyke Software) and O. =
Saarenmaa
(F-Secure)?  I've been able to follow these drafts for each SFTP version =
from 3-6.
It isn't easy, but it is possible and doesn't require a lot of reverse =
engineering at
all, just testing just like FTP.

> I've been trying to push this message - that SFTP is flakey compared =
to FTP
> over TLS simply because SFTP essentially relies on each server / =
client author
> making tweaks to have it work with those they test with, rather than =
coding to
> a unified standard like FTP over TLS.

Flakey?  How so?  I've implemented a server which supports SFTP and have =
had
better compatibility than I've seen with many FTPS clients.  If one =
follows the
documentation to the letter and tests with several clients, they all =
seem to work
well.  Many clients base their code on putty, some implement their own, =
and
others rely on libraries.  Those based on putty usually exhibit the same =
behavior.

> Maybe that's not a problem for those of you with SFTP capabilities in =
your
> servers, but personally, I don't find that I want to implement an =
undocumented
> standard.

It's well documented, just not yet an RFC.  Sure the draft is expired =
but both
clients and servers have adopted the protocol widely and is in heavy use =
in the
Linux world.  Each version is documented well, the last that I know of =
is draft 13
which documents the latest version 6 of the protocol:

http://tools.ietf.org/html/draft-ietf-secsh-filexfer-13

Since it is so widely adapted, why can't it become an RFC?

> The "Can't make FTP over TLS work through a NAT / firewall" is =
irritating
> too, partly because it seems to be mostly true. ....

Yes, and all the more reason to use a protocol that is easier for =
end-users to
implement, configure, and to use.  They are the reason we do what we do.

> Again, SFTP wins out here, because it works over one port, and one =
port only
> - although opening up port 22 (SSH) essentially says "allow anything",
> because SSH is used as a tunnel for multiple random protocols as well =
as SSH
> and SFTP.

Right, so let end-users make the choice what they want available via =
port 22 and
SSH2.

> Well, I've said it before, and got absolutely no response, so I'm =
asking
> again - why don't we use the default port as defined in RFC 959 and =
before?

IMO it's because FTP has been around so long and because FTP is =
implemented
on so many platforms, many of which are no longer being developed.  Most
implementations stick with the basics of 959, plain and simple (that =
goes for both
the client and server).

> So, who else supports MODE B for firewall / NAT traversal?

I am sorry to say I haven't had a chance looking at MODE B.  I can say =
your
distaste for SFTP, however, is at the very least intriguing.  It is a =
good
protocol, with some faults, yes, but they can be much more easily
addressed than with FTP.

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



From: Alun Jones=20
Sent: Thursday, December 23, 2010 9:55 PM
To: ftpext@ietf.org=20
Subject: [ftpext] Firewalls & FTP over TLS.


I frequently find I have a hard time selling my FTP server into =
environments that are looking for a secure and standard file transfer =
server.

=20

Not because it's not a good and standard implementation of FTP over TLS =
- I've found it to work very well with numerous clients.

=20

The failure is twofold - one, because the perceived "standard" for this =
is SFTP, and two, because of the headache of getting FTP (and =
particularly FTP over TLS) to work through a firewall.

=20

The "SFTP is a standard" complaint is galling, because of course, SFTP =
is not a documented standard, and pretty much requires reverse =
engineering in order to make it work. I've been trying to push this =
message - that SFTP is flakey compared to FTP over TLS simply because =
SFTP essentially relies on each server / client author making tweaks to =
have it work with those they test with, rather than coding to a unified =
standard like FTP over TLS. Maybe that's not a problem for those of you =
with SFTP capabilities in your servers, but personally, I don't find =
that I want to implement an undocumented standard.

=20

The "Can't make FTP over TLS work through a NAT / firewall" is =
irritating too, partly because it seems to be mostly true. In MODE S, =
TYPE I transfers, the PORT command or PASV response have to be filtered =
and altered to open a port and/or change the IP address to make the =
connection work. The alternative is to open a wide swath of ports at the =
firewall, which security teams shy away from, and in many companies, =
outright prohibit.

=20

Again, SFTP wins out here, because it works over one port, and one port =
only - although opening up port 22 (SSH) essentially says "allow =
anything", because SSH is used as a tunnel for multiple random protocols =
as well as SSH and SFTP. It would be really nice if FTP could work over =
predictable port numbers, especially if they were already opened by the =
firewall's usual operation.

=20

Well, I've said it before, and got absolutely no response, so I'm asking =
again - why don't we use the default port as defined in RFC 959 and =
before?

=20

An FTP (or FTP over TLS) client connecting from port U to port L and =
sending a RETR or STOR command (or equivalent) without a PORT or PASV =
(or EPRT, EPSV, etc) command will cause the server to connect from =
server port L-1 to client port U, and because of the nature of =
firewalls, they will generally have opened a hole (server:any =3D> =
client:U) already.

=20

Great, that works for the first transfer, because in MODE S, you close =
the TCP data connection to indicate the end of a transfer, and can't =
open a new socket (server:L-1 =3D> client:U) for another two to four =
minutes.

=20

Again, there's already an RFC 959 way of getting around this - instead =
of using MODE S, use MODE B. Then, although there's a slight penalty in =
terms of the chunk markers and restart markers, there's no issue with =
closing and re-opening connections in rapid-fire transfers of small =
files or directory listings, and it gets through a firewall and a NAT =
quite happily without having to provide external IP address mappings, =
UPNP, or large firewall holes.

=20

While I've been able to test this with my own crappy test client (WFTPD =
Client hasn't had enough work put into it to be really good), it would =
be great to see this supported across multiple FTP clients and servers. =
IIS FTP server already supports MODE B, but I don't really have any idea =
as to how wide-spread support for MODE B is, or what features clients =
and servers expect to see, or get confused by. I know that one failing =
in my own server is a lack of support for restart markers (although it =
currently works if you specify byte counts, as if it was in MODE S).

=20

Another thing that needs discussing for MODE B support is how ABOR =
should work - that's not exactly clear, either.

=20

So, who else supports MODE B for firewall / NAT traversal?

=20

Alun.

~~~~



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


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

------=_NextPart_000_0047_01CBA2F9.81C4DCF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:v =3D "urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16700">
<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;}
span.EmailStyle17
	{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;}
--></STYLE>
</HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody lang=3DEN-US leftMargin=3D0 link=3Dblue =
topMargin=3D0 vLink=3Dpurple=20
CanvasTabStop=3D"true" name=3D"Compose message area">
<DIV><FONT size=3D2>Hi Alun,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I just have a couple comments regarding your SFTP=20
comments.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&gt; The "SFTP is a standard" complaint is galling, =
because of=20
course, SFTP is<BR>&gt; not a documented standard, and pretty much =
requires=20
reverse engineering in<BR>&gt; order to make it work.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>What are the drafts drafted by J. Galbraith (VanDyke =
Software)=20
and O. Saarenmaa<BR>(F-Secure)?&nbsp; I've been able to follow these =
drafts for=20
each SFTP version from 3-6.</FONT></DIV>
<DIV><FONT size=3D2>It isn't easy, but it is possible and doesn't =
require a lot of=20
reverse engineering at</FONT></DIV>
<DIV><FONT size=3D2>all, just testing just like FTP.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&gt; I've been trying to push this message - that =
SFTP is=20
flakey compared to FTP</FONT></DIV>
<DIV><FONT size=3D2>&gt; over TLS simply because SFTP essentially relies =
on each=20
server / client author</FONT></DIV>
<DIV><FONT size=3D2>&gt; making tweaks to have it work with those they =
test with,=20
rather than coding to</FONT></DIV>
<DIV><FONT size=3D2>&gt; a unified standard like FTP over =
TLS.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Flakey?&nbsp; How so?&nbsp; I've implemented a =
server which=20
supports SFTP </FONT><FONT size=3D2>and have had</FONT></DIV>
<DIV><FONT size=3D2>better compatibility than I've seen with many FTPS=20
clients.&nbsp; If one </FONT><FONT size=3D2>follows the</FONT></DIV>
<DIV><FONT size=3D2>documentation to the letter and tests with several =
clients,=20
they all seem </FONT><FONT size=3D2>to work</FONT></DIV>
<DIV><FONT size=3D2>well.&nbsp; Many clients base their code on putty, =
some=20
implement their own, and</FONT></DIV>
<DIV><FONT size=3D2>others rely on libraries.&nbsp; Those based on putty =
usually=20
exhibit the same behavior.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&gt; Maybe that's not a problem for those of you =
with SFTP=20
capabilities in your<BR>&gt; servers, but personally, I don't find that =
I want=20
to implement an undocumented</FONT></DIV>
<DIV><FONT size=3D2>&gt; standard.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>It's well documented, just not yet an RFC.&nbsp; =
Sure the=20
draft is expired but both</FONT></DIV>
<DIV><FONT size=3D2>clients and servers have adopted the protocol widely =
and is in=20
heavy use in the</FONT></DIV>
<DIV><FONT size=3D2>Linux world.&nbsp; Each version is documented well, =
the last=20
that I know of is draft 13</FONT></DIV>
<DIV><FONT size=3D2>which documents the latest version 6 of the=20
protocol:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://tools.ietf.org/html/draft-ietf-secsh-filexfer-13">http://t=
ools.ietf.org/html/draft-ietf-secsh-filexfer-13</A></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Since it is so widely adapted, why can't it become =
an=20
RFC?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&gt; The "Can't make FTP over TLS work through a NAT =
/=20
firewall" is irritating<BR>&gt; too, partly because it seems to be =
mostly true.=20
....</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Yes, and all the more reason to use a protocol that =
is easier=20
for end-users to</FONT></DIV>
<DIV><FONT size=3D2>implement, configure, and to use.&nbsp; They are the =
reason we=20
do what we do.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&gt; Again, SFTP wins out here, because it works =
over one=20
port, and one port only<BR>&gt; - although opening up port 22 (SSH) =
essentially=20
says "allow anything",<BR>&gt; because SSH is used as a tunnel for =
multiple=20
random protocols as well as SSH<BR>&gt; and SFTP.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Right, so let end-users make the choice what they =
want=20
available via port 22 and</FONT></DIV>
<DIV><FONT size=3D2>SSH2.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; Well, I've said it before, and got absolutely no response, so =
I'm=20
asking<BR>&gt; again - why don't we use the default port as defined in =
RFC 959=20
and before?</DIV>
<DIV>&nbsp;</DIV>
<DIV>IMO it's because FTP has been around so long and because FTP is=20
implemented</DIV>
<DIV>on so many platforms, many of which are no longer being =
developed.&nbsp;=20
Most</DIV>
<DIV>implementations stick with the basics of 959, plain and simple =
(that goes=20
for both</DIV>
<DIV>the client and server).</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; So, who else supports MODE B for firewall / NAT =
traversal?</DIV>
<DIV>&nbsp;</DIV>
<DIV>I am sorry to say I haven't had a chance looking at MODE B.&nbsp; I =
can say=20
your</DIV>
<DIV>distaste for SFTP, however, is at the very least intriguing.&nbsp; =
It is a=20
good</DIV>
<DIV>protocol, with some faults, yes, but they can be much more =
easily</DIV>
<DIV>addressed than with FTP.<BR></FONT><FONT size=3D2><BR>Mark P. =
Peterson -=20
President<BR><A 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></DIV></FONT>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><FONT face=3DArial></FONT><FONT face=3DArial></FONT><FONT=20
face=3DArial></FONT><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A title=3Dalun@wftpd.com=20
href=3D"mailto:alun@wftpd.com">Alun Jones</A> </DIV>
<DIV><B>Sent:</B> Thursday, December 23, 2010 9:55 PM</DIV>
<DIV><B>To:</B> <A title=3Dftpext@ietf.org=20
href=3D"mailto:ftpext@ietf.org">ftpext@ietf.org</A> </DIV>
<DIV><B>Subject:</B> [ftpext] Firewalls &amp; FTP over =
TLS.</DIV></DIV></DIV>
<DIV><FONT size=3D2></FONT><FONT size=3D2></FONT><FONT =
size=3D2></FONT><FONT=20
size=3D2></FONT><BR></DIV>
<DIV class=3DWordSection1>
<P class=3DMsoNormal>I frequently find I have a hard time selling my FTP =
server=20
into environments that are looking for a secure and standard file =
transfer=20
server.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Not because it=92s not a good and standard =
implementation of=20
FTP over TLS =96 I=92ve found it to work very well with numerous=20
clients.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>The failure is twofold =96 one, because the =
perceived=20
=93standard=94 for this is SFTP, and two, because of the headache of =
getting FTP=20
(and particularly FTP over TLS) to work through a =
firewall.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>The =93SFTP is a standard=94 complaint is galling, =
because of=20
course, SFTP is not a documented standard, and pretty much requires =
reverse=20
engineering in order to make it work. I=92ve been trying to push this =
message =96=20
that SFTP is flakey compared to FTP over TLS simply because SFTP =
essentially=20
relies on each server / client author making tweaks to have it work with =
those=20
they test with, rather than coding to a unified standard like FTP over =
TLS.=20
Maybe that=92s not a problem for those of you with SFTP capabilities in =
your=20
servers, but personally, I don=92t find that I want to implement an =
undocumented=20
standard.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>The =93Can=92t make FTP over TLS work through a NAT =
/ firewall=94=20
is irritating too, partly because it seems to be mostly true. In MODE S, =
TYPE I=20
transfers, the PORT command or PASV response have to be filtered and =
altered to=20
open a port and/or change the IP address to make the connection work. =
The=20
alternative is to open a wide swath of ports at the firewall, which =
security=20
teams shy away from, and in many companies, outright =
prohibit.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Again, SFTP wins out here, because it works over =
one port,=20
and one port only =96 although opening up port 22 (SSH) essentially says =
=93allow=20
anything=94, because SSH is used as a tunnel for multiple random =
protocols as well=20
as SSH and SFTP. It would be really nice if FTP could work over =
predictable port=20
numbers, especially if they were already opened by the firewall=92s =
usual=20
operation.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Well, I=92ve said it before, and got absolutely no =
response, so=20
I=92m asking again =96 why don=92t we use the default port as defined in =
RFC 959 and=20
before?<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>An FTP (or FTP over TLS) client connecting from =
port U to=20
port L and sending a RETR or STOR command (or equivalent) without a PORT =
or PASV=20
(or EPRT, EPSV, etc) command will cause the server to connect from =
server port=20
L-1 to client port U, and because of the nature of firewalls, they will=20
generally have opened a hole (server:any =3D&gt; client:U) =
already.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Great, that works for the first transfer, because =
in MODE S,=20
you close the TCP data connection to indicate the end of a transfer, and =
can=92t=20
open a new socket (server:L-1 =3D&gt; client:U) for another two to four=20
minutes.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Again, there=92s already an RFC 959 way of getting =
around this=20
=96 instead of using MODE S, use MODE B. Then, although there=92s a =
slight penalty=20
in terms of the chunk markers and restart markers, there=92s no issue =
with closing=20
and re-opening connections in rapid-fire transfers of small files or =
directory=20
listings, and it gets through a firewall and a NAT quite happily without =
having=20
to provide external IP address mappings, UPNP, or large firewall=20
holes.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>While I=92ve been able to test this with my own =
crappy test=20
client (WFTPD Client hasn=92t had enough work put into it to be really =
good), it=20
would be great to see this supported across multiple FTP clients and =
servers.=20
IIS FTP server already supports MODE B, but I don=92t really have any =
idea as to=20
how wide-spread support for MODE B is, or what features clients and =
servers=20
expect to see, or get confused by. I know that one failing in my own =
server is a=20
lack of support for restart markers (although it currently works if you =
specify=20
byte counts, as if it was in MODE S).<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Another thing that needs discussing for MODE B =
support is how=20
ABOR should work =96 that=92s not exactly clear, either.<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>So, who else supports MODE B for firewall / NAT=20
traversal?<o:p></o:p></P>
<P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
<P class=3DMsoNormal>Alun.<o:p></o:p></P>
<P class=3DMsoNormal>~~~~<o:p></o:p></P></DIV>
<P>
<HR>

<P></P>_______________________________________________<BR>ftpext mailing =

list<BR>ftpext@ietf.org<BR>https://www.ietf.org/mailman/listinfo/ftpext<B=
R></BODY></HTML>

------=_NextPart_000_0047_01CBA2F9.81C4DCF0--


