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

[Dehart, John]

Lixia,

I think our latest responses just said the same thing at the same time!

Other than the mess it is going to cause for anything that is already configured or
certificates that are already issued, does anyone have any reason why
the UCLA router (spurs.cs.wustl.edu<http://spurs.cs.wustl.edu>) should not have its default prefix
changed to /ndn/edu/ucla/cs?

I won’t be doing anything until after SIGCOMM but perhaps we can decide
what should be done.

John

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


On Aug 18, 2017, at 7: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.

as I looked the picture in Haitao's original message, a further and related issue is that we should have one router's name (UCLA CS router) as the *prefix* of another router (e.g. /ndn/edu/ucla/remap) -- this confuses forwarding.
By the same token, if "/ndn/edu/ucla/" is configured as name for "region", then the same name must not be used again to name a router.



<ii_15df2e4164b32d8d.png>

_______________________________________________
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/af359f01/attachment-0001.html>