<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Apologies to those who have already seen this but it ought still to be of interest to everyone in the WG.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Begin forwarded message:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:rfc-editor@rfc-editor.org" class="">rfc-editor@rfc-editor.org</a><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">[IRTF-Announce] RFC 8576 on Internet of Things (IoT) Security: State of the Art and Challenges</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">27 April 2019 at 04:12:31 CEST<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:ietf-announce@ietf.org" class="">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org" class="">rfc-dist@rfc-editor.org</a>, <a href="mailto:irtf-announce@irtf.org" class="">irtf-announce@irtf.org</a><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Cc: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:drafts-update-ref@iana.org" class="">drafts-update-ref@iana.org</a>, <a href="mailto:t2trg@irtf.org" class="">t2trg@irtf.org</a>, <a href="mailto:rfc-editor@rfc-editor.org" class="">rfc-editor@rfc-editor.org</a><br class=""></span></div><br class=""><div class=""><div class="">A new Request for Comments is now available in online RFC libraries.<br class=""><br class=""><br class=""> RFC 8576<br class=""><br class=""> Title: Internet of Things (IoT) Security: <br class=""> State of the Art and Challenges <br class=""> Author: O. Garcia-Morchon, <br class=""> S. Kumar,<br class=""> M. Sethi<br class=""> Status: Informational<br class=""> Stream: IRTF<br class=""> Date: April 2019<br class=""> Mailbox: <a href="mailto:oscar.garcia-morchon@philips.com" class="">oscar.garcia-morchon@philips.com</a>, <br class=""> <a href="mailto:sandeep.kumar@signify.com" class="">sandeep.kumar@signify.com</a>, <br class=""> <a href="mailto:mohit@piuha.net" class="">mohit@piuha.net</a><br class=""> Pages: 50<br class=""> Characters: 128372<br class=""> Updates/Obsoletes/SeeAlso: None<br class=""><br class=""> I-D Tag: draft-irtf-t2trg-iot-seccons-16.txt<br class=""><br class=""> URL: <a href="https://www.rfc-editor.org/info/rfc8576" class="">https://www.rfc-editor.org/info/rfc8576</a><br class=""><br class=""> DOI: 10.17487/RFC8576<br class=""><br class="">The Internet of Things (IoT) concept refers to the usage of standard<br class="">Internet protocols to allow for human-to-thing and thing-to-thing<br class="">communication. The security needs for IoT systems are well<br class="">recognized, and many standardization steps to provide security have<br class="">been taken -- for example, the specification of the Constrained<br class="">Application Protocol (CoAP) secured with Datagram Transport Layer<br class="">Security (DTLS). However, security challenges still exist, not only<br class="">because there are some use cases that lack a suitable solution, but<br class="">also because many IoT devices and systems have been designed and<br class="">deployed with very limited security capabilities. In this document,<br class="">we first discuss the various stages in the lifecycle of a thing.<br class="">Next, we document the security threats to a thing and the challenges<br class="">that one might face to protect against these threats. Lastly, we<br class="">discuss the next steps needed to facilitate the deployment of secure<br class="">IoT systems. This document can be used by implementers and authors<br class="">of IoT specifications as a reference for details about security<br class="">considerations while documenting their specific security challenges,<br class="">threat models, and mitigations.<br class=""><br class="">This document is a product of the IRTF Thing-to-Thing Research Group<br class="">(T2TRG).<br class=""><br class="">This document is a product of the Thing-to-Thing of the IRTF.<br class=""><br class=""><br class="">INFORMATIONAL: This memo provides information for the Internet community.<br class="">It does not specify an Internet standard of any kind. Distribution of<br class="">this memo is unlimited.<br class=""><br class="">This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see<br class=""> <a href="https://www.ietf.org/mailman/listinfo/ietf-announce" class="">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br class=""> <a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" class="">https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br class=""> <a href="https://www.irtf.org/mailman/listinfo/irtf-announce" class="">https://www.irtf.org/mailman/listinfo/irtf-announce</a><br class=""><br class="">For searching the RFC series, see <a href="https://www.rfc-editor.org/search" class="">https://www.rfc-editor.org/search</a><br class="">For downloading RFCs, see <a href="https://www.rfc-editor.org/retrieve/bulk" class="">https://www.rfc-editor.org/retrieve/bulk</a><br class=""><br class="">Requests for special distribution should be addressed to either the<br class="">author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org" class="">rfc-editor@rfc-editor.org</a>. Unless<br class="">specifically noted otherwise on the RFC itself, all RFCs are for<br class="">unlimited distribution.<br class=""><br class=""><br class="">The RFC Editor Team<br class="">Association Management Solutions, LLC<br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></body></html>