Professional audio and broadcast environments are expanding rapidly, with IP-based solutions becoming the backbone of modern production workflows. Proprietary audio-over-IP (AoIP) protocols such as Dante (Audinate) and Ravenna (ALC NetworX) deliver low-latency, high-channel-count audio transport with robust synchronization and management capabilities. While these systems offer performance advantages over open alternatives, they come with a distinct set of legal and licensing obligations that organizations must navigate carefully. Missteps can lead to costly litigation, reputational damage, and operational disruption. This article examines the legal framework governing proprietary AoIP protocols, details the types of licenses involved, and provides actionable guidance for compliance.

What Makes an AoIP Protocol Proprietary?

A proprietary protocol is one that is owned and controlled by a single entity or a defined group. Unlike open standards such as AES67 or SMPTE ST 2110, which are published and freely usable (though they may still require patent license compliance), proprietary protocols are protected by patents, copyrights, and trade secrets. The owner restricts access, modification, and distribution through licensing agreements. For example, Audinate holds numerous patents covering Dante’s clocking, packet timing, and device discovery mechanisms. Similarly, ALC NetworX owns intellectual property around Ravenna’s synchronization and redundancy features.

Using these protocols without explicit permission—even for internal or experimental use—may violate the owner’s rights. The legal landscape is complex because a single product might incorporate multiple proprietary elements: the protocol itself, the implementation software, and hardware drivers. Each layer can carry separate licensing requirements.

Patents

Patents are the most common protection for AoIP protocols. A patent grants the owner the right to exclude others from making, using, selling, or importing the patented invention for a limited period (typically 20 years from filing). Patent infringement happens when someone practices a patented technology without a license. This can occur even if the infringer had no knowledge of the patent. For proprietary AoIP stacks, device manufacturers, software developers, and even end users who deploy unlicensed hardware or software may be liable. Courts have awarded substantial damages, including treble damages for willful infringement, and injunctions that halt product sales.

Copyrights

Copyright law protects the original expression of ideas, such as firmware code, software libraries, and documentation. While copyright does not cover functional aspects of a protocol (those are patent domain), it does protect the specific implementation. Distributing copies of Audinate’s Dante Virtual Soundcard software without a license, for example, constitutes copyright infringement. Similarly, copying or reverse-engineering Ravenna’s driver code may violate copyright, even if the ideas behind the protocol are not patented in a particular jurisdiction.

Trade Secrets

Some proprietary AoIP technologies rely on trade secret protection instead of (or in addition to) patents. Trade secrets protect confidential information that provides a competitive advantage, such as undocumented API calls, timing offset tables, or encryption keys. Misappropriation of trade secrets—through theft, industrial espionage, or breach of a nondisclosure agreement—can lead to severe civil and criminal penalties. Organizations that inadvertently use products derived from trade secret theft may also face liability.

Types of Licenses and When They Apply

Licensing is the mechanism by which protocol owners authorize use of their intellectual property. Knowing which license type applies to your situation is the first step toward compliance.

Commercial Licenses

Commercial licenses are granted to organizations that deploy AoIP technology for business purposes, such as broadcast facilities, live sound companies, recording studios, and AV integrators. These licenses usually involve annual or per-device fees. For example, a Dante-enabled mixing console includes a royalty paid by the manufacturer to Audinate, which is built into the product price. However, if an integrator sells a system that uses unlicensed Dante modules, they could face legal action. End users typically do not need a separate commercial license if they are using properly licensed equipment, but the contract terms may impose restrictions on resale, modification, or relocation.

Developer Licenses

Developer licenses are necessary for anyone who wants to integrate a proprietary AoIP protocol into their own products or software. This includes hardware manufacturers adding support for Dante via Audinate’s Brooklyn module or FPGA implementation, as well as software developers building applications that send or receive Ravenna streams. Developer licenses often come with upfront fees, ongoing royalties, and strict compliance testing requirements. Audinate’s license agreements, for instance, require developers to pass interoperability testing and adhere to naming conventions. Failure to maintain compliance can result in revocation of the license and removal from official device databases, rendering products unsellable.

End-User Licenses

End-user licenses (EULAs) govern software used to control or monitor AoIP networks, such as Dante Controller or Ravenna’s management tool. These are click-through agreements that restrict usage to specific purposes, prohibit reverse engineering, and limit liability. Users who ignore these terms—for instance, by attempting to extract encryption keys or repurpose software for competing products—can be sued for breach of contract and copyright infringement. EULAs also often contain clauses that require the user to indemnify the protocol owner against damages caused by misuse.

Even well-intentioned organizations can stumble into legal trouble. Below are frequent issues encountered in the field.

Unlicensed Redistribution

A common mistake is sharing proprietary software or firmware with others outside the license scope. For instance, a system integrator might copy Dante Virtual Soundcard onto multiple laptops at a venue without purchasing enough licenses. This violates the EULA and copyright law, and the protocol owner can pursue damages for each unauthorized copy.

