IETF Logo Mail Archive

Re: [dtn] proposed DTN workgroup - what is process being followed?

"Ivancic, William D. (GRC-LCA0)" <william.d.ivancic@nasa.gov> Thu, 23 October 2014 14:52 UTC

Return-Path: <william.d.ivancic@nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2C71A9170; Thu, 23 Oct 2014 07:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 2FIsREljxEGh; Thu, 23 Oct 2014 07:52:38 -0700 (PDT)
Received: from ndmsnpf02.ndc.nasa.gov (ndmsnpf02.ndc.nasa.gov [IPv6:2001:4d0:8302:1100::102]) by ietfa.amsl.com (Postfix) with ESMTP id 827C61A9022; Thu, 23 Oct 2014 07:52:37 -0700 (PDT)
Received: from ndjsppt102.ndc.nasa.gov (ndjsppt102.ndc.nasa.gov [198.117.1.196]) by ndmsnpf02.ndc.nasa.gov (Postfix) with ESMTP id 89B9ED001B; Thu, 23 Oct 2014 09:52:36 -0500 (CDT)
Received: from NDJSCHT107.ndc.nasa.gov (ndjscht107-pub.ndc.nasa.gov [198.117.1.207]) by ndjsppt102.ndc.nasa.gov (8.14.7/8.14.7) with ESMTP id s9NEqaIY007563; Thu, 23 Oct 2014 09:52:36 -0500
Received: from NDJSMBX203.ndc.nasa.gov ([169.254.3.230]) by NDJSCHT107.ndc.nasa.gov ([198.117.1.207]) with mapi id 14.03.0195.001; Thu, 23 Oct 2014 09:52:36 -0500
From: "Ivancic, William D. (GRC-LCA0)" <william.d.ivancic@nasa.gov>
To: "Juan A. Fraire" <juanfraire@gmail.com>, William Ivancic <ivancic@syzygyengineering.com>
Subject: Re: [dtn] proposed DTN workgroup - what is process being followed?
Thread-Topic: [dtn] proposed DTN workgroup - what is process being followed?
Thread-Index: AQHP6t98gNPJ+16N5EWz3BMTYH22NJw2PUkAgARu0oCAAFwggIAAiE4AgAFKEYCAASJfAIAAF2aA///ImYA=
Date: Thu, 23 Oct 2014 14:52:35 +0000
Message-ID: <D06E8D1E.210F3%william.d.ivancic@nasa.gov>
References: <1413638841.79127.YahooMailNeo@web28903.mail.ir2.yahoo.com> <1413642432.88432.YahooMailNeo@web28901.mail.ir2.yahoo.com> <544630B5.3080006@gmail.com> <1413905917.2651.YahooMailNeo@web125103.mail.ne1.yahoo.com> <1413935188.59957.YahooMailNeo@web125105.mail.ne1.yahoo.com> <CAEFTjmV8K5tTJU+x3HWdFM+eja-Lr6+1V4LVc7YZwKAqrej8wA@mail.gmail.com> <1414068426.90690.YahooMailNeo@web125106.mail.ne1.yahoo.com> <CAAdWZLbk9tB853sVoN2ycAajcB=WAnJQGM8ZUpvRaP6k3ij86g@mail.gmail.com>
In-Reply-To: <CAAdWZLbk9tB853sVoN2ycAajcB=WAnJQGM8ZUpvRaP6k3ij86g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [139.88.111.195]
Content-Type: multipart/alternative; boundary="_000_D06E8D1E210F3williamdivancicnasagov_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-10-23_05:2014-10-23,2014-10-23,1970-01-01 signatures=0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MwV0bYuAq7DG8dOnFGNsmG3lg5U
X-Mailman-Approved-At: Thu, 23 Oct 2014 10:53:56 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, Kevin Fall <kfall@kfall.net>, Martin Stiemerling <mls.ietf@gmail.com>, "iab@iab.org" <iab@iab.org>, "iesg@ietf.org" <iesg@ietf.org>, "dtn@ietf.org" <dtn@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Oct 2014 14:52:45 -0000

Juan,

