RFC 5657: Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard
In plain English — editorial summary, not part of the RFC
Advancing a protocol to Draft Standard requires documentation of the interoperation and implementation of the protocol. Historic reports have varied widely in form and level of content and there is little guidance available to new report preparers. This document updates the existing processes and provides more detail on what is appropriate in an interoperability and implementation report. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5657
- Published
- September 2009
- Authors
- L. Dusseault; R. Sparks
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- BCP9
- Updates:
- RFC 2026
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7127Characterization of Proposed StandardsCurrent
January 2014
- RFC 8134Management Incident Lightweight Exchange (MILE) Implementation ReportCurrent
May 2017
- RFC 2209Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing RulesCurrent
September 1997
- RFC 3661Media Gateway Control Protocol (MGCP) Return Code UsageCurrent
December 2003
- RFC 1357A Format for E-mailing Bibliographic RecordsObsoleted
July 1992
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?