[iot-discussion] Proposed US legislation

Thanks for these.  I know there are many cool IETF efforts in the IoT space and I try to track them technically and commercially though not always successfully.  But I always start with what’s already out there and popular to try to figure out where to focus my energy.  So many times I feel stuck in various echo chambers…so I just look at packets ;-)


From: Gordon Lennox [mailto:gordon.lennox.13 at gmail.com]
Sent: Wednesday, August 9, 2017 1:40 PM
To: Richard Lamb <richard.lamb at icann.org>
Cc: iot-discussion at ripe.net
Subject: Re: [iot-discussion] Proposed US legislation

We seem though to be drifting back into HomeNet territory.

https://www.youtube.com/watch?v=SkQN7QGZMps

https://datatracker.ietf.org/wg/homenet/about/

Which I feel is a good thing in this context.

I still like this particular video:

https://www.youtube.com/watch?v=wQdfWUsG4uI

So naming and addressing, routing and service discovery? What is not to like?

Gordon


On 8 Aug 2017, at 22:29, Richard Lamb <richard.lamb at icann.org<mailto:richard.lamb at icann.org>> wrote:

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

<image002.jpg>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/iot-wg/attachments/20170810/a3842734/attachment.html>