<HTML dir=ltr><HEAD>
<META content="text/html; charset=unicode" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 11.00.10586.162"></HEAD>
<BODY style="WORD-WRAP: break-word">
<DIV id=idOWAReplyText6367 dir=ltr>
<DIV dir=ltr><FONT color=#000000 face=Arial>Dear Spyridon,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial>I greatly appreciate your help.</FONT></DIV>
<DIV dir=ltr><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE dir=ltr type="cite">
<DIV>
<DIV>
<P><FONT color=#800080 size=2>3- What is the difference between Name(Name to be resolved) and Hint(Name Hint) in digApp? They are both set to "/ndn”</FONT></P></DIV></DIV></BLOCKQUOTE>
<DIV dir=ltr><FONT color=#800080>According to the SNAMP paper, a name of some data should be resolved directly to a LINK object that contains a number of globally routable name (forwarding hints). In the current implementation, I think that the name of some data is resolved to a globally routable name directly.</FONT></DIV><FONT color=#800080></FONT></DIV>
<P><FONT color=#800080><FONT color=#000000>So, apart from what is set in the scenario, a query for /ndn (Name) may retrieve /ucla (Hint), right?</FONT></FONT></P>
<P><FONT color=#800080><FONT color=#000000></FONT></FONT> </P><FONT color=#800080>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>
<P><FONT size=2>4- From consumer's perspective, firstly a digApp should query for a "hint" for a prefix, then attach query's answer as a Link object to Interest?<BR></FONT></P></DIV></DIV></BLOCKQUOTE>
<DIV>In theory, the application should retrieve the LINK object directly from NDNS. However, in this case you are right.</DIV>
<DIV dir=ltr><FONT color=#000000></FONT> </DIV>
<DIV dir=ltr><FONT color=#000000>You mean in your scenario digApp sends interest for some entity other than NDNS? I suppose any node on which NdnsServerApp is running would be an instance of NDNS.</FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>
<P><FONT size=2>5- What relation is in place between what has been done in your scenario, and Link related functions in ndnSIM?<BR></FONT></P></DIV></DIV></BLOCKQUOTE>
<DIV>Sorry, but I do not understand the question.</DIV>
<DIV> </DIV>
<DIV>I mean, currently we have this class in ndnSIM:</DIV>
<DIV><A href="http://ndnsim.net/2.1/doxygen/classndn_1_1Link.html">http://ndnsim.net/2.1/doxygen/classndn_1_1Link.html</A></DIV></DIV>
<DIV dir=ltr><FONT color=#000000>For example, where does addDelegation() stores a Link object? Or, where does getDelegations() retrieve Link objects from? Is there any relation between extensions in your scenario and ndn::Link Class? Because I didn't see any reference to ndn::Link in the extensions.</FONT></DIV>
<P><FONT color=#000000>Anything you say helps. I've put Alex in cc. Hope he sees.</FONT></P>
<P><FONT color=#000000></FONT> </P>
<P><FONT color=#000000>Many thanks,</FONT></P>
<P><FONT color=#000000>Sabet</FONT></P>
<DIV dir=ltr><BR></DIV></FONT>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Spyridon (Spyros) Mastorakis [mailto:mastorakis@cs.ucla.edu]<BR><B>Sent:</B> Fri 4/1/2016 1:57 AM<BR><B>To:</B> Muhammad Hosain Abdollahi Sabet<BR><B>Cc:</B> ndnsim@lists.cs.ucla.edu<BR><B>Subject:</B> Re: [ndnSIM] Link resolver server<BR></FONT><BR></DIV>
<DIV>Please see my answer inline. I am not that familiar with the NDNS implementation, so I will try to answer the questions that I know in the best possible way:
<DIV>
<DIV>
<DIV>
<DIV>
<DIV><BR></DIV></DIV></DIV></DIV>
<DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>
<P><FONT size=2>Thank you. You scenario works. Regarding to that, there are questions I need to ask you:<BR>1- What is the content of test.db?<BR></FONT></P></DIV></DIV></BLOCKQUOTE>
<DIV>It is the database of the current NDNS instance (storing the records).</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>
<P><FONT size=2>2- What is the procedure to add a zone or identity? I guess there should be some key-chain related routine I'm not familiar with.<BR></FONT></P></DIV></DIV></BLOCKQUOTE>
<DIV>I think that this has to do with this file:</DIV>
<DIV><BR></DIV>
<DIV><A href="https://github.com/spirosmastorakis/ndns-scenario/blob/master/extensions/ndns-create-zone.hpp">https://github.com/spirosmastorakis/ndns-scenario/blob/master/extensions/ndns-create-zone.hpp</A></DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>
<P><FONT size=2>3- What is the difference between Name(Name to be resolved) and Hint(Name Hint) in digApp? They are both set to "/ndn”</FONT></P></DIV></DIV></BLOCKQUOTE>According to the SNAMP paper, a name of some data should be resolved directly to a LINK object that contains a number of globally routable name (forwarding hints). In the current implementation, I think that the name of some data is resolved to a globally routable name directly.<BR>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>
<P><FONT size=2>4- From consumer's perspective, firstly a digApp should query for a "hint" for a prefix, then attach query's answer as a Link object to Interest?<BR></FONT></P></DIV></DIV></BLOCKQUOTE>
<DIV>In theory, the application should retrieve the LINK object directly from NDNS. However, in this case you are right.</DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>
<P><FONT size=2>5- What relation is in place between what has been done in your scenario, and Link related functions in ndnSIM?<BR></FONT></P></DIV></DIV></BLOCKQUOTE>
<DIV>Sorry, but I do not understand the question.</DIV>
<DIV><BR></DIV>
<DIV>NDNS was Alex’s thesis, so he can elaborate more on the implementation details. Hope that my answer helped though.</DIV><BR></DIV>
<DIV>
<DIV><SPAN style="FLOAT: none; DISPLAY: inline">Spyridon (Spyros) Mastorakis</SPAN><BR><SPAN style="FLOAT: none; DISPLAY: inline">Personal Website: </SPAN><A href="http://cs.ucla.edu/~mastorakis/">http://cs.ucla.edu/~mastorakis/</A><BR><SPAN style="FLOAT: none; DISPLAY: inline">Internet Research Laboratory</SPAN><BR><SPAN style="FLOAT: none; DISPLAY: inline">Computer Science Department</SPAN><BR><SPAN style="FLOAT: none; DISPLAY: inline">UCLA</SPAN></DIV>
<DIV><SPAN style="FLOAT: none; DISPLAY: inline"><BR></SPAN></DIV></DIV><BR></DIV></DIV></BODY></HTML>