Requesting Comments: Enabling Readers to Annotate RFCs
draft-sheffer-ietf-rfc-annotations-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yaron Sheffer | ||
| Last updated | 2017-06-30 (Latest revision 2016-12-27) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
RFCs were initially intended as, literally, requests for comments. Since then, they have turned into standards documents, with a peculiar process to report errors and a highly onerous process to actually have the RFC modified/republished. Non-IETF participants are typically unaware of any way to provide feedback to published RFCs, other than direct email to the listed authors. This is very different from the way many web specifications are developed today and arguably leads to the value of published RFCs diminishing over time. This document proposes an experiment to remedy this situation through the deployment of web annotations.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)