From prvs=6090aca705=mehta@ll.mit.edu Mon Jan 13 13:29:35 2014 Return-Path: X-Original-To: dtn-users@ietfa.amsl.com Delivered-To: dtn-users@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 861EB1AE033 for ; Mon, 13 Jan 2014 13:29:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.736 X-Spam-Level: X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, UNPARSEABLE_RELAY=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 4A6B6-ihTcq4 for ; Mon, 13 Jan 2014 13:29:33 -0800 (PST) Received: from mx2.ll.mit.edu (MX2.LL.MIT.EDU [129.55.12.46]) by ietfa.amsl.com (Postfix) with ESMTP id 80A4D1ADFE4 for ; Mon, 13 Jan 2014 13:29:33 -0800 (PST) Received: from LLE2K7-HUB02.mitll.ad.local (LLE2K7-HUB02.mitll.ad.local) by mx2.ll.mit.edu (unknown) with ESMTP id s0DLTKGs012375 for ; Mon, 13 Jan 2014 16:29:20 -0500 From: "Mehta, Devanshu - 0665 - MITLL" To: "dtn-users@irtf.org" Date: Mon, 13 Jan 2014 16:29:17 -0500 Thread-Topic: Unavailable opportunistic links Thread-Index: Ac8QpoTe2QjMM4k4Q/mOXf7Ahv0SFg== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_CEF9C4DD10AA2mehtallmitedu_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-01-13_03:2014-01-13,2014-01-13,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=1 spamscore=1 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1401130152 Subject: [dtn-users] Unavailable opportunistic links X-BeenThere: dtn-users@irtf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Users." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 21:29:35 -0000 --_000_CEF9C4DD10AA2mehtallmitedu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, If I have a simple two-node network using an OPPORTUNISTIC (TCP) link that = becomes UNAVAILABLE because the nodes are out of range for >30 seconds, wha= t is the appropriate automated method for setting this link back to AVAILAB= LE when they are back in range? By "appropriate", I mean consistent with the DTN architecture and the rest = of dtn 2.9.0. (My actual network is not this simple, but the above illustration gets to t= he heart of what I want to get done) Thanks, -- Devanshu Mehta Airborne Networks MIT Lincoln Laboratory --_000_CEF9C4DD10AA2mehtallmitedu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Folks,
If I ha= ve a simple two-node network using an OPPORTUNISTIC (TCP) link that becomes= UNAVAILABLE because the nodes are out of range for >30 seconds, what is= the appropriate automated method for setting this link back to AVAILABLE w= hen they are back in range?

By "appropriate", I me= an consistent with the DTN architecture and the rest of dtn 2.9.0.

(My actual network is not this simple, but the above illus= tration gets to the heart of what I want to get done)

