[Nfd-dev] Network Nack Usage

Brown, Andrew andrew.brown at intel.com
Thu May 5 16:59:09 PDT 2016

Thanks Alex for the note on Lixia's point 2 below; I was referring more to
point 1. I wanted to know specifically not if anyone is using the
application-level Nack but the network-level one that is exposed in the
APIs. I will take the absence of comments to mean that this is yet to be




Andrew Brown

IoTG Strategy and Integrated Products


From: Lixia Zhang [mailto:lixia at cs.ucla.edu] 
Sent: Tuesday, May 3, 2016 12:14 PM
To: Brown, Andrew <andrew.brown at intel.com>
Cc: nfd-dev at lists.cs.ucla.edu; Ilya Moiseenko <iliamo at mailbox.org>
Subject: Re: [Nfd-dev] Network Nack Usage



On May 3, 2016, at 8:58 AM, Brown, Andrew <andrew.brown at intel.com
<mailto:andrew.brown at intel.com> > wrote:




Is anyone using the different NACK codes to alter the flow of their


there could be different ways to interpret the question:


1/ how applications use different NACK codes to alter the "data flow"

e.g. Ilya (copied him here) used application NACK to tell consumers to wait
for a specific time period when data is not ready


2/ how network layer (NFD) use different NACKs to alter the paths of dat

(as Alex mentioned)

I am looking at
457b9b#diff-e12e36065baf92aa80b384cbfb3eef02R35 and was interested in
finding out the different actions others are taking: obviously log in all
cases, wait and re-send for congestion, fail and throw for no route, ___ for




Andrew Brown

IoTG Strategy and Integrated Products


Nfd-dev mailing list
 <mailto:Nfd-dev at lists.cs.ucla.edu> Nfd-dev at lists.cs.ucla.edu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160505/e9d5e24f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3954 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160505/e9d5e24f/attachment.bin>

More information about the Nfd-dev mailing list