<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body class="" style="word-wrap:break-word" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Dear Junxiao,<br>
<div><br>
</div>
<div> Auto prefix propagation finally works. </div>
<div> The problem was clock synchronization. My machine is about 30 seconds off-synced with the Illinois forwarder.</div>
<div> I did not know the relation between auto prefix propagation and clock synchronization.</div>
<div><br>
</div>
<div> After synching my machine to one of NTP servers, auto prefix works just fine.</div>
<div> Thanks for pointing it out, Junxiao.</div>
<div><br>
</div>
<div>Best wishes,<br>
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div>Jongdeog Lee (JD)</div>
<div><br>
</div>
<div>------------------------------------------------</div>
<div><i>Ph.D. Student</i></div>
<div><i>Department of Computer Science</i></div>
<div><i>University of Illinois at Urbana-Champaign</i></div>
</div>
</div>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF98814" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Junxiao Shi [shijunxiao@email.arizona.edu]<br>
<b>Sent:</b> Wednesday, March 22, 2017 9:54 AM<br>
<b>To:</b> Lee, Jongdeog<br>
<b>Cc:</b> nfd-dev@lists.cs.ucla.edu<br>
<b>Subject:</b> Re: [Nfd-dev] Auto prefix propagation on multiple machines<br>
</font><br>
</div>
<div></div>
<div>Hi Jongdeog
<div class=""><br class="">
</div>
<div class="">“authorization reject” is the message used in the management dispatcher on ControlResponse with code 403.</div>
<div class="">NFD-RIB commands on /localhop/nfd/rib prefix is verified by the trust schema defined on rib.localhop_security config section.</div>
<div class="">If you are getting 403 in reply to a prefix registration command, this means the command is not authenticated or authorized by that trust schema.</div>
<div class=""><br class="">
</div>
<div class="">It’s intentional to hide the detailed error from the client, to prevent leaking sensitive information.</div>
<div class="">Currently, the detailed error isn’t logged on the server (router) side either. You may try to add logging to the <a href="https://github.com/named-data/NFD/blob/d396b61ba14a84b34d3ae65db4530062f7d43301/rib/rib-manager.cpp#L331" class="" target="_blank">authorization
function</a>, and install the re-compiled version on the router.</div>
<div class=""><br class="">
</div>
<div class="">Yours, Junxiao</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Mar 17, 2017, at 1:59 PM, Lee, Jongdeog <<a href="mailto:jlee700@illinois.edu" class="" target="_blank">jlee700@illinois.edu</a>> wrote:</div>
<div class="">
<div class="" style="font-style:normal; font-weight:normal; letter-spacing:normal; orphans:auto; text-align:start; text-indent:0px; text-transform:none; white-space:normal; widows:auto; word-spacing:0px; direction:ltr; font-family:Tahoma; font-size:10pt">
<div class="">what are the conditions that the NDN node replies this error message to the producer regarding auto prefix registration: "authorization rejected"</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</body>
</html>