<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [Ndn-interest] NDN-friendly Mobility solutions</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Good point! I agree that NDN supports subscriber mobility in it's nature and as you said most of mobility issues in subscriber-side scenarios disappear automatically. But what about some producer ones? As an example, the application scenario we are talking about could be voice/video chat when both caller and callee are mobile. How could we consider it in a non-P2P model?<BR>
<BR>
Could you please guide me to find about possibility for intelligent broadcast/multicast using self-learning path selection ?<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Wentao Shang [<A HREF="mailto:wentaoshang@gmail.com">mailto:wentaoshang@gmail.com</A>]<BR>
Sent: Sun 2/15/2015 3:47 AM<BR>
To: Muhammad Hosain Abdollahi Sabet; Lixia Zhang; ndn-interest@lists.cs.ucla.edu<BR>
Subject: Re: [Ndn-interest] NDN-friendly Mobility solutions<BR>
<BR>
On Sat Feb 14 2015 at 9:26:50 AM Muhammad Hosain Abdollahi Sabet <<BR>
M.AbdollahiSabet@mail.sbu.ac.ir> wrote:<BR>
<BR>
> Thank you so much for answering.<BR>
> Actually it struck my mind that "it" is unclear, which I'm sorry for the<BR>
> ambiguity. The second one was the closest one. I meant: "Is the solution<BR>
> for producer-side mobility clear enough that there hasn't been real attempt<BR>
> about it?<BR>
> I'll be absolutely glad to help. ?As far as I understand we have another<BR>
> paradigm shifting again in some mobility application scenarios like mobile<BR>
> caller-callee. NDN shifts networking from host-centric(point to point) to a<BR>
> content-centric architecture. And now we want to make point to point<BR>
> connection overlay of NDN. Right?<BR>
><BR>
Not sure why you want to make point-to-point connection over NDN. Is it a<BR>
requirement from specific application in your mind? NDN shifts away from<BR>
the P2P connection model and therefore provides new opportunity for better<BR>
mobility support. Perhaps it is more efficient to design your application<BR>
in the NDN model (in which case some mobility issue may disappear<BR>
automatically) than to fit the old model into the new architecture.<BR>
<BR>
<BR>
> So I think using some IP-like producer mobility solutions is not<BR>
> avoidable. On the other hand some of NDN features like being broadcast<BR>
> finendly which is referred to in "A New Perspective in Mobility Support''<BR>
> as a suggestion, isn't practical in large scale because of producing heavy<BR>
> overhead of controlling data(specially in hard-state mode).<BR>
><BR>
Broadcast is impractical for large scale IP network. But NDN has a smarter<BR>
forwarding plain which opens possibility for intelligent<BR>
broadcast/multicast using self-learning path selection and traffic<BR>
reduction.<BR>
<BR>
Different mobility solutions are designed for different application<BR>
scenarios. In some extreme cases where the network is so dynamic that it is<BR>
impossible to maintain a stable topology, broadcast/multicast may be the<BR>
only choice.<BR>
<BR>
<BR>
> Furthermore, hierarchical naming brings some location dependency,<BR>
><BR>
It is not that hierarchical naming brings location dependency. Any<BR>
identifier that is used in routing and forwarding will cause location<BR>
dependency. That's why people invented the concept of Locator/ID<BR>
separation, which is mentioned in the mobility TR. The "forwarding hint" is<BR>
one way to implement that in NDN.<BR>
<BR>
Wentao<BR>
<BR>
<BR>
> and maybe we need some conventions in this field, in which network can<BR>
> approximate location of endpoint while pinpointing location of endpoint can<BR>
> be postponed to last steps.<BR>
> I just listed some of the challenges I faced till now. I'll be grateful to<BR>
> know your opinion about them.<BR>
><BR>
> Thanks again,<BR>
> Sabet<BR>
><BR>
><BR>
><BR>
><BR>
> -----Original Message-----<BR>
> From: Lixia Zhang [<A HREF="mailto:lixia@cs.ucla.edu">mailto:lixia@cs.ucla.edu</A> <lixia@cs.ucla.edu>]<BR>
> Sent: Fri 2/13/2015 8:26 PM<BR>
> To: Muhammad Hosain Abdollahi Sabet<BR>
> Cc: ndn-interest@lists.cs.ucla.edu<BR>
> Subject: Re: [Ndn-interest] NDN-friendly Mobility solutions<BR>
><BR>
><BR>
> > On Feb 12, 2015, at 2:16 PM, Muhammad Hosain Abdollahi Sabet <<BR>
> M.AbdollahiSabet@mail.sbu.ac.ir> wrote:<BR>
> ><BR>
> > Hello everyone.<BR>
> > I've been studying NDN for a couple of months now. For supporting<BR>
> mobility in environments without any clear infrastructure and topology like<BR>
> MANET (VANET in particular), it's been developing like a charm. But as far<BR>
> as I've learned, it's producer-side mobility support in large scales still<BR>
> has some serious challenges, particularly in scenarios like mobile<BR>
> caller-callee. And as "A New Perspective on Mobility Support" has reported,<BR>
> none of the proposed solutions(Proxy based, Rendezvous point based, ...)<BR>
> seems to have a NDN-likely technique. I'm eager to work on it as my B.S<BR>
> thesis. But the problem is, when I look at the ICN workshops, conferences,<BR>
> articles, posters, demos and etc, I cannot find real attempts on<BR>
> this(unless Kite I may say). Not that I've seen for example about Routing<BR>
> or Security. And now I'm wondering: Is it really that clear?! Maybe you can<BR>
> guide me to a vision I don't have.<BR>
> ><BR>
> > Thanks,<BR>
> > Sabet<BR>
><BR>
> Sabet,<BR>
><BR>
> thanks for your msg. I wonder what you meant by "Is it really that<BR>
> clear?!".<BR>
> If you are asking whether it is clear that NDN can offer superior mobility<BR>
> support than TCP/IP, then you know the answer is YES, right?<BR>
> If you are asking whether mobile producer solutions have been fully<BR>
> developed: it is still being developed, hence the need for your effort on<BR>
> this problem. We *are* developing solutions, first for specific<BR>
> application scenarios, which help us understand how to provide general<BR>
> solutions.<BR>
> If you are asking for examples of routing solutions: I'm sure you've seen<BR>
> NLSR work as an example; we are also actively working on hyperbolic routing<BR>
> as potential long term directly.<BR>
> For security, you may look into recent NDN retreat which focused on<BR>
> security solution development.<BR>
><BR>
> Lixia<BR>
><BR>
><BR>
><BR>
> _______________________________________________<BR>
> Ndn-interest mailing list<BR>
> Ndn-interest@lists.cs.ucla.edu<BR>
> <A HREF="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</A><BR>
><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>