Dear Collegues, on the latest IETF meeting the SMART WG of the IRTF was created: https://www.ietf.org/mail-archive/web/smart/current/msg00003.html Researching ways to identify malicious encrypted traffic might also be interesting for projects working on detecting unusual IoT device behaviour (i.e. SPIN or the project of the IETF home networking group presented by CERA on the latest RIPE meeting). If this research project succeeds it will raise a couple of other questions about encrypted traffic - to be honest I’m not sure if I like a positive outcome in terms of privacy and data protection… Best regards, Peter
Hi,
On 13 Nov 2018, at 10:56, Peter Steinhäuser <ps@embedd.com> wrote:
Dear Collegues,
on the latest IETF meeting the SMART WG of the IRTF was created:
https://www.ietf.org/mail-archive/web/smart/current/msg00003.html
To be clear, this is a *proposed* IRTF *research* group (so RG, not WG). It is not yet formally chartered as an IRTF research group, but may be in due course. In the meantime, interested folks should join the mailing list to stay abreast of future meetings, workshops and research contributions. https://www.irtf.org/mailman/listinfo/smart Regards, Mat
Hi Mat, you’re right - thanks for the clarification! Best regards, Peter
Am 13.11.2018 um 12:27 schrieb Mat Ford <ford@isoc.org>:
Hi,
On 13 Nov 2018, at 10:56, Peter Steinhäuser <ps@embedd.com> wrote:
Dear Collegues,
on the latest IETF meeting the SMART WG of the IRTF was created:
https://www.ietf.org/mail-archive/web/smart/current/msg00003.html
To be clear, this is a *proposed* IRTF *research* group (so RG, not WG). It is not yet formally chartered as an IRTF research group, but may be in due course. In the meantime, interested folks should join the mailing list to stay abreast of future meetings, workshops and research contributions.
https://www.irtf.org/mailman/listinfo/smart
Regards, Mat
On 13 Nov 2018, at 10:56, Peter Steinhäuser <ps@embedd.com> wrote:
on the latest IETF meeting the SMART WG of the IRTF was created:
https://www.ietf.org/mail-archive/web/smart/current/msg00003.html
Researching ways to identify malicious encrypted traffic might also be interesting for projects working on detecting unusual IoT device behaviour (i.e. SPIN or the project of the IETF home networking group presented by CERA on the latest RIPE meeting).
As Mat kindly pointed out this is a proposed Research Group, not a Working Group, that has still to be formally created. Though that looks very likely to happen. Please note that the draft charter for this RG-to-be is much, much wider than IoT. Though IoT security stuff will be one topic that's in scope. The motivation for SMART is to bring cybersecurity research (for some definition of that term) to the IETF so it can inform protocol development in WGs. Anyone wanting to know more should sign up for the SMART mailing list. https://www.irtf.org/mailman/listinfo/smart I think there's still time to comment on the draft charter before this gets approved and the RG is created. The first meeting of SMART is likely to be at IETF104.
On 11/13/18 12:47 PM, Jim Reid wrote:
Please note that the draft charter for this RG-to-be is much, much wider than IoT. Though IoT security stuff will be one topic that's in scope. The motivation for SMART is to bring cybersecurity research (for some definition of that term) to the IETF so it can inform protocol development in WGs.
Anyone wanting to know more should sign up for the SMART mailing list. https://www.irtf.org/mailman/listinfo/smart
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. From skimming the list and proposed charter it seems it will be very general indeed, maybe too much so, but definitely worth checking in on. Jelte
On 13 Nov 2018, at 12:10, Jelte <ripe@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.
participants (4)
-
Jelte -
Jim Reid -
Mat Ford -
Peter Steinhäuser