Re: [dtn] on obsoleting RFC5050

"Templin (US), Fred L" <> Fri, 18 October 2019 18:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BEA88120942; Fri, 18 Oct 2019 11:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 Z8Mk7DMvWVYm; Fri, 18 Oct 2019 11:19:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5174212094B; Fri, 18 Oct 2019 11:19:56 -0700 (PDT)
Received: from localhost (localhost []) by (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id x9IIJr0a026860; Fri, 18 Oct 2019 14:19:53 -0400
Received: from ( []) by (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id x9IIJig5025703 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Fri, 18 Oct 2019 14:19:44 -0400
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1779.2; Fri, 18 Oct 2019 11:19:43 -0700
Received: from ([fe80::e065:4e77:ac47:d9a8]) by ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.1779.002; Fri, 18 Oct 2019 11:19:43 -0700
From: "Templin (US), Fred L" <>
To: Marc Blanchet <>, DTN WG <>
CC: "" <>
Thread-Topic: [dtn] on obsoleting RFC5050
Thread-Index: AQHVhNRJiSr/MQ4UNUW+KV/XitbZK6dgt1Ng
Date: Fri, 18 Oct 2019 18:19:43 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-snts-smtp: C9A62FBF829EC6D11F4BFF9EC50753EDE848DD0E5EF5CEF20F7735E3B3447CC62000:8
Content-Type: multipart/alternative; boundary="_000_5e4a6a1de45d42dc8f06f9678bd7c035boeingcom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [dtn] on obsoleting RFC5050
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, 18 Oct 2019 18:20:00 -0000

I appreciate the well thought-out rationale and support this proposal.


From: dtn [] On Behalf Of Marc Blanchet
Sent: Thursday, October 17, 2019 3:19 AM
To: DTN WG <>
Subject: [dtn] on obsoleting RFC5050

based on the various inputs and good discussion on the mailing list regarding obsoleting RFC5050, the chairs have come to this conclusion. Please state your support or not so we can move forward.

Regards, Marc&Rick, co-chairs.

  *   RFC5050 is an experimental RFC, done in IRTF, while draft-ietf-dtn-bpbis will be a Standard track RFC, done in IETF. Different streams, different processes.
  *   we believe there is a strong consensus to not continue working on RFC5050 and not try to be backward compatible. RFC5050 implementations and deployments can continue as they see fit.
  *   IANA registries have their own life, whatever the stream or type of RFC they were created from. They can always be updated by a new RFC.
  *   Given that, we suggest the following steps:

     *   1) draft-ietf-dtn-bpbis would not obsolete RFC5050. Instead we would notify IRTF that draft-ietf-dtn-bpbis is an update of RFC5050. IRTF will decide what they want to do, if anything, with RFC5050.
     *   2) in the new version of the charter that we are currently working on, we will state clearly that there is no intent to work on or make compatible work with RFC5050 and related RFCs
     *   3) DTN working group document authors will review the IANA registries as they are today and request whatever modifications needed, which may include changing the policies, the content, the rules, …