Re: [dtn] new charter items

Rick Taylor <rick@tropicalstormsoftware.com> Mon, 16 September 2019 14:05 UTC

Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 259D8120090 for <dtn@ietfa.amsl.com>; Mon, 16 Sep 2019 07:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gak_cljJGhOQ for <dtn@ietfa.amsl.com>; Mon, 16 Sep 2019 07:05:28 -0700 (PDT)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D281A120045 for <dtn@ietf.org>; Mon, 16 Sep 2019 07:05:27 -0700 (PDT)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::48e4:acbb:6065:8168]) by tss-server1.home.tropicalstormsoftware.com ([fe80::48e4:acbb:6065:8168%16]) with mapi id 14.03.0468.000; Mon, 16 Sep 2019 15:05:24 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "marc.blanchet@viagenie.ca" <marc.blanchet@viagenie.ca>, "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: [dtn] new charter items
Thread-Index: AQHVY0rEejOVytDhWkWlDm/mbKLJHqcuWDMA
Date: Mon, 16 Sep 2019 14:05:24 +0000
Message-ID: <60ea553334b948f529ea5e51043a7e4e49624b74.camel@tropicalstormsoftware.com>
References: <AE68CA71-F9BB-4D4F-A863-AFCFC8918AC9@viagenie.ca>
In-Reply-To: <AE68CA71-F9BB-4D4F-A863-AFCFC8918AC9@viagenie.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Evolution 3.32.1-2
x-originating-ip: [10.10.1.5]
Content-Type: text/plain; charset="utf-8"
Content-ID: <82E6F0CC7FCD6B45AB262BDCF18A9619@home.tropicalstormsoftware.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/fAA4hF8AGi9fWWf-Sc02g5Iy61s>
Subject: Re: [dtn] new charter items
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 14:05:31 -0000

One of the things I consider missing from the current DTN working group
documents is a logical architecture.

With the BPbis and TCP-CL documents we introduce some of the concepts
around 'convergence layers' and 'bundle processing', and although those
of us who are long-time followers of the WG understand what these
concepts mean, and how they are the building blocks of a layered
architecture, I believe there is merit in formally describing the
architecture we currently elude to.

As we start to look deeper into endpoint addressing, concepts such as
'convergence-layer-local endpoint addresses' start to become important,
particularly with routing, and without an architecture to reference,
formally defining such things is just harder.

So, is there any interest in defining a logical model?

Regards,

Rick