Proprietary protocol

In telecommunications, a proprietary protocol is a communications protocol owned by a single organization or individual.^[1]

Intellectual property rights and enforcement

Ownership by a single organization gives the owner the ability to place restrictions on the use of the protocol and to change the protocol unilaterally. Specifications for proprietary protocols may or may not be published, and implementations are not freely distributed. Proprietors may enforce restrictions through control of the intellectual property rights, for example through enforcement of patent rights, and by keeping the protocol specification a trade secret. Some proprietary protocols strictly limit the right to create an implementation; others are widely implemented by entities that do not control the intellectual property but subject to restrictions the owner of the intellectual property may seek to impose.

Examples

The Skype protocol is a proprietary protocol.^[2]

The Venturi Transport Protocol (VTP) is a patented proprietary protocol^[3] that is designed to replace TCP transparently in order to overcome perceived inefficiencies related to wireless data transport.

Microsoft Exchange Server protocols are proprietary^[4] open access protocols. The rights to develop and release protocols are held by Microsoft, but all technical details are free for access and implementation.^[5]

Microsoft developed a proprietary extension to the Kerberos network authentication protocol for the Windows 2000 operating system. The extensions made the protocol incompatible with implementations supporting the original standards, and this has raised concerns that this, along with the licensing restrictions, effectively denies products unable to conform to the standard access to a Windows 2000 Server using Kerberos.^[6]

Effects of incompatibility

The use of proprietary instant messaging protocols meant that instant messaging networks were incompatible and people were unable to reach friends on other networks.^[7]

Reverse engineering

Reverse engineering is the process of retrieving a protocol’s details from a software implementation of the specification. Methods of reverse-engineering a protocol include packet sniffing and binary decompilation and disassembly.

There are legal precedents when the reverse-engineering is aimed at interoperability of protocols.^[8][9][10] In the United States, the Digital Millennium Copyright Act grants a safe harbor to reverse engineer software for the purposes of interoperability with other software.^[11][12]

References

1. Proprietary protocol Definition — PC Magazine Encyclopedia
2. "Help for Skype". Retrieved 17 March 2015.^{[dead link]} - "Help for Skype"
3. US 5883893 
4. Microsoft Exchange Server Protocols January 23, 2009, at the Wayback Machine
5. Microsoft Open Protocols February 17, 2009, at the Wayback Machine
6. . 2000-05-11. Archived from the original on 2014-02-22.
7. Instant messaging: This conversation is terminated — BBC News
8. Sega v. Accolade, 1992
9. Sony v. Connectix, 2000
10. Samuelson, Pamela; Scotchmer, Suzanne (May 2002). (PDF). Yale Law Journal. 111 (7): 1575–1663. doi:10.2307/797533. JSTOR 797533. Archived from the original (PDF) on 2011-07-16. Retrieved 17 March 2015.
11. 17 U.S.C. Sec. 1201(f).
12. WIPO Copyright and Performances and Phonograms Treaties Implementation Act