<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello Hirayama --<div class=""><br class=""></div><div class="">I think that trying to modify the NDN protocol to make it fit your desire to have multiple responses to a single interest is not going to get you to a well-designed system.</div><div class=""><br class=""></div><div class="">Knowing that NDN operates in flow balance, it's probably time to rethink your higher level protocol. If your current design for collecting votes/questions relyies on sending a "what is your vote on xxx" interest, and collecting the responses then you've got both a mismatch with the NDN flow balance property, and a distribution scaling problem. That design would require the underlying system to distribute the Interest packet to *every possible* system(person) that might be providing a vote/questionaire answer -- flooding it to the world and then collecting up the multiple different responses to that interest.</div><div class=""><br class=""></div><div class="">A more scalable way to structure the interaction would be to turn that "inside-out" -- for the individual voter to express a single interest in voting/answering the poll (higher level design could do discovery for what polls are available, but that's a different topic) and in response obtain a token for voting. Part of the voter's original interest (tail of the name) could be a name which would allow the voting system to then express an interest in the voter's response, which would be sent back as content, including the token they obtained from the voting system.</div><div class=""><br class=""></div><div class="">With this structure there is flow balance, the names in the interests can always be structured to aid routing, and there is no reliance on a single interest packet reaching every station in the universe.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">Nick Briggs</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 24, 2021, at 7:40 PM, .平山 智己 via Ndn-interest <<a href="mailto:ndn-interest@lists.cs.ucla.edu" class="">ndn-interest@lists.cs.ucla.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">Thank you, Lixia and Junxiao.<br class="">Sorry for the late reply because of other courses.<br class=""><br class="">What I’m trying to do is like a questionnaire/voting system using NDN<br class="">So I want to receive multiple data packets for Interest with one name.<br class="">I will try my best to continue to use NDN and enable it to send an Interest and receive multiple feedbacks.<br class=""><br class="">Thank you very much.<br class=""><br class="">Hirayama.<br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2021年11月15日(月) 19:41 Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" class="">shijunxiao@email.arizona.edu</a>>:<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 class=""><div dir="auto" class="">Hi Hirayama</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">One of the NDN protocol design principles is <b class="">hop-by-hop flow balance</b>: over each link, one Interest packet should bring back no more than one Data packet.</div><div dir="auto" class=""><div class=""><a href="https://named-data.net/project/ndn-design-principles/" target="_blank" class="">https://named-data.net/project/ndn-design-principles/</a></div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Regardless of which library you are using, it isn't possible to receive multiple Data packets in response to one Interest.</div><div dir="auto" class="">Instead, you should send multiple Interests with different names.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Yours, Junxiao</div></div><div class=""><div dir="auto" class=""><br class=""><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Mon, Nov 15, 2021 at 05:30 .平山 智己 via Ndn-interest <<a href="mailto:ndn-interest@lists.cs.ucla.edu" target="_blank" class="">ndn-interest@lists.cs.ucla.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"><p style="text-align:center" class=""><font style="color:rgb(255,0,0)" class=""><strong class="">External Email</strong><br class=""></font></p><div dir="ltr" class=""><div class="">Hi Lan.</div><div class=""><br class=""></div><div class="">Thank you for the last time.</div>Sending Interest using multicast worked fine. However, after the first response is replied, no other response can be received.<br class="">The library uses ndn-python, and as far as "ndn / transport / stream_soket.py" is seen, it is estimated that NFD closes PIT when the first response is received. Is it possible to receive multiple responses using ndn-python?<br class=""></div><div class="gmail_quote"><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 class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto" class=""><br class=""></div></blockquote></div></div></blockquote></div>
</blockquote></div></div>
</div>
</blockquote></div></div>
_______________________________________________<br class="">Ndn-interest mailing list<br class=""><a href="mailto:Ndn-interest@lists.cs.ucla.edu" class="">Ndn-interest@lists.cs.ucla.edu</a><br class="">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest<br class=""></div></blockquote></div><br class=""></div></body></html>