Remember,  we are not just discussing space applications. We are discussing general applications hundreds of millions of nodes.
Bundling may work well for your application in space with four or five nodes, but perhaps not so much for general Internet.  Remember IETF is INTERNET Engineering Task Force.  CCSDS is Space.  If IETF is going to work on something, it needs to address the general needs of the Internet user base, not just Space.  That is CCSDS' realm.

Will


A good overview:
https://www.youtube.com/watch?v=3zOLrQJ5kbU

Some papers are here with link to  presentations.
http://named-data.net/publications/


But above is just one viewpoint of ICN.  ICNRG should lead you to others.
https://irtf.org/icnrg


A publish/subscribe architecture is what BBN came up with for F6 (Fractionated Spacecraft)
http://dl.acm.org/citation.cfm?doid=2348616.2348626


Will
******************************
William D. Ivancic
Phone 216-433-3494
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic


From: "Juan A. Fraire" <juanfraire@gmail.com<mailto:juanfraire@gmail.com>>
Date: Thursday, October 23, 2014 10:10 AM
To: William Ivancic <ivancic@syzygyengineering.com<mailto:ivancic@syzygyengineering.com>>
Cc: "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.org>>, Kevin Fall <kfall@kfall.net<mailto:kfall@kfall.net>>, Martin Stiemerling <mls.ietf@gmail.com<mailto:mls.ietf@gmail.com>>, "iab@iab.org<mailto:iab@iab.org>" <iab@iab.org<mailto:iab@iab.org>>, "iesg@ietf.org<mailto:iesg@ietf.org>" <iesg@ietf.org<mailto:iesg@ietf.org>>, Lloyd Wood <lloyd.wood@yahoo.co.uk<mailto:lloyd.wood@yahoo.co.uk>>, "dtn@ietf.org<mailto:dtn@ietf.org>" <dtn@ietf.org<mailto:dtn@ietf.org>>
Subject: Re: [dtn] proposed DTN workgroup - what is process being followed?

Hi Will,

Where can I read (not slides) about how ICN handles routing, forwarding, buffering, network-level congestion, and contact predictability? Is there an RFC or good article about these?

Thanks,


J.Fraire
Universidad Nacional de Córdoba, Argentina


On Thu, Oct 23, 2014 at 9:47 AM, William Ivancic <ivancic@syzygyengineering.com<mailto:ivancic@syzygyengineering.com>> wrote:
Hi Kevin,

Yes, I worked closely with this group.  Chart 19 says it all. Buy the way, don't confuse the need for DTN with the need for the Bundle protocol.  Chart 19 supports Wes' comments.  There is not way this group can deploy large networks without item 2.

Challenging network environment leads to link and network disruptions

  1.  Need to develop a robust DTN based transport service
  2.  Requires solutions to addressing, routing, management, discovery and forwarding/QOS

I have not seen this group actively participating on any of the DTN mail list in the past year or two or perhaps more.  Time flies.

Will


________________________________
From: Kevin Fall <kfall@kfall.net<mailto:kfall@kfall.net>>
To: William Ivancic <ivancic@syzygyengineering.com<mailto:ivancic@syzygyengineering.com>>
Cc: "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.org>>; Martin Stiemerling <mls.ietf@gmail.com<mailto:mls.ietf@gmail.com>>; "iab@iab.org<mailto:iab@iab.org>" <iab@iab.org<mailto:iab@iab.org>>; "iesg@ietf.org<mailto:iesg@ietf.org>" <iesg@ietf.org<mailto:iesg@ietf.org>>; Lloyd Wood <lloyd.wood@yahoo.co.uk<mailto:lloyd.wood@yahoo.co.uk>>; "dtn@ietf.org<mailto:dtn@ietf.org>" <dtn@ietf.org<mailto:dtn@ietf.org>>
Sent: Wednesday, October 22, 2014 3:27 PM
Subject: Re: [dtn] proposed DTN workgroup - what is process being followed?

Based on a meeting I recently attended and 2014 references such as this:

(http://nsrc.cse.psu.edu/talks_2014/thoughts_on_future_army_waveforms_20Mar2014.pdf)

I cannot share your conclusion.



_______________________________________________
dtn mailing list
dtn@ietf.org<mailto:dtn@ietf.org>
https://www.ietf.org/mailman/listinfo/dtn

v2.23.0 | Report a Bug | By Email