The Internet of Things (IoT) involves the application of Internet technologies to physical things such as machines, vehicles, buildings, appliances, and industrial infrastructure. XMPP-based implementations already exist in several areas of IoT, including demand-response systems for power grids via the OpenADR Alliance <http://www.openadr.org/> and smart transducer interfaces via the IEEE XMPP Interface Working Group <http://standards.ieee.org/develop/wg/XMPPI.html>. In addition, a number of XMPP Extension Protocols (XEPs) have been proposed at the XMPP Standards Foundation (XSF) over the years related to the Internet of Things.
Unfortunately, there has been a lack of communication and coordination among the various IoT initiatives in the broader XMPP community of developers and standards development organization. To improve matters, the authors of this document propose to create a forum and process for constructive discussions within the XSF, in the form of an Internet of Things Special Interest Group (IoT SIG) that shall be structured in compliance with Special Interest Groups (XEP-0002)  and that shall report to the XMPP Council  in accordance with Article VIII of the XSF's XSF Bylaws .
The role of the IoT SIG shall be as follows:
The IoT SIG shall not itself approve XMPP extension protocols (XEPs), which tasks shall remain under the purview of the XMPP Council.
The IoT SIG shall be open to the public and shall not be limited to elected members of the XMPP Standards Foundation. IoT SIG discussions shall be conducted in open forums, including a dedicated mailing list at <email@example.com> (which already exists).
The IoT SIG shall be a standing SIG, and shall exist as long as the XMPP Council deems it useful.
The IoT SIG should at a minumum produce an informational XEP that provides an overview of the XMPP IoT "landscape"; this document could help the XMPP community (including XSF members, leadership, and teams) understand the Intenet of Things and especially the applicability of XMPP to common IoT use cases.
The IoT SIG should also produce or coordinate the production of core protocol specifications or profiles that are suitable for use in common IoT use cases. If the IoT SIG produces such protocol specifications, they should be designed so that they can be extended by private parties or other standards development organizations for more particular use cases. In coordination with the XMPP Council, the IoT SIG may also produce a requirements document or roadmap to guide its work on protocol specifications.
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF).
Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <firstname.lastname@example.org> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <email@example.com>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
2. The XMPP Council is a technical steering committee, authorized by the XSF Board of Directors and elected by XSF members, that approves of new XMPP Extensions Protocols and oversees the XSF's standards process. For further information, see <https://xmpp.org/about/xmpp-standards-foundation#council>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/