[Nfd-dev] What is a "region" ?

[Alex Afanasyev]

> On Feb 23, 2016, at 1:24 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:
> 
> 
> Hi,
> 
> Even after looking at relevant sections in the NFD developer's guide, we are blocked on finishing the NDNFit forwarding hint design by not understanding the specific definition of what  a "region" is, and how they should be confirmed in practice...
> 
> For example, see section 4.2 of the NFD developer's guide.
> http://named-data.net/wp-content/uploads/2015/10/ndn-0021-5-nfd-developer-guide.pdf
> <Screenshot 2016-02-23 13.18.21.png>
> 
> 
> 1) What is a region?

I don't have a good definition for the region, I can only give an implicit definition through its usage (details are in Section 4.2.3 of dev guide).

Given Interest with data name and LINK with a set of delegations (forwarding hints),  the set of "network region prefixes" determines whether the router should use "best" delegation or data name to forward the interest.

It is related to a prefix or a set of prefixes that have (global) reachability---can be used to direct interests towards the NDN network or an NDN router.

> 2) How should they be configured at each NFD?

As of right now, manually.

Note that this configuration must be done only on routers that do not have "default route", i.e., only on NDN Testbed routers.  NFD that has default route always uses data name to forward the interest.  In other words, clients connected to testbed routers don't need to do anything.

> 3) [And, who is expected to configure them, and when?]

As of right now, hub operator.  Need to be configured whenever reachability changes (new prefixes are announced in NLSR).

In the long term, there should be a form of automation (injecting from NLSR or NLSR should announce based on centralized config).

---
Alex

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160223/26e8b68d/attachment.bin>