<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>That's an excellent point, in terms of the producer having a bug
here.</p>
<p>But, I stand by my comment that it would be helpful for NFD to
flag the bug when it's encountered. Here, it's outputting
something that says "hey, I got a match on a prefix". That's
presumably because until it does that lookup, it doesn't know if
there is something in the PIT that says that prefixes are OK. So
I'm simply suggesting that when it does that lookup and finds
something, it includes a debug message to the effect that it's
being ignored because the thing that matched specified that prefix
matches weren't OK. <br>
</p>
<p>Lots of stuff gets logged in NFD. This seems like the sort of
logging message that would be useful, IMHO. <br>
</p>
<p>Fred<br>
</p>
<div class="moz-cite-prefix">On 3/27/2019 5:08 PM, Junxiao Shi
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOFH+OYH9ysbhY1sB0UGMoLprLumu1AgDQgGV3Czccqw=bJj-A@mail.gmail.com">
<div>
<div dir="auto">Hi Fred</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">This isn’t a forwarder problem, but a producer
problem. The producer shouldn’t respond to an Interest with a
Data that violates CanBePrerix element. If logging is required,
it should happen at the producer.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Yours, Junxiao</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Mar 27, 2019 at
12:41 Fred Douglis <<a
href="mailto:fdouglis@perspectalabs.com"
moz-do-not-send="true">fdouglis@perspectalabs.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">
<div>
<p>I've been using NFD 0.6.3; it's possible this has been
changed in a later version, or at least a known issue,
so if so please just advise.</p>
<p>I was trying to do a simple test, using the ndnpeek
test application. I could see that the interest was
reaching the producer and making its way back to NFD,
but NFD was rejecting it as <i>unsolicited data</i>. <br>
</p>
<p>It took me longer than it should have to realize that
I'd neglected to include the -P flag. But when I look
at the NFD log, it could definitely be a bit more
informative. It shows that it looks up the name
provided in the data and fails, then matches the name
provided in the interest. At which point it says it's
an unsolicited data packet. <br>
</p>
<p>I assume what is happening under the covers is that
when it matches the prefix, it is looking for the
CanBePrefix flag, not finding it, and declaring it to be
unsolicited. A DEBUG or TRACE-level message to that
effect would, I think, help what must be a somewhat
common occurrence. Or perhaps there is a further debug
level or something else that would already have revealed
this?</p>
<p>Thanks,</p>
<p>Fred<br>
</p>
<div class="m_3425099468344300804moz-signature"><br>
</div>
</div>
_______________________________________________<br>
Nfd-dev mailing list<br>
<a href="mailto:Nfd-dev@lists.cs.ucla.edu" target="_blank"
moz-do-not-send="true">Nfd-dev@lists.cs.ucla.edu</a><br>
<a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.lists.cs.ucla.edu_mailman_listinfo_nfd-2Ddev&d=DwMFaQ&c=YC-d702opsuYKpiO2Bmlzg&r=EJmyfY3ULfVHBtsckANZFhs27SCvXVOHQdc0rPAI0ag&m=tGOfLlmVV1CMspBynlg2pOGaZRL3ioY7spC_MAXfvBk&s=-K8qOP2N9ElWEBgAPkUE8-5DEfTf4EWP9cS8yWzCQyo&e="
rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
[lists.cs.ucla.edu]</a><br>
</blockquote>
</div>
</div>
</blockquote>
<div class="moz-signature">-- <br>
<img src="cid:part4.392BDF6F.20D97550@perspectalabs.com"
border="0"></div>
</body>
</html>