[Nfd-dev] Incorrect handling of exclude filter in CS lookup

[Junxiao Shi]

Hi Wentao

As of NFD:commit:eab7249b74d4819f9dc32e2f2d12d392f36acdc1:

   - Cs::find returns an Entry only if Entry::canSatisfy returns true; this
   condition is checked in both Cs::findLeftmost and
   Cs::findRightmostAmongExact.
   - Entry::canSatisfy returns true only if Interest::matchesData returns
   true.
   - Interest::matchesData evaluates the Exclude Selector.


If you have a problematic case, please open a Bug on NFD Redmine site.
The Bug report should contain a concise code snippet or tcpdump trace that
reproduces the problem.

Yours, Junxiao

On Thu, Mar 19, 2015 at 10:28 PM, Wentao Shang <wentaoshang at gmail.com>
wrote:

> Hi team,
>
> When I was testing NFD on iOS, I noticed that NFD doesn't seem to handle
> Exclude filter correctly in CS lookup. I looked into the code and noticed
> that in ./daemon/table/cs.cpp, the Cs::find method only handles the child
> selector but never checks the exclude filter. And I suspect this is a bug.
> Can someone verify whether this is a real issue or the exclude filter is
> actually checked somewhere else? If it's a "feature not a bug", I wonder
> what is the reason behind the design decision to leave out exclude filter
> in CS lookup.
>
> Thanks,
> Wentao
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150319/758097a9/attachment.html>