[Ndn-interest] Usefulness of routing protocol?

[Dennis Olvany]

Paper located--will give it a read. Thx!
On Sun, Jan 17, 2016 at 10:45 PM Muhammad Hosain Abdollahi Sabet <
M.AbdollahiSabet at mail.sbu.ac.ir> wrote:

> Hi Dennis,
>
> If that is the case, you can take a look at forwarding strategies(Adaptive
> Forwarding paper which you can find it on named-data.net) and also Link
> State Routing Protocol(NLSR).
>
>
> What you're saying is not exactly the way ndn network works. Initial
> flooding could be a solution in LANs, maybe. But in large scales, no.
>
> Thanks,
> Sabet
>
>
> -----Original Message-----
> From: Ndn-interest on behalf of Dennis Olvany
> Sent: Mon 1/18/2016 6:52 AM
> To: Syed Hassan Ahmed; Lixia Zhang
> Cc: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] Usefulness of routing protocol?
>
> Lixia,
>
> The NDN papers that I have read thus far seem to suggest that a router
> receives an interest on a given face and then forwards the interest out of
> its other faces. My impression is that this occurs at each router in the
> network until the interest reaches the origin. As the data returns to the
> client, all routers will learn the path based on the data incoming face.
> Routers could then cease flooding once there is a known path. Clearly, my
> understanding may be incorrect as I have only been researching NDN for a
> week.
>
> -Dennis
> On Sun, Jan 17, 2016 at 9:23 PM Syed Hassan Ahmed <s.h.ahmed at ieee.org>
> wrote:
>
> > Dear Dennis,
> > cc: Prof. Lixia Zhang and Dr. Alexander
> >
> > Somehow your question is valid, since we use Broadcasting interface in
> > case of wireless, so eventually the Interest is flooded. For example,
> Every
> > neighboring node  of consumer C1, overhears the Interest packet, and then
> > has to perform all those basic operations, including PIT, CS, FIB search.
> > Moreover, if there is a case when those neighbors of C1 are not in intra
> > transmission range, may involve in interest forwarding as well. That
> > creates kind of broadcast storm, given that if there is only one provider
> > initially in the network. I have explored this problem in case of
> vehicular
> > environments, when we tried to simulate CCN on top of 802.11p. For
> > reference, please read my following paper:
> >
> > http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7145392
> >
> > P.S: If you find my paper useful, don't hesitate to cite it :)
> >
> > 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 Mon, Jan 18, 2016 at 4:50 AM, Lixia Zhang <lixia at cs.ucla.edu> wrote:
> >
> >>
> >> > On Jan 17, 2016, at 10:48 AM, Dennis Olvany <dennisolvany at gmail.com>
> >> wrote:
> >> >
> >> > The flooding behavior of NDN is already akin to a routing protocol.
> >> Clearly, there may be a benefit of knowing data reachability before
> >> interest is expressed, but it is also not useful to know data
> reachability
> >> if interest is never expressed. Is there a good use case for routing
> >> protocol integration with NDN?
> >>
> >> interesting questions.
> >>
> >> let me ask a clarification question first: wonder exactly what you meant
> >> by "The flooding behavior of NDN"?
> >>
> >> Since NDN interest looks for data and not aims at any specific node, NDN
> >> takes advantages of any communication media that is broadcast in nature
> >> (e.g. WiFi) in that whoever hears the questions may answer.  But I dont
> >> think NDN interests in general get flooded in wide areas.
> >>
> >> Wonder exactly what you meant by "routing protocol integration with
> >> NDN"?  The NDN testbed is running a routing protocol.
> >>
> >> Lixia
> >>
> > _______________________________________________
> >> 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/20160118/b683f32a/attachment.html>