* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Dtn Status Pages

Delay/Disruption Tolerant Networking (Active WG)
Tsv Area: Mirja Kühlewind, Spencer Dawkins | 2014-Nov-07 —  
Chairs
 
 


2017-02-16 charter

Delay/Disruption Tolerant Networking (dtn)
------------------------------------------

 Charter

 Current Status: Active

 Chairs:
     Marc Blanchet <Marc.Blanchet@viagenie.ca>
     Rick Taylor <rick@tropicalstormsoftware.com>

 Transport Area Directors:
     Spencer Dawkins <spencerdawkins.ietf@gmail.com>
     Mirja Kühlewind <ietf@kuehlewind.net>

 Transport Area Advisor:
     Spencer Dawkins <spencerdawkins.ietf@gmail.com>

 Secretary:
     Edward Birrane <edward.birrane@jhuapl.edu>

 Mailing Lists:
     General Discussion: dtn@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/dtn
     Archive:            https://mailarchive.ietf.org/arch/browse/dtn/

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, i.e.,
  RFC 5050, RFC 7122, RFC 7242, RFC 6257 and RFC 6260,  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 this working group is to update the base
  specifications in light of implementation experience. The group shall
  do a review of deployment problems and lessons learned, come to
  consensus on the issues to be addressed in the base protocol
  documents, and update the specifications accordingly. The group shall
  not endeavour to change the underlying architecture or the bundle
  protocol principle.

  Work items are:

   o  Agree to a list of use cases for evolving the DTN specifications and
      a list of work items to be worked on.

   o  Create updates to RFC5050, convergence layer RFCs, and security
      (RFC6257), as standard track documents.

   o  Document a registry for DTN Service Identifiers.


Goals and Milestones:
  Done     - Use Cases for evolving the DTN specifications and list of work items to be worked on.
  Dec 2016 - RFC5050bis
  Dec 2016 - TCP CL update
  Feb 2017 - Neighbor Discovery
  Feb 2017 - Network Management Requirements
  Feb 2017 - Key Management Requirements
  May 2017 - Registry of Service Identifiers
  May 2017 - Addressing Architecture
  May 2017 - Bundle Security Protocol


All charter page changes, including changes to draft-list, rfc-list and milestones:



Generated from PyHt script /wg/dtn/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -