[Ndn-interest] NameSpace

[Pengyuan Zhou]

Hi Ioannis,

Thanks for replying.

Yes, as you said, I think the explicit naming feature of ICN, has a potentiality to introduce more built in features into network.

Such as your previous work and IoT with timestamps as mentioned.

To do that, I think including more info into namespace, packets with a standardised flexible structure is necessary.

Thanks.

Best,
Pengyuan


> On 26 Mar 2017, at 22:49, Psaras, Ioannis <i.psaras at ucl.ac.uk> wrote:
> 
> Hi Pengyuan,
> 
> I believe the namespace can be used to include some useful information to help the network act accordingly on the data (especially in mobile environments).
> 
> We’ve got the following three (admittedly rather preliminary) works, that enhance, or rather extend the namespace with extra information. In most cases, the extra info comes in terms of metadata, or tags.
> 
> - Keyword-Based Mobile Application Sharing, ACM MobiArch 2016: https://www.ee.ucl.ac.uk/~uceeips/files/kebapp-mobiarch16.pdf
> 
> - Name-based replication priorities in disaster cases, NOMEN 2014: https://www.ee.ucl.ac.uk/~uceeips/files/nrep-nom14.pdf
> 
> - Information Exposure through named content, Q-ICN 2014: https://www.ee.ucl.ac.uk/comit-project/files/infoexp-qicn14.pdf
> 
> I suspect that timestamped information would be especially useful in IoT scenarios.
> 
> Best regards,
> Yiannis.
> 
> On 23 Mar 2017, at 10:06, Pengyuan Zhou <zpymyyn at gmail.com> wrote:
> 
>> Hi all,
>> 
>> I’m curious if including some related info into the namespace of Interest packet and Data packet would help, or at least not harmful.
>> 
>> Such as author’s name, generated timestamp etc.
>> 
>> Thanks.
>> 
>> Best,
>> Pengyuan 
>> 
>> University of Helsinki
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>