You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

72 lines
4.7 KiB

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM "xep.ent">
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<title>Internet of Things Special Interest Group (IoT SIG)</title>
<abstract>This document proposes the formation of a Special Interest Group SIG) within the XSF devoted to the application of XMPP technologies to the Internet of Things (IoT).</abstract>
<initials>XEP Editor: jsc</initials>
<remark>Accepted by Council</remark>
<initials>XEP Editor: ssw</initials>
<remark>Initial published version.</remark>
<remark>Initial version.</remark>
<section1 topic='Introduction' anchor='intro'>
<p>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 &lt;; and smart transducer interfaces via the IEEE XMPP Interface Working Group &lt;;. 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.</p>
<p>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 &xep0002; and that shall report to the &COUNCIL; in accordance with Article VIII of the XSF's &BYLAWS;.</p>
<section1 topic='Scope and Role' anchor='scope'>
<p>The role of the IoT SIG shall be as follows:</p>
<li>Produce, or coordinate the production, of relevant XMPP Extension Protocol (XEP) documents as described below under Deliverables.</li>
<li>Provide advice to the XMPP Council regarding work within the XSF on IoT topics.</li>
<li>Provide advice to the XMPP Council and the XSF Board of Directors regarding work outside the XSF happening at other standards development organizations.</li>
<li>Manage a dedicated forum for discussion of IoT topics within the XMPP community.</li>
<p>The IoT SIG shall not itself approve XMPP extension protocols (XEPs), which tasks shall remain under the purview of the XMPP Council.</p>
<section1 topic='Membership' anchor='membership'>
<p>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 &lt;; (which already exists).</p>
<section1 topic='Lifetime' anchor='lifetime'>
<p>The IoT SIG shall be a standing SIG, and shall exist as long as the XMPP Council deems it useful.</p>
<section1 topic='Deliverables' anchor='deliverables'>
<p>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.</p>
<p>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.</p>