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

[Lixia Zhang]

> On Dec 2, 2019, at 11:52 AM, Zhiyi Zhang <zhiyi at cs.ucla.edu> wrote:
> 
> 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

1/ I didn't realize that NDNLP has this hard-coded seq# field -- this is really not IoT friendly.  Why not TLV?

2/ NDN-Lite subsumed NDN-RIOT, I'd suggest whoever played with NDN-RIOT consider moving to NDN-Lite.

3/ I think it is important to make NDNLP and NDN-Lite compatible. 
I'll discuss this with the NDN-Lite group to see how to get this done quick (but LP needs to be made IoT friendly, e.g. Lite cannot afford 8-byte seq#)

my 2 cents,
Lixia

> On Mon, Dec 2, 2019 at 7:50 AM Junxiao Shi <shijunxiao at email.arizona.edu <mailto: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 <mailto: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 <mailto:Nfd-dev at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev <http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev>
> _______________________________________________
> 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/20191203/b3bca8e9/attachment.html>