<div dir="ltr"><div><div><div><div>Dear Stewart,<br><br></div>Thank you for your reply. From your reply I understood the following:<br><br></div>1. There is no intrinsic push-based mechanism support in NDN architecture.<br></div>2. If a producer wants to take initiative for pushing content before it is requested, it will have to use "request for interest" interest.<br><br></div>According to second point, we'll have to explicitly set producer to perform "request for interest" functionality to do pushing of content. Am I right?<br><div><div><div><div><div><div><div><div><div><div class="gmail_extra"><br clear="all"><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 3:22 PM, <span dir="ltr"><<a href="mailto:ndn-interest-request@lists.cs.ucla.edu" target="_blank">ndn-interest-request@lists.cs.ucla.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Ndn-interest mailing list submissions to<br>
<a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a 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>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:ndn-interest-request@lists.cs.ucla.edu">ndn-interest-request@lists.cs.ucla.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:ndn-interest-owner@lists.cs.ucla.edu">ndn-interest-owner@lists.cs.ucla.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Ndn-interest digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. go-ndn 1.2 (Tai-Lin Chu)<br>
2. Producer taking initiative to "Push" content to network.<br>
(Muhammad Faran)<br>
3. Re: Producer taking initiative to "Push" content to network.<br>
(Syed Hassan Ahmed)<br>
4. Re: Producer taking initiative to "Push" content to network.<br>
(Muhammad Faran)<br>
5. Re: Producer taking initiative to "Push" content to network.<br>
(stewart mackenzie)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 4 Dec 2015 11:50:07 -0800<br>
From: Tai-Lin Chu <<a href="mailto:tailinchu@gmail.com">tailinchu@gmail.com</a>><br>
To: "<a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a>" <<a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a>><br>
Subject: [Ndn-interest] go-ndn 1.2<br>
Message-ID:<br>
<CABf5LwDg_vLh6Gh6=<a href="mailto:0-OPT4E5PdkoaTBsaxdxwVos9zHo3v7ng@mail.gmail.com">0-OPT4E5PdkoaTBsaxdxwVos9zHo3v7ng@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
This release is not possible without some individual contributors.<br>
<br>
Major Feature:<br>
<br>
- experimental "send/push" semantics: A data sender sends interests<br>
with name "<nodeName>/ACK/<dataName>" to ensure that a specific node<br>
receives a specific data packet. This is implemented with<br>
`mux.Notifier` and `mux.Listener`. Feel free to share how you achieve<br>
send or push in NDN.<br>
<br>
- go-ndn/health: instrument your ndn application easily. It stores<br>
per-minute stats like interest request count and response time on<br>
disk, and presents on a nice web interface. All web interface assets<br>
are directly compiled into application and are available offline. (See<br>
<a href="https://github.com/go-ndn/health" rel="noreferrer" target="_blank">https://github.com/go-ndn/health</a>)<br>
<br>
Tutorial:<br>
<br>
- Generate Data Before Interest: Discuss two common design patterns to<br>
publish data "before" interests, and show how "self-generated/fake<br>
interests" can achieve this.<br>
<br>
<a href="https://github.com/go-ndn/example/blob/master/before-interest.md" rel="noreferrer" target="_blank">https://github.com/go-ndn/example/blob/master/before-interest.md</a><br>
<br>
<br>
Contributer:<br>
- Oli Gavin<br>
- qhsong<br>
- Mahyuddin Husairi<br>
<br>
More details: <a href="https://github.com/go-ndn/example#news" rel="noreferrer" target="_blank">https://github.com/go-ndn/example#news</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sat, 5 Dec 2015 13:55:40 +0700<br>
From: Muhammad Faran <<a href="mailto:m.faran.majeed@gmail.com">m.faran.majeed@gmail.com</a>><br>
To: <a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a><br>
Subject: [Ndn-interest] Producer taking initiative to "Push" content<br>
to network.<br>
Message-ID:<br>
<CAFMc_X8ttDQ9zuByk7Cg=<a href="mailto:5WSvYBa8SOphT5NQmE2xrRCuZ639w@mail.gmail.com">5WSvYBa8SOphT5NQmE2xrRCuZ639w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi!<br>
<br>
So far, I have been viewing NDN architecture working as pull-based<br>
mechanism. Is there any possibility to incorporate "Push" mechanism in it?<br>
Because for some environments, (vehicular/MANET), pull-based mechanism may<br>
not work properly.<br>
<br>
Scenario: In a highly dynamic environment, the producer moving quickly<br>
among content routers, capturing and publishing video. So, producer can not<br>
wait for an interest and want to push the video content in-network before<br>
its local storage is full.<br>
<br>
<br>
Kind regards,<br>
<br>
Faran,<br>
AIT, Thailand<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20151205/ce47c02b/attachment-0001.html" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20151205/ce47c02b/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sat, 5 Dec 2015 16:12:42 +0900<br>
From: Syed Hassan Ahmed <<a href="mailto:s.h.ahmed@ieee.org">s.h.ahmed@ieee.org</a>><br>
To: Muhammad Faran <<a href="mailto:m.faran.majeed@gmail.com">m.faran.majeed@gmail.com</a>><br>
Cc: <a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a><br>
Subject: Re: [Ndn-interest] Producer taking initiative to "Push"<br>
content to network.<br>
Message-ID:<br>
<<a href="mailto:CAJeX4qfbnp2wgcAB5LWT5iOW4JdkwUc_QTyBdCC%2Bhp%2B%2B-qLCnA@mail.gmail.com">CAJeX4qfbnp2wgcAB5LWT5iOW4JdkwUc_QTyBdCC+hp++-qLCnA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Faran,<br>
<br>
Experts may response in this regards, however, here is my answer:<br>
<br>
In Vehicular NDN research, mostly authors assume that content routers are<br>
installed in each vehicle, especially, when we say that no infrastructure<br>
support is there such as RSU. So my point is that almost every node/vehicle<br>
is performing as a content router + provider + consumer role at different<br>
instances under the given circumstances.<br>
<br>
Now, if we talk about "Push" based communications, then we might have a<br>
look at Pub/Sub mechanisms. If the vehicles in any area are subscribed to<br>
the specific type of data, then they don't need to send interest(s) every<br>
time. On the other hands, the producers start "pushing" the data into the<br>
network. However, in naive NDN, this approach may have its own<br>
consequences. Because, when you push, then it will cost extra cost in terms<br>
of overhead and additional copies of the packets and there might be a case,<br>
that all the neighboring nodes do not want to have that video content so<br>
why they pay the cost of channel utilization for receiving the data, they<br>
don't want or have any interest.<br>
<br>
I am not sure, that did I give you the required answer.<br>
Good Luck~~<br>
<br>
Kind Regards,<br>
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~<br>
*Syed Hassan Ahmed*<br>
??? ?? ????<br>
<br>
PhD Research Scholar,<br>
MoNeT Wireless Lab, <<a href="http://monet.knu.ac.kr" rel="noreferrer" target="_blank">http://monet.knu.ac.kr</a>><br>
Kyungpook National University,<br>
Daegu City, Republic of Korea.<br>
Cell: +82-10-9883-0786<br>
<a href="https://sites.google.com/site/shahmedknu/" rel="noreferrer" target="_blank">https://sites.google.com/site/shahmedknu/</a><br>
<br>
On Sat, Dec 5, 2015 at 3:55 PM, Muhammad Faran <<a href="mailto:m.faran.majeed@gmail.com">m.faran.majeed@gmail.com</a>><br>
wrote:<br>
<br>
> Hi!<br>
><br>
> So far, I have been viewing NDN architecture working as pull-based<br>
> mechanism. Is there any possibility to incorporate "Push" mechanism in it?<br>
> Because for some environments, (vehicular/MANET), pull-based mechanism may<br>
> not work properly.<br>
><br>
> Scenario: In a highly dynamic environment, the producer moving quickly<br>
> among content routers, capturing and publishing video. So, producer can not<br>
> wait for an interest and want to push the video content in-network before<br>
> its local storage is full.<br>
><br>
><br>
> Kind regards,<br>
><br>
> Faran,<br>
> AIT, Thailand<br>
><br>
> _______________________________________________<br>
> Ndn-interest mailing list<br>
> <a href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a><br>
> <a 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>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20151205/d6f441c9/attachment-0001.html" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20151205/d6f441c9/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sat, 5 Dec 2015 15:12:08 +0700<br>
From: Muhammad Faran <<a href="mailto:m.faran.majeed@gmail.com">m.faran.majeed@gmail.com</a>><br>
To: Syed Hassan Ahmed <<a href="mailto:s.h.ahmed@ieee.org">s.h.ahmed@ieee.org</a>><br>
Cc: <a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a><br>
Subject: Re: [Ndn-interest] Producer taking initiative to "Push"<br>
content to network.<br>
Message-ID:<br>
<<a href="mailto:CAFMc_X95z3ruk2Nm95raq389xHxCs3bf-YkHQw%2BkUJhOgEoOAQ@mail.gmail.com">CAFMc_X95z3ruk2Nm95raq389xHxCs3bf-YkHQw+kUJhOgEoOAQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Hassan,<br>
<br>
Thank you for prompt response. Actually, I can define the scenario in<br>
following two points:<br>
<br>
1. As per application perspective, the producer needs to send content<br>
whether it is needed or not by consumers. Or there can be archiving of the<br>
content later after its production.<br>
2. Due to requirements of the application, the network has to adapt to<br>
push-based mechanism and might not be limited to only pull-based mechanism<br>
where an interest MUST be issued to retrieve content.<br>
<br>
What I've understood from your reply:<br>
<br>
1. In vehicular environment, every node is performing as all in all. So do<br>
every node does in normal environment to be content router, producer and<br>
consumer, nothing different. But even in vehicular applications such as<br>
monitoring, a producer that wants to use the network to just accommodate<br>
its content may need to just push content.<br>
2. According to my sense, channel utilization is the task of layers below<br>
the "strategy layer" of NDN. Even for channel utilization, if content<br>
routers are aware of the application needs then they have to accommodate<br>
the content.<br>
<br>
Kind regards,<br>
<br>
Faran<br>
AIT, Thailand<br>
<br>
On Sat, Dec 5, 2015 at 2:12 PM, Syed Hassan Ahmed <<a href="mailto:s.h.ahmed@ieee.org">s.h.ahmed@ieee.org</a>><br>
wrote:<br>
<br>
> Dear Faran,<br>
><br>
> Experts may response in this regards, however, here is my answer:<br>
><br>
> In Vehicular NDN research, mostly authors assume that content routers are<br>
> installed in each vehicle, especially, when we say that no infrastructure<br>
> support is there such as RSU. So my point is that almost every node/vehicle<br>
> is performing as a content router + provider + consumer role at different<br>
> instances under the given circumstances.<br>
><br>
> Now, if we talk about "Push" based communications, then we might have a<br>
> look at Pub/Sub mechanisms. If the vehicles in any area are subscribed to<br>
> the specific type of data, then they don't need to send interest(s) every<br>
> time. On the other hands, the producers start "pushing" the data into the<br>
> network. However, in naive NDN, this approach may have its own<br>
> consequences. Because, when you push, then it will cost extra cost in terms<br>
> of overhead and additional copies of the packets and there might be a case,<br>
> that all the neighboring nodes do not want to have that video content so<br>
> why they pay the cost of channel utilization for receiving the data, they<br>
> don't want or have any interest.<br>
><br>
> I am not sure, that did I give you the required answer.<br>
> Good Luck~~<br>
><br>
> Kind Regards,<br>
> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~<br>
> *Syed Hassan Ahmed*<br>
> ??? ?? ????<br>
><br>
> PhD Research Scholar,<br>
> MoNeT Wireless Lab, <<a href="http://monet.knu.ac.kr" rel="noreferrer" target="_blank">http://monet.knu.ac.kr</a>><br>
> Kyungpook National University,<br>
> Daegu City, Republic of Korea.<br>
> Cell: +82-10-9883-0786<br>
> <a href="https://sites.google.com/site/shahmedknu/" rel="noreferrer" target="_blank">https://sites.google.com/site/shahmedknu/</a><br>
><br>
> On Sat, Dec 5, 2015 at 3:55 PM, Muhammad Faran <<a href="mailto:m.faran.majeed@gmail.com">m.faran.majeed@gmail.com</a>><br>
> wrote:<br>
><br>
>> Hi!<br>
>><br>
>> So far, I have been viewing NDN architecture working as pull-based<br>
>> mechanism. Is there any possibility to incorporate "Push" mechanism in it?<br>
>> Because for some environments, (vehicular/MANET), pull-based mechanism may<br>
>> not work properly.<br>
>><br>
>> Scenario: In a highly dynamic environment, the producer moving quickly<br>
>> among content routers, capturing and publishing video. So, producer can not<br>
>> wait for an interest and want to push the video content in-network before<br>
>> its local storage is full.<br>
>><br>
>><br>
>> Kind regards,<br>
>><br>
>> Faran,<br>
>> AIT, Thailand<br>
>><br>
>> _______________________________________________<br>
>> Ndn-interest mailing list<br>
>> <a href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a><br>
>> <a 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>
>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20151205/6d89c50c/attachment-0001.html" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20151205/6d89c50c/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sat, 5 Dec 2015 16:22:11 +0800<br>
From: stewart mackenzie <<a href="mailto:setori88@gmail.com">setori88@gmail.com</a>><br>
To: <a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a><br>
Subject: Re: [Ndn-interest] Producer taking initiative to "Push"<br>
content to network.<br>
Message-ID:<br>
<CA+Lh=<a href="mailto:n2kFZYAzHEdOtSFTJbbK5TYcgwhkQgky54mkaTptAN3uA@mail.gmail.com">n2kFZYAzHEdOtSFTJbbK5TYcgwhkQgky54mkaTptAN3uA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Your "push" producer could issue an interest that contains a "request<br>
for interest", when the push target gets the interest in responds with<br>
an ack.<br>
Then the push target immediately issues an interest for the data as<br>
detailed in the "request for interest" interest.<br>
<br>
2cw<br>
<br>
/sjm<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Ndn-interest mailing list<br>
<a href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a><br>
<a 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>
<br>
------------------------------<br>
<br>
End of Ndn-interest Digest, Vol 21, Issue 2<br>
*******************************************<br>
</blockquote></div><br></div></div></div></div></div></div></div></div></div></div></div>