<= div>Thanks,
-- 
Devanshu Mehta
Airborne Networks
MIT Lincoln Laboratory
--_000_CEF9C4DD10AA2mehtallmitedu_-- From david.a.zoller@nasa.gov Wed Jan 15 07:31:17 2014 Return-Path: X-Original-To: dtn-users@ietfa.amsl.com Delivered-To: dtn-users@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27851AE3A8 for ; Wed, 15 Jan 2014 07:31:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.262 X-Spam-Level: X-Spam-Status: No, score=0.262 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, 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 9wPByKeNA3er for ; Wed, 15 Jan 2014 07:31:14 -0800 (PST) Received: from ndjsnpf01.ndc.nasa.gov (ndjsnpf01.ndc.nasa.gov [IPv6:2001:4d0:a302:1100::101]) by ietfa.amsl.com (Postfix) with ESMTP id B4A8B1AE397 for ; Wed, 15 Jan 2014 07:31:14 -0800 (PST) Received: from ndmsppt103.ndc.nasa.gov (ndmsppt103.ndc.nasa.gov [198.117.0.68]) by ndjsnpf01.ndc.nasa.gov (Postfix) with ESMTP id 270CAD0445; Wed, 15 Jan 2014 09:31:17 -0600 (CST) Received: from NDMSCHT109.ndc.nasa.gov (ndmscht109-pub.ndc.nasa.gov [198.117.0.209]) by ndmsppt103.ndc.nasa.gov (8.14.5/8.14.5) with ESMTP id s0FFV2Pa030059; Wed, 15 Jan 2014 09:31:02 -0600 Received: from NDMSMBX404.ndc.nasa.gov ([169.254.4.13]) by NDMSCHT109.ndc.nasa.gov ([198.117.0.209]) with mapi id 14.03.0158.001; Wed, 15 Jan 2014 09:31:02 -0600 From: "Zoller, David A. (MSFC-EO50)[HOSC SERVICES CONTRACT]" To: "Mehta, Devanshu - 0665 - MITLL" , "dtn-users@irtf.org" Thread-Topic: Unavailable opportunistic links Thread-Index: Ac8QpoTe2QjMM4k4Q/mOXf7Ahv0SFgBXhR1w Date: Wed, 15 Jan 2014 15:31:01 +0000 Message-ID: <94CFB3711B4CAE4DBFC5BEB3374BF0C60670CA@NDMSMBX404.ndc.nasa.gov> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [198.119.225.34] Content-Type: multipart/alternative; boundary="_000_94CFB3711B4CAE4DBFC5BEB3374BF0C60670CANDMSMBX404ndcnasa_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-01-15_05:2014-01-15,2014-01-15,1970-01-01 signatures=0 Subject: Re: [dtn-users] Unavailable opportunistic links X-BeenThere: dtn-users@irtf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Users." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 15:31:17 -0000 --_000_94CFB3711B4CAE4DBFC5BEB3374BF0C60670CANDMSMBX404ndcnasa_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Devanshu, I have not experimented with the opportunistic links enough to give you a d= efinitive answer but the when an alwayson link drops it tries to reconnect = every now and then based on the parameters link_min_retry_interval and link= _max_retry_interval. I suspect that opportunistic works the same way but it= will not try to reconnect unless it has bundles pending for the destinatio= n. Hope this helps a bit, DZ From: dtn-users [mailto:dtn-users-bounces@irtf.org] On Behalf Of Mehta, Dev= anshu - 0665 - MITLL Sent: Monday, January 13, 2014 3:29 PM To: dtn-users@irtf.org Subject: [dtn-users] Unavailable opportunistic links Folks, If I have a simple two-node network using an OPPORTUNISTIC (TCP) link that = becomes UNAVAILABLE because the nodes are out of range for >30 seconds, wha= t is the appropriate automated method for setting this link back to AVAILAB= LE when they are back in range? By "appropriate", I mean consistent with the DTN architecture and the rest = of dtn 2.9.0. (My actual network is not this simple, but the above illustration gets to t= he heart of what I want to get done) Thanks, -- Devanshu Mehta Airborne Networks MIT Lincoln Laboratory --_000_94CFB3711B4CAE4DBFC5BEB3374BF0C60670CANDMSMBX404ndcnasa_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Devanshu,

I have not experimented w= ith the opportunistic links enough to give you a definitive answer but the = when an alwayson link drops it tries to reconnect every now and then based on the parameters link_min_retry_interval and link_max_= retry_interval. I suspect that opportunistic works the same way but it will= not try to reconnect unless it has bundles pending for the destination.

Hope this helps a bit,

DZ

 <= /p>

From: dtn-user= s [mailto:dtn-users-bounces@irtf.org] On Behalf Of Mehta, Devanshu - 0665 - MITLL
Sent: Monday, January 13, 2014 3:29 PM
To: dtn-users@irtf.org
Subject: [dtn-users] Unavailable opportunistic links

 

Folks,

If I have a simple two-node= network using an OPPORTUNISTIC (TCP) link that becomes UNAVAILABLE because= the nodes are out of range for >30 seconds, what is the appropriate automated method for setting this link back to AVAILABLE when = they are back in range?

 

By "appropriate",= I mean consistent with the DTN architecture and the rest of dtn 2.9.0.

 

(My actual network is not t= his simple, but the above illustration gets to the heart of what I want to = get done)

 

Thanks,

-- <= /p>

Devanshu Mehta

Airborne Networks

MIT Lincoln Laboratory=

