[Nfd-dev] Handling new content in app for pending interest in NFD

[Burke, Jeff]

Hi,

To clarify, this is for an NDN application which receives an interest for data that's not yet ready.

Jeff


From: Anil Jangam <anilj.mailing at gmail.com<mailto:anilj.mailing at gmail.com>>
Date: Mon, 30 Mar 2015 10:43:45 -0700
To: Jeff Burke <jburke at remap.ucla.edu<mailto:jburke at remap.ucla.edu>>
Cc: <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>
Subject: Re: [Nfd-dev] Handling new content in app for pending interest in NFD


Hi Jeff,

Point #1 suggest that application is ndn aware since you're forwarding Interest. But IMO it isn't always required. Also I am not sure where application is running.

I think it will be appropriate to let NFD pull the data from application (or poll it) and decide how and when it can satisfy the Interest. This specially important, in the context of sensor node, due to computing resources constraints.

If NFD is not supposed to have such custmizations, we can have an agent between NFD and all sensor nodes. This agent potentially be ndn capable and also have application specific customizations.

/anil.

On Mar 30, 2015 10:28 AM, "Burke, Jeff" <jburke at remap.ucla.edu<mailto:jburke at remap.ucla.edu>> wrote:

Hi folks,

We are facing this scenario in a few applications:

1) Interest received by NFD, passed to an application
2) Application not able to respond to interest, so interest stays in NFD PIT
3) Some time passes, but not enough for the Interest to expire
4) Application generates data (e.g., from a sensor reading) that would answer the Interest in the NFD PIT

Question: How does app know to inform NFD it has the data after step 4, and how should it do that?

- In this type of app, should it push the data unsolicited to the NFD and let it decide if there is something to do?
- Is it recommended to implement an application-level PIT so the app is sure this data is solicited?  (Why add another PIT?)

Thank you,
Jeff


_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto:Nfd-dev at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150330/b1305dbb/attachment.html>