Updating RFCs
draft-wilde-updating-rfcs-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-03-27 (latest revision 2016-09-14) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-wilde-updating-rfcs-00.txt
https://www.ietf.org/archive/id/draft-wilde-updating-rfcs-00.txt
Abstract
As part of document metadata, RFCs can reference existing RFC that they update or obsolete. While obsoleting is well-understood (replace the obsoleted RFC in its entirety), updating has more nuances because the updated RFC remains valid. This document contains some clarifications about how to handle updating in a way that makes it easier for readers to understand how the original and the updating RFC relate. Note to Readers This draft should be discussed on the wgchairs mailing list [1]. Online access to all versions and files is available on github [2].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)