<p dir="ltr">Lixia,</p>
<p dir="ltr">You mean in addition to LINK objects, NDNS will be responsible for storing and maintaining keys? Then there may be different types of Interests for querying LINKs or certificates? Currently we don't have *type* for Interests.</p>
<p dir="ltr">Thanks,<br>
Sabet</p>
<div class="gmail_quote">On Oct 11, 2016 5:59 PM, "Lixia Zhang" <<a href="mailto:lixia@cs.ucla.edu">lixia@cs.ucla.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Peter, <div><br></div><div>thanks for the question. </div><div>this should be one of those we are collecting for the retreat discussion.</div><div>My 2 cents: whoever generates a cert should not be the only place to retrieve the cert.</div><div>This seems related to the repo use question Patrick brought up already.</div><div>We also have a new student looking into reviving NDNS.</div><div><br><div><blockquote type="cite"><div>On Oct 10, 2016, at 12:57 PM, Gusev, Peter <<a href="mailto:peter@remap.ucla.edu" target="_blank">peter@remap.ucla.edu</a>> wrote:</div><br class="m_-4189616549342237706Apple-interchange-newline"><div>
<div style="word-wrap:break-word">
Hi architects,
<div><br>
</div>
<div>I have an "NDN applications eco-system”-related question which came up recently while preparing the new release of
<i>ndncon.</i></div>
<div><br>
</div>
<div>Right now, according to previous discussions w/ Junxiao, Alex, I see the right way to manage application identity is the following:</div>
<div><br>
</div>
<div>- on the first launch, application is supplied with the <b>
signing identity</b> by the user (i.e. <i>/ndn/edu/ucla/remap/peter</i>)</div>
<div>- application creates long-lived <b>app identity and KSK certificate</b> (i.e. <i>…/peter/ndncon)</i></div>
<div>- application generates short-lived <b>instance identity and DSK certificate</b> (i.e.
<i>…/peter/ndncon/instance-id</i>) and implements the certificate roll-over</div>
<div>- application publishes data under instance identity namespace</div>
<div>- application is responsible for serving <b>instance certificate</b>.</div>
<div><br>
</div>
<div>That said, the question is -- is it the application who’s responsible for serving
<b>app certificate</b> as well? Or is some kind of local NDN-app infrastructure (think, NDN repo) will be responsible (in the future?) for serving all app certificates installed on the end host?</div>
<div>This seems to be related to the cases when several instances of the same app can be run simultaneously.</div>
<div><br>
</div>
<div>
<div>
<div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="font-family:Helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
Thanks, </div>
<div style="font-family:Helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<br>
</div>
<div style="font-family:Helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
-- <br>
Peter Gusev</div>
<div style="font-family:Helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<br>
<a href="mailto:peter@remap.ucla.edu" target="_blank">peter@remap.ucla.edu</a><br>
+1 213 5872748<br>
peetonn_ (skype)</div>
<div style="font-family:Helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<br>
</div>
<div style="font-family:Helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
Software Engineer/Programmer Analyst @ REMAP UCLA<br>
<br>
Video streaming/ICN networks/<wbr>Creative Development</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
______________________________<wbr>_________________<br>Nfd-dev mailing list<br><a href="mailto:Nfd-dev@lists.cs.ucla.edu" target="_blank">Nfd-dev@lists.cs.ucla.edu</a><br><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev" target="_blank">http://www.lists.cs.ucla.edu/<wbr>mailman/listinfo/nfd-dev</a><br></div></blockquote></div><br></div></div><br>______________________________<wbr>_________________<br>
Nfd-dev mailing list<br>
<a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/<wbr>mailman/listinfo/nfd-dev</a><br>
<br></blockquote></div>