[Ndn-interest] Producer taking initiative to "Push" content to network
Muhammad Faran
m.faran.majeed at gmail.com
Sat Dec 5 00:44:51 PST 2015
Dear Stewart,
Thank you for your reply. From your reply I understood the following:
1. There is no intrinsic push-based mechanism support in NDN architecture.
2. If a producer wants to take initiative for pushing content before it is
requested, it will have to use "request for interest" interest.
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?
Kind regards,
Faran
AIT, Thailand
On Sat, Dec 5, 2015 at 3:22 PM, <ndn-interest-request at lists.cs.ucla.edu>
wrote:
> Send Ndn-interest mailing list submissions to
> ndn-interest at lists.cs.ucla.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
> or, via email, send a message with subject or body 'help' to
> ndn-interest-request at lists.cs.ucla.edu
>
> You can reach the person managing the list at
> ndn-interest-owner at lists.cs.ucla.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ndn-interest digest..."
>
>
> Today's Topics:
>
> 1. go-ndn 1.2 (Tai-Lin Chu)
> 2. Producer taking initiative to "Push" content to network.
> (Muhammad Faran)
> 3. Re: Producer taking initiative to "Push" content to network.
> (Syed Hassan Ahmed)
> 4. Re: Producer taking initiative to "Push" content to network.
> (Muhammad Faran)
> 5. Re: Producer taking initiative to "Push" content to network.
> (stewart mackenzie)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 4 Dec 2015 11:50:07 -0800
> From: Tai-Lin Chu <tailinchu at gmail.com>
> To: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>
> Subject: [Ndn-interest] go-ndn 1.2
> Message-ID:
> <CABf5LwDg_vLh6Gh6=
> 0-OPT4E5PdkoaTBsaxdxwVos9zHo3v7ng at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> This release is not possible without some individual contributors.
>
> Major Feature:
>
> - experimental "send/push" semantics: A data sender sends interests
> with name "<nodeName>/ACK/<dataName>" to ensure that a specific node
> receives a specific data packet. This is implemented with
> `mux.Notifier` and `mux.Listener`. Feel free to share how you achieve
> send or push in NDN.
>
> - go-ndn/health: instrument your ndn application easily. It stores
> per-minute stats like interest request count and response time on
> disk, and presents on a nice web interface. All web interface assets
> are directly compiled into application and are available offline. (See
> https://github.com/go-ndn/health)
>
> Tutorial:
>
> - Generate Data Before Interest: Discuss two common design patterns to
> publish data "before" interests, and show how "self-generated/fake
> interests" can achieve this.
>
> https://github.com/go-ndn/example/blob/master/before-interest.md
>
>
> Contributer:
> - Oli Gavin
> - qhsong
> - Mahyuddin Husairi
>
> More details: https://github.com/go-ndn/example#news
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 5 Dec 2015 13:55:40 +0700
> From: Muhammad Faran <m.faran.majeed at gmail.com>
> To: ndn-interest at lists.cs.ucla.edu
> Subject: [Ndn-interest] Producer taking initiative to "Push" content
> to network.
> Message-ID:
> <CAFMc_X8ttDQ9zuByk7Cg=
> 5WSvYBa8SOphT5NQmE2xrRCuZ639w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20151205/ce47c02b/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Sat, 5 Dec 2015 16:12:42 +0900
> From: Syed Hassan Ahmed <s.h.ahmed at ieee.org>
> To: Muhammad Faran <m.faran.majeed at gmail.com>
> Cc: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] Producer taking initiative to "Push"
> content to network.
> Message-ID:
> <
> CAJeX4qfbnp2wgcAB5LWT5iOW4JdkwUc_QTyBdCC+hp++-qLCnA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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>
> 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
> > 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/d6f441c9/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Sat, 5 Dec 2015 15:12:08 +0700
> From: Muhammad Faran <m.faran.majeed at gmail.com>
> To: Syed Hassan Ahmed <s.h.ahmed at ieee.org>
> Cc: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] Producer taking initiative to "Push"
> content to network.
> Message-ID:
> <
> CAFMc_X95z3ruk2Nm95raq389xHxCs3bf-YkHQw+kUJhOgEoOAQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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>
> 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
> >
> > 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
> >> 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/6d89c50c/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 5
> Date: Sat, 5 Dec 2015 16:22:11 +0800
> From: stewart mackenzie <setori88 at gmail.com>
> To: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] Producer taking initiative to "Push"
> content to network.
> Message-ID:
> <CA+Lh=
> n2kFZYAzHEdOtSFTJbbK5TYcgwhkQgky54mkaTptAN3uA at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Your "push" producer could issue an interest that contains a "request
> for interest", when the push target gets the interest in responds with
> an ack.
> Then the push target immediately issues an interest for the data as
> detailed in the "request for interest" interest.
>
> 2cw
>
> /sjm
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
>
> ------------------------------
>
> End of Ndn-interest Digest, Vol 21, Issue 2
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20151205/2c62f29b/attachment.html>
More information about the Ndn-interest
mailing list