[Ndn-interest] Scope of Link object?

[Muhammad Hosain Abdollahi Sabet]

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

You're right. I was talking in Web Namespace. By two I meant firstly one
for /com, /net, /ir , etc and secondly /prefix.


​​
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 those interests carrying "/google" prefix (in
its name or LINK) toward the nearest carrying announcement location
(assuming best path strategy).

Actually geographical location is not matter to me here if there wouldn't
be difference in routing costs. I mean for example, I enroll /sabet under
/google in a LINK delegation. So interests carrying /sabet when arrive at
DFZ will look for /google, then in /google network will be directly looked
up. The question is if there are /google in multiple places(like one in US
and one in West Asia) which leads to multiple topological places, and I
create the LINK in West Asia, how can interests carrying /sabet in EU reach
/sabet in West Asia, supposing US is the best path for EU in comparison to
West Asia? Solving such situations are on network owners'(e.g /google)?
Considerations should be considered by produces(e.g /sabet)?

Thanks,
Sabet


On Tue, May 24, 2016 at 9:25 AM, Lixia Zhang <lixia at cs.ucla.edu> wrote:

>
> On May 23, 2016, at 2:53 PM, Lixia Zhang <lixia at cs.ucla.edu> wrote:
>
>
> 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).
>
>
> my apology -- I just noticed that my quick cut&paste looked confusing: it
> should be:
>
> ​​
> if the prefix "/google" is announced into the network from multiple
> places, then a router simply steers those interests carrying "/google"
> prefix (in either its name or LINK) toward the nearest announcement
> location (assuming best path strategy).
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160524/be994489/attachment.html>