<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">Christos,</div>
<div class=""><br class="">
</div>
I am in the process of gathering references/info for existing proposals, designs and implementations.
<div class="">Is this the CSU one you refer to:</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://named-data.net/wp-content/uploads/2017/03/ndn-0055-2-trace.pdf" class="">https://named-data.net/wp-content/uploads/2017/03/ndn-0055-2-trace.pdf</a></div>
<div class=""><br class="">
</div>
<div class="">I’m familiar with the NIST one described here:</div>
<div class=""><br class="">
</div>
<div class=""><a href="http://conferences.sigcomm.org/acm-icn/2017/proceedings/icn17-86.pdf" class="">http://conferences.sigcomm.org/acm-icn/2017/proceedings/icn17-86.pdf</a></div>
<div class=""><br class="">
</div>
<div class="">If other folks could supply links to other designs or documents, that would be helpful.</div>
<div class=""><br class="">
</div>
<div class="">John</div>
<div class=""><br class="">
</div>
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">On Oct 6, 2017, at 12:35 PM, Christos Papadopoulos <<a href="mailto:christos@colostate.edu" class="">christos@colostate.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">John,<br class="">
<br class="">
Before we get deeper into a discussion, have you looked at the existing implementations of NDNtrace? I know CSU has one that can be ported to NFD, and I thought NIST has another one.<br class="">
<br class="">
Could you use one of them?<br class="">
<br class="">
Christos.<br class="">
<br class="">
<br class="">
<br class="">
On 10/06/2017 09:38 AM, Dehart, John wrote:<br class="">
<blockquote type="cite" class="">All:<br class="">
<br class="">
After our recent discussions about ndn traceroute, I was tasked with<br class="">
describing my view of what an ndn traceroute capability would be like.<br class="">
I will try to find some time to review all the current and past traceroute<br class="">
designs, but for now, this email will serve to keep the conversation going.<br class="">
<br class="">
Keep in mind that I have not been involved in nfd development so<br class="">
I won’t be getting in to the details of what all this means for nfd code.<br class="">
Also, my terminology might not agree with the offical terminology.<br class="">
<br class="">
My immediate goal is to understand how interests are routed in the NDN<br class="">
Testbed at any given time. For example, I have a simple test that I have<br class="">
been running lately where I run 'ndnping /ndn/edu/ucla’ on the WU node<br class="">
and I see RTT’s bouncing around between 80ms and 1000ms<br class="">
and at times ndnping timeouts.<br class="">
<br class="">
For me, an ideal first step for an ndn traceroute capability would<br class="">
be to augment ndnping, ndnpingserver and nfd so that the ndnping interests<br class="">
would be augmented at each forwarder with a tag for that node. Then<br class="">
ndnpingserver could take those tags and return them in the data packet<br class="">
sent back to ndnping. ndnping could then report the RTT and the path.<br class="">
<br class="">
I understand that this would not test the possibility of finding application<br class="">
data in a Content Store along the path. But for me, that is fine. I’m not<br class="">
looking right now to test the intricate data flow of a multi-party application.<br class="">
Perhaps there is a better way to collect and return the path data to<br class="">
the source, something that would make it possible for a future version<br class="">
to include Content Store hits.<br class="">
<br class="">
I also believe that this will be an important tool for Jeff Burke’s group in the<br class="">
application testing they are trying to do. It may not be 100% of what they<br class="">
want and need, but I believe it will be a good start.<br class="">
<br class="">
In working with Jeff and Peter on ndnrtc testing, I came across my WU to<br class="">
UCLA ndnping test results. Without an actual ndn-traceroute, I built my<br class="">
own with the capabilities I have as manager of the NDN Testbed. I set the<br class="">
US nodes up with nfd running in DEBUG, ran my ndnping test, collected<br class="">
nfd log files and wrote some scripts to parse them and find the path that<br class="">
my ndnpings were taking. Not exactly something that any user or app<br class="">
developer could do. I could only do it because I have privileged access<br class="">
to all the NDN Testbed nodes.<br class="">
<br class="">
John<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Nfd-dev mailing list<br class="">
<a href="mailto:Nfd-dev@lists.cs.ucla.edu" class="">Nfd-dev@lists.cs.ucla.edu</a><br class="">
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
Nfd-dev mailing list<br class="">
<a href="mailto:Nfd-dev@lists.cs.ucla.edu" class="">Nfd-dev@lists.cs.ucla.edu</a><br class="">
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>