File transfers of entire trees require a lot more metadata and prior setup to link paths to files with unique ids so that clients can track them. This profile provides a more robust method of defining that metadata so that directory trees can be transfered.

• Provide a full featured set of information that is applicable to tree transfers.
• Meta-data that is to be provided:
  • number of files
  • size of entire tree
  • list of files and stream ids

The tree transfer profile is in the "http://jabber.org/protocol/si/profile/tree-transfer" namespace. The profile is fairly simple: it consists of the root element with child elements that specify a directory structure of files with stream ids that will be used for each file.

This profile requires support for the File Transfer profile described in SI File Transfer (XEP-0096) XEP-0096: SI File Transfer <https://xmpp.org/extensions/xep-0096.html>.. Once you have accepted this SI, a new SI using the File Transfer profile will be offered for each file in the tree. This profile provides a mapping of files with paths and reserved stream ids which will be used to auto-accept a File Transfer SI that uses that same stream id from the sender.

The root element is <tree> and has two attributes. The attributes are used only during the offer stage of stream initiation:

• size - The size, in bytes, of all of the files to be sent.
• numfiles - The number of files/File Transfer SIs that are in the tree.

The size and numfiles attributes MUST be present in the profile.

The only possible child element of the root is <directory/> since there are other specifications that handle single file transfers. The directory structure is sent in a hierarchical manner with nested <directory/> and/or <file/> tags. One or more <file/> elements will be sent, one for each file. One or more <directory/> elements will be sent, one for each directory.

The <directory/> element has one attribute:

• name - The name of the directory to create on the target system.

The attribute is REQUIRED on each <directory/> element.

The <file/> element has two attributes:

• sid - The stream id that MUST be sent for the File Transfer SI.
• name - The name of the file. The file should be saved to the same location in the target directory tree as the <directory/> hierarchy defines.

Both attributes are REQUIRED on each <file/> element. The total number of <file> elements MUST equal the numfiles attribute sent in the <tree/> element.

The stream-method that is accepted for a Tree Profile SI MUST be remembered and the subsequent File Transfer SIs MUST NOT provide a Feature Negotiation packet. The stream-method has already been chosen and should be used for all of the streams.

Implementations of this profile MUST support Stream Initiation (XEP-0095) XEP-0095: Stream Initiation <https://xmpp.org/extensions/xep-0095.html>. and XEP-0096.

Above is repeated for ft2, ft3, etc...

No interaction with the Internet Assigned Numbers Authority (IANA) 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/>. is required as a result of this document.

The profile described in this document will be registered with XMPP Registrar 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/>. as a valid Stream Initiation profile.