<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-IE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal style='margin-bottom:10.0pt;line-height:12.65pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi all,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:10.0pt;line-height:12.65pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I’m new to the mailing list so greetings! I recently posted on the ICNRG mailing list and Lixia Zhang kindly pointed me in this direction as a mailing list of interest.<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:10.0pt;line-height:12.65pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I’m attending the ACM ICN conference in 2 weeks so looking forward to meeting many of you there. I recently joined the academic staff in the Department to Computer Science in University College Cork (Ireland) and am interested in investigating ICN, particularly its application within the IoT and edge networks. My background is in network communication protocols, specifically geo-routing and location service protocol design for ad-hoc networks.<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:10.0pt;line-height:12.65pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>This is an area that is new to me but one that I’m interested in exploring. If I anyone has any suggestions/opportunities for the best way to connect in with existing work in this space or is searching for an able and interested person to further explore some of the existing research challenges please let me know.<o:p></o:p></span></p><p class=MsoPlainText>A high level question for you that I would really be interested in hearing your views on:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There seems to be a school of thought that adoption of ICN (whatever the architecture) may never come about because of the amount of effort and money already invested in TCP/IP. A more optimistic view is that the deployment will most likely being a hybrid ICN over IP with a slow phase out over 20-30 years. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Extending this to the IoT, I would foresee that a hybrid stack isn’t feasible as the goal is to lighten the stack not increase its complexity which may not be feasible for resource constrained devices. So does sufficient quantitative evidence exist to provide a very strong and compelling motivation for why IoT should transition from the CoAP/UDP/RPL/IPv6/6LoWPAN/802.15.4 stack to an ICN approach in terms of network performance benefits OR is the argument that IoT is still relatively in its infancy and thus a clean slate approach is still feasible given that ICN is naturally a better fit without providing a strong migration argument? I do note that some quantitative evaluation was conducted in a sub-section in a paper “ICN in the IoT: Experiments with NDN in the Wild” (really interesting paper).<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText> It seems like there is significant further work to be done to provide quantitative motivation. Is this a fair observation? I’d be interested to hear your opinions.<o:p></o:p></p><p class=MsoNormal style='margin-bottom:10.0pt;line-height:12.65pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:10.0pt;line-height:12.65pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Best regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:10.0pt;line-height:12.65pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Aisling O’ Driscoll.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div></body></html>