Re: [dtn] DTN BoF Proposal for IETF90
"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 06 June 2014 21:56 UTC
Return-Path: <Fred.L.Templin@boeing.com>
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 986281A02A9 for <dtn@ietfa.amsl.com>; Fri, 6 Jun 2014 14:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.841
X-Spam-Level:
X-Spam-Status: No, score=-4.841 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_HTML_ATTACH=0.01] 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 JOMi1HYapaU0 for <dtn@ietfa.amsl.com>; Fri, 6 Jun 2014 14:55:59 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E50241A0273 for <dtn@ietf.org>; Fri, 6 Jun 2014 14:55:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s56LtpIB013637; Fri, 6 Jun 2014 14:55:51 -0700
Received: from XCH-PHX-209.sw.nos.boeing.com (xch-phx-209.sw.nos.boeing.com [130.247.25.29]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s56LtfFs013124 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 6 Jun 2014 14:55:42 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.105]) by XCH-PHX-209.sw.nos.boeing.com ([169.254.9.197]) with mapi id 14.03.0181.006; Fri, 6 Jun 2014 14:55:40 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Burleigh, Scott C (312G)" <scott.c.burleigh@jpl.nasa.gov>, "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: [dtn] DTN BoF Proposal for IETF90
Thread-Index: Ac+AQa9Fez/CplZaSwyaLFpzb8tj0wAiVZ0AAAXfQWAADdLFAAAnSnygAAQYTsAAApCFwA==
Date: Fri, 06 Jun 2014 21:55:39 +0000
Message-ID: <2134F8430051B64F815C691A62D983181B2C0855@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983181B2BE63E@XCH-BLV-504.nw.nos.boeing.com> <EDBFE89D-2775-4E40-B566-EBDBEC216F28@netapp.com> <2134F8430051B64F815C691A62D983181B2BF3F7@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983181B2BF96C@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983181B2C05A4@XCH-BLV-504.nw.nos.boeing.com> <A5BEAD028815CB40A32A5669CF737C3B423C155B@ap-embx-sp40.RES.AD.JPL>
In-Reply-To: <A5BEAD028815CB40A32A5669CF737C3B423C155B@ap-embx-sp40.RES.AD.JPL>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: multipart/mixed; boundary="_002_2134F8430051B64F815C691A62D983181B2C0855XCHBLV504nwnosb_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dtn/ZsQTg7ZfLHGJJ9lBtttuW_mEmqo
Subject: Re: [dtn] DTN BoF Proposal for IETF90
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: Fri, 06 Jun 2014 21:56:02 -0000
Hi Scott, > Fred, a couple of suggested tweaks to the charter: Yes to both - see below for the update, plus attached diffs. Thanks - Fred fred.l.templin@boeing.com --- Draft BoF Agenda (2.5hrs): ************************** 1) Problem statement (IETF wg motivation) - 30min 2) RFC5050(bis) - 15min 3) Streamlined Bundle Security Protocol (SBSP) - 15min 4) Bundle-in-Bundle Encapsulation - 10min 5) Security Key Management - 10min 6) Registry for Service Identifiers - 10min 7) Network Management - 10min 8) Open Discussion - 50min Proposed working group charter: ******************************* 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: TBD 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. The work is motivated by well known limitations of standard Internet protocols that expect end-to-end connectivity between communicating endpoints, sub-second transmission delays and robust packet delivery ratios. In environments where these favorable conditions do not apply, existing mechanisms such as reliable transport protocols and routing protocols can fail to converge resulting in communication failures. Furthermore, classical end-to-end security associations cannot be coordinated when communicating endpoints cannot conduct multi-message keying exchanges in a timely fashion. These limitations suggest the need for a new approach. Delay-Tolerant Networking (DTN) protocols have been the subject of extensive research and development in the Delay-Tolerant Networking Research Group of the Internet Research Task Force since 2002. In particular, the DTN Bundle Protocol (RFC 5050) and Licklider Transmission Protocol (RFC 5326) have been shown to address the issues identified above in substantial fielded deployments [1]. The success of the BP/LTP protocol stack -- the core protocols of the "DTN Architecture" originally described in RFC 4838 -- may be attributed to the following fundamental design principles: - There is never any expectation of contemporaneous end-to-end connectivity between any two network nodes. - Because end-to-end connectivity can never be assumed, each node on the path between source and destination must be prepared to handle incoming "bundles" of data that cannot immediately be forwarded. - Again because end-to-end connectivity can never be assumed, end-to-end conversational data exchange can never be assumed to complete in a timely manner; protocol features that rely on timely conversational data exchange must be excluded from the architecture. The DTNWG believes that protocols adhering to these principles offer opportunities for enhancing the functionality of the Internet - in particular, for facilitating the extension of the Internet into environments such as the ocean floor and deep space in which the core Internet protocols operate sub-optimally for the reasons discussed earlier. We believe that the extensive research, demonstration, and pilot operations performed to date using the DTNRG protocols provides a firm basis for publishing Internet standards derived from that work. Work items related to Delay/Disruption Tolerant Networking include: o A mechanism for the exchange of protocol data units, termed "bundles", that are designed to obviate conversational communications by containing values for all potentially relevant configuration parameters. These protocol data units are typically larger than network-layer packets. We will derive this bundle exchange mechanism from the DTN Bundle Protocol (BP) documented in RFC 5050 by publishing a new document for which [2] is a proposed first draft (where appendix A provides a summary of the proposed changes). o A security protocol for ensuring that the network in which bundles are exchanged is secured against unauthorized access and denial of service attacks, and to ensure data integrity and confidentiality in that network where necessary. We will derive this security protocol from a "streamlined" adaptation of the DTN Bundle Security Protocol documented in RFC 6257. o An encapsulation protocol for "tunneling" BP traffic within bundles that are secured and/or routed in different way from the encapsulated bundles. o A delay-tolerant security key management scheme for ensuring that public keys are certified by a globally trusted authority to protect the integrity of the infrastructure. o A simple datagram convergence layer protocol for adaptation of the bundle protocol to underlying internetworks. We expect to derive this convergence layer protocol from the Datagram Convergence protocol documented in RFC 7122. o A delay-tolerant network management protocol for management of the infrastructure in the presence of long delays and/or intermittent connectivity. o A registry for DTN Service Identifiers The working group will consider extending the current milestones based on new information and knowledge gained while working on the initial charter, as well as to accommodate new work items beyond the scope of the initial phase. For example, we expect that transport protocols such as LTP and the Saratoga protocol are among the candidates for work in this phase. Goals and Milestones: start+3mos - Submit 'Bundle Protocol Specification (RFC5050bis)' as a working group document [2]. To be Proposed Standard. Start+3mos - Submit 'Streamlined Bundle Security Protocol (SBSP)' as a working group document [3]. To be Proposed Standard. start+6mos - Submit 'Bundle In Bundle Encapsulation (BIBE)' as a working group document [4]. To be Proposed Standard. start+12mos - Submit 'Delay Tolerant Networking Security Key Management' as a working group document. To be Proposed Standard. start+18mos - WG determination for merging RFC5050bis, SBSP, BIBE and/or Key Mgmt into a combined draft or keep as separate drafts. start+18mos - Submit RFC5050bis, SBSP, BIBE and Key Mgmt to the IESG either as a combined draft or as separate drafts. start+18mos - Submit Network Management [5], Registry [6] and Simple Convergence Layer [7] as working group documents. start+20mos - Survey appropriate forums (e.g., DTNRG) for emerging technologies (e.g., convergence layer protocols, dynamic routing protocols, naming and addressing services, etc.) ready for transition into IETF DTN Working Group. Publish draft on survey results as independent submission related to the WG. start+24mos - Submit Network Management, Registry and Simple Convergence Layer to IESG start+24mos - Recharter to accommodate new work items or close Working Group [1] "BP/LTP deployment on EPOXI spacecraft" [2008], http://committees.comsoc.org/tccc/ccw/2010/slides/DINET_CCW.pdf [2] "Proposed Revised Bundle Protocol" [2014], https://datatracker.ietf.org/doc/draft-burleigh-bpv7/ [3] "Streamlined Bundle Security Protocol Specification" [2014], https://datatracker.ietf.org/doc/draft-irtf-dtnrg-sbsp/ [4] "Bundle-in-Bundle Encapsulation" [2013], http://tools.ietf.org/id/draft-irtf-burleigh-bibe [5] "Delay Tolerant Network Management Protocol" [2013], http://tools.ietf.org/id/draft-irtf-dtnrg-dtnmp [6] "Delay-Tolerant Networking Bundle Protocol IANA Registries" [2011], https://datatracker.ietf.org/doc/rfc6255/ [7] "Datagram Convergence Layers ..." [2014], https://datatracker.ietf.org/doc/rfc7122/
- [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Eggert, Lars
- Re: [dtn] DTN BoF Proposal for IETF90 l.wood
- Re: [dtn] DTN BoF Proposal for IETF90 Eric Travis
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Eric Travis
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 l.wood
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 l.wood
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Burleigh, Scott C (312G)
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Birrane, Edward J.
- Re: [dtn] DTN BoF Proposal for IETF90 l.wood
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Krupiarz, Christopher
- Re: [dtn] DTN BoF Proposal for IETF90 ccaini
- Re: [dtn] DTN BoF Proposal for IETF90 Burleigh, Scott C (312G)
- Re: [dtn] DTN BoF Proposal for IETF90 Pete Resnick
- Re: [dtn] DTN BoF Proposal for IETF90 Ramachandran, Vignesh R. (Vinny)
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Krupiarz, Christopher
- Re: [dtn] DTN BoF Proposal for IETF90 Birrane, Edward J.
- Re: [dtn] DTN BoF Proposal for IETF90 Pete Resnick
- Re: [dtn] DTN BoF Proposal for IETF90 Krupiarz, Christopher
- Re: [dtn] DTN BoF Proposal for IETF90 Birrane, Edward J.
- Re: [dtn] DTN BoF Proposal for IETF90 Marius Feldmann
- Re: [dtn] DTN BoF Proposal for IETF90 l.wood
- Re: [dtn] DTN BoF Proposal for IETF90 Burleigh, Scott C (312G)
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Elwyn Davies
- Re: [dtn] DTN BoF Proposal for IETF90 Sebastian Schildt
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Elwyn Davies
- Re: [dtn] DTN BoF Proposal for IETF90 Spencer Dawkins
- Re: [dtn] DTN BoF Proposal for IETF90 Elwyn Davies
- Re: [dtn] DTN BoF Proposal for IETF90 Sebastian Schildt
- Re: [dtn] DTN BoF Proposal for IETF90 Elwyn Davies
- Re: [dtn] DTN BoF Proposal for IETF90 Spencer Dawkins
- Re: [dtn] DTN BoF Proposal for IETF90 Elwyn Davies
- Re: [dtn] DTN BoF Proposal for IETF90 Nikolaos Bezirgiannidis
- Re: [dtn] DTN BoF Proposal for IETF90 Spencer Dawkins
- Re: [dtn] DTN BoF Proposal for IETF90 Martin Stiemerling
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Sebastian Schildt
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Sebastian Schildt
- Re: [dtn] DTN BoF Proposal for IETF90 Templin, Fred L
- Re: [dtn] DTN BoF Proposal for IETF90 Burleigh, Scott C (312G)
- Re: [dtn] DTN BoF Proposal for IETF90 l.wood
- Re: [dtn] DTN BoF Proposal for IETF90 Burleigh, Scott C (312G)