Feature #4762
open
Add a new UnsolicitedDataPolicy that admits unsolicited data by prefix
Added by Ernest McCracken about 6 years ago.
Updated almost 3 years ago.
Description
We would like to add an unsolicited data policy that allows applications to specify which prefixes they would like to cache unsolicited data for.
The proposed design is as follows:
Create a new UnsolicityDataPolcy called AdmitPrefixesUnsolicitedDataPolicy that defines two additional methods register(name) and unregister(name).
Prefixes are stored in a table which is looked up in the decide method.
Create a new manager class to allow applications to use the Interest based API to add/remove prefixes as needed.
Files
- Subject changed from Add a new UnsolicitedDataPolicy that admits unsolicited data by prefix. to Add a new UnsolicitedDataPolicy that admits unsolicited data by prefix
- Start date deleted (
10/23/2018)
I've mostly finished the changes needed for the UnsolicitedDataPolicy implementation. I do have questions about management.
The choice of UnsolicitedDataPolicy is made in the config file. Is there any benefit to changing the policy while NFD is running?
If not then does it make sense for the content store management module to handle requests to add and remove prefixes from the AdmitPrefixesUnsolicitedDataPolicy (if that is the current policy) instead of creating a new management module just for UnsolicitedDataPolicy?
- Status changed from New to In Progress
Some Issues to think about:
The number or prefixes that might be unsolicited. If the order reaches into 1000's then a name tree instead of unordered_set would be more appropriate. This may be something that simply needs to be monitored once the feature is being used.
Use of regular expressions. Beneficial from a machine learning perspective as well as reducing the size of unsolicited prefixes.
What's the status of this issue?
Davide Pesavento wrote:
What's the status of this issue?
Ernest implemented this feature but the code has not been reviewed or merged. If there's interest in the code, I can ask Alex to take on this task after he's done with the ASF changes.
- Category changed from Management to Forwarding
- Status changed from In Progress to New
- Assignee deleted (
Ernest McCracken)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by