[Ndn-interest] Producer taking initiative to "Push" content to network.

Sat Dec 5 06:00:56 PST 2015

Push-based communication in NDN (and its security implications) was also
explored in the context of sensing and actuation. See these two papers:

J. Burke, P. Gasti, N. Nathan and G. Tsudik, Secure Sensing over Named 
Data Networking 
<http://sprout.ics.uci.edu/projects/ndn/papers/ndn_secure_sensing.pdf>, 
/13th International Symposium on Network Computing and Applications 
(NCA)/, Cambridge, MA, 2014.

and

J. Burke, P. Gasti, N. Nathan and G. Tsudik, Securing Instrumented 
Environments over Content-Centric Networking: the Case of Lighting 
Control 
<http://sprout.ics.uci.edu/projects/ndn/papers/ndn_lighting.pdf>, /the 
2nd IEEE International Workshop on Emerging Design Choices in 
Name-Oriented Networking (NOMEN)/, Italy, 2013.

Cheers,
Gene

======================
Gene Tsudik
Chancellor's Professor of Computer Science
University of California, Irvine

On 12/5/15 1:49 AM, Syed Hassan Ahmed wrote:
> Dear Faran,
>
> Stewart mentioned a very valid point and by sending "request for 
> interest" is also a pull based mechanism. So by default it will be a 
> conventional one.
>
> However, "interest" structure needs to be defined. :)
>
> For the community and your kind self, I am sharing few papers 
> regarding Vehicular ICN papers:
>
> http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7145392
>
> http://www.sciencedirect.com/science/article/pii/S0140366415003552
>
> http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7182541
>
> http://dl.acm.org/citation.cfm?id=2811411.2811539&coll=DL&dl=ACM
>
> http://dl.acm.org/citation.cfm?doid=2695664.2695844
>
> http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7297653
>
>
> Kind Regards,
> Syed Hassan Ahmed. (하산)
> PhD Scholar @ KNU,
> Daegu, Republic of Korea.
> https://sites.google.com/site/shahmedknu/
>
>
>
> On Dec 5, 2015, at 5:12 PM, Muhammad Faran <m.faran.majeed at gmail.com 
> <mailto:m.faran.majeed at gmail.com>> wrote:
>
>> Dear Hassan,
>>
>> Thank you for prompt response. Actually, I can define the scenario in 
>> following two points:
>>
>> 1. As per application perspective, the producer needs to send content 
>> whether it is needed or not by consumers. Or there can be archiving 
>> of the content later after its production.
>> 2. Due to requirements of the application, the network has to adapt 
>> to push-based mechanism and might not be limited to only pull-based 
>> mechanism where an interest MUST be issued to retrieve content.
>>
>> What I've understood from your reply:
>>
>> 1. In vehicular environment, every node is performing as all in all. 
>> So do every node does in normal environment to be content router, 
>> producer and consumer, nothing different. But even in vehicular 
>> applications such as monitoring, a producer that wants to use the 
>> network to just accommodate its content may need to just push content.
>> 2. According to my sense, channel utilization is the task of layers 
>> below the "strategy layer" of NDN. Even for channel utilization, if 
>> content routers are aware of the application needs then they have to 
>> accommodate the content.
>>
>> Kind regards,
>>
>> Faran
>> AIT, Thailand
>>
>> On Sat, Dec 5, 2015 at 2:12 PM, Syed Hassan Ahmed <s.h.ahmed at ieee.org 
>> <mailto:s.h.ahmed at ieee.org>> wrote:
>>
>>     Dear Faran,
>>
>>     Experts may response in this regards, however, here is my answer:
>>
>>     In Vehicular NDN research, mostly authors assume that content
>>     routers are installed in each vehicle, especially, when we say
>>     that no infrastructure support is there such as RSU. So my point
>>     is that almost every node/vehicle is performing as a content
>>     router + provider + consumer role at different instances under
>>     the given circumstances.
>>
>>     Now, if we talk about "Push" based communications, then we might
>>     have a look at Pub/Sub mechanisms. If the vehicles in any area
>>     are subscribed to the specific type of data, then they don't need
>>     to send interest(s) every time. On the other hands, the producers
>>     start "pushing" the data into the network. However, in naive NDN,
>>     this approach may have its own consequences. Because, when you
>>     push, then it will cost extra cost in terms of overhead and
>>     additional copies of the packets and there might be a case, that
>>     all the neighboring nodes do not want to have that video content
>>     so why they pay the cost of channel utilization for receiving the
>>     data, they don't want or have any interest.
>>
>>     I am not sure, that did I give you the required answer.
>>     Good Luck~~
>>
>>     Kind Regards,
>>     ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
>>     *Syed Hassan Ahmed*
>>     사예드 하산 아흐메드
>>
>>     PhD Research Scholar,
>>     MoNeT Wireless Lab, <http://monet.knu.ac.kr>
>>     Kyungpook National University,
>>     Daegu City, Republic of Korea.
>>     Cell: +82-10-9883-0786
>>     https://sites.google.com/site/shahmedknu/
>>
>>     On Sat, Dec 5, 2015 at 3:55 PM, Muhammad Faran
>>     <m.faran.majeed at gmail.com <mailto:m.faran.majeed at gmail.com>> wrote:
>>
>>         Hi!
>>
>>         So far, I have been viewing NDN architecture working as
>>         pull-based mechanism. Is there any possibility to incorporate
>>         "Push" mechanism in it? Because for some environments,
>>         (vehicular/MANET), pull-based mechanism may not work properly.
>>
>>         Scenario: In a highly dynamic environment, the producer
>>         moving quickly among content routers, capturing and
>>         publishing video. So, producer can not wait for an interest
>>         and want to push the video content in-network before its
>>         local storage is full.
>>
>>
>>         Kind regards,
>>
>>         Faran,
>>         AIT, Thailand
>>
>>         _______________________________________________
>>         Ndn-interest mailing list
>>         Ndn-interest at lists.cs.ucla.edu
>>         <mailto:Ndn-interest at lists.cs.ucla.edu>
>>         http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>
>>
>
>
>
> _______________________________________________
> 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/20151205/27b4a9d8/attachment.html>