Understanding the Foundation of AES67

The Audio Engineering Society standard AES67, officially titled "AES standard for audio applications of networks – High-performance audio-over-IP interoperability," has become a cornerstone for modern networked audio. It defines a common set of protocols and requirements that allow audio devices from different manufacturers to discover each other, synchronize clocks, transport audio streams, and manage sessions over standard IP networks. AES67 is not an entire audio networking system in itself; rather, it is an interoperability mode that bridges the gaps between proprietary systems like Dante, RAVENNA, Livewire, and Q-LAN. For manufacturers, understanding AES67 compliance means ensuring their products can speak this universal language, while for users, it means the freedom to build systems using the best tools from any vendor without being locked into a single ecosystem.

The standard leverages well-established technologies: Real-time Transport Protocol (RTP) for audio data transport, Session Initiation Protocol (SIP) for connection management, and IEEE 1588 Precision Time Protocol (PTP) for clock synchronization. By specifying exactly how these protocols must be implemented for audio applications, AES67 creates a deterministic, low-latency, and interoperable environment. The standard supports audio formats from 16-bit to 24-bit at sample rates of 44.1 kHz and 48 kHz, with optional support for 96 kHz and beyond. It also defines a maximum latency of 125 microseconds per hop, which is critical for live sound and broadcast applications where timing is everything.

Core Technical Requirements of AES67 Compliance

Synchronization and Timing

Achieving sample-accurate synchronization is arguably the most challenging aspect of AES67 compliance. Devices must implement IEEE 1588-2008 (PTPv2) to establish a grandmaster clock that provides a common time reference across all network nodes. The standard mandates a specific profile (the AES67 Media Clock Profile) that defines timing constraints for audio applications. This includes clock accuracy requirements better than 1 microsecond relative to the grandmaster, and a stability that ensures no audible drift or jitter over hours of operation. Manufacturers must pay close attention to both hardware clocking (e.g., using dedicated PTP hardware timestamping) and software integration to meet these tolerances.

For users, this means that AES67-compliant devices will automatically synchronize with each other once placed on the same network, provided the network itself is properly configured. There is no need for a separate master clock or manual word clock distribution — the network carries timing alongside audio data, simplifying system design and reducing cabling. However, the network infrastructure (switches, routers, cabling) must support PTP transparent clocks or boundary clocks, and must be engineered with adequate bandwidth and low latency to maintain synchronization.

Audio Transport and Stream Management

AES67 specifies the use of RTP over UDP (User Datagram Protocol) for audio transport, with optional support for FEC (Forward Error Correction) to protect against packet loss. The standard defines a specific RTP payload format for uncompressed PCM audio, along with IP multicast address ranges and port numbers to facilitate device discovery and stream subscription. Stream management is handled via a simple SIP-based mechanism or through proprietary control layers like RAVENNA's API or Dante Controller's discovery protocol. For compliance, devices must implement a SIP User Agent (UA) that can respond to INVITE, OPTIONS, and BYE messages to set up and tear down streams.

From a user perspective, AES67 simplifies the workflow of routing audio across a network. A mixing console can receive inputs from a microphone preamp made by a different company and send outputs to a loudspeaker processor from a third manufacturer — all through a single Cat6 cable. The setup process typically involves a software controller that lists all AES67-compatible devices on the network; the user then makes point-to-point or multicast connections as needed. Because the standard uses industry-standard IP protocols, IT departments can manage these audio networks using familiar tools like SNMP and VLANs, integrating seamlessly into existing enterprise data networks.

Quality of Service and Network Requirements

To ensure reliable, low-latency audio, AES67 requires the network to provide a certain level of Quality of Service (QoS). Specifically, the standard recommends classifying AES67 traffic with a Differentiated Services Code Point (DSCP) value of 46 (Expedited Forwarding), which prioritizes audio packets over other data. Network switches must support IGMP snooping to manage multicast traffic efficiently, preventing flooding of audio streams to ports that do not need them. Additionally, the standard outlines specific network design guidelines, such as avoiding multiple audio streams on a single 100 Mbps link, and recommends using dedicated VLANs for audio traffic to isolate it from bursts of data traffic that could cause jitter or packet loss.

Manufacturers must provide clear documentation about their devices' network requirements, including recommended switch configurations and bandwidth usage. Some manufacturers offer network certification programs to verify that their switches meet the stringent demands of AES67. For users, selecting a network switch that is officially tested for AES67 compliance can eliminate many common troubleshooting headaches.

The Business Case: Why AES67 Matters for Manufacturers and Users

For Manufacturers: Market Expansion and Reduced Development Costs

By integrating AES67 compliance, manufacturers immediately open their products to a much larger market. A sound reinforcement loudspeaker that supports AES67 can be used not only with its own brand's digital mixer but also with any other AES67-compatible console. This reduces the friction of vendor lock-in and makes the product more attractive to system integrators and consultants who design multi-vendor systems. Moreover, the AES67 standard provides a clear specification that streamlines development. Instead of inventing a proprietary audio transport protocol, engineers can follow the defined RTP and PTP profiles, reducing time to market and testing efforts. Many manufacturers find that AES67 compliance also simplifies product certification for large-scale projects, such as those in broadcast or government installations, where open standards are often mandated.

For Users: Flexibility, Scalability, and Future-Proofing

Users gain the most obvious benefit: the ability to choose the best equipment for each task without compatibility concerns. A live sound company might use a Swiss-made digital console, British outboard gear, and American loudspeaker processors — all working seamlessly over an AES67 network. This flexibility reduces inventory costs (one type of network cable replaces dozens of analog snakes) and simplifies training because technicians only need to learn one networking standard. Additionally, AES67 forms the basis of more advanced standards like AES67-2018, which incorporates the SMPTE ST 2110 standard for broadcast video, and the NMOS (Networked Media Open Specifications) suite for discovery and registration. Products that are AES67 compliant today are ready to adopt these future extensions, providing a natural upgrade path.

