[dcc2] Files Draft

[Dave Johnson]

Dan Smith writes:
> Hi everyone,
> 
> I have updated our working copy of the header draft to reflect the move 
> from XML to http header style name:value pairs.  There are only three 
> required fields (id,name,size).  All other fields are optional and up to 
> the client to implement.
> 
> http://www.dcc2.org/specifications/draft-smith-irc-dcc2-files-00.htm
> 
> Does the ABNF look ok?  Any comments on the format?  Is there any other 
> information that is needed in the headers?  What character encoding should 
> this header use (currently 7 bit ascii)?


General:

Much better without XML, thanks.



Section 3.2.2 (Method)

Would it be better if the sending client closes the TCP connection on
receipt of the 'COMPLETE' command instead of the receiving client
closing right after sending the 'COMPLETE' command?  This may be
better in preventing lingering TCP connections and provide a better
tear-down.

Single transfers should be as already written (reciever closes).


Section 3.2.3 (Multi Send Syntax):

Did my 'partial transfers' comment from Apr-25th fall through the
cracks or did no one like it?  It was about adding an END or FINISH
option in addition to the already present START or OFFSET option in
the SEND command.



Section 4 (Security Considerations):

Shouldn't paragraphs 1 and 3 be in the negotiation draft, they dont
seem file specific.

-- 
Dave