Re: [dtn] Marking RFC5050 as Obsolete?

Rick Taylor <> Mon, 23 September 2019 08:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9058512018B for <>; Mon, 23 Sep 2019 01:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id w8ieTLABUCQO for <>; Mon, 23 Sep 2019 01:54:56 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A5599120106 for <>; Mon, 23 Sep 2019 01:54:55 -0700 (PDT)
Received: from ([fe80::48e4:acbb:6065:8168]) by ([fe80::48e4:acbb:6065:8168%16]) with mapi id 14.03.0468.000; Mon, 23 Sep 2019 09:54:53 +0100
From: Rick Taylor <>
To: "" <>
Thread-Topic: [dtn] Marking RFC5050 as Obsolete?
Thread-Index: AQHVb8zJ4yFYQLaGbkWRYSuGB6CGYqc43faAgAAKygA=
Date: Mon, 23 Sep 2019 08:54:52 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
user-agent: Evolution 3.32.1-2
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [dtn] Marking RFC5050 as Obsolete?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Sep 2019 08:54:58 -0000


For those looking for clarity between obsolete and historic: I refer to

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:

* 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

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

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.