[dtn] draft-ietf-dtn-bpis CRC error handling
Lucas Kahlert <lucas.kahlert@tu-dresden.de> Mon, 06 February 2017 17:31 UTC
Return-Path: <lucas.kahlert@tu-dresden.de>
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 232F41295A4 for <dtn@ietfa.amsl.com>; Mon, 6 Feb 2017 09:31:38 -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] 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 Gmu9HRgbF1yY for <dtn@ietfa.amsl.com>; Mon, 6 Feb 2017 09:31:36 -0800 (PST)
Received: from mailout5.zih.tu-dresden.de (mailout5.zih.tu-dresden.de [141.30.67.74]) (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 4C4561295A9 for <dtn@ietf.org>; Mon, 6 Feb 2017 09:31:35 -0800 (PST)
Received: from mail.zih.tu-dresden.de ([141.76.14.4]) by mailout5.zih.tu-dresden.de with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <lucas.kahlert@tu-dresden.de>) id 1can8X-0006FU-GQ for dtn@ietf.org; Mon, 06 Feb 2017 18:31:33 +0100
Received: from 77-64-188-193.dynamic.primacom.net ([77.64.188.193] helo=[192.168.1.12]) by server-50.mailclusterdns.zih.tu-dresden.de with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (envelope-from <lucas.kahlert@tu-dresden.de>) id 1can8X-000079-7j for dtn@ietf.org; Mon, 06 Feb 2017 18:31:33 +0100
From: Lucas Kahlert <lucas.kahlert@tu-dresden.de>
To: dtn <dtn@ietf.org>
Message-ID: <64ba798a-6554-7d29-a81d-150438295e64@tu-dresden.de>
Date: Mon, 06 Feb 2017 18:31:32 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-TUD-Original-From: lucas.kahlert@tu-dresden.de
X-TUD-Virus-Scanned: mailout5.zih.tu-dresden.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/GNvatN31amblyqTY3GA_B3tTFQ8>
Subject: [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: Mon, 06 Feb 2017 17:31:38 -0000
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] draft-ietf-dtn-bpis CRC error handling Lucas Kahlert
- Re: [dtn] draft-ietf-dtn-bpis CRC error handling Burleigh, Scott C (312B)