Practical Implementation: Challenges and Considerations

Hardware and Software Integration

Manufacturers must carefully choose their network interface hardware. Many rely on standard Ethernet MAC/PHY chips combined with an FPGA or dedicated AoIP coprocessor to handle PTP timestamping and RTP packetization at line rate. Audio DSPs must be configured to run a PTP stack that synchronizes the device's local audio sample clock to the network grandmaster. This often involves a phased-locked loop (PLL) that adjusts the audio clock based on PTP timestamps. Software components include an implementation of the AES67 SIP stack, a multicast discovery mechanism (often based on SAP or mDNS), and a user-facing configuration interface. For smaller manufacturers, developing all of this in-house can be expensive; many instead license a certified AES67 software stack from companies like RAVENNA or Merging Technologies. The AES standards committee maintains a list of registered AES67 implementations and provides conformance test documents.

Network Infrastructure and System Design

For users and integrators, deploying an AES67 network requires more than just plugging in devices. The network must be designed to avoid packet loss, minimize jitter, and ensure sufficient bandwidth. A typical AES67 stream at 48 kHz, 24-bit, stereo, uses about 10 Mbps of bandwidth. With dozens or hundreds of streams, a 1 Gbps backbone is often necessary. Network switches must support IGMPv3 snooping for efficient multicast handling, and must be capable of setting up fast forwarding for PTP event messages. It is recommended to configure dedicated VLANs for audio traffic, with QoS policies that mark AES67 packets as high priority. Many manufacturers publish network design guides that include approved switch models and configuration instructions. A common pitfall is using consumer-grade switches that do not properly handle PTP or multicast; a managed switch with full Layer 3 capabilities is often required for larger installations.

Testing and Certification

The AES itself provides a conformance test specification (AES67-2018-TS) that details how to validate a device's compliance. Third-party test houses and consortiums (such as the AIMS Alliance for IP Media Solutions) offer certification programs that include both self-testing and laboratory verification. For manufacturers, obtaining official certification can be a differentiator in the market — it assures customers that the product has been rigorously tested for interoperability. For users, looking for a "Certified for AES67" logo or a mention of compliance in the product datasheet is essential. However, even if a product claims AES67 compliance, real-world interoperability can still have nuances; testing with multiple devices before purchase is advisable. The AIMS Alliance provides resources on interoperable IP media networking, including AES67 test events.

Common Use Cases Across Industries

AES67 compliance has found its way into a wide variety of professional audio environments. In broadcast, it underpins the transport of audio within SMPTE ST 2110 deployments, enabling seamless integration of microphones, mixing consoles, codecs, and loudness processors from different vendors all sharing the same IP infrastructure. Radio stations frequently use AES67 to connect studio equipment with transmitters, and to link remote broadcast sites over WAN connections with deterministic timing. In live sound, tour-grade digital mixing consoles and stage boxes now commonly include AES67 as an alternative to proprietary Dante, allowing rental companies to mix and match inventory. Installed sound systems in stadiums, convention centers, and houses of worship also benefit from AES67's scalability: a single network can handle hundreds of audio channels, control signals, and even video, reducing the complexity of separate cabling plants.

Education and corporate AV are also adopting AES67. Lecture halls with multiple rooms can route audio from any podium microphone to any loudspeaker zone over a centralized IP network, simplifying switching and reducing hardware costs. In these environments, system integrators appreciate the standard's ability to coexist with data IT networks, as long as QoS is properly implemented. Audinate, the developer of Dante, has incorporated AES67 mode into their Dante protocol, allowing Dante devices to interoperate with AES67-only devices — a significant step for expanding the ecosystem.

The Future: AES67 Beyond Audio

AES67 is not the final word in networked media. The standard has evolved to be part of a larger family: AES67-2018 incorporated the best practices from earlier deployments and aligned more closely with the SMPTE ST 2110 suite for video. The next logical step is the adoption of the NMOS (Networked Media Open Specifications) for discovery and registration, which AES67-based devices can use to simplify the process of finding and connecting streams across a network. Many manufacturers are already implementing NMOS alongside AES67 to enable plug-and-play operation. Additionally, the AES is working on an updated standard (AES67-2022) that addresses higher sample rates, redundant streaming (AES67 Seamless Redundancy), and enhanced security features such as encryption and authentication.

For manufacturers, staying ahead means not only complying with current AES67 requirements but also monitoring the evolution of the standard and participating in interoperability workshops. For users, purchasing AES67-compliant gear today is a safe investment — the standard will remain relevant for at least the next decade, and future firmware updates will likely extend compatibility to newer protocols. The industry is converging on IP-based media transport, and AES67 is the gateway.

Conclusion: A Universal Language for Audio

AES67 has transformed from a niche interoperability profile into the de facto language of professional audio-over-IP. For manufacturers, achieving AES67 compliance opens doors to broader markets, reduces development complexity, and aligns with the industry-wide push toward open standards. For users, it delivers the freedom to design flexible, multi-vendor systems that are easier to deploy, manage, and scale. While successful implementation requires careful attention to network design and device certification, the benefits far outweigh the challenges. As the audio industry continues its shift away from analog snakes and proprietary digital trunks, AES67 compliance stands as a key indicator of a product's readiness for the networked future. By embracing this standard, both manufacturers and users can build systems that are not only interoperable today but also prepared for the innovations of tomorrow.