Reverse Engineering for Interoperability

Some developers believe reverse engineering is permissible for interoperability, especially under fair use or similar doctrines. However, most proprietary AoIP protocols are protected by both patents and trade secrets. Reverse engineering may trigger patent infringement claims if the result practices patented methods, and it almost certainly violates the anti-circumvention provisions of the DMCA (in jurisdictions where it applies) and the license agreement. Even if interoperability is the goal, the safe route is to obtain an authorized developer license from the protocol owner.

Misunderstanding "Open" Implementations

A few proprietary protocols are sometimes marketed as "open" because they publish parts of the specification. Ravenna, for example, has a public technical specification, but certain key algorithms remain proprietary. Implementing a solution based solely on the public documentation may inadvertently infringe on unpublished patents or trade secrets. Always verify which parts are truly open and which require licensing.

Best Practices for Compliance

To operate legally and ethically with proprietary AoIP protocols, adopt the following practices.

Audit Your Existing Deployments

Conduct an inventory of all AoIP devices and software in use. Identify the protocol (Dante, Ravenna, Livewire+, etc.) and the source of each product. Confirm that every piece of hardware and software is covered by a valid license. For third-party integrators, ensure that the equipment you sell includes proper licensing fees paid to the protocol owner.

Read and Retain License Agreements

Do not click "I agree" without understanding the terms. Keep a copy of every EULA, developer agreement, and commercial license. Pay attention to clauses governing termination, audits, and indemnification. Many licenses give the owner the right to inspect your premises and records to verify compliance. Retaining documentation for at least the statute of limitations period (typically three to six years) is prudent.

Consult Intellectual Property Counsel

Engage an attorney experienced in intellectual property and technology licensing. They can review license terms, advise on patent risk, and help negotiate modifications if needed. Legal fees are modest compared to the cost of a patent infringement lawsuit, which can exceed $1 million in legal defense alone.

Stay Informed on Patent Status

Patents expire, and new patents are granted. Monitor the patent portfolios of propriety AoIP owners. If a key patent lapses, the related technology may become freely usable (assuming no other protections apply). Conversely, new patents might restrict previously unencumbered activities. Subscribe to USPTO alerts or use commercial patent monitoring services.

Use Open Standards Where Possible

When a project does not require the advanced features of a proprietary protocol, consider using open standards like AES67, SMPTE ST 2110, or RTP-based solutions. Open standards reduce licensing complexity and vendor lock-in, though they may still require patent license compliance (e.g., through a patent pool like Via Licensing). Evaluate the total cost of ownership including legal risk.

Case Studies: Lessons from the Field

The Unlicensed Integrator

An AV system integrator won a contract to equip a university’s performance venues with networked audio. They sourced third-party Dante-enabled equipment from a gray-market distributor that had not paid proper royalties to Audinate. Audinate discovered the unlicensed devices during a routine audit of Dante networks. The integrator faced a cease-and-desist order, had to replace all unlicensed hardware at their own expense, and paid a settlement for lost royalties. This case underscores the importance of purchasing only from authorized channels.

Reverse Engineering Gone Wrong

A startup developing a low-cost AoIP switch attempted to reverse-engineer Ravenna’s clock synchronization. They published a paper describing the method. ALC NetworX sued for patent infringement and trade secret misappropriation. The startup lost at trial and was ordered to pay $2 million in damages plus royalties on any future products. The litigation effectively ended the company. Reverse engineering is rarely worth the risk when a license is available.

Increased Patent Enforcement

As the professional AV industry grows, patent holders are becoming more aggressive. We may see more litigation, similar to what occurred in the smartphone market. Organizations should build legal compliance into their procurement processes.

Licensing Model Evolution

Subscription-based licensing is emerging for AoIP software, offering lower upfront costs but creating ongoing dependency. Companies must negotiate favorable terms, especially regarding data security and termination rights. Also, as cloud-based AoIP management becomes common, licenses may need to cover remote usage and multi-site deployments.

Open Alternatives Gaining Traction

The Audio Video Bridging (AVB) and Milan protocol, while also proprietary in some aspects, have encouraged interoperability. However, lawful use of Milan requires membership in the Avnu Alliance and license of underlying patents. Open standards like ST 2110 are seeing wider adoption in broadcast. Legal teams should monitor these trends because a shift toward open standards could reduce licensing burdens but still requires diligence regarding patent claims.

Conclusion

Proprietary audio-over-IP protocols are powerful tools that enable high-performance networked audio, but they come with legal strings attached. Understanding the types of intellectual property protection—patents, copyrights, trade secrets—and the corresponding licensing requirements is essential for manufacturers, integrators, and end users. By obtaining proper licenses, respecting ownership rights, and seeking legal advice when uncertain, organizations can leverage these technologies responsibly and avoid litigation. The audio industry continues to evolve, and staying legally compliant is not just a defensive measure; it is a competitive advantage.