<div dir="ltr"><div><span>Felix</span>, <br><font face="arial, sans-serif"><br></font>can’t speak to how it’s ‘ill suited’ - but i can point to <a href="http://named-data.net/publications/techreports/trlighting/" target="_blank">past work</a> that demonstrates signed interests in NDN, and of course Wentao's further work in <a href="http://named-data.net/publications/techreports/ndn-js_tr/" target="_blank">NDN-JS and BMS</a>. <br><font face="arial, sans-serif"><br></font>also, the lighting control during the demos yesterday used signed interests. </div><div><br></div><div>more generally - <span style="font-family:arial,sans-serif">the following is a follow-up to our discussion yesterday / what your poster made me think of. </span></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">(to those not familiar w/ his poster, his proposal is a sort of 'NDN <a href="https://www.pinterest.com/" target="_blank">Pinterest</a> or <a href="https://mural.ly/" target="_blank">Mural.ly</a>' (all apologies Felix :))</font></div><div><font face="arial, sans-serif"><br></font>what I was trying to say yesterday re: ‘documents’ - <br><font face="arial, sans-serif"><br></font>a) each ‘document’ is a <a href="http://en.wikipedia.org/wiki/Merkle_tree" target="_blank">merkle tree</a> of the names (including versions) of the elements <br>you call them bits, i’d change that terminology for this crowd :) - i used ‘elements’ in my namespace)<br><font face="arial, sans-serif"><br></font>b) there is a ‘<a href="http://named-data.net/doc/ndn-tlv/data.html" target="_blank">link</a>’ data object that you can use, avoids duplicating content by linking back to a different content object. it’s like a filesystem symbolic link. Likely not necessary in initial implementations, but something to keep in mind. <br><font face="arial, sans-serif"><br></font>here is a potential app namespace:<font face="arial, sans-serif"><br><br></font>/ndn/appname/user/document/[name]/[version]<br>/ndn/appname/user/document/[name]/[version]/[element]/[version]/<br><font face="arial, sans-serif"><br></font>the [element] above is shorthand for:<br><font face="arial, sans-serif"><br></font>/ndn/appname/user/element/[name]/[version]<br><font face="arial, sans-serif"><br></font>in this way. each user has<br><font face="arial, sans-serif"><br></font>/documents<br>/elements<br><font face="arial, sans-serif"><br></font>this is potential way for users to include other user’s content/elements in their ‘documents’, and it will automatically allow each user to update the elements in their document, or use the element version that they created it with (or any other version). <br><font face="arial, sans-serif"><br></font>anyway - this is what your poster made me think of...<font face="arial, sans-serif"><br><br></font>it could arguably even be implemented by sticking <a href="https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_data_attributes" target="_blank">data</a>=[NDN NAME] in exiting HTML Divs. <br><font face="arial, sans-serif"><br></font>that way you can replace content in the divs with the content of the NDN packet<br><font face="arial, sans-serif"><br></font>in this way you can use a browser as-is, and use NDN as transport. <br><font face="arial, sans-serif"><br></font><div>this can all be done with javascript, with a back-end <a href="https://github.com/named-data/repo-ng" target="_blank">repo</a> on same machine as NFD to store content permanently. </div><div><br></div><div>note there would be some discussion w/ team required to see what prefix (other than /ndn/appname/) should be used to make your application globally routable... but you can pick any prefix for development, and make sure it's easy to change when ready for others to use :) </div><div><br></div><div>anyway, just some notes & suggestions to start, likely better ways.</div><div><br></div><div>cheers</div></div><div><br></div><div>Alex</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Sep 5, 2014 at 10:54 AM, Felix Rabe <span dir="ltr"><<a href="mailto:felix@rabe.io" target="_blank">felix@rabe.io</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
This morning I was having a short discussion with someone about email over NDN and how current protocols are ill suited to secure replying and forwarding of signed messages.<br>
<br>
I can't remember who you were; please quickly drop me a line to <a href="mailto:felix@rabe.io" target="_blank">felix@rabe.io</a>. I'd like to continue the discussion.<br>
<br>
- Felix<br>
______________________________<u></u>_________________<br>
Ndn-interest mailing list<br>
<a href="mailto:Ndn-interest@lists.cs.ucla.edu" target="_blank">Ndn-interest@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" target="_blank">http://www.lists.cs.ucla.edu/<u></u>mailman/listinfo/ndn-interest</a><br>
</blockquote></div><br></div></div>