Project

General

Profile

Actions

Feature #4343

open

ASF strategy should isolate timed-out or NACK'd interests into separate namespaces

Added by Nicholas Gordon about 7 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Forwarding
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:

Description

In the week of October 9, 2017, some problems occurred on the NDN Testbed that revealed some flaws with the ASF strategy.

Currently, if the local NFD instance has a FIB entry for a very broad prefix (in our case, it was /ndn/edu/ucla), then even one misbehaving or malicious prefix anchored there is capable of causing major routing disruptions for all traffic at that prefix. The strategy should be able to defend against things like this, in some way.

I have one suggestion to mitigate this: Whenever some interest provokes a NACK or is timed-out, the strategy should remember which namespace that was, and only change its nexthop selection for that namespace. Moreover, the strategy could choose to isolate a namespace that's an n-component prefix of the offending interest. The amount of components to remove should be configurable.

Actions

Also available in: Atom PDF