[Ndn-interest] Sending NACKs with ndn-cpp

Cesar Ghali cghali at uci.edu
Thu Oct 13 08:29:13 PDT 2016

That's right, mixing network and application NACKs is not a good idea. From
a security perspective, this separation is discussed in details in:



On Wed, Oct 12, 2016 at 16:07 Junxiao Shi <shijunxiao at email.arizona.edu>

> Hi JeffT
> I have a temperature sensor based on ESP8266 microcontroller. It uses
> ndn-cpp-lite, connects to a remote forwarder over TCP, and acts as a
> producer.
> The ESP8266, clocked at 80MHz, has limited signing capability. It can sign
> or verify 8 ECDSA signatures per second.
> If Interests are arriving too fast, I want to be able to send a
> NetworkNack-Congestion so that the remote forwarder can forward less
> Interests to the sensor.
> An application Nack cannot fulfill this purpose because it still requires
> a signature. Allowing the Interests to time out increases overhead at the
> remote forwarder because PIT entries stay longer.
> Yours, Junxiao
> On Wed, Oct 12, 2016 at 10:08 AM, Thompson, Jeff <jefft0 at remap.ucla.edu>
> wrote:
>> Hi Matteo.
>> A NetworkNack is a ³network² nack because it is generated by a forwarder
>> in the network, such as NFD. A client library like ndn-cpp is meant to be
>> used by an application which does not generate network-level messages. It
>> is called a ³network² nack to distinguish from an ³application² nack. Can
>> you describe the situation where your application needs to generate a
>> nack?
>> - Jeff T
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20161013/d928aaa1/attachment.html>

More information about the Ndn-interest mailing list