[Nfd-dev] Interest scoping and broadcast channels

[Junxiao Shi]

Hi Jeff

There's a proposal about supporting parasitic Interests directly using
LocalControlHeader.
http://redmine.named-data.net/issues/2007
Please provide your comments on this idea.

Yours, Junxiao

On Tue, May 27, 2014 at 2:07 AM, Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Jeff
>
> Parasitic Interest is possible in NFD 0.1.0.
>
> To issue such an Interest:
>
>    1. set client-control strategy on the namespace
>    2. send the Interest, and specify application's own face as next-hop,
>    so that this Interest won't be propagated
>    3. to send a regular Interest to be propagated, specify the wireless
>    multicast face
>
>
> Yours, Junxiao
>
> On Mon, May 19, 2014 at 3:55 AM, Burke, Jeff <jburke at remap.ucla.edu>
> wrote:
>
>>  If this host needs to know the content from other host, use NFD's
>> packet capture feature. The packet capture feature allows a program to
>> listen for a subset of packets processed by NFD, with filters on face,
>> direction, and name prefix. There is no Task for this feature yet.
>> [jb] Ok, we'll keep an eye out for this.  While I figured that something
>> like this was possible, I had previously come to the conclusion that it was
>> better to preserve NDN semantics – if it is Data that an application is
>> interested in, wouldn't it be most NDN-like if it issued an Interest for
>> it?     This sort of "parasitic Interest", which "listens" on a Face for
>> data but doesn't propagate, seems useful in a variety of contexts having to
>> do with low-bandwidth broadcast channels or power-constrained consumers.
>>  The advantage is that the callback mechanism is exactly the same as what
>> app developers would be used to, without having to descend into a different
>> (packet capture) API.
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141007/57795862/attachment.html>