Re: [dtn] Marking RFC5050 as Obsolete?

Rick Taylor <> Fri, 20 September 2019 18:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5867C1208AA for <>; Fri, 20 Sep 2019 11:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZZ60V8QASWzk for <>; Fri, 20 Sep 2019 11:20:32 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E229A120852 for <>; Fri, 20 Sep 2019 11:20:31 -0700 (PDT)
Received: from ([fe80::48e4:acbb:6065:8168]) by ([fe80::48e4:acbb:6065:8168%16]) with mapi id 14.03.0468.000; Fri, 20 Sep 2019 19:20:29 +0100
From: Rick Taylor <>
To: Stan Ratliff <>, "Burleigh, Scott C (US 312B)" <>
CC: "" <>
Thread-Topic: [dtn] Marking RFC5050 as Obsolete?
Thread-Index: AQHVb8zJ4yFYQLaGbkWRYSuGB6CGYqc0zaoA///7SoCAABd88A==
Date: Fri, 20 Sep 2019 18:20:28 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-originating-ip: [2a02:1648:4000:120:a553:e844:7313:ea2c]
Content-Type: multipart/alternative; boundary="_000_38A5475DE83986499AEACD2CFAFC3F9801F51403F1tssserver1hom_"
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: Fri, 20 Sep 2019 18:20:35 -0000

+1 to marking RFC 5050 as obsolete

With my personal hat on…


From: Stan Ratliff []
Sent: 20 September 2019 18:56
To: Burleigh, Scott C (US 312B)
Cc: Rick Taylor;
Subject: Re: [dtn] Marking RFC5050 as Obsolete?

+1 on marking RFC5050 as obsolete.


On Fri, Sep 20, 2019 at 1:50 PM Burleigh, Scott C (US 312B) <<>> wrote:
If I understand correctly, it sounds like choosing not to mark RFC5050 as obsolete would commit the DTN WG to considering alignment with BPv6 (as well as BPv7) in all future deliberations on DTN standards.  I think that would be a troublesome constraint on the working group.

We've done a lot of good work with BPv6, and existing BPv6 deployments certainly must continue to be supported.  However, I don't think that support necessarily has to extend to the development and standardization of new BPv6 features.

The BPv7 specification, together with bundle-in-bundle encapsulation, is an improved protocol design that encompasses a superset of BPv6 capabilities.  Migrating existing BPv6 deployments to BPv7 will not be effortless, but I think the investment will be amply repaid over the next few years.

So on this reasoning I support the IETF 105 consensus to obsolete RFC5050.


-----Original Message-----
From: dtn <<>> On Behalf Of Rick Taylor
Sent: Friday, September 20, 2019 9:02 AM
Subject: [EXTERNAL] [dtn] Marking RFC5050 as Obsolete?

Hi All,

During the DTN interim meeting on Sept 18th, there was a discussion on making RFC5050 obsolete or not. This discussion also happened at IETF
105 and the consensus of the room was to obsolete RFC5050.
This consensus was not formally called and verified on the mailing list afterwards (although minutes were posted), and so this is the purpose of this email.

It is well understood by the working group that there is existing investment in RFC5050 implementations and installations, and that these will not immediately move to BPv7 if RFC5050 is marked as obsolete.
However, by doing so a strong signal is sent to industry that the working group considers BPv7 as the replacement for RFC5050, and that future effort by the working group will be directed solely at BPv7.
This would not automatically preclude any work around supporting moving from RFC5050 to BPv7 or interoperability, but such work would not be considered a priority.

If the working group does not choose to mark RFC5050 as obsolete, we are committing to maintain it as a suitable target for convergence layers, addressing schemes, routing and management protocols, etc. that may be standardised in the future by the working group.

Hence, here is the request: Should draft-ietf-dtn-bpbis obsolete RFC5050?


Rick & Marc
dtn mailing list<>

dtn mailing list<>