Definition of new tags for relations between RFCs
draft-kuehlewind-update-tag-03

Document Type Expired Internet-Draft (individual)
Authors Mirja K├╝hlewind  , Suresh Krishnan 
Last updated 2021-05-06 (latest revision 2020-11-02)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized 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-kuehlewind-update-tag-03.txt

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 (mirja.kuehlewind@ericsson.com)
Suresh Krishnan (suresh@kaloom.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)