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] the vague IoT/RIPE-NCC training question

Previous message (by thread): [iot-wg] the vague IoT/RIPE-NCC training question

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Michael Richardson mcr+ietf at sandelman.ca
Tue May 31 19:45:51 CEST 2022

sandoche Balakrichenan <sandoche.balakrichenan at afnic.fr> wrote:
    > In addition to security, IMHO RIPE-NCC could focus on the identifiers (Naming
    > & addressing) side of IoT for training. For example, the usage of IPv6 for
    > IoT devices.

That seems far too researchy to me.
It seems like it might be something this WG could discuss, and maybe even do
some kind of document.


--
Michael Richardson <mcr+IETF at sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 515 bytes
Desc: not available
URL: </ripe/mail/archives/iot-wg/attachments/20220531/db557c7c/attachment.sig>

Previous message (by thread): [iot-wg] the vague IoT/RIPE-NCC training question

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ iot-wg Archives ]