IETF Logo Mail Archive

Re: [dtn] new charter items

Rick Taylor <rick@tropicalstormsoftware.com> Mon, 16 September 2019 19:44 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 1426C1200B1 for <dtn@ietfa.amsl.com>; Mon, 16 Sep 2019 12:44:20 -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 A7E5cbMsjatV for <dtn@ietfa.amsl.com>; Mon, 16 Sep 2019 12:44:13 -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 B0DDB1200C1 for <dtn@ietf.org>; Mon, 16 Sep 2019 12:44:12 -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 20:44:10 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Mehmet Adalier <madalier@antarateknik.com>, "marc.blanchet@viagenie.ca" <marc.blanchet@viagenie.ca>, "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: [dtn] new charter items
Thread-Index: AQHVY0rEejOVytDhWkWlDm/mbKLJHqcuWDMAgAA1SYCAADfzYA==
Date: Mon, 16 Sep 2019 19:44:09 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801F51322B8@tss-server1.home.tropicalstormsoftware.com>
References: <AE68CA71-F9BB-4D4F-A863-AFCFC8918AC9@viagenie.ca> <60ea553334b948f529ea5e51043a7e4e49624b74.camel@tropicalstormsoftware.com> <AFDEDB18-BF37-4A8D-9E51-6A8708ADA25F@antarateknik.com>
In-Reply-To: <AFDEDB18-BF37-4A8D-9E51-6A8708ADA25F@antarateknik.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2a02:1648:4000:120:a553:e844:7313:ea2c]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/yts5qfqxHkTxunwLjNOCpUDcYbA>
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 19:44:20 -0000

I've been reminded that RFC 4838 exists, and I've just mentioned wanting a DTN architecture...

As a clarification: My desire is for a (reasonably concise) document that defines the layering inside a single bundle processing agent, and the forwarding process followed inside that agent, rather than a reworking of the excellent RFC 4838.

My concern is that as WG members propose interesting endpoint addressing schemes, neighbour discovery mechanisms and routing protocols - a consistent logical view of the behaviour/logical layers within a node is required.

At an earlier IETF (I will have to look back through the minutes to find which one) I presented a short slide deck on a logical representation of a forwarding plane/routing table for a BPA, not because it was particularly novel, but simply to try to introduce a formal model that could capture implementer's and protocol designer's opinions of the inner workings of a BPA.

Regards,

Rick

> -----Original Message-----
> From: Mehmet Adalier [mailto:madalier@antarateknik.com]
> Sent: 16 September 2019 18:16
> To: Rick Taylor; marc.blanchet@viagenie.ca; dtn@ietf.org
> Subject: Re: [dtn] new charter items
> 
> Yes, and I'll volunteer to contribute to the best of my abilities
> 
> mehmet
> 
> On 9/16/19, 7:05 AM, "dtn on behalf of Rick Taylor" <dtn-bounces@ietf.org
> on behalf of rick@tropicalstormsoftware.com> wrote:
> 
>     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
>     _______________________________________________
>     dtn mailing list
>     dtn@ietf.org
>     https://www.ietf.org/mailman/listinfo/dtn
> 
>

v2.23.0 | Report a Bug | By Email