Link is great. In my particular case I'm using ethernet to transmit audio and video via the TSN (Time Sensitive Networking) protocol. My cameras and video system use SMTPE for clock sync. I've set up this way to eliminate latency/jitter - and to do realtime processing of video and audio (and FX/Signal Chains etc). Link has a 3ms guarantee (if memory serves), whereas Dante and TSN offer about .67ms.
Ableton - by example, cannot generate MTC, so you have Link, or an external converter. I'd rather have it clocked to ALK, and with a more reliable clock. I realize some may chuff the differences in latency, however, in a multi-computer/video scenario like mine - it's crucial. Running a few softwares, MacOS, iOS, and Windows, with USB MIDI hardware... etc., all adds up to buffer issues that are hard to pinpoint, especially when time code and software buffering or latency compensation is ill-handled.
Lastly, the "type" of music I produce is kinda in the drumcode zone, and I'm doing much with intermodulations, ambi/vibrasonics - also which make crucial that timing is spot on. Apologies for the long answer, I fairly obsessed with time code for a long time (and I designed matrixed video systems back in the day). I wrote this as well a few months back - about how to sync with MTC from Ableton to iOS using some external tools: https://aud-ios.com/2017/01/29/midi-timecode-generation-sync-from-ableton-to-ios/. Cheers ~