IETF Logo Mail Archive

Re: [dtn] draft-ietf-dtn-bpis CRC error handling

"Burleigh, Scott C (312B)" <scott.c.burleigh@jpl.nasa.gov> Tue, 07 February 2017 18:11 UTC

Return-Path: <scott.c.burleigh@jpl.nasa.gov>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10245129450 for <dtn@ietfa.amsl.com>; Tue, 7 Feb 2017 10:11:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 CT2fjJ_VsGIP for <dtn@ietfa.amsl.com>; Tue, 7 Feb 2017 10:11:51 -0800 (PST)
Received: from mail.jpl.nasa.gov (smtp.jpl.nasa.gov [128.149.139.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9932A12942F for <dtn@ietf.org>; Tue, 7 Feb 2017 10:11:51 -0800 (PST)
Received: from mail.jpl.nasa.gov (ap-ehub-sp02.jpl.nasa.gov [128.149.137.149]) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id v17IBoR2006693 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256 bits) verified NO); Tue, 7 Feb 2017 10:11:51 -0800
Received: from AP-EMBX-SP10.RES.AD.JPL ([169.254.1.111]) by ap-ehub-sp02.RES.AD.JPL ([fe80::dd85:7b07:1e36:7e3c%15]) with mapi id 14.03.0319.002; Tue, 7 Feb 2017 10:11:51 -0800
From: "Burleigh, Scott C (312B)" <scott.c.burleigh@jpl.nasa.gov>
To: Lucas Kahlert <lucas.kahlert@tu-dresden.de>, dtn <dtn@ietf.org>
Thread-Topic: [dtn] draft-ietf-dtn-bpis CRC error handling
Thread-Index: AQHSgJ7hJqgkR7efB0eqrirPz6+AaaFd2PpQ
Date: Tue, 07 Feb 2017 18:11:49 +0000
Message-ID: <A5BEAD028815CB40A32A5669CF737C3B6130C752@ap-embx-sp10.RES.AD.JPL>
References: <64ba798a-6554-7d29-a81d-150438295e64@tu-dresden.de>
In-Reply-To: <64ba798a-6554-7d29-a81d-150438295e64@tu-dresden.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.149.137.82]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Source-Sender: scott.c.burleigh@jpl.nasa.gov
X-AUTH: Authorized
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/cnI6M5zhj997tzximFuA8EnGyCA>
Subject: Re: [dtn] draft-ietf-dtn-bpis CRC error handling
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 07 Feb 2017 18:11:53 -0000

Hi, Lucas.  I think what µPCN already does is the right thing.  The most frequent cause of CRC errors will be transmission bit errors due to channel noise; dropping the bundle will silently trigger automatic retransmission, the right response.  Informing the source node of every channel bit hit would generate an awful lot of traffic, unnecessarily.

Scott

-----Original Message-----
From: dtn [mailto:dtn-bounces@ietf.org] On Behalf Of Lucas Kahlert
Sent: Monday, February 6, 2017 9:32 AM
To: dtn <dtn@ietf.org>
Subject: [dtn] draft-ietf-dtn-bpis CRC error handling

Hello,

I am a German student implementiung the current draft-ietf-dtn-bpis in the context of the [µPCN project](http://upcn.eu/).

I came across the CRC validation and wonder what a bundle protocol agent should do if an CRC error occurs. Are there any development proposals for handling CRC errors. Currently µPCN siliently deletes any bundle with invalid CRC. Should the sender be notified about the transmission error?

Regrads,
Lucas Kahlert

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

v2.23.0 | Report a Bug | By Email