Understanding AES67: The Audio‑over‑IP Interoperability Standard

The shift from analog to digital audio infrastructure has created an urgent need for devices from different manufacturers to communicate without proprietary lock‑in. AES67 – formally titled “AES standard for audio applications of networks – High‑performance streaming audio‑over‑IP interoperability” – was developed to fill exactly this gap. Published by the Audio Engineering Society (AES) in 2013, AES67 defines a common set of network transport, synchronization, and encoding parameters that allow audio streams to flow seamlessly between otherwise incompatible audio‑over‑IP (AoIP) platforms such as RAVENNA, Dante, LiveWires, and Q‑LAN.

Because AES67 is a layer‑2/3 interoperability bridge rather than a full control protocol, it does not replace existing ecosystems. Instead, it enables a device that speaks Dante to send audio to a device that speaks RAVENNA, provided both support AES67. This cross‑platform compatibility has made the standard a cornerstone of modern broadcast, live sound, installed sound, and recording environments. The standard operates at sampling rates up to 96 kHz and supports up to eight audio channels per stream, ensuring sufficient headroom for demanding professional applications.

The Ecosystem of Standards Bodies Behind AES67

AES67 did not emerge from a vacuum. Its development and ongoing adoption are driven by several standards organizations, each contributing technical expertise, industry credibility, and market momentum. Understanding the roles of these bodies clarifies why AES67 has become the de‑facto baseline for AoIP interoperability. Each organization brings a unique perspective, from the AES’s deep roots in audio engineering to the IEEE’s foundational networking protocols.

Audio Engineering Society (AES) – The Originator

As the parent organization, the AES conceived and published AES67. Its Standards Committee (AESSC) oversees working groups that maintain and extend the standard. The AES provides the official specification, publishes errata, and coordinates liaison with other standards bodies. The society’s publication process ensures rigorous peer review and open comment periods, giving all stakeholders – manufacturers, integrators, and users – a voice in the standard’s evolution. The AES also hosts regular conventions and conferences where engineers share implementation experiences, fostering a community of practice around the standard.

IEEE – Timing and Network Foundation

The Institute of Electrical and Electronics Engineers (IEEE) played an indirect but essential role. AES67 relies on the IEEE 1588 Precision Time Protocol (PTP) for sample‑accurate synchronization across the network. Without IEEE 1588’s sub‑microsecond clock distribution, the tight timing needed for AoIP would be impossible. The IEEE’s ongoing work on PTP profiles (notably IEEE 1588‑2019) directly influences how AES67 devices achieve clock alignment, especially in mixed‑vendor installations. The IEEE 802.1 Working Group also contributes through Time‑Sensitive Networking (TSN) standards, which are increasingly relevant for deterministic audio delivery.

SMPTE – Broadcast Integration

The Society of Motion Picture and Television Engineers (SMPTE) developed the SMPTE ST 2110 suite for professional media over managed IP networks. While ST 2110‑30 specifies audio transport, it uses AES67 as its audio payload format. This symbiotic relationship means that AES67 compliance is built into virtually all ST 2110‑compliant audio equipment, extending the standard’s reach from live sound into television production and video‑centric environments. SMPTE’s rigorous testing and certification processes ensure that broadcast equipment meets the stringent timing and synchronization requirements of live production.

European Broadcasting Union (EBU) – Adoption and Testing

The EBU has been active in promoting AES67 through its EBU Tech 3326 implementation guidelines. These documents help manufacturers build compliant devices and provide broadcasters with recipes for multi‑vendor AoIP deployment. The EBU also organizes plug‑fests and interoperability tests that accelerate market readiness. These events are crucial for identifying edge cases and ensuring that devices from different vendors work together reliably in real‑world conditions.

Avnu Alliance – Certification and Ecosystem

Avnu Alliance, an industry consortium, administers certification programs for Time‑Sensitive Networking (TSN) and, by extension, for AES67 devices. Avnu’s testing and logo program gives buyers confidence that a product will interoperate with other certified gear. This third‑party validation is critical for large‑scale installations where trust in cross‑vendor performance is paramount. The Avnu certification process includes rigorous testing of PTP synchronization, stream formatting, and redundancy mechanisms.

