Definition of new tags for relations between RFCs
draft-kuehlewind-update-tag-04
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mirja Kühlewind , Suresh Krishnan | ||
| Last updated | 2022-01-13 (Latest revision 2021-07-12) | ||
| Replaced by | draft-kuehlewind-rswg-updates-tag | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-kuehlewind-rswg-updates-tag | |
| 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
An RFC can include a tag called "Updates" which can be used to link a new RFC to an existing RFC. On publication of such an RFC, the existing RFC will include an additional metadata tag called "Updated by" which provides a link to the new RFC. However, this tag pair is not well-defined and therefore it is currently used for multiple different purposes, which leads to confusion about the actual meaning of this tag and inconsistency in its use. This document recommends the discontinuation of the use of the updates/updated by tag pair, and instead proposes three new tag pairs that have well-defined meanings and use cases.
Authors
Mirja Kühlewind
Suresh Krishnan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)