What Makes for a Successful Protocol?
RFC 5218, “What Makes for a Successful Protocol?”, is an Informational document published in July 2008 by D. Thaler, B. Aboba. The canonical text is published by the RFC Editor.
Abstract
The Internet community has specified a large number of protocols to date, and these protocols have achieved varying degrees of success. Based on case studies, this document attempts to ascertain factors that contribute to or hinder a protocol's success. It is hoped that these observations can serve as guidance for future protocol work. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5218 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5217 Memorandum for Multi-Domain Public Key Infrastructure Interoperability
- RFC 5219 A More Loss-Tolerant RTP Payload Format for MP3 Audio
- RFC 5216 The EAP-TLS Authentication Protocol
- RFC 5220 Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules
- RFC 5215 RTP Payload Format for Vorbis Encoded Audio
- RFC 5221 Requirements for Address Selection Mechanisms
- RFC 5214 Intra-Site Automatic Tunnel Addressing Protocol
- RFC 5222 LoST: A Location-to-Service Translation Protocol