Time-Triggered Ethernet

Shouldn’t we be building systems with not just Ethernet, but Time-Triggered Ethernet? Just saw this:

TTE provides two key benefits not available in regular Ethernet. They are:

  • A time-triggered paradigm where all devices are tightly synchronized and send messages at a predetermined schedule. This can reduce latency to hundreds of microseconds and jitter to near zero.
  • Fault tolerance—TTE replicates the whole network into multiple planes and forwards messages across all planes at once. The TTE network onboard Gateway has three planes.

Wow! Zero jitter! So the next time someone tries to sell you an audiophile box with an Ethernet port, ask them if they support SAE 6802a.


Difficult to gauge how much of commentary was tongue-in-cheek…

Time criticality would be for things like life-safety applications, it would be pointless in a buffered application such as streamed music. As we know, network jitter is not an issue for streamed audio.

This is a real niche standard. It’s almost like a solution looking for a problem. If latency or contention is going to be an issue in Earth-bound environments, we’d shift all that traffic into a separate network anyway. But when it costs thousands of dollars per kilo of payload to put items into space, then I sort of get it.


Audio Video Bridging.

It’s the IEEE spec for creating an “audio bus” at the link layer of Ethernet. For audio, this is the right way to go. It competes with a bunch of other proprietary standards (like Dante and ravenna) for audio steering and synchronization audio over ethernet.


But streaming isn’t a real-time digital audio stream like Dante and Ravenna they are more akin to spdif so what advantage does this really bring when it’s asynchronous data and doesn’t need the exact timing of those protocols.