Alliance for IP Media Solutions (AIMS) – Industry Advocacy

AIMS is an industry group that promotes the adoption of open IP standards, including AES67, SMPTE ST 2110, and NMOS. AIMS works closely with standards bodies to align requirements and accelerate market adoption. Through its member companies – including major broadcast and pro‑audio manufacturers – AIMS drives awareness and provides a unified voice for the industry. The organization also hosts interoperability testing events and publishes deployment guides that help integrators navigate the transition to IP-based workflows.

How Standards Bodies Shape Development

Working Groups and Open Balloting

Each standards body employs a formal development process. In the AES, the SC‑02‑02‑L Working Group on Audio‑over‑IP meets regularly to review proposed amendments. Proposed changes are circulated for ballot among AES members, with comments resolved before final publication. This transparent, multi‑stakeholder approach prevents any single vendor from dominating the standard. The balloting process ensures that all technical perspectives are considered, from small integrators to multinational manufacturers.

Interoperability Testing and Plug‑Fests

No standard is useful until products actually work together. Bodies like the EBU and Avnu organize plug‑fests where engineers from competing manufacturers gather to test AES67 streams, synchronization, and redundancy. These events uncover edge‑case bugs and clarify ambiguous specification language. The feedback loop from plug‑fests directly results in specification revisions – for example, clarifications on PTP domain numbers and stream‑ID formatting in AES67‑2015 and AES67‑2018. Plug‑fests also build trust among manufacturers, reducing the time from specification to market-ready products.

Liaison Agreements

Standards bodies do not operate in silos. The AES maintains formal liaison agreements with SMPTE, IEEE, and the International Electrotechnical Commission (IEC). These agreements ensure that work on AES67 does not conflict with related standards (e.g., SMPTE ST 2110‑30 or IEC 61883 for FireWire audio). Liaison representatives attend cross‑organizational meetings, reducing duplication and fostering alignment on terminology and test methodologies. This coordination is essential for maintaining a cohesive ecosystem of related standards.

Technical Documentation and Guidelines

Beyond the core specification, standards bodies produce extensive technical documentation that guides implementation. The AES publishes Technical Documents (TDs) that cover specific topics like PTP configuration for AES67 networks. The EBU’s Tech 3326 offers detailed recommendations for network design, switch configuration, and stream management. These documents are invaluable for engineers who need to deploy AES67 in complex, multi‑vendor environments.

Promoting Adoption Through Certification and Education

Certification Programs

Avnu Alliance’s certification for AES67 is perhaps the most visible adoption driver. A product that passes Avnu’s rigorous test suite can bear the Avnu mark, which integrators recognize as a guarantee of interoperability. Similarly, the AES operates a Manufacturer Qualification Program that validates conformance to AES67. These programs reduce integration risk and are often required in public‑bid RFPs for broadcast and installed‑sound projects. Certification also encourages manufacturers to compete on features while maintaining a baseline of compatibility.

Conferences, Workshops, and Online Resources

Standards bodies use conferences (AES International Conventions, NAB Show, IBC) to host workshops on AES67 deployment. The AES also publishes Technical Documents (TDs) that explain implementation best practices. For example, AES67 Interoperability White Paper (available on the AES website) helps engineers design networks that avoid common pitfalls like improper IGMP snooping or incorrect PTP profile settings. Hands‑on training sessions at these events allow engineers to gain practical experience with AES67 configuration and troubleshooting.

Industry‑Wide Task Forces

In 2020, the Audio Engineering Society, the EBU, and the AIMS formed a joint task force to address AES67 adoption barriers in live sound. This collaboration produced simplified deployment guidelines that have been cited by major console manufacturers like Yamaha, DiGiCo, and Behringer when implementing AES67 in their firmware. Such cooperative efforts accelerate real‑world use far faster than any single organization could achieve alone. Task forces also address emerging use cases, such as wireless audio transport and cloud‑based production workflows.

