[ndnSIM] Mobile package
adhysatya820 at gmail.com
Mon Oct 9 11:27:23 PDT 2017
I am looking on the TODOs from the code and have a few questions.
1. In the first TODO in the `doSend() ` -here
where we need to remove the previous tag if it exists, does
`lpPacket.get<::ndn::lp::GeoTagField>();` work like the PeekPacketTag()?
i.e., does it search for a matching tag and calls deserialize()? I don't
understand why line 95 is commented out.
2. What is the reason of setting isLocal to true if geo tag field exists?
3. On Line #112, what the reason for checking the HopCount after computing
the WaitingTime? There's no reference to hopCount in the Rapid Traffic
4. How do I associate the v2v-net-device-transport to my link type? Or how
do I hardcode my simulation to use the v2v-net-device?
I hope I can finish this code and contribute to the project :)
On Tue, Aug 29, 2017 at 6:11 PM, Spyridon (Spyros) Mastorakis <
mastorakis at cs.ucla.edu> wrote:
> the strategy is explained (more or less) in this paper:
> To finish the v2v net device transport implementation, you can take a look
> at the .c file. There is a number of TODOs there. I think that if you
> finish those TODOs and do some debugging, you should be good to go.
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> Internet Research Laboratory
> Computer Science Department
> On Aug 28, 2017, at 6:30 AM, Adhy Satya <adhysatya820 at gmail.com> wrote:
> Hi Spyros,
> Thank you for your answer.
> If I understood correctly, the broadcast strategy uses the exponential
> Interest suppression, which is the only mechanism preventing flooding
> (since the v2v-transport is not being use).
> What is needed to be able to use the v2v-net-device-transport? Is it a
> feature implemented in the new version of NFD that is not implemented in
> the 0.4 version?
> On Fri, Aug 25, 2017 at 6:45 PM, Spyridon (Spyros) Mastorakis <
> mastorakis at cs.ucla.edu> wrote:
>> if I recall correctly, we did not get to use the v2v-net-device
>> transport. We directly modified the net device transport instead (
>> From the perspective of long term design planning, a Face of NFD will be
>> associated with a link of specific type. This link can be an ad-hoc or a
>> point-to-point link, etc, so this could determine how a strategy makes its
>> decisions. I do not think that an application will be able to know the type
>> of the underlying link (unless it sends a query to NFD somehow — this could
>> be implemented as a hack in ndnSIM if needed).
>> We are planning to integrate the latest version of NFD with ndnSIM this
>> fall to be able to use the link type feature in simulations, so please stay
>> Thank you,
>> Spyridon (Spyros) Mastorakis
>> Personal Website: http://cs.ucla.edu/~mastorakis/
>> Internet Research Laboratory
>> Computer Science Department
>> On Aug 24, 2017, at 9:29 PM, Adhy Satya <adhysatya820 at gmail.com> wrote:
>> Hi Spyros,
>> I downloaded and tested the mobile simulation package code. It's very
>> helpful to me, thanks
>> My question is how does the application/strategy knows which
>> net-device-face to use, since there are the "original"
>> net-device-transport" and the v2v-net-device-transport.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ndnSIM