RFC 6982: Improving Awareness of Running Code: The Implementation Status Section
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7942.
Current version: RFC 7942 — Improving Awareness of Running Code: The Implementation Status Section
In plain English — editorial summary, not part of the RFC
This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. The process in this document is offered as an experiment. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. The authors of this document intend to collate experiences with this experiment and to report them to the community.
Document record
- Document ID
- RFC6982
- Published
- July 2013
- Authors
- Y. Sheffer; A. Farrel
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 7942
Referenced by
One later RFC formally updates or obsoletes part of this document.
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?