IETF Logo Mail Archive

[dtn] Hop Count exceeding

Lucas Kahlert <lucas.kahlert@tu-dresden.de> Sun, 12 March 2017 19:02 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 7F33D1294BD for <dtn@ietfa.amsl.com>; Sun, 12 Mar 2017 12:02:24 -0700 (PDT)
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 TEOBRhMPohFg for <dtn@ietfa.amsl.com>; Sun, 12 Mar 2017 12:02:22 -0700 (PDT)
Received: from mailout6.zih.tu-dresden.de (mailout6.zih.tu-dresden.de [141.30.67.75]) (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 BB59F129493 for <dtn@ietf.org>; Sun, 12 Mar 2017 12:02:22 -0700 (PDT)
Received: from mail.zih.tu-dresden.de ([141.76.14.4]) by mailout6.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 1cn8l2-0000S0-UG for dtn@ietf.org; Sun, 12 Mar 2017 20:02:21 +0100
Received: from 77-64-188-193.dynamic.primacom.net ([77.64.188.193] helo=[192.168.1.12]) by server-40.mailclusterdns.zih.tu-dresden.de with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (envelope-from <lucas.kahlert@tu-dresden.de>) id 1cn8l1-0006hR-SE for dtn@ietf.org; Sun, 12 Mar 2017 20:02:19 +0100
To: dtn <dtn@ietf.org>
From: Lucas Kahlert <lucas.kahlert@tu-dresden.de>
Message-ID: <7a2caf75-9fcb-e50d-5e6b-f0cb9dbc61b8@tu-dresden.de>
Date: Sun, 12 Mar 2017 20:02:19 +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: 7bit
X-TUD-Original-From: lucas.kahlert@tu-dresden.de
X-TUD-Virus-Scanned: mailout6.zih.tu-dresden.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/uc64Cbs6Jh7uUJdMXN0P2wYYS1M>
Subject: [dtn] Hop Count exceeding
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: Sun, 12 Mar 2017 19:02:24 -0000

Hello,

draft-ietf-dtn-bpbis-06 states in section 4.3.4 "a bundle SHOULD be 
deleted when its hop count exceeds its hop limit".
My question is: which method should be invoked:

  - 5.14. Bundle Deletion or
  - 5.15. Discarding a Bundle

And if a "Bundle Deletion" should be performed what is the appropriate 
reason code for a potential Bundle Status Report?

Maybe this point can be clarified in the document?

Regards,
Lucas

v2.23.0 | Report a Bug | By Email