Online Knowledge Bases and Community Forums

Standards bodies and industry consortia maintain online resources that provide ongoing support for implementers. The AES website includes a repository of technical papers, presentation slides from workshops, and discussion forums where engineers can ask questions and share solutions. These resources lower the barrier to entry for smaller manufacturers and integrators who may not have dedicated R&D teams for IP audio.

Impact on Industry Verticals

Broadcast

Broadcasters were early adopters because AES67 provided a migration path from SDI‑based audio to IP. A single AES67 stream can carry up to eight channels of 48 kHz, 24‑bit linear PCM audio. Major broadcast equipment vendors (e.g., Grass Valley, EVS, Lawo) now ship ST 2110‑30/AES67 cards as standard. This has reduced cabling costs, simplified signal routing, and enabled multivendor consoles to share audio cues seamlessly during large live events such as the Olympics and World Cup. Broadcasters have also benefited from reduced equipment room footprints and more flexible signal routing through IP networks.

Live Sound

In touring and fixed installation, AES67 has broken down walls between previously incompatible digital snakes, consoles, and processing racks. Systems like DiGiCo’s DMI‑AES67 cards and Yamaha’s NY64‑D interface allow a Yamaha console to receive audio from a DiGiCo stagebox, or vice versa. The live‑sound industry has embraced AES67 as a way to future‑proof systems: engineers can rent equipment from different suppliers with confidence that it will connect without proprietary adapters or converters. The standard also simplifies multitrack recording from front‑of‑house consoles to DAWs, enabling seamless live capture.

Installed Sound and Corporate AV

Corporate AV integrators use AES67 to combine audio from teleconferencing codecs (Cisco, Biamp), DSPs (QSC, Biamp, Shure), and amplifiers (Crown, Powersoft) without needing expensive proprietary media converters. The standard’s support for redundant streams – using two independent network paths for failover – is especially valued in mission‑critical boardrooms and houses of worship. AES67 also simplifies system integration in large‑scale installations like stadiums, conference centers, and transportation hubs where multiple systems must coexist.

Recording and Music Production

Recording studios and music production facilities are increasingly adopting AES67 to interconnect digital consoles, audio interfaces, and monitoring systems. The standard’s low latency and deterministic timing make it suitable for high‑resolution audio workflows. Studios benefit from the flexibility to route audio between rooms and equipment racks without investing in a single proprietary ecosystem. AES67 also enables remote collaboration by allowing audio streams to be transported over wide‑area networks with predictable performance.

ProAV and Live Events

In the pro‑AV space, AES67 supports integration of audio from diverse sources – wireless microphones, playback systems, and remote participation platforms – into unified production workflows. Live event production companies rely on AES67 to connect front‑of‑house consoles, monitor systems, and broadcast feeds. The standard’s support for multiple sample rates and channel configurations accommodates the varied requirements of concerts, theater productions, and corporate events.

Future Outlook: AES67 in the Next Decade

Higher Channel Counts and Sample Rates

Current AES67 supports stereo to 8‑channel streams; future revisions may extend to 16 or 32 channels per stream and support sample rates up to 96 kHz for high‑resolution audio workflows. Standards bodies are already studying the impact of higher bitrates on network jitter budgets. Moving to higher channel densities will enable more efficient use of network bandwidth and support large‑scale immersive audio formats like Dolby Atmos and Auro‑3D.

Integration with TSN and IEEE 802.1

Time‑Sensitive Networking (TSN) – the IEEE 802.1 standards – is often cited as the next evolutionary step. AES67 currently works on standard Ethernet networks using PTP and IGMP, but TSN can provide deterministic latency and bandwidth reservation. Bodies like the IEEE 802.1 Working Group and the AES are collaborating on a “TSN Profile for AoIP” that would define how AES67 devices can leverage TSN features for mission‑critical broadcast and pro‑audio applications. TSN integration would also improve performance in congested networks and simplify network design for large‑scale installations.

