This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/iot-wg@ripe.net/
[iot-wg] IRTF SMART WG
- Previous message (by thread): [iot-wg] IRTF SMART WG
- Next message (by thread): [iot-wg] InnoITeam - a new Center of Excellence in IoT Science and Technology
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Nov 13 13:37:49 CET 2018
On 13 Nov 2018, at 12:10, Jelte <ripe at tjeb.nl> wrote: > > To add to that, it has also been proposed to not use 'SMART' as the RG name, as 'smart' tends to be associated with IoT these days, whereas AFAICT IoT is only in scope in the sense that it can be a platform for malware. Well yes. But quibbling over the acronym is shed-painting IMO. It really doesn't matter much what the RG is called, provided it's not misleading or ambiguous. After all the charter explains what the RG will and won't do, not the name. SMART is just another in a depressingly long list of contrived acronyms for IETF WGs and RGs: sipbrandy, lemonade, drinks, modern, suit, dots, taps, acme, etc, etc. And hey, at least it's not using a reserved word in C. Which one now dead WG did. :-) Stopping Malware And Reducing Threats seems to be a reasonable enough approximation to what this new RG will do. Though if anyone here has better suggestions, I'm sure the IETF will be thrilled to hear about them on the SMART mailing list.
- Previous message (by thread): [iot-wg] IRTF SMART WG
- Next message (by thread): [iot-wg] InnoITeam - a new Center of Excellence in IoT Science and Technology
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]