[Ndn-interest] Scope of Link object?

Lixia Zhang lixia at CS.UCLA.EDU
Mon May 23 14:53:32 PDT 2016

> On May 23, 2016, at 12:43 PM, Muhammad Hosain Abdollahi Sabet <mhasabet at gmail.com> wrote:
> Alex,
> So, the one thing we are sure about, is that Forwarding Hint should be globally routable. It means at least the first two components of it, should be available in DFZ. Is that correct?

the forwarding hint (LINK) should be able to find a match from FIB; there isn't any specific limit on the number of components.

> I'm not looking for this one right now, but I'm curios. When you say Link could point to a network, how could one locate that network if it is available in more that one topologic location. Take /google as an example.

if you use the word "topological" (not geographical): network topology is not equivalent to locations.  
if the prefix "/google" is announced into the network from multiple places, then a router simply steers interests "/google" prefix (in its name or LINK) toward the nearest carrying announcement location (assuming best path strategy).

> On Mon, May 23, 2016 at 8:55 AM, Alex Afanasyev <aa at cs.ucla.edu <mailto:aa at cs.ucla.edu>> wrote:
> This is not exactly correct. The granularity of the LINK can be anything.  It can be a prefix that correspond to something like an AS (/att), it can be a name that points to a network within the ISP (/att/net1/net2), or it can be a host within the network (/att/net1/net2/net3/host).
> The specific usage would depend on what make sense for your application and environment.  With a more generic name (/att) you're relying on name-based forwarding to direct your interests within that network directly.
> --
> Alex

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160523/01ce7919/attachment.html>

More information about the Ndn-interest mailing list