[Nfd-dev] How far that we can do inside NFD forwarding strategy virtual class?

[Junxiao Shi]

Hi Mahyuddin

I want to develop a new forwarding strategy which has some extra features
> apart on just managing interest forwarding. But im a bit clueless about
> which NFD API can be access inside forwarding strategy and which are not.
>
See NFD devguide <https://named-data.gitlab.io/TR-NDN-0021-NFD-dev-guide/>
"Forwarding Strategy - How to Develop a New Strategy - Should I Develop a
New Strategy" section for limitations.

1. How to react to after receive data event which are not supported in
> forwarding strategy?
>
Currently you can't.
#4290 <https://redmine.named-data.net/issues/4290> is to add this
capability. Watch this issue on Redmine to get updates.


> 2.  How to capture information (e.g name prefix and upstream face) from
> data packet in forwarding strategy to become a new FIB entry (content
> discovery through reactive content routing).
>
Currently you can't.
#4285 <https://redmine.named-data.net/issues/4285> is to add this
capability. Watch this issue on Redmine to get updates.



> 3. Create our own broadcast suppression method as friend method/function
> of forwarding strategy virtual class instead external method inside other
> class?
>
You can only suppress incoming Interest, in after receive Interest trigger.
Suppressing incoming Data depends on #4290.

Human knowledge Belongs to The World
>
This line is awesome.

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170917/d90c467d/attachment.html>