[dtn] new version of charter
Marc Blanchet <marc.blanchet@viagenie.ca> Tue, 30 September 2014 18:10 UTC
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9921A8717 for <dtn@ietfa.amsl.com>; Tue, 30 Sep 2014 11:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_44=0.6, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 aPRUKvTIBKmL for <dtn@ietfa.amsl.com>; Tue, 30 Sep 2014 11:10:39 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 66A6C1A8714 for <dtn@ietf.org>; Tue, 30 Sep 2014 11:10:39 -0700 (PDT)
Received: from h226.viagenie.ca (h226.viagenie.ca [206.123.31.226]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B0433412C4 for <dtn@ietf.org>; Tue, 30 Sep 2014 14:10:37 -0400 (EDT)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <37B5F068-FD47-4680-9D80-88A847BF25DD@viagenie.ca>
Date: Tue, 30 Sep 2014 14:10:35 -0400
To: dtn@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dtn/6YUnBToymXvchZksiEgkjx5cpWY
Subject: [dtn] new version of charter
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 30 Sep 2014 18:10:41 -0000
Hello, after our conf call today, there was a concensus within the group who attended (about ~20 people) that we would use this version of the charter, as the base. Therefore, please use the one below for comments. Regards, Marc&Fred. ============================== Working group name: Delay/Disruption Tolerant Networking Working Group (DTNWG) Chair(s): TBD Area and Area Director(s): Transport Area: ADs Spencer Dawkins <spencerdawkins.ietf at gmail.com>, Martin Stiemerling <mls.ietf at gmail.com> Responsible Area Director: Martin Stiemerling <mls.ietf at gmail.com> Mailing list: General Discussion: dtn at ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/dtn Archive: http://www.ietf.org/mail-archive/web/dtn/current/maillist.html Description of Working Group: The Delay/Disruption Tolerant Network Working Group (DTNWG) specifies mechanisms for data communications in the presence of long delays and/or intermittent connectivity. Delay-Tolerant Networking (DTN) protocols have been the subject of extensive research and development in the Delay-Tolerant Networking Research Group (DTNRG) of the Internet Research Task Force since 2002. The key documents are the « DTN Architecture » (RFC 4838), the Bundle Protocol (RFC 5050), Licklider Transmission Protocol (RFC 5326) and convergence layers (RFC 7122, 7242). Multiple independent implementations exist for these technologies and multiple deployments in space and terrestrial environments. There is an increase interest in the commercial world for these technologies, for similar and different use cases, such as unmanned air vehicles. In this context, there is a need to update the base specifications based on the deployment and implementation experience as well as the new use cases. Moreover, there is also a need to have standards track documents for the market. Therefore, the purpose of the working group is to document the new use cases and requirements and to update the base specifications. The group shall not endeavour to change the underlying architecture or the bundle protocol principle. Work items are: o An informational « DTN Revision Problem Statement, Use Cases, Requirements and Development Strategy » document o Updates to RFC5050, convergence layer RFCs, security(RFC6257), as standard track documents. o A registry for DTN Service Identifiers Before the updates of the protocol specifications are worked on, the Problem statement should be agreed within the working group and with the IESG, specially on what the additional work items will be. Goals and Milestones: April 2015 Informational document sent to IESG
- [dtn] new version of charter Marc Blanchet
- Re: [dtn] new version of charter Ivancic, William D. (GRC-LCA0)
- Re: [dtn] new version of charter Nabil Benamar
- Re: [dtn] new version of charter Marc Blanchet
- Re: [dtn] new version of charter Templin, Fred L
- Re: [dtn] new version of charter Nabil Benamar
- Re: [dtn] new version of charter Sebastian Schildt
- Re: [dtn] new version of charter Will Ivancic
- Re: [dtn] new version of charter Martin Stiemerling
- Re: [dtn] new version of charter Martin Stiemerling
- Re: [dtn] new version of charter John Dowdell
- Re: [dtn] new version of charter l.wood