DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type:content-transfer-encoding;
 b=jz6m2Uh5ik1Z5/9cyxHXwmiJVpLsd0Eg+G28BW7eyHSwDs2XAMXr+CSesSONxc3Ivq
 0bQvLjZXNhYzfLvC0IczIYDV3Zgk+tXAizMtuOwhq0u28sV1z3dRWcqMBE5EKQGAasVl
 lgjuJ10bTPQnLo7kNa43gGGGgADCcTqJxFsnU=
MIME-Version: 1.0
In-Reply-To: <AANLkTinriyMy5_thOnx29HbGQ41NcYW+MS27YGDAjoNT@mail.gmail.com>
References: <1791E3B42BE242848B7FFFC7015B4563@rhinooffice.net>
 <AANLkTimeH+O4E4XEq6cdw0UaM4UpDTo6EKB9kB1x4PJh@mail.gmail.com>
 <139EAF2195BC496AA3F25288D56BFB43@rhinooffice.net>
 <AANLkTinriyMy5_thOnx29HbGQ41NcYW+MS27YGDAjoNT@mail.gmail.com>
Date: Wed, 1 Dec 2010 01:00:31 -0500
Message-ID: <AANLkTik9qaJgeVR4j-K+G-VErCCjHA2SL0cnkYq_+_J4@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: "Mark P. Peterson" <mpp@rhinosoft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] Posted Update to
 "draft-peterson-streamlined-ftp-command-extensions"
Precedence: list

looking good! the new version is up...

On Sat, Sep 18, 2010 at 5:13 AM, Anthony Bryan <anthonybryan@gmail.com> wro=
te:
>
> some other issues...
>
> 3) would it be useful to have more exact error responses like we are
> talking about for HASH? (same for section 4.2).
>
> 3.2. DSIZ Error Responses
>
> =A0 In the event that the pathname is not a directory, the server MUST
> =A0 return a permanent 550 error reply. =A0Where the command cannot be
> =A0 parsed, a 500 or 501 reply SHOULD be sent. =A0The client MUST NOT
> =A0 assume that the presence of a 550 reply indicates that it cannot
> =A0 access the directory or its contents. =A0The server may generate this
> =A0 error for other reasons, for example the overhead required for the
> =A0 operation is too great.
>
> 4c)
>
> =A0 The AVBL
> =A0 command offers an interface for retrieving this value in a way that
> =A0 can be machine parsed.
>
> also mentioned a few lines later in 4.1 (I think once in 4.1 is enough):
>
> =A0 The 213 reply is formatted in such a way that the returned size can
> =A0 be machine parsed.


in 3.1 you have:

   The 213 reply is formatted in such a way that the returned size value
   can be machine parsed; the response MUST simply be the command
   response followed by an integer value with no delimiters.

don't you want the same in 4.1?

> 5) see 4a. don't you want some consistency here?
>
> =A0 A successful response includes a numeric value that may be the number
> =A0 of octets available as dictated by the physical limitations of the
> =A0 underlying storage mechanism. =A0It may also be a limit imposed upon
> =A0 <pathname> or even the user that issued the command. =A0The exact
> =A0 method for calculating this numeric value is up to the specific
> =A0 server-FTP process implementation.

this seems pretty vague and open ended. is it intended to be?

maybe something like this?

   A successful response includes a numeric value that is the number
   of octets available as dictated by the physical limitations of the
   underlying storage mechanism, or a limit imposed upon
   <pathname> or a limit imposed upon the user that issued the command.

> 6) THMB FEAT response is in 5.3
>
> =A0 Image formats supported by the server are listed in the THMB FEAT
> Response [6.3].

still unfixed.

11) as mentioned before, CSID is not in the IANA considerations section.

> On Fri, Sep 17, 2010 at 5:44 PM, Mark P. Peterson <mpp@rhinosoft.com> wro=
te:
>> Hi Anthony,
>>
>> Thank you. =A0I have updated the draft. =A0It can be found here:
>>
>> https://datatracker.ietf.org/doc/draft-peterson-streamlined-ftp-command-=
extensions/
>>
>> Mark P. Peterson - President
>> http://www.RhinoSoft.com
>> Voice: +1(262) 560-9627
>> FAX: +1(262) 560-9628
>>
>>
>> --------------------------------------------------
>> From: "Anthony Bryan" <anthonybryan@gmail.com>
>> Sent: Friday, September 17, 2010 3:08 AM
>> To: "Mark P. Peterson" <mpp@rhinosoft.com>
>> Cc: <ftpext@ietf.org>
>> Subject: Re: [ftpext] Posted Update to "draft-peterson-streamlined-ftp-c=
ommand-extensions"
>>
>> On Wed, Sep 15, 2010 at 8:20 AM, Mark P. Peterson <mpp@rhinosoft.com> wr=
ote:
>>> Hello,
>>>
>>> I have updated "draft-peterson-streamlined-ftp-command-extensions"
>>> as per some suggestions from Anthony Bryan. =A0The IANA Considerations
>>> section has been updated to reflect his suggestions. =A0The draft is
>>> located here:
>>>
>>> https://datatracker.ietf.org/doc/draft-peterson-streamlined-ftp-command=
-extensions/
>>
>> thanks, Mark! I plan to give this a more thorough review soon, & I
>> hope others will too.
>>
>>
>> looking at the last example in each of these, should the last line of ea=
ch be
>>
>> =A0 =A0 =A0 =A0 S> 550 file.fid: Is a file.
>>
>> ?
>>
>> 3.4. DSIZ Examples
>>
>> =A0 Assuming the presence of directory "A" on the server and that the
>> =A0 client has the necessary permissions to access and list it, a typica=
l
>> =A0 DSIZ client-server exchange would be:
>>
>> =A0 =A0 =A0 =A0 C> DSIZ A
>> =A0 =A0 =A0 =A0 S> 213 123456
>>
>> =A0 Where 123456 is the number of octets on the server's file system
>> =A0 occupied by the directory "A" and its contents.
>>
>> =A0 Assuming directory "A" cannot be listed due to client permissions,
>> =A0 the client-server exchange would be:
>>
>> =A0 =A0 =A0 =A0 C> DSIZ A
>> =A0 =A0 =A0 =A0 S> 550 A: Permission denied.
>>
>> =A0 Assuming the client provides the argument "file.fid" where "file.fid=
"
>> =A0 is an existing file, the client-server exchange would be:
>>
>> =A0 =A0 =A0 =A0 C> DSIZ file.fid
>> =A0 =A0 =A0 =A0 S> 550 A: Is a file.
>>
>>
>> 4.4. AVBL Examples
>>
>> =A0 Assuming the client provides the argument "file.fid" where "file.fid=
"
>> =A0 is an existing file, the client-server exchange would be:
>>
>> =A0 =A0 =A0 =A0 C> AVBL file.fid
>> =A0 =A0 =A0 =A0 S> 550 A: Is a file.
>>
>>
>> --
>> (( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
>> =A0)) Easier, More Reliable, Self Healing Downloads
>>
>>
>
>
>
> --
> (( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
> =A0 )) Easier, More Reliable, Self Healing Downloads
>



--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads