[Nfd-dev] NDNLPv2 and NDN-RIOT L2 fragmentation

Zhiyi Zhang zhiyi at cs.ucla.edu
Mon Dec 2 11:52:22 PST 2019


I would agree with Junxiao.
NDN-LITE's fragmentation protocol follows the design in NDN-RIOT made by
Wentao.
The ideal solution is to make NDN-LITE compatible with NDNLPv2.

Best,
Zhiyi

On Mon, Dec 2, 2019 at 7:50 AM Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Aboodi
>
> No, ndn-lite fragmentation differs from NDNLPv2 fragmentation. There are
> major design problem in ndn-lite fragmentation protocol: it has overly
> strict limit on frame size. Thus, I don't recommend using that protocol.
> The solution would be implementing NDNLPv2 fragmentation in ndn-lite.
>
> Yours, Junxiao
>
> On Mon, Dec 2, 2019 at 9:29 AM Aboodi Ahed Hussein Ali <
> aboodi at student.usm.my> wrote:
>
>> Hi everyone,
>>
>> Does NDNLPv2 of NDN support the L2 fragmentation of NDN-RIOT?  if yes,
>> How to enable it?
>>
>> if no, any suggestion on how I can make native NDN and NDN-RIOT
>> communicate knowing that both fragmentation headers are different?
>> In fact, I was thinking about the possibility of translating, copying or
>> matching the values of the fields for both fragmentation headers. However,
>> the fragmentation header in NDN-RIOT has no Fragmentation Count. Besides,
>> the Sequence field in NDNLPv2 is larger (8-bytes) than the on in
>> NDN-RIOT (5-bits).
>>
>> I would really appreciate any suggestions.
>>
>> Ahed,
>>
>> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20191202/0913f10e/attachment-0001.html>


More information about the Nfd-dev mailing list