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

[Dave Oran (oran)]

Isn’t this what the repo was invented for?

Holding packets in a router that has forgotten that they were asked for is a giant invitation to cache pollution/poisoning attacks.

> On Mar 30, 2015, at 2:24 PM, Haowei Yuan <hyuan at wustl.edu> wrote:
> 
> I think as long as the data has actually been requested by an Interest
> packet, it is safe to send the Data packet to NFD. The NFD will either
> forward or drop the Data packet by checking if the Interest has
> expired.
> 
> If the Interest has expired, Data packet is dropped, and the consumer
> is still interested in the data, the consumer could resend the
> Interest. Hopefully this time, the Data packet can be generated and
> sent faster by the application so that NFD will forward it.
> 
> Haowei
> 
> 
> On Mon, Mar 30, 2015 at 1:12 PM, Anil Jangam <anilj.mailing at gmail.com> wrote:
>> 
>> On Mar 30, 2015 11:08 AM, "Dehart, John" <jdd at wustl.edu> wrote:
>>> 
>>> 
>>> Is there any harm in it pushing the data out without knowing for sure if
>>> the
>>> Interest is still active?
>>> 
>> If data is so critical, can the Interest be refreshed proactively before it
>> expires?
>> 
>> /anil
>> 
>>> John
>>> 
>>>> On Mar 30, 2015, at 1:05 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> 
>>>>> On Mon, Mar 30, 2015 at 10:28 AM Burke, Jeff <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?
>>>>> 
>>>>> 
>>>>> In my opinion, as long as the application is certain that the Interest
>>>>> has arrived and is stored in NFD's PIT, it can just push the data out to
>>>>> NFD.
>>>> 
>>>> 
>>>> 
>>>> How certain does it have to be?  There is a chance it could have
>>>> expired...
>>>> jeff
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> Wentao
>>>>> 
>>>>>> 
>>>>>> - 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
>>>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>>> 
>>>> _______________________________________________
>>>> Nfd-dev mailing list
>>>> Nfd-dev at lists.cs.ucla.edu
>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Nfd-dev mailing list
>>> Nfd-dev at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>> 
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev