Re: [Iot-directorate] Question on IETF IOT-devices scope

["Schooler, Eve M" <[e-mail]>]

For some time, I have been wanting the IETF’s definition of IoT to mean more than constrained devices (Carsten is probably tired of me raising this point in T2T!). While constrained devices are certainly an interesting class of IoT, so are (i) low-latency IoT domains and (ii) Edge IoT contexts that generate lots of data and disrupt where the compute, control, and data management need to reside.
My 2c’s,
Eve

From: Iot-directorate <[e-mail]> On Behalf Of Chakrabarti, Samita
Sent: Monday, March 15, 2021 2:56 PM
To: IETF IoT Directorate <[e-mail]>; Eric Vyncke (evyncke) <[e-mail]>; Ari Keränen <[e-mail]>; Ines Robles <[e-mail]>; Erik Kline <[e-mail]>
Subject: [Iot-directorate] Question on IETF IOT-devices scope

Hello All:

In pre-IETF IOT-DIRECTORATE meeting, Ted Lemon has pointed to two documents regarding connecting the Thread Mesh networks to the traditional IP Infrastructure:
1) (https://datatracker.ietf.org/doc/draft-lemon-stub-networks-ps/)  - Problem Statement
2) https://datatracker.ietf.org/doc/draft-lemon-stub-networks/         - A possible solution


IoT-Directorate co-chairs and the responsible ADs would like to discuss if it makes sense to extend the IOT-Directorate charter towards less constrained devices such as some of the home devices considered as 'things'.

The charter of the directorate says : (https://datatracker.ietf.org/group/iotdir/about/)

"The Internet of Things (IoT) refers to devices, that are often constrained in communication and computation capabilities, now becoming more commonly connected to the Internet, and various services that are built on top of the capabilities these devices jointly provide. It is expected that this development will usher in more machine-to-machine communication using the Internet with no human user actively involved."

Should IoT-Directorate members consider Thread Mesh stub networks as one of topics under IOT-DIR scope of discussion or part of IoT work?

Thanks,

-Samita