--_000_94CFB3711B4CAE4DBFC5BEB3374BF0C60670CANDMSMBX404ndcnasa_-- From james@telixnet.com Wed Jan 15 08:45:21 2014 Return-Path: X-Original-To: dtn-users@ietfa.amsl.com Delivered-To: dtn-users@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2A221AE3D9 for ; Wed, 15 Jan 2014 08:45:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 FrFLO7SYdp4I for ; Wed, 15 Jan 2014 08:45:19 -0800 (PST) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0181.outbound.protection.outlook.com [207.46.163.181]) by ietfa.amsl.com (Postfix) with ESMTP id A2D971AE178 for ; Wed, 15 Jan 2014 08:45:18 -0800 (PST) Received: from BN1PR06MB086.namprd06.prod.outlook.com (10.242.211.147) by BN1PR06MB088.namprd06.prod.outlook.com (10.242.211.155) with Microsoft SMTP Server (TLS) id 15.0.851.11; Wed, 15 Jan 2014 16:45:04 +0000 Received: from BN1PR06MB086.namprd06.prod.outlook.com ([169.254.10.52]) by BN1PR06MB086.namprd06.prod.outlook.com ([169.254.10.74]) with mapi id 15.00.0851.011; Wed, 15 Jan 2014 16:45:04 +0000 From: James Jones To: "dtn-users@irtf.org" Thread-Topic: FEC in DTN Thread-Index: AQHPEhEjNhZE487naEixITCn0YKuwA== Date: Wed, 15 Jan 2014 16:45:03 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [50.195.8.201] x-forefront-prvs: 00922518D8 x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(779001)(679001)(689001)(189002)(199002)(80022001)(81342001)(54356001)(85852003)(77982001)(87936001)(49866001)(54316002)(74502001)(79102001)(53806001)(74366001)(65816001)(2656002)(46102001)(69226001)(93136001)(56776001)(93516002)(31966008)(76796001)(76482001)(63696002)(16236675002)(74662001)(47976001)(87266001)(47446002)(81686001)(81816001)(83072002)(80976001)(77096001)(83322001)(4396001)(74876001)(74706001)(50986001)(47736001)(59766001)(56816005)(76176001)(66066001)(51856001)(85306002)(76786001)(92566001)(90146001)(92726001)(36756003)(81542001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR06MB088; H:BN1PR06MB086.namprd06.prod.outlook.com; CLIP:50.195.8.201; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: multipart/alternative; boundary="_000_CEFC24573021Ejamestelixnetcom_" MIME-Version: 1.0 X-OriginatorOrg: telixnet.com Subject: [dtn-users] FEC in DTN X-BeenThere: dtn-users@irtf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Users." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 16:45:22 -0000 --_000_CEFC24573021Ejamestelixnetcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Greetings, I am still quite new to this list and DTN. I had a few really quick questio= ns: 1. What is currently being used for FEC (Forward Error Correction), if a= ny? 2. If there is already work being done is there anyway to do testing aga= inst vs a different FEC method? 3. Is most DTNs IP based? -James --_000_CEFC24573021Ejamestelixnetcom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
Greetings,

I am still quite new to this list and DTN. I had a few really quick qu= estions:

  1. What is currently being used for FEC (Forward Error Correction), if any= ?
  2. If there is already work being done is there anyway to do testing= against vs a different FEC method?
  3. Is most DTNs IP based?
  4. -James
    --_000_CEFC24573021Ejamestelixnetcom_-- From william.d.ivancic@nasa.gov Wed Jan 15 09:53:04 2014 Return-Path: X-Original-To: dtn-users@ietfa.amsl.com Delivered-To: dtn-users@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 438261AE378 for ; Wed, 15 Jan 2014 09:53:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.438 X-Spam-Level: X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, 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 Og_vUFy0piic for ; Wed, 15 Jan 2014 09:53:02 -0800 (PST) Received: from ndmsnpf02.ndc.nasa.gov (ndmsnpf02.ndc.nasa.gov [IPv6:2001:4d0:8302:1100::102]) by ietfa.amsl.com (Postfix) with ESMTP id 252E81AE24B for ; Wed, 15 Jan 2014 09:53:01 -0800 (PST) Received: from ndjsppt104.ndc.nasa.gov (ndjsppt104.ndc.nasa.gov [198.117.1.198]) by ndmsnpf02.ndc.nasa.gov (Postfix) with ESMTP id 20783D000E; Wed, 15 Jan 2014 11:52:52 -0600 (CST) Received: from NDJSCHT109.ndc.nasa.gov (ndjscht109-pub.ndc.nasa.gov [198.117.1.209]) by ndjsppt104.ndc.nasa.gov (8.14.5/8.14.5) with ESMTP id s0FHqmwp022015; Wed, 15 Jan 2014 11:52:49 -0600 Received: from NDJSMBX203.ndc.nasa.gov ([169.254.2.158]) by NDJSCHT109.ndc.nasa.gov ([198.117.1.209]) with mapi id 14.03.0158.001; Wed, 15 Jan 2014 11:52:49 -0600 From: "Ivancic, William D. (GRC-RHN0)" To: James Jones , "dtn-users@irtf.org" Thread-Topic: [dtn-users] FEC in DTN Thread-Index: AQHPEhEjNhZE487naEixITCn0YKuwJqGIeMA Date: Wed, 15 Jan 2014 17:52:48 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.8.130913 x-originating-ip: [184.56.61.175] Content-Type: multipart/alternative; boundary="_000_CEFC309DCC31williamdivancicnasagov_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-01-15_06:2014-01-15,2014-01-15,1970-01-01 signatures=0 Subject: Re: [dtn-users] FEC in DTN X-BeenThere: dtn-users@irtf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Users." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 17:53:04 -0000 --_000_CEFC309DCC31williamdivancicnasagov_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable FEC and DTN has many connotations. Perhaps you might specify where you wa= nt the FEC. Basically FEC on the point-to-point link between DTN forwarding agents is a= transport thing. FEC or rather erasure codes somewhere in the Application/DTN chain is a bi= t of a different animal. Look at some of the BBN proposals. http://tools.ietf.org/html/draft-irtf-dtnrg-zinky-erasure-coding-extension-= 00 http://tools.ietf.org/html/draft-irtf-dtnrg-zinky-erasure-coding-objects-00 Here is a presentation: http://www.ietf.org/proceedings/81/slides/DTNRG-2.pdf Most DTNs you will probably find information on have been run over IP simpl= y because it is the easiest to start and DTN is a network overlay. NASA JP= L has run DTN over, I believe, CCSDS space links. The DARPA program BBN Sp= indle implementation ran IP over DTN with, I believe, DTN mapped to the ra= dio MAC. (Others, feel free to add or correct these statements.) Cheers, Will From: James Jones > Date: Wednesday, January 15, 2014 11:45 AM To: "dtn-users@irtf.org" > Subject: [dtn-users] FEC in DTN Greetings, I am still quite new to this list and DTN. I had a few really quick questio= ns: 1. What is currently being used for FEC (Forward Error Correction), if a= ny? 2. If there is already work being done is there anyway to do testing aga= inst vs a different FEC method? 3. Is most DTNs IP based? -James --_000_CEFC309DCC31williamdivancicnasagov_ Content-Type: text/html; charset="us-ascii" Content-ID: <8BEA48ED1DCFEF4BB38418BF09E9E9D9@mail.nasa.gov> Content-Transfer-Encoding: quoted-printable

    FEC and DTN has many connotations.  Perhaps you might specify &nb= sp;where you want the FEC.

    Basically FEC on the point-to-point link between DTN forwarding agents= is a transport thing.

    FEC  or rather erasure codes somewhere in the Application/DTN cha= in is a bit of a different animal.  Look at some of the BBN proposals.=
    Here is a presentation:


    Most DTNs you will probably find information on have been run over IP = simply because it is the easiest to start and DTN is a network overlay. &nb= sp;NASA JPL has run DTN over, I believe, CCSDS space links.  The DARPA= program BBN Spindle implementation ran IP over DTN with, I believe,  DTN mapped to the radio MAC.  (Others= , feel free to add or correct these statements.)

    Cheers,

    Will

    From: James Jones <james@telixnet.com>
    Date: Wednesday, January 15, 2014 1= 1:45 AM
    To: "dtn-users@irtf.org" <dtn-users@irtf.org>
    Subject: [dtn-users] FEC in DTN

    Greetings,

    I am still quite new to this list and DTN. I had a few really quick qu= estions:

    1. What is currently being used for FEC (Forward Error Correction), if any= ?
    2. If there is already work being done is there anyway to do testing= against vs a different FEC method?
    3. Is most DTNs IP based?
    4. -James
    --_000_CEFC309DCC31williamdivancicnasagov_-- From dellard@bbn.com Wed Jan 15 12:54:50 2014 Return-Path: X-Original-To: dtn-users@ietfa.amsl.com Delivered-To: dtn-users@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 659511AE24C for ; Wed, 15 Jan 2014 12:54:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.739 X-Spam-Level: X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, 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 ZHLp-D5CgcZi for ; Wed, 15 Jan 2014 12:54:48 -0800 (PST) Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id BBAFC1AE0D5 for ; Wed, 15 Jan 2014 12:54:48 -0800 (PST) Received: from smp.bbn.com ([192.1.122.26]:33119) by smtp.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1W3XTw-000HD0-97; Wed, 15 Jan 2014 15:54:36 -0500 Received: from senshu.bbn.com ([128.89.72.225]:57546) by smp.bbn.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1W3XTv-000DLr-PA; Wed, 15 Jan 2014 15:54:36 -0500 Message-ID: <52D6F58B.5090605@bbn.com> Date: Wed, 15 Jan 2014 15:54:35 -0500 From: Daniel Ellard User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: dtn-users@irtf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: dellard Subject: Re: [dtn-users] FEC in DTN X-BeenThere: dtn-users@irtf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Users." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 20:54:50 -0000 On 1/15/14 12:52 PM, Ivancic, William D. (GRC-RHN0) wrote: > > > Most DTNs you will probably find information on have been run over IP simply because it is the easiest to start and DTN is a network overlay. NASA JPL has run DTN over, I believe, CCSDS space links. The DARPA program BBN Spindle implementation ran IP over DTN with, I believe, DTN mapped to the radio MAC. (Others, feel free to add or correct these statements.) A minor correction: the SPINDLE implementation ran DTN over several convergence layers, including TCP, UDP and radio MACs. The WNaN project, which used the SPINDLE codebase, used DTN-over-radio-MAC to implement reliable IP. The layers were completely independent, so you could, if you wanted to, run the SPINDLE TCP CLA on top of the IP layer provided by running the SPINDLE MAC CLA over the radio... -Dan -- Daniel Ellard, Ph.D. Senior Scientist, Network Research Raytheon BBN Technologies dellard@bbn.com 617-873-8004 From l.wood@surrey.ac.uk Wed Jan 15 13:58:44 2014 Return-Path: X-Original-To: dtn-users@ietfa.amsl.com Delivered-To: dtn-users@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 699971AE245 for ; Wed, 15 Jan 2014 13:58:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 pOPOMkecpIxU for ; Wed, 15 Jan 2014 13:58:42 -0800 (PST) Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.151]) by ietfa.amsl.com (Postfix) with ESMTP id 52DF51AE102 for ; Wed, 15 Jan 2014 13:58:42 -0800 (PST) Received: from [195.245.231.67:57568] by server-15.bemta-5.messagelabs.com id 05/94-08490-58407D25; Wed, 15 Jan 2014 21:58:29 +0000 X-Env-Sender: l.wood@surrey.ac.uk X-Msg-Ref: server-3.tower-82.messagelabs.com!1389823109!34022420!1 X-Originating-IP: [131.227.200.43] X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5997 invoked from network); 15 Jan 2014 21:58:29 -0000 Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-3.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 15 Jan 2014 21:58:29 -0000 Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Wed, 15 Jan 2014 21:58:28 +0000 From: To: , Date: Wed, 15 Jan 2014 21:57:31 +0000 Thread-Topic: FEC in DTN Thread-Index: AQHPEhEjNhZE487naEixITCn0YKuwJqGVXHA Message-ID: <290E20B455C66743BE178C5C84F1240847E63346CD@EXMB01CMS.surrey.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dtn-users] FEC in DTN X-BeenThere: dtn-users@irtf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Users." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 21:58:44 -0000 Actually, I think it's fair to say that most DTNs are *TCP*/IP based - and = most use of the bundle protocol has been over TCP. Lloyd Wood http://about.me/lloydwood ________________________________________ From: dtn-users [dtn-users-bounces@irtf.org] On Behalf Of James Jones [jame= s@telixnet.com] Sent: 15 January 2014 16:45 To: dtn-users@irtf.org Subject: [dtn-users] FEC in DTN Greetings, I am still quite new to this list and DTN. I had a few really quick questio= ns: 1. What is currently being used for FEC (Forward Error Correction), if an= y? 2. If there is already work being done is there anyway to do testing agai= nst vs a different FEC method? 3. Is most DTNs IP based? -James