Network Protocols

Both the FTP and AIM protocols detailed previously provide examples of network protocols. The Internet is all about network protocols and there is no shortage of them. We have protocols for data transfer, routing, e-mail, streaming media, instant messaging, and more types of communication than you could ever hope for. As a wise man once said, “The best thing about standards is that there are so many of them to choose from.” The standards that are network protocols are no exception.

How are network protocols developed? The answer to the question depends largely on whether the protocol is open or proprietary. Proprietary protocols can be developed by a closed group within a single company to be used by specific products maintained and controlled by that same company. In a way, developers of proprietary protocols have an inherent advantage as they only need to reach a consensus among a small group of developers when agreeing on a standard. On the other hand, Internet protocols are inherently open and therefore require a consensus among many diverse groups. In general, Internet protocols are developed and maintained by the Internet Engineering Task Force (IETF).^[8] The IETF has a lengthy process for publishing and obtaining feedback on proposed Internet standards, which begins with the publication of Requests for Comment (RFCs), which are public documents used to detail protocols and solicit peer review. Following appropriate debate and revision, RFCs can then be adopted by the IETF as Internet standards.

^[8] http://www.ietf.org/