[Nfd-dev] What link object to use on testbed?

Dehart, John jdd at wustl.edu
Fri Aug 18 07:59:22 PDT 2017


On Aug 18, 2017, at 9:44 AM, Lixia Zhang <lixia at cs.ucla.edu<mailto:lixia at cs.ucla.edu>> wrote:


On Aug 18, 2017, at 6:10 AM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:

Hi Haitao

Link object in Interest has been replaced by forwarding hint. However, your question still applies when forwarding hint is used.


I tried to send an Interest with link object to the testbed, but the producer didn't receive the interest. Could you help to see what is wrong with my link object?

Here is what I did:
(1) The producer registers prefix /org/openmhealth/<user-id> on ucla router (spurs.cs.ucla.edu<http://spurs.cs.ucla.edu/>)
(2) A consumer connecting to remap router (128.97.98.7) sends an interest with prefix /org/openmhealth/<user-id>, and with link object. The link object has name  /org/openmhealth/<user-id>, and a delegation /ndn/edu/ucla(it is ucla router's routable prefix), and it is signed by a cert /org/openmhealth/KEY/<user-id>/...., which is signed by ndnfit trust anchor, a second trust anchor on the testbed.


REMAP router is configured <https://github.com/WU-ARL/NDN_Ansible/blob/138020756db384222e62802baeaca0b6a090c6d7/host_vars/REMAP> to have network region name /ndn/edu/ucla/remap.

I do not know what have been defined as the rules for configuring so called "region"; in this specific case the outcome does not sound correct -- REMAP router should remove forwarding hint only if
the forwarding hint = /ndn/edu/ucla/remap.

I wonder if the problem is perhaps on the other side. The default prefix for the UCLA node should perhaps
be more like /ndn/edu/ucla/cs.
Then the forwarding hint included in the example could be /ndn/edu/ucla/cs and REMAP would not remove it.

I’ve never completely understood the semantics of the network region. Is it written down somewhere?

John



Lixia
_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto:Nfd-dev at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170818/e1b3908c/attachment.html>


More information about the Nfd-dev mailing list