This is a reiteration on Stateless Inline Media Sharing (XEP-0385)  with some significant changes:
To share a file, a user sends a message stanza including
<file-sharing/> to the inteded recipient contact or group.
<file-sharing/> element includes a
<file/> metadata element as described in File metadata element (XEP-xxxx)  as well as a
<sources/> element provides one or multiple sources that the receiving client may use to obtain the file.
It is RECOMMENDED that the file metadata specifies name, media-type, size and one or multiple hash elements as described in Use of Cryptographic Hash Functions in XMPP (XEP-0300) . The hash elements provide end-to-end file integrity and allow efficient caching and flexible retrieval methods.
The message MAY include a suitable fallback body.
The fallback body MUST NOT include any information that is not also represented in
<sources/> element includes an
<url-data/> element that can be represented as a single URL, adding a Out-of-Band Data (XEP-0066)  x-oob reference is RECOMMENDED for compatibility.
If the message has an empty body, it is RECOMMENDED to add a message processing hint, see Message Processing Hints (XEP-0334) , to indicate the message to be stored in message stores like Message Archive Management (XEP-0313) .
On receive of a message including a
<file-sharing/> element, the receiving entity SHOULD lookup in a local storage, whether the file with any of the proivded hashes has already been retrieved and is available.
In that case no transfer needs to be initated and the cached file can be used instead.
If the file is not available locally, the file can be obtained by one of the sources listed in the
If further sources have been attached (as described in Attaching a source), the receiving entity may also try to obtain the file from any of those.
When the source is an
<url-data/> element as described in URL Address Information (XEP-0103) , the receiving entity MAY obtain the file by downloading it from the specified URL.
If the URL uses HTTP or HTTPS and additional HTTP request information as specified in HTTP Scheme for URL Data (XEP-0104)  is provided, the receiving entity SHOULD use such information when obtaining the file.
When sending and receiving files using
<url-data/>, it is RECOMMENDED to prefer secure protocols (e.g. HTTPS, FTPS).
Please read security considerations when implementing support for insecure URLs.
When the source is a
<jingle-pub/> element as described in Publishing Available Jingle Sessions (XEP-0358) , the receiving entity MAY obtain the file using the protocol described in Publishing Available Jingle Sessions (XEP-0358) .
<hash/> is provided, the receiving entity MAY obtain the file by requesting it as described in Jingle File Transfer (XEP-0234) .
If sources of any other type are provided, clients MAY attempt to obtain the files from such sources. The details of obtaining such file are out of scope of this document.
<media-type/> of the shared file is such that it can be displayed inline, the receiving entity MAY display the file inline.
<media-type/> is provided or the
<media-type/> indicates that the file can not be displayed inline, i.e. when the media type is
application/octet-stream, the receiving entity SHOULD NOT display the file inline and instead offer to download it or save it on the users file system.
TODO: The following section relies on Message Attaching (XEP-0367) , however other methods to attach information to another message like the recently proposed Message Fastening (XEP-0422)  might be suitable here as well. This is to be clarified before advancing to Draft.
After a user shared a file using one entity and another entity in the conversation obtained it or found it in its local storage, that entity MAY announce that the file is now available with an additional source. This increases availability of the file in case the sender goes offline before all the intended recipients were able to fetch the file. It also allows for peer-to-peer file distribution in group chats.
The entity MUST NOT announce itself as an additional source before verifying that all hashes provided match the hash of the file. If no hashes are provided, the entity SHOULD NOT announce itself as an additional source.
Depending on the lifetime of the newly attached source, it may be useful to add a message processing hint, see Message Processing Hints (XEP-0334) , to indicate the message to be stored in message stores like Message Archive Management (XEP-0313) .
<hash/> using any supported algorithm is provided, the receiving client SHOULD verify that the
<hash/> of the announced file matches the obained file before presenting it to the user.
<hash/> is provided or the
<hash/> elements provided use unsupported algorithms, receiving clients MUST ignore any attached sources from other senders and only obtain the file from the sources announced by the original sender.
<hash/> is provided or the
<hash/> elements provided use unsupported algorithms, receiving clients MUST ignore any sources that use unsecure protocols (e.g. HTTP without TLS).
For most methods of transferring a file proposed through the
<sources/> element, obtaining files requires revealing private information like IP addresses to the sending user or third-parties.
Sources that do not require revealing private information to untrusted entities SHOULD be preferred by receiving entitites.
Receiving entities SHOULD ask users for confirmation before obtaining a file, if doing so would require revealing private information to untrusted entities.
If the protocol that is used when obtaining the file is not secure (e.g. HTTP without TLS), this SHOULD be considered as if the protocol reveals private information.
The security considerations of File metadata element (XEP-xxxx)  apply.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) .
Thanks to the authors of Stateless Inline Media Sharing (XEP-0385)  which heavily inspired this XEP.
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF).
Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <email@example.com> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <firstname.lastname@example.org>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
2. XEP-xxxx: File metadata element <https://xmpp.org/extensions/inbox/file-metadata.html>.
18. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.
19. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/