Project

General

Profile

Actions

Task #4910

open

Suppress sub-prefix of a hub's prefix advertised by NFD

Added by Saurab Dulal over 5 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Start date:
04/10/2019
Due date:
% Done:

0%

Estimated time:

Description

It's more likely that the prefix propagated by local NFD to a testbed hub can be a sub-prefix of the hub’s advertised prefix. Currently, the propagated prefix are not suppressed rather are advertised.

Actions #1

Updated by Saurab Dulal over 5 years ago

  • Target version changed from Minor release v0.5.1 to v0.6.0
Actions #2

Updated by Saurab Dulal almost 4 years ago

  • Target version changed from v0.6.0 to Minor Release v0.6.1
Actions #3

Updated by Junxiao Shi almost 3 years ago

Such prefix should not be suppressed/aggregated.

Suppose an end host advertises /ndn/edu/memphis/brock1987 at both Memphis and UCLA.
If the Memphis router suppresses this advertisement, all Interests would go to UCLA according to longest prefix match rules.

Actions

Also available in: Atom PDF