Термины Обновления и Obsoletes раньше определяется RFC 2223, но он устарел по RFC 7322, который не явно определить эти термины.
Я думаю, что более ранние RFC хорошо определили эти термины.
РЛК 2223, 1543 и 1111, которые вся существенная "Инструкция по RFC Авторам", определил эти термины как их "по отношению к другому РЛКУ". RFC 825 был очень ранней версией и не определял термины.
RFC 2223 — 6. Relation to other RFCs
6. Relation to other RFCs
Sometimes an RFC adds information on a topic discussed in a previous
RFC or completely replaces an earlier RFC. There are two terms used
for these cases respectively, Updates and Obsoletes. A document that
obsoletes an earlier document can stand on its own. A document that
merely updates an earlier document cannot stand on its own; it is
something that must be added to or inserted into the previously
existing document, and has limited usefulness independently. The
terms Supercedes and Replaces are no longer used.
Updates
To be used as a reference from a new item that cannot be used
alone (i.e., one that supplements a previous document), to refer
to the previous document. The newer publication is a part that
will supplement or be added on to the existing document; e.g., an
addendum, or separate, extra information that is to be added to
the original document.
Obsoletes
To be used to refer to an earlier document that is replaced by
this document. This document contains either revised information,
or else all of the same information plus some new information,
however extensive or brief that new information is; i.e., this
document can be used alone, without reference to the older
document.
For example:
On the Assigned Numbers RFCs the term Obsoletes should be used
since the new document actually incorporate new information
(however brief) into the text of existing information and is
more up-to-date than the older document, and hence, replaces it
and makes it Obsoletes.
In lists of RFCs or the RFC-Index (but not on the RFCs themselves)
the following may be used with early documents to point to later
documents.
Obsoleted-by
To be used to refer to the newer document(s) that replaces the
older document.
Updated-by
To be used to refer to the newer section(s) which are to be added
to the existing, still used, document.
RFC 7322 не определяет "по отношению к другим РЛК" РЛК как ранее РЛК сделал.
Я только найти несколько упоминаний терминов:
https://tools.ietf.org/html/rfc7322#section-4.1.4
4.1.4. Updates and Obsoletes
When an RFC obsoletes or updates a previously published RFC or RFCs,
this information is included in the document header. For example:
"Updates: nnnn" or "Updates: nnnn, ..., nnnn"
"Obsoletes: nnnn" or "Obsoletes: nnnn, ... , nnnn"
If the document updates or obsoletes more than one document, numbers
will be listed in ascending order.
https://tools.ietf.org/html/rfc7322#section-4.1.
4.1. First-Page Header
Headers will follow the format described in "RFC Streams, Headers,
and Boilerplates" [RFC5741] and its successors. In addition, the
following conventions will apply.
RFC 5741 упомянут, который устарел с RFC 7841. Он описывает формат заголовка для RFC «Отношение к другим RFC», но он просто ссылается на RFC 7322.
RFC 7841 — header format for an RFCs "Relation to other RFCs"
...
[<RFC relation>:<RFC number[s]>] Some relations between RFCs in the
series are explicitly noted in the RFC header. For example, a new
RFC may update one or more earlier RFCs. Currently two
relationships are defined: "Updates" and "Obsoletes" [RFC7322].
Variants like "Obsoleted by" are also used (e.g, in [RFC5143]).
Other types of relationships may be defined by the RFC Editor and
may appear in future RFCs.