<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Push-based communication in NDN (and its security implications) was
also <br>
explored in the context of sensing and actuation. See these two
papers:<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
J. Burke, P. Gasti, N. Nathan and G. Tsudik, <a
href="http://sprout.ics.uci.edu/projects/ndn/papers/ndn_secure_sensing.pdf">Secure
Sensing over Named Data Networking</a>, <i>13th International
Symposium on Network Computing and Applications (NCA)</i>,
Cambridge, MA, 2014.<br>
<br>
and<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
J. Burke, P. Gasti, N. Nathan and G. Tsudik, <a
href="http://sprout.ics.uci.edu/projects/ndn/papers/ndn_lighting.pdf">Securing
Instrumented Environments over Content-Centric Networking: the
Case of Lighting Control</a>, <i>the 2nd IEEE International
Workshop on Emerging Design Choices in Name-Oriented Networking
(NOMEN)</i>, Italy, 2013.<br>
<br>
Cheers,<br>
Gene<br>
<pre class="moz-signature" cols="72">======================
Gene Tsudik
Chancellor's Professor of Computer Science
University of California, Irvine
</pre>
<div class="moz-cite-prefix">On 12/5/15 1:49 AM, Syed Hassan Ahmed
wrote:<br>
</div>
<blockquote cite="mid:CE768844-EA0E-4F4F-ADB4-998DB86CFB70@ieee.org"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>Dear Faran,</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>However, "interest" structure needs to be defined. :) </div>
<div><br>
</div>
<div>For the community and your kind self, I am sharing few papers
regarding Vehicular ICN papers: </div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7145392">http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7145392</a></div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://www.sciencedirect.com/science/article/pii/S0140366415003552">http://www.sciencedirect.com/science/article/pii/S0140366415003552</a></div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7182541">http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7182541</a></div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://dl.acm.org/citation.cfm?id=2811411.2811539&coll=DL&dl=ACM">http://dl.acm.org/citation.cfm?id=2811411.2811539&coll=DL&dl=ACM</a></div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://dl.acm.org/citation.cfm?doid=2695664.2695844">http://dl.acm.org/citation.cfm?doid=2695664.2695844</a></div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7297653">http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7297653</a></div>
<div><br>
<br>
<div>
<div style="font-family: UICTFontTextStyleBody; font-size:
16px; -webkit-text-size-adjust: auto;">Kind Regards,</div>
<div style="font-family: UICTFontTextStyleBody; font-size:
16px; -webkit-text-size-adjust: auto;">Syed Hassan Ahmed.
(하산)</div>
<div style="font-family: UICTFontTextStyleBody; font-size:
16px; -webkit-text-size-adjust: auto;">PhD Scholar @ KNU,</div>
<div style="font-family: UICTFontTextStyleBody; font-size:
16px; -webkit-text-size-adjust: auto;">Daegu, Republic of
Korea. </div>
<div style="font-family: UICTFontTextStyleBody; font-size:
16px; -webkit-text-size-adjust: auto;"><a
moz-do-not-send="true"
href="https://sites.google.com/site/shahmedknu/"><a class="moz-txt-link-freetext" href="https://sites.google.com/site/shahmedknu/">https://sites.google.com/site/shahmedknu/</a></a> </div>
<div style="font-family: UICTFontTextStyleBody; font-size:
16px; -webkit-text-size-adjust: auto;"><br>
</div>
<div style="font-family: UICTFontTextStyleBody; font-size:
16px; -webkit-text-size-adjust: auto;"><br>
</div>
</div>
</div>
<div><br>
On Dec 5, 2015, at 5:12 PM, Muhammad Faran <<a
moz-do-not-send="true" href="mailto:m.faran.majeed@gmail.com"><a class="moz-txt-link-abbreviated" href="mailto:m.faran.majeed@gmail.com">m.faran.majeed@gmail.com</a></a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>Dear Hassan,<br>
<br>
</div>
Thank you for prompt response. Actually, I can
define the scenario in following two points:<br>
<br>
</div>
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.<br>
</div>
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.<br>
<br>
</div>
What I've understood from your reply:<br>
<br>
</div>
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.<br>
</div>
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.<br>
<br>
<div class="gmail_extra">
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Kind regards,<br>
<br>
Faran<br>
AIT, Thailand<br>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Sat, Dec 5, 2015 at 2:12 PM,
Syed Hassan Ahmed <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:s.h.ahmed@ieee.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:s.h.ahmed@ieee.org">s.h.ahmed@ieee.org</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-family:arial,helvetica,sans-serif">Dear
Faran, </div>
<div style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif">Experts
may response in this regards, however, here is my
answer:</div>
<div style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif">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. </div>
<div style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif">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. </div>
<div style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif">I
am not sure, that did I give you the required
answer. </div>
<div style="font-family:arial,helvetica,sans-serif">Good
Luck~~</div>
<div class="gmail_extra">
<div>
<div>
<div dir="ltr">
<div>
<div dir="ltr"><span
style="font-family:arial,helvetica,sans-serif;font-size:small"><br>
</span></div>
<div dir="ltr">Kind Regards,<br>
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~<br>
<b>Syed Hassan Ahmed</b><br>
사예드 하산 아흐메드<br>
<br>
PhD Research Scholar,<br>
<a moz-do-not-send="true"
href="http://monet.knu.ac.kr"
target="_blank">MoNeT Wireless Lab,</a><br>
Kyungpook National University,<br>
Daegu City, Republic of Korea.<br>
Cell: +82-10-9883-0786<br>
<a moz-do-not-send="true"
href="https://sites.google.com/site/shahmedknu/"
target="_blank">https://sites.google.com/site/shahmedknu/</a> </div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div>
<div class="h5">On Sat, Dec 5, 2015 at 3:55
PM, Muhammad Faran <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:m.faran.majeed@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:m.faran.majeed@gmail.com">m.faran.majeed@gmail.com</a></a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div>
<div class="h5">
<div dir="ltr">
<div>
<div>Hi!<br>
<br>
</div>
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.<br>
</div>
<div><br>
</div>
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.<br>
<br>
<div>
<div><br clear="all">
<div>
<div>
<div>
<div dir="ltr">
<div>
<div dir="ltr">Kind
regards,<br>
<br>
</div>
<div>Faran,<br>
</div>
<div>AIT, Thailand<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
_______________________________________________<br>
Ndn-interest mailing list<br>
<a moz-do-not-send="true"
href="mailto:Ndn-interest@lists.cs.ucla.edu"
target="_blank">Ndn-interest@lists.cs.ucla.edu</a><br>
<a moz-do-not-send="true"
href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest"
rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ndn-interest mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a>
<a class="moz-txt-link-freetext" href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a>
</pre>
</blockquote>
<br>
</body>
</html>