What Makes for a Successful Protocol?

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 28
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.
Publication Date: 2008-07-01
Status Note: Informational
DOI: 10.17487/RFC5218
Link: https://doi.org/10.17487/RFC5218
Author(s): Dave Thaler
Dr. Bernard D. Aboba

Latest version of IETF RFC 5218

Document Versions — IETF RFC 5218

▶ IETF RFC 5218 (2008-07-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IEEE.STD802.11.2007 — 7 EXTERNAL
ISO.8879.1986 — ISO-8879 EXTERNAL
NTT DoCoMo, "i-mode", < http://www.nttdocomo.com/services/imode/index.html >. EXTERNAL
Open Mobile Alliance, "Wireless Application Protocol Architecture Specification", <http:// www.openmobilealliance.org/tech/affiliates/ LicenseAgreement.asp?DocName=/wap/ wap-210-waparch-20010712-a.pdf>. EXTERNAL
Carrel, D. and L. Grant, "The TACACS+ Protocol, Version 1.78", Work in Progress, January 1997. EXTERNAL
Novell, "IPX Router Specification", Novell Part Number 107-000029-001, 1992. EXTERNAL
IETF RFC 768 [Active*]
IETF RFC 791 [Active*]
IETF RFC 793 [Superseded*]
IETF RFC 826 [Active*]
IETF RFC 959 [Active*]
IETF RFC 1035 [Active, Amended*]
IETF RFC 1058 [Active*]
IETF RFC 1436 [Active*]
IETF RFC 1661 [Active*]
IETF RFC 1866 [Superseded*]
IETF RFC 1958 [Active*]
IETF RFC 2131 [Active*]
IETF RFC 2328 [Active*]
IETF RFC 2460 [Superseded*]
IETF RFC 2616 [Superseded*]
IETF RFC 2821 [Superseded*]
IETF RFC 2865 [Active*]
IETF RFC 3022 [Active*]
IETF RFC 3261 [Active*]
IETF RFC 3552 [Active*]
IETF RFC 3954 [Active*]
IETF RFC 4120 [Active*]
IETF RFC 4251 [Active*]
IETF RFC 4271 [Active*]
IETF RFC 4301 [Active, Amended*]
IETF RFC 4436 [Active*]
IETF RFC 4864 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5218.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 5218, What Makes for a Successful Protocol?. Available at https://doi.org/10.17487/RFC5218

Snippet:

IETF RFC 5218, What Makes for a Successful Protocol?. Available at https://doi.org/10.17487/RFC5218

HTML (ISO 690 compliant)

Preview:

IETF RFC 5218, What Makes for a Successful Protocol?. Available at https://doi.org/10.17487/RFC5218

Snippet:

<span class="citation"><cite>IETF RFC 5218</cite>, What Makes for a Successful Protocol?. Available at <a href="https://doi.org/10.17487/RFC5218" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5218</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5218, What Makes for a Successful Protocol?
doi: 10.17487/RFC5218
url: https://doi.org/10.17487/RFC5218

Snippet:

<li>
<cite id="bib-rfc5218">IETF RFC 5218</cite>, What Makes for a Successful Protocol?
<span class="doi">10.17487/RFC5218</span>
</li>

Referenced By

IETF RFC 6180 [Active*]
IETF RFC 6709 [Active*]
IETF RFC 7452 [Active*]