[Ndn-interest] NDN Load Balancing and Alternative Path

[Junxiao Shi]

Hi Boubakr

Yes, load balancing and usage of alternate paths apply to Interest
forwarding only, while Data simply follows the reverse of an Interest.
There is no "consumer address" in the Data, so that there is no way to send
the Data on another path.
The consumer is ultimately responsible for retrieving the Data it wants. If
there is a link failure, the downstream (consumer or otherwise) can
retransmit the Interest, in order to reach a node that has the Data (either
producer or cache). It is also downstream's responsibility to load balance
its Interests among multiple paths, in reaction to congestion marks.
You may have seen schemes that add a return address to Data packets. Such
schemes would not work with Interest aggregation: if the Data is routed via
an alternate path according to the return address, other consumers whose
Interests have been aggregated could not receive the Data because the Data
no longer passes through the node that performed the aggregation.

Yours, Junxiao

On Mon, Apr 24, 2017 at 19:49 <n.boubakr at bit.edu.cn> wrote:

> Hello,
>
>
>
> Starting from the point that the Data packet is routed back to consumer
> using the reverse path of Interest. How can we achieve a load balancing in
> Data delivery, and how can we migrate from a link to another link in case
> of link failure.
>
> Another question, most of efforts in NDN congestion control propose using
> alternative path, how can we use an alternative path and NDN forwarding
> engine uses the PIT table to deliver data.
>
> The idea of alternative path and load balancing is valid only in Interest
> path and can not be realized in Data path.
>
>
>
> Boubakr Nour (Ph.D Candidate)
> Beijing Institute of Technology (北京理工大学)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170425/6850aa52/attachment.html>