<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="">We seem though to be drifting back into HomeNet territory.<div class=""><br class=""></div><div class=""><a href="https://www.youtube.com/watch?v=SkQN7QGZMps" class="">https://www.youtube.com/watch?v=SkQN7QGZMps</a></div><div class=""><br class=""></div><div class=""><a href="https://datatracker.ietf.org/wg/homenet/about/" class="">https://datatracker.ietf.org/wg/homenet/about/</a><br class=""><div class=""><br class=""></div><div class="">Which I feel is a good thing in this context.</div><div class=""><br class=""></div><div class="">I still like this particular video:</div><div class=""><br class=""></div><div class="">https://www.youtube.com/watch?v=wQdfWUsG4uI</div><div class=""><br class=""></div><div class="">So naming and addressing, routing and service discovery? What is not to like?</div><div class=""><br class=""></div><div class="">Gordon</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 8 Aug 2017, at 22:29, Richard Lamb <richard.lamb@icann.org> wrote:</div><br class="Apple-interchange-newline"><div class="">

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)" class="">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style class=""><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:0in;
        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;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
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]-->

<div lang="EN-US" link="blue" vlink="purple" class="">
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D" class="">Thank you for that. I will read more thoroughly.  But iIMHO the excerpt sounds a bit one-sided towards telco/itu/nb-iot/lte-m ‘ish as you elude to with your sim
 card reference. I guess I do a bit of delineation between wide-area RF (telco/sigfox) and near range (wifi,bt,..).  Above that phys layer there seems to be some common use of traditional internet stuff (ip, dns, tls, mqtt) but past that i still see a morass
 of custom protocols for the “controllers” that each use their own device identity formats.  From what I hear from trade shows like CES, I think that will not change, i.e., there will remain a common way to communicate but competing APPs each with their own
 identifiers (and encryption approaches).  From my admittedly simple research (I continue to buy various iot devices and then do packet traces. Picture of what I see below) I have not seen a scalability issue for the typical wifi, ble via gateway connected
 devices to the cloud based (many in AWS) broker+controllers.  –Rick<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D" class=""><o:p class=""> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D" class=""><span id="cid:image002.jpg@01D3104A.53960000"><image002.jpg></span><o:p class=""></o:p></span></p><p class="MsoNormal"><br class=""></p>
</div></div></div></blockquote></div><br class=""></div></div></body></html>