[Ndn-interest] Interest Fields

shijunxiao at email.arizona.edu shijunxiao at email.arizona.edu
Mon Dec 19 08:50:02 PST 2016

Hi Matteo

PublisherPublicKeyDigest has been replaced by PublisherPublicKeyLocator. The benefit is that routers do not need to compute the digest; the drawback is that the field is longer.

AnswerOriginKind belongs to CCNx 0.7.2 but never made to NDN packet format. Its primary purpose is to restrict only producer or only cache can answer an Interest, but we believe it can be used for DoS attacks. Its secondary purpose is to delete a Data packet from local ccnd CS; we plan to implement a management command for this, but there has never been a reasonable use case.

Yes, you can implement a CS policy to cache only certain prefixes. In afterInsert trigger of this policy, it should immediately evict any entries you do not want to cache by emitting beforeEvict signal.

Yours, Junxiao

From: Matteo Bertolino
Sent: Monday, December 19, 2016 09:34
To: ndn-interest at lists.cs.ucla.edu
Subject: [Ndn-interest] Interest Fields

Good morning guys,
I have some questions about interest fields and the content store.  

1- In a paper I've seen that an Interest could take the following  
optional fields:
a) PublisherPublicKeyDigest (I just see PublisherPublicKeyLocator)
b) AnswerOriginKind.
But, grepping on ndn-cxx repo, I did not see that names. Does ndn-cxx  
provide the following fields?

2- Is it possible just caching some prefixes in the content store?

Thanks to everyone!

This message was sent using EURECOM Webmail: http://webmail.eurecom.fr

Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu

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

More information about the Ndn-interest mailing list