What connection-role check do you use before adding another SRT destination?

[srt-cloud]

Disclosure: I work with SRT distribution workflows at SRT Cloud. I’m sharing an operational checklist, not proposing a protocol change.

Before adding another taker to a live contribution feed, I would record four things for that destination: (1) source and receiving owner, (2) caller/listener/rendezvous role, (3) host, port, and passphrase owner, and (4) a named receipt confirmation.

The SRT protocol uses a listener/caller model and separately defines caller-listener and rendezvous handshakes. That makes the role decision worth recording before a live event, rather than diagnosing it during one. Source: https://haivision.github.io/srt-rfc/draft-sharabayko-srt.html

My other rule is to test every taker independently. A successful first destination does not prove the endpoint details or operating path for the next one. I would also make one controlled endpoint-change test before handover, while retaining a receipt confirmation and owner for each destination.

What would you add to this handover checklist for a multi-destination contribution event?