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

[Junxiao Shi]

Hi Lixia and John

>
> 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.
>
> No. It is necessary for a forwarding hint with a shorter prefix to match a
network region with a longer name. Consider a large ISP with multiple POPs,
such as Level 3. For a large website such as MSN, its name can be announced
across the entire ISP, and be accessible with forwarding hint /level3. For
a small website such as yoursunny.com , its name is announced within a
single POP, and can be accessed with forwarding hint /level3/lax, or even a
smaller scale such as /level3/lax/woothosting.

Requiring exact match on network region names would require every router in
Level 3 network to be configured with multiple network region names in
order to match every possible forwarding hint. For example, the core router
at LAX POP would need at least /level3 and /level3/lax. Using search-prefix
match allows the router configuration to only have the most specific
/level3/lax.

>
> 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.
>
Yes, exactly. You can even be more specific and include the router name as
part of the network region name.

Then the forwarding hint included in the example could be /ndn/edu/ucla/cs
> and REMAP would not remove it.
>
Yes.


> I’ve never completely understood the semantics of the network region. Is
> it written down somewhere?
>
See NFD developer guide. I'm in the process of updating it from Link
objects to forwarding hint (watch https://redmine.named-data.net/issues/4055
for progress), but concept is the same.

Yours, Junxiao

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