[Nfd-dev] What is a "region" ?
lixia at CS.UCLA.EDU
Tue Feb 23 18:54:38 PST 2016
> On Feb 23, 2016, at 4:02 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:
> Thanks... It would be great to better understand the nature of the misconception, and what a "region" is – I can't find a definition anywhere.
Let me try a simple explanation:
1/ a LINK is to get an interest to the place where the name in the interest can be used directly for lookup
2/ routers do FIB lookup using LINK first (if interest carries one), until the interest reaches the place (so called "region") where its name is in the FIB, then the router will do look up using the interest name
3/ a router decides whether the LINK has finished its job by comparing LINK with its own name: if the LINK is either its prefix or an exact match to the name, then the LINK is no longer needed.
Every entity in an NDN network should know its own name (how it learns the name is design/implementation question).
> From: Lixia Zhang <lixia at cs.ucla.edu <mailto:lixia at cs.ucla.edu>>
> Date: Tuesday, February 23, 2016 at 3:46 PM
> To: Jeff Burke <jburke at remap.ucla.edu <mailto:jburke at remap.ucla.edu>>
> Cc: "nfd-dev at lists.cs.ucla.edu <mailto:nfd-dev at lists.cs.ucla.edu>" <nfd-dev at lists.cs.ucla.edu <mailto:nfd-dev at lists.cs.ucla.edu>>
> Subject: Re: [Nfd-dev] What is a "region" ?
>> we are in group meeting now and explained how LINK (= forwarding hint) works to Zhehao and Haitao. We also trying to figure out a solution to the function you wanted (NDNfit's original design was based on a misconception of LINK).
>> LINK is a forwarding hint, it just carries an interest to the place where the name in the interest can be used directly for lookup.
>>> On Feb 23, 2016, at 1:24 PM, Burke, Jeff <jburke at remap.ucla.edu <mailto:jburke at remap.ucla.edu>> wrote:
>>> 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 <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?
>>> 2) How should they be configured at each NFD?
>>> 3) [And, who is expected to configure them, and when?]
>>> 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 <http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nfd-dev