Convergence with ST 2110 and NMOS

The Advanced Media Workflow Association (AMWA) promotes the NMOS (Networked Media Open Specifications) suite. AES67 is already the audio backbone for NMOS‑controlled IP production systems. Future NMOS versions will likely require AES67 compliance, further entrenching the standard in professional media environments. Standards bodies will need to keep AES67 aligned with NMOS connection management (IS‑04/IS‑05) and stream registration. This convergence will simplify the deployment of unified IP production infrastructures that handle video, audio, and data simultaneously.

Security and Authentication

As AoIP moves into broadcast and public venues, security becomes critical. The AES is developing an addendum to AES67 that defines mandatory encryption (AES‑128 or AES‑256) and authentication for stream sources. This work is being coordinated with the IEEE 1722 Secure Audio Video Transport efforts. Once published, adoption will be pushed by government broadcasters and large‑scale installations that require encrypted audio links. Security addenda will also address key management, certificate handling, and secure bootstrapping of devices.

Cloud and Remote Production Workflows

The rise of cloud‑based production and remote collaboration is creating new requirements for AES67. Standards bodies are exploring how to transport AES67 streams over wide‑area networks with controlled latency and jitter. This includes developing guidelines for using AES67 with public cloud infrastructure and virtualized network functions. Remote production workflows will benefit from AES67’s ability to scale across geographic boundaries while maintaining the synchronization and timing integrity required for professional audio.

Wireless Audio Transport

Wireless audio systems – including IEMs, wireless microphones, and intercom systems – are beginning to adopt AES67 for integration with wired AoIP networks. Standards bodies are working on profiles that address the unique latency and reliability constraints of wireless transport. This will enable seamless hybrid wired/wireless audio systems where wireless devices participate in the same network as their wired counterparts, using the same synchronization and addressing schemes.

The Essential Role of Standards Bodies Going Forward

The original vision of AES67 – a single interoperability mode shared by all AoIP technologies – has been largely realized. However, maintaining that interoperability requires constant vigilance. Standards bodies will continue to:

  • Maintain and revise the standard through open balloting and errata publication.
  • Operate certification programs that hold manufacturers accountable for consistent implementation.
  • Organise plug‑fests to catch regressions before they become costly field issues.
  • Educate the industry via tutorials, white papers, and conference tracks.
  • Coordinate with other standards bodies (SMPTE, IEEE, AMWA) to avoid fragmentation.
  • Develop implementation guidelines that help engineers navigate complex deployment scenarios.
  • Support emerging markets such as cloud production, wireless audio, and immersive formats.

Without these neutral, non‑commercial organisations, the audio industry would likely revert to a handful of proprietary silos. AES67’s success proves that when manufacturers compete on features but cooperate on connectivity, everyone – from the touring engineer to the corporate IT manager – benefits. The standards ecosystem also provides a forum for resolving disputes and building consensus, preventing the fragmentation that could occur if individual vendors pursued incompatible extensions.

Conclusion

The development and adoption of AES67 are not just technical achievements; they are triumphs of collaboration facilitated by established standards bodies. The AES, IEEE, SMPTE, EBU, Avnu Alliance, and AIMS have each played a distinct role – from writing the specification to certifying products to educating the market. As audio systems continue their migration to all‑IP infrastructures, these organisations will remain indispensable guides, ensuring that AES67 evolves to meet new challenges while preserving the backward compatibility that the industry relies on. The ongoing work of these bodies guarantees that audio‑over‑IP will remain an open, interoperable foundation for decades to come.

For engineers and systems integrators, understanding the standards ecosystem behind AES67 is more than academic: it informs purchasing decisions, deployment strategies, and contingency planning. By staying engaged with the standards bodies and their activities, professionals can anticipate changes in the landscape, contribute to the evolution of the standard, and ensure that their installations remain compatible with the broader industry. The collaboration that produced AES67 serves as a model for other areas of professional audio and media, demonstrating what can be achieved when organizations work together toward a common technical goal.