#13 Improve reactive forwarding


We can increase ION's rate of successful bundle delivery in at least two ways:

  1. When a bundle is reforwarded due to expiration of its xmitOverdue timer (indicating the failure of a routing decision that was expected to be successful; analogous to reception of a Custody Refused signal), in computing a revised route we should be open to the possibility that the best plan might be to forward the bundle back to the node from which we originally received it. That is, in this case the sending node should be omitted from the Excluded Nodes list.

  2. Continuing in this vein: the other mechanism we've got for backtracking in the network is Custody Refused signals, but those signals are issued only for bundles for which custody transfer is requested. Since custody transfer is not mandatory but we always need the ability to send a bundle back through the network to a node that can compute an alternative route for it (the "snub" system), we should send Custody Refused signals whenever forwarding a bundle is impossible, even if no custody transfer was requested.


  • Scott Burleigh

    Scott Burleigh - 2013-12-20
    • Group: 3.2.0 --> 3.2.1
  • Scott Burleigh

    Scott Burleigh - 2014-07-14
    • Group: 3.2.1 --> 3.3.0
  • Scott Burleigh

    Scott Burleigh - 2015-01-04

    These two changes are implemented in feature branch req-0013-reactive-forwarding.

  • Scott Burleigh

    Scott Burleigh - 2015-01-04
    • status: accepted --> pending
  • Scott Burleigh

    Scott Burleigh - 2015-03-06
    • status: pending --> closed


Cancel  Add attachments

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks