8.1 Choreography

This clause defines the method by which a company can provide Batches of messages defined in the Recording Data and Rights Notification Standard and the Recording Data and Rights Revenue Reporting Standard to a business partner via (i) an SFTP server that is hosted by the message sender, (ii) an SFTP server that is hosted by the message recipient or (iii) an SFTP server that is hosted by a third party. This specification does not therefore define on whose hardware the files are being stored. This is for the Message Sender and the Message Recipient to agree.

The choreography of the FTP Batch Profile is as depicted below:

The trigger to indicate that a Batch is complete is a ManifestMessage as defined in Clause 9 of this standard. 

The RdrAcknowledgementMessage is defined in this standard and is also defined in Clause 9.

The structure and file naming conventions for the Batched FTP Profile are defined in Clause 8.3 and Clause 8.4 of this standard.

This standard does not define when the Message Sender shall start or finish to upload subsequent messages. Equally, this standard does not define when the Message Recipient shall start or finish its download.

The recipient of the RdrAcknowledgementMessage may remove an RdrAcknowledgementMessage from the FTP server after an appropriate and mutually agreed period of time. The default period is one month.