Milan Myths

There are several persistent myths surrounding Milan and its foundational technology, AVB.

This page addresses the most common misconceptions with clear, technically accurate explanations.

Info

This page assumes you are familiar with the relationship between AVB and Milan.
For a brief overview, see the AVB Academy introduction.


Myth: AVB is obsolete

It is often claimed that AVB is obsolete because the IEEE AVB working group ended its activities in 2012 when it was renamed into the Time-Sensitive Networking (TSN) task group to focus on industrial applications.

Reality: AVB is very much alive

The AVB specification (IEEE 802.1BA) is still active and maintained, with the latest revision published in 2021. The renaming of the working group reflected an expanded scope, not a move away from AVB.

Audio and video transport remains a core use case within TSN, alongside newer applications in industrial automation, automotive, and aerospace. Rather than being obsolete, AVB has evolved within a broader standards family.


Myth: Milan is old and outdated

Milan is sometimes perceived as a legacy solution that has been surpassed by newer, IP-based audio networking technologies.

See also: Myth: AVB is obsolete

Reality: Milan is one of the most modern audio networking standards

Milan is actually among the most recent professional audio networking standards. It was first released in 2018, while widely adopted IP-based standards like AES67 date back to 2013.

More importantly, Milan provides deterministic performance and precise timing that IP-based solutions still struggle to match. It combines Ethernet transport with guaranteed delivery and bounded latency, making it ideal for high-performance audio applications.


Myth: Milan is a proprietary protocol

Some claim that Milan is a proprietary protocol, used exclusively by a selected group of ProAV manufacturers.

Reality: Milan is based on open IEEE standards

Milan is not proprietary. It is a clearly defined, open specification built on top of IEEE open standards including 802.1AS (time synchronization), 802.1Q (traffic shaping), 1722 (streaming transport), and 1722.1 (device discovery and control).

The Milan protocol is developed collaboratively by leading ProAV manufacturers within the Avnu Alliance, ensuring it meets the real-world needs of professional users. Any manufacturer can implement Milan without licensing fees, and the full specification is freely available from the Avnu Alliance website.


Myth: Milan always has a latency of 2ms

Because AVB networks originally introduced a default latency of 2ms, some believe this is the fixed or only possible latency for Milan systems.

Reality: Milan guarantees a bounded latency, not a fixed one

Milan networks are fully time-aware. All devices, including switches, share a synchronized understanding of time. This enables them to calculate and guarantee precise end-to-end transmission delays.

As a result, Milan can guarantee a minimum playout delay tailored to the specific path and stream characteristics. Typical configurations range from 0.25 ms to 2 ms.


Myth: There are no AVB-capable switches available

It is often claimed that Milan is impractical because it requires specialized switches, and that mainstream networking vendors no longer support AVB.

Reality: Certified AVB switches are widely available

AVB-capable switches incorporate advanced Ethernet technologies such as the Precision Time Protocol v2 (PTPv2) for precise clock synchronization. Additionally, they implement traffic shaping and bandwidth reservation mechanisms defined by the AVB standards to guarantee bounded latency and deterministic delivery of audio streams.

A wide range of manufacturers produce certified AVB switches, including Netgear, Cisco, Extreme Networks, Luminex, Niveo Professional, Adamson Systems Engineering, d&b audiotechnik, L-Acoustics, and others. The ecosystem continues to expand with new certified products regularly introduced.

You can find the current list of certified switches in the Avnu Alliance Certified Product Registry.


Myth: Milan always blocks 75% of the available network bandwidth

There is a persistent belief that Milan blocks 75% of the network bandwidth, severely limiting other traffic.

Reality: Your network is not 75% full by default

Milan uses bandwidth reservation to guarantee time-sensitive delivery, but only reserves the bandwidth required by each stream. For example, an 8-channel stream at 48 kHz reserves around 17 Mbps.

All remaining bandwidth is available for other traffic. The 75% figure refers to the maximum possible reservation (based on AVB Class A and B limits), not the typical usage. You can find a detailed calculation in the description of the Stream Reservation Protocol.


Myth: Milan control is still under development

It is sometimes assumed that Milan control is incomplete or still evolving, making it unsuitable for real-world deployment.

Reality: Milan control is fully defined and standardized

Milan uses the ATDECC protocol (defined in IEEE 1722.1) for control, which defines standardized mechanisms for device discovery, enumeration, and stream management.

These control capabilities have been part of the Milan specification since its initial release and are already implemented in certified Milan devices.