<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 2, 2019, at 11:52 AM, Zhiyi Zhang <<a href="mailto:zhiyi@cs.ucla.edu" class="">zhiyi@cs.ucla.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I would agree with Junxiao.<div class="">NDN-LITE's fragmentation protocol follows the design in NDN-RIOT made by Wentao.</div><div class="">The ideal solution is to make NDN-LITE compatible with NDNLPv2.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Zhiyi</div></div></div></blockquote><div><br class=""></div>1/ I didn't realize that NDNLP has this hard-coded seq# field -- this is really not IoT friendly. Why not TLV?</div><div><br class=""></div><div>2/ NDN-Lite subsumed NDN-RIOT, I'd suggest whoever played with NDN-RIOT consider moving to NDN-Lite.</div><div><br class=""></div><div><div>3/ I think it is important to make NDNLP and NDN-Lite compatible. </div><div>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#)</div></div><div><br class=""></div><div>my 2 cents,</div><div>Lixia</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 2, 2019 at 7:50 AM Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" class="">shijunxiao@email.arizona.edu</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><div dir="ltr" class="">Hi Aboodi<div class=""><br class=""></div><div class="">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.</div><div class="">The solution would be implementing NDNLPv2 fragmentation in ndn-lite.</div><div class=""><br class=""></div><div class="">Yours, Junxiao</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 2, 2019 at 9:29 AM Aboodi Ahed Hussein Ali <<a href="mailto:aboodi@student.usm.my" target="_blank" class="">aboodi@student.usm.my</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
Hi everyone,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
Does NDNLPv2 of NDN support the L2 fragmentation of NDN-RIOT? if yes, How to enable it? </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<br class="">
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
if no, any suggestion on how I can make native NDN and NDN-RIOT communicate knowing that both fragmentation headers are different?</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">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 <span style="font-family:Calibri,Arial,Helvetica,sans-serif;background-color:rgb(255,255,255);display:inline" class="">NDNLPv2 is larger (8-bytes) than the on in NDN-RIOT
(5-bits). </span></span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class=""><span style="font-family:Calibri,Arial,Helvetica,sans-serif;background-color:rgb(255,255,255);display:inline" class=""><span style="font-family:Calibri,Arial,Helvetica,sans-serif;background-color:rgb(255,255,255);display:inline" class=""><br class="">
</span></span></span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class=""><span style="font-family:Calibri,Arial,Helvetica,sans-serif;background-color:rgb(255,255,255);display:inline" class=""><span style="font-family:Calibri,Arial,Helvetica,sans-serif;background-color:rgb(255,255,255);display:inline" class="">I
would really appreciate any suggestions.</span></span></span><br class="">
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class=""><br class="">
</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">
<span style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">Ahed,</span></div>
</div><br class="">
</blockquote></div></div>
_______________________________________________<br class="">
Nfd-dev mailing list<br class="">
<a href="mailto:Nfd-dev@lists.cs.ucla.edu" target="_blank" class="">Nfd-dev@lists.cs.ucla.edu</a><br class="">
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev" rel="noreferrer" target="_blank" class="">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a><br class="">
</blockquote></div>
_______________________________________________<br class="">Nfd-dev mailing list<br class=""><a href="mailto:Nfd-dev@lists.cs.ucla.edu" class="">Nfd-dev@lists.cs.ucla.edu</a><br class="">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br class=""></div></blockquote></div><br class=""></body></html>