[Ndn-interest] Disabling NDN's in-network caching

Muhammad Hosain Abdollahi Sabet M.AbdollahiSabet at mail.sbu.ac.ir
Thu Mar 19 09:52:48 PDT 2015

Hmmm. By setting the capacity to zero, the logic would be the same. I mean, still there would be a ContentStore checking in the process which  is not needed then, right?


-----Original Message-----
From: Junxiao Shi [mailto:shijunxiao at email.arizona.edu]
Sent: Thu 3/19/2015 8:03 PM
To: Muhammad Hosain Abdollahi Sabet
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Disabling NDN's in-network caching
Hi Muhammad

Yes, you may disable in-network caching by *setting ContentStore capacity
to zero*.
The relevant configuration option is tables.cs_max_packets in

However, this is an *unsupported configuration*.
In particular,

   - StatusDataset and Notification in NFD Management won't work before #
   2182 <http://redmine.named-data.net/issues/2182>, which implies
   nfd-status won't work.
   - Remote prefix registration won't work before #1529

There could be other limitations as well.

Yours, Junxiao

On Thu, Mar 19, 2015 at 9:10 AM, Muhammad Hosain Abdollahi Sabet <
M.AbdollahiSabet at mail.sbu.ac.ir> wrote:

>  Hi,
> In "A case for stateful forwarding plane", in the simulation part it said
> "Since we focus out evaluation on the effectiveness of stageful adaptive
> forwarding, we disabled NDN's in-network caching in the simulation." The
> question is: Is it possible to disable in-network caching in  real NFD?
> Thanks,
> Sabet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150319/8d161b78/attachment.html>

More information about the Ndn-interest mailing list