Re: [dtn] Draft DTNWG Charter Text
sburleig.sb@gmail.com Mon, 26 July 2021 15:18 UTC
Return-Path: <sburleig.sb@gmail.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 A9CBA3A192F for <dtn@ietfa.amsl.com>; Mon, 26 Jul 2021 08:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XZRU19Tys5Bu for <dtn@ietfa.amsl.com>; Mon, 26 Jul 2021 08:18:14 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2D6A3A18D9 for <dtn@ietf.org>; Mon, 26 Jul 2021 08:18:05 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id i10so8901677pla.3 for <dtn@ietf.org>; Mon, 26 Jul 2021 08:18:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=mGQmEt1AcuD2TSYDYkm0CoUln548qOUtcNYir3DetxE=; b=cXZON0awBE4AglO1eOEQF6OEya1sooV0scmUOiwZtZiASt6GvESMUcfDOudMC7kF+Z 021yn+A2IlHGHd/5WKo25NcJ6HFAnmE3M250WyDjmVxVZMTbusYz5Hjg4wTu1ei6K3Jx 9G0PogVl+PFh+tc4pMhf55gB6NFRK4OXdOIal4BhUi/vy+DASmA+LCnyfb9j3Z5JE4/C 8JqCuJffLNRzYCrEXJh9gvTiqflk3YfJi1XSRMCLPlZPOhyw2p3pQa7harlHJReeNRhK 0yVT8Hy6SP4SEP7qETjckD6Zd7JLlPdtweQwxJ6C3ATH6FHSDsKhaZiGviPKnPTp629n hGJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=mGQmEt1AcuD2TSYDYkm0CoUln548qOUtcNYir3DetxE=; b=fGpIQKrO4IQRxV20Bsac5kxH5UenVLQHhAqe8P499fmstd+NglSUjqh6uHA+WV6WdM nk4ktDB0q+7lZPjO++7UbYJhCWv8e18VCxJ2xV8VwIpXg4rPAp6FY3kxq+ZQBAVX+rCt 1YhApxRXB4fRtUt0JRQU8wDYufd2QVZ1V3fk9qXRssg8VgRctCuO5J4L1Bv6m/2q8VAQ 8DlRg+zWd7DCSEJyWyoDEzsG3WfupmXrj0XZmkCaEay8xxnb3+KAK5fTVmVwhJokjNN+ xHcaPbcr+H/u7e4p5czkbX9bT5BBvbYIzz5sp6iAkQxu8k95lxebAqFKwhDkANByRtWf oaBQ==
X-Gm-Message-State: AOAM531p3wcDSPuhkaSQcfsErSANgfP16LDLTgCrvm9qsGoppD8hTE7x gcoHz2oKEFzCA+zGBvajW3+mbjg4ukgCLA==
X-Google-Smtp-Source: ABdhPJx1LqE/FPKfIKzV+USbbCqAcxBDcalVRiwP0blk6i6ZSjYmICzQ6Ns7OMvKXKuBNT5au1VdYw==
X-Received: by 2002:a05:6a00:24d1:b029:33d:d5ad:b903 with SMTP id d17-20020a056a0024d1b029033dd5adb903mr18983208pfv.0.1627312684489; Mon, 26 Jul 2021 08:18:04 -0700 (PDT)
Received: from Nick ([2600:8801:be24:eb00:76:2e68:4e05:1029]) by smtp.gmail.com with ESMTPSA id k11sm8850pgc.30.2021.07.26.08.18.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Jul 2021 08:18:04 -0700 (PDT)
From: sburleig.sb@gmail.com
To: 'Rick Taylor' <rick@tropicalstormsoftware.com>, Felix.Flentge@esa.int, "'Birrane, Edward J.'" <Edward.Birrane@jhuapl.edu>
Cc: dtn@ietf.org
References: <ed08508a9b0b4e64b089d620b251bc6d@aplex01.dom1.jhuapl.edu> <OF50334D55.392F4E94-ONC125871E.00365897-C125871E.00369E03@esa.int> <38A5475DE83986499AEACD2CFAFC3F9801F5AD6B22@tss-server1.home.tropicalstormsoftware.com>
In-Reply-To: <38A5475DE83986499AEACD2CFAFC3F9801F5AD6B22@tss-server1.home.tropicalstormsoftware.com>
Date: Mon, 26 Jul 2021 08:18:04 -0700
Message-ID: <015301d78231$6ed525f0$4c7f71d0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0154_01D781F6.C2764DF0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGPmIoHmqYujbs+O/6QVBhZrEvbXwIG6lejApOsZKmrwFrRYA==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/Z1KKgRn4dkzPPXim4cpnpdJZfsM>
Subject: Re: [dtn] Draft DTNWG Charter Text
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, 26 Jul 2021 15:18:19 -0000
Hi, Rick. My understanding of the mechanism Felix and I have been discussing (Felix, please correct anything I get wrong!) is that it's not necessarily about reliable bundle delivery, but more about giving the source node information on which it could decide about the disposition of source data. The intent is to be very lightweight, with minimal state information retained at the source; it's aggregate bundle status reporting, functionally similar to the aggregate custody signaling that was developed for BPv6 on the Space Station. I can say a little more about it during the meeting if that would be helpful. Scott From: dtn <dtn-bounces@ietf.org> On Behalf Of Rick Taylor Sent: Monday, July 26, 2021 8:00 AM To: Felix.Flentge@esa.int; Birrane, Edward J. <Edward.Birrane@jhuapl.edu> Cc: dtn@ietf.org Subject: Re: [dtn] Draft DTNWG Charter Text Hi Felix, A pity you can't make it, but I think we all understand a busy schedule. Perhaps an option might be to have a more generic charter item around "reliable bundle delivery" rather than explicitly naming custody transfer as the only solution? Or does that result in a completely generic work item that we can never achieve in a reasonable time? Cheers, Rick From: dtn [mailto:dtn-bounces@ietf.org] On Behalf Of Felix.Flentge@esa.int <mailto:Felix.Flentge@esa.int> Sent: 26 July 2021 10:57 To: Birrane, Edward J. Cc: dtn@ietf.org <mailto:dtn@ietf.org> Subject: Re: [dtn] Draft DTNWG Charter Text All, sorry for the very short notice. I cannot attend today but would like to propose an additional work item: * Efficient Bundle Status Reporting I have had some background discussions on this with Scott and it is something ESA might like to use for High Data Rate Space-to-Earth Downlink where it could be used as an (better) alternative to custody transfer. I plan to present the initial ideas later this week in the CCSDS DTN WG but I thought it would not harm to have it in the IETF charter as well (maybe even replacing the custody transfer for reliable bundle delivery). Regards, Felix -- Dr. Felix Flentge Software Engineer, OPS-GSB Ground Systems Engineering Department Directorate of Operations ESA - ESOC Robert-Bosch-Str.5, D-64293 Darmstadt, Germany Phone: +49 6151 90 4075 | Email: Felix.Flentge@esa.int <mailto:Felix.Flentge@esa.int> "dtn" <dtn-bounces@ietf.org <mailto:dtn-bounces@ietf.org> > wrote on 23/07/2021 15:50:06: > From: "Birrane, Edward J." <Edward.Birrane@jhuapl.edu <mailto:Edward.Birrane@jhuapl.edu> > > To: "dtn@ietf.org <mailto:dtn@ietf.org> " <dtn@ietf.org <mailto:dtn@ietf.org> > > Date: 23/07/2021 15:53 > Subject: [dtn] Draft DTNWG Charter Text > Sent by: "dtn" <dtn-bounces@ietf.org <mailto:dtn-bounces@ietf.org> > > > DTNWG, > > Below is the draft revision of the DTNWG charter that we will be > discussing at our meeting at IETF111. Please review prior to the > meeting and come with questions and comments. > > --- > > The Delay/Disruption Tolerant Network Working Group (DTNWG) > specifies mechanisms for data communications in the presence of long > delays and/or intermittent connectivity. The Working Group has > submitted the Bundle Protocol v7 (BPv7), corresponding Bundle > Protocol Security Protocol (BPSec) and corresponding Default > Security Contexts, and the TCP Convergence Layer documents to the > IESG for publication as standards track RFCs. > > The purpose of this Working Group now turns to further work relevant > to the area of Delay/Disruption Tolerant Networking, divided into 3 > broad categories: > > * Revision of protocols and capabilities that were defined in DTN > IRTF documents, but excluded from the current output of the Working Group. > > * The definition of protocols and best practice in the areas of > Naming, Addressing and Forwarding, Key Management, and Operations, > Administration, and Management (OAM). > > * Extensions to existing protocols, including Extension Blocks to > add additional capabilities to Bundle Protocol, additional Security > Context definitions for BPSec, and new convergence layer adaptors. > > Work Items are: > > * An update to the Licklider Transmission Protocol (RFC5326) > * Bundle-in-Bundle Encapsulation > * Quality of Service indication in Bundles > * Custody Transfer for reliable bundle delivery > * Asynchronous Management Protocol and Data Model > * Naming and Addressing Architecture > * Neighbor Discovery > * Service Identifiers > * A COSE BPSec Security Context > > --- > > - Ed and Rick, co-chairs. > > --- > Edward J. Birrane, III, Ph.D. (he/him/his) > Embedded Applications Group Supervisor > Space Exploration Sector > Johns Hopkins Applied Physics Laboratory > (W) 443-778-7423 / (F) 443-228-3839 > > > > _______________________________________________ > dtn mailing list > dtn@ietf.org <mailto:dtn@ietf.org> > <https://www.ietf.org/mailman/listinfo/dtn> https://www.ietf.org/mailman/listinfo/dtn
- [dtn] Draft DTNWG Charter Text Birrane, Edward J.
- Re: [dtn] Draft DTNWG Charter Text Felix.Flentge
- Re: [dtn] Draft DTNWG Charter Text Rick Taylor
- Re: [dtn] Draft DTNWG Charter Text sburleig.sb