Re: [dtn] Marking RFC5050 as Obsolete?

[Rick Taylor <[e-mail]>]

All,

For those looking for clarity between obsolete and historic: I refer to
https://www.ietf.org/about/groups/iesg/statements/designating-rfcs-
historic-2014-07-20/

From my reading (and I am not an IESG process expert, but as chair I
can go find one to quiz if required), two bullets give critical
information, and I quote:

<quote>
* A document is obsolete when there is a newer version that replaces
it. RFC 821 is obsoleted by RFC 2821, which is, in turn, obsoleted by
RFC 5321. The technology that RFC 821 describes — SMTP — is still
current technology, but the documentation of it in RFC 821 is
obsolete. 

* A document is labelled Historic when what it describes is no longer
considered current: no longer recommended for use.
</quote>

The proposal is to mark RFC5050 as obsolete, pointing readers to BPbis,
as the consensus in the room at IETF-105 was that Bundle Protocol is
still "current technology", but the bundle formats and protocol rules
have evolved, as compared to "no longer recommended for use".

Additionally, Lloyd Wood asks a valid question about whether an IETF
working group can mark an IRTF document obsolete/historic.  I am hoping
someone with more experience in this area can add clarification.

Regards,

Rick