[Ndn-interest] Scope of Link object?

[Alex Afanasyev]

Which exactly prefix link points to is up to the environment.  In the global environment, it make sense to use globally reachable names as part of hints.

As for the second question.  Let me use the attached picture to explain



If the link includes just /ucla, then the prefix /ndn/ndnsim/... has to be routable within the whole UCLA network.  If it is hard/infeasible to achieve (user needs to have some agreement with the campus network about it), then one can use a more specific prefix, e.g., /ucla/cs.  This prefix needs to be routable within UCLA network and it is network operator responsibility to make it happen.  Within CS dept network, the agreement to announce /net/ndnsim prefix is much simpler accomplish.  However, if that part is also hard/infeasible, one can use the most specific prefix (i.e., prefix that is managed by the network operators) that points to the actual server.

Consumers don't do anything to determine the link, except they looking it up in the mapping database.  For producers, it should be up to agreements between producer and the network to determine where the app's prefix can go.  The agreements themselves can be realized in form of proper namespace certificate chains.

---
Alex

> 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?
> 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.
> 
> Thanks,
> Sabet
> 
> On Mon, May 23, 2016 at 8:55 AM, Alex Afanasyev <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
> 
>> On May 22, 2016, at 8:44 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
>> 
>> Hi Sabet
>> 
>> The granularity is an Autonomous System (AS). Within the AS, the name prefix should be announced into intra-domain routing protocol, and Link object is not used.
>> In NFD implementation, whether to use Link object is determined by tables.network_region configuration option. See NFD devguide for more information.
>> 
>> Yours, Junxiao
>> 
>> On May 21, 2016 11:02 PM, "Muhammad Hosain Abdollahi Sabet" <mhasabet at gmail.com> wrote:
>> >
>> > Could you elaborate a bit more on this? If LINK points to a place, what can be granularity of it?
>> >
>> > Regards,
>> > Sabet
>> 
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160523/86bd54f2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mapnencap-example-ndn.jpg
Type: image/jpeg
Size: 62970 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160523/86bd54f2/attachment.jpg>
-------------- 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/ndn-interest/attachments/20160523/86bd54f2/attachment.bin>