[Ndn-interest] NDN-friendly Mobility solutions
wentaoshang at gmail.com
Thu Feb 19 13:08:09 PST 2015
Yes, I think the "CDN-style" model could be a starting point for solving a
class of mobility problems. A few things that are still unclear to me
1/ Can we use this rendezvous model for real-time communications like
video/audio conferencing? Not sure how the indirection will affect the
2/ If we plan to use Interest-Interest communication, how do we handle the
case when the producer doesn't have a routable prefix (or doesn't know he
has)? The Kite approach (i.e., using PIT to do reverse path forwarding) is
a significant change to the architecture and I still don't understand the
implication of this change yet.
On Thu Feb 19 2015 at 7:16:07 AM Mark Stapp <mjs at cisco.com> wrote:
> Hi Wentao,
> On 2/15/15 2:18 PM, Wentao Shang wrote:
> > While any solution must be based on the specific application scenario,
> > there are still some general guidelines that you may consider:
> > 3/ A more NDN-ish design (in my opinion) is to use rendezvous point as
> > indirection: you can have your producer publish its data to a well-known
> > location, such as an NDN repo, so that the consumer can fetch data from
> > the repo instead of talking to the producer directly.
> hmm - that sure sounds like a CDN design, the kind that we use all the
> time - facebook, flickr, gmail. is that the kind of thing you had in
> mind? if so, as you know I agree, and I think there should be more focus
> on mechanisms that support this design.
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest