[Standards] Proposed XMPP Extension: Requirements for IM File Transfer

Peter Saint-Andre stpeter at stpeter.im
Tue Sep 18 17:41:43 UTC 2007

Olivier Goffart wrote:
> Le vendredi 14 septembre 2007, Michal 'vorner' Vaner a écrit :
>> Hello
>> On Thu, Sep 13, 2007 at 04:39:46PM -0500, XMPP Extensions Editor wrote:
>>> Title: Requirements for IM File Transfer
>> With some more thinking, I have few more things that would be good to
>> have:
>> • Serverless mode (for link-local)
>> • Doesn't go to server and back on LAN (If you have bad internet
>> connection, but more computers on LAN).
>> • Way of checking the transfer went well - some kind of hash
>> • Sending whole directories (may be another XEP, that just advertises a
>> directory with all its files and will auto-accept an transfer for each
>> of the files)
>> • I often hear people asking, if encrypted transfers are possible
>> Furthermore, it should be easy to implement. (if we just all had IPv6,
>> simple TCP connection would work)
> I agree that P2P filetransfer should be used whenever possible.
> A server should be used only if:
>  - restrictive firewall or NAT make P2P impossible or difficult.
>  - sending to a contact which is offline
>  - willing to send the same file to multiple senders


- company policy forbids p2p file transfer
- server-side virus checking desired/required before download

It is difficult to define consistent requirements for consumer-oriented
services on the open internet and employee-oriented services within
enterprise deployments.


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070918/ae4ae7fc/attachment.bin>

More information about the Standards mailing list