[Nfd-dev] Receiving interests over WebSocket

[Junxiao Shi]

Hi JeffT

NFD can forward an Interest toward the micro forwarder via WebSocket, if
there's a FIB nexthop record pointing to the WebSocket face, and the
forwarding strategy decides to use this nexthop.
There's no technical barrier in this regard. NDN-JS browser application is
already able to act as a producer, and the micro forwarder isn't different
from a browser application from NFD's point of view.

In order to get a FIB nexthop record pointing to the WebSocket face, the
micro forwarder should send a prefix registration command to NFD under
/localhop/nfd prefix, similar to NFD-RIB's automatic prefix propagation.
As indicated in #3568 <http://redmine.named-data.net/issues/3568>, the
testbed certificate itself, rather than a sub-certificate, must be used to
sign this prefix registration command, because the router NFD cannot fetch
sub-certificates.
Thus, the user has to manually request a testbed certificate from ndncert,
export it into a format compatible with NDN-JS (step 1-2
<http://www.lists.cs.ucla.edu/pipermail/ndn-lib/2014-October/000183.html>, step
3 <http://www.lists.cs.ucla.edu/pipermail/ndn-lib/2014-October/000188.html>,
step 4-5
<http://www.lists.cs.ucla.edu/pipermail/ndn-lib/2014-October/000193.html>),
and import it into the micro forwarder.

Yours, Junxiao

On Fri, Apr 29, 2016 at 4:25 PM, Thompson, Jeff <jefft0 at remap.ucla.edu>
wrote:

> Hi Junxiao,
>
> As we discussed at the Hackathon, the NDN Micro Forwarder in the browser
> needs to make a WebSocket connection to a remote NFD and needs to receive
> interests over the same connection.
>
> How would you like to proceed? Is there a Redmine issue for this? (I
> couldn’t find it.) Should we discuss it on an NFD call?
>
> Thanks,
> - Jeff T
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160429/8a35fc27/attachment.html>