<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Junxiao,<div class=""><br class=""></div><div class="">Thank you, wow this looks neat. I haven’t followed ICN/NDN for several years and didn’t know so many improvements have been made.</div><div class="">Thank you for the info and previous discussions.</div><div class=""><br class=""></div><div class="">BR</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 30 Jun 2020, at 14.40, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" class="">shijunxiao@email.arizona.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div dir="auto" class="">Hi Pengyuan</div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">What you are looking for is Named Function Networking. <div class=""><a href="http://conferences2.sigcomm.org/acm-icn/2017/files/tutorial-ndn-ccnlite-riot/9-NFN.pdf" class="">http://conferences2.sigcomm.org/acm-icn/2017/files/tutorial-ndn-ccnlite-riot/9-NFN.pdf</a></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">You still don’t need to embed data into Interests.</div><div dir="auto" class="">Instead, both the command (lambda function) and input data are published as Data packets.</div><div dir="auto" class="">To execute a function, you send an Interest that names the result, whose parameters carry the <b class="">names</b> of command and input data.</div><div dir="auto" class="">The network will find a middle box execute the command, which includes retrieving the input data by name.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Yours, Junxiao</div></div><div class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 29, 2020 at 12:22 Pengyuan Zhou via Ndn-interest <<a href="mailto:ndn-interest@lists.cs.ucla.edu" class="">ndn-interest@lists.cs.ucla.edu</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p style="text-align:center" class=""><font color="red" class=""><strong class="">External Email</strong><br class=""></font></p><div dir="ltr" class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:georgia,serif">Hi, Prof. Lixia,</div><div class="gmail_default" style="font-family:georgia,serif"><br class=""></div><div class="gmail_default" style="font-family:georgia,serif">Ya I agree that idea opposites the inherent nature of Interest Packet.</div><div class="gmail_default" style="font-family:georgia,serif">Still, can't help thinking if it can provide some interesting extended feature for ICN in general.</div><div class="gmail_default" style="font-family:georgia,serif">Imagine if Interest Packet can carry user-defined command data and pull data that needs processing to a middlebox, <br class="">and process the data right there with the command data. <br class="">It can end up with providing a openflow-ish in-network processing feature based on content names.</div><div class="gmail_default" style="font-family:georgia,serif"><br class=""></div><div class="gmail_default" style="font-family:georgia,serif">Just brainstorming.</div><div class="gmail_default" style="font-family:georgia,serif">BR</div></div></div><br class="">
</blockquote></div></div>
</div></blockquote></div><br class=""></div></body></html>