XEP-xxxx: Internet of Things - Events

Abstract:This specification describes an architecture based on the XMPP protocol whereby Things can subscribe to events from other Things based on sensor data available.
Author:Peter Waher
Copyright:© 1999 - 2014 XMPP Standards Foundation. SEE LEGAL NOTICES.
Status:ProtoXEP
Type:Standards Track
Version:0.0.1
Last Updated:2014-08-13

WARNING: This document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards Foundation, and this document is not yet an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at <http://xmpp.org/extensions/> and announced on the <standards@xmpp.org> mailing list.


Table of Contents


1. Introduction
2. Glossary
3. Use Cases
    3.1. Request Subscription of momentary values
    3.2. Subscription rejected
    3.3. Unsubscribing a subscription
    3.4. Requesting subscription of changes to fields values
    3.5. Requesting subscription of historical data correlated to events
    3.6. Requesting subscription of historical data correlated to events
    3.7. Requesting subscription of nodes behind a concentrator
4. Determining Support
5. Implementation Notes
    5.1. Change conditions
    5.2. When to check event conditions
    5.3. Removal of friendships
    5.4. Power-down and persistence of subscriptions
    5.5. Overriding subscriptions
6. Security Considerations
    6.1. Re-evaluation of subscription contents
7. IANA Considerations
8. XMPP Registrar Considerations
9. XML Schema
10. For more information

Appendices
    A: Document Information
    B: Author Information
    C: Legal Notices
    D: Relation to XMPP
    E: Discussion Venue
    F: Requirements Conformance
    G: Notes
    H: Revision History


1. Introduction

This document specifies a method whereby devices or applications can subscribe to events from a Thing, based on sensor data, as defined in XEP-0323: Internet of Things - Sensor Data (XEP-0323) [1]. While XEP-0323 defines a method whereby the device or application can request sensor data information from a Thing when the device or application requires it, this document specifies a method whereby the Thing itself informs the device or application of desired sensor data, when certain conditions have been met, defined by the device or application.

The architecture defined in this document, permits the specification of conditions individually, something that would not be possible, or very difficult to achieve, if a centralized publish/subscribe or multi-cast pattern would have been used. By allowing individual conditions to be specified, devices or applications can be informed of information that best suit them, and when it suits them, instead of having to figure out, from the Thing perspective, a common denominator, sufficiently good for all intended devices or applications. Furthermore, by aligning itself with XEP-0323 and the request/response pattern, the Thing can easily integrate with a provisioning server, as defined in XEP-0324: Internet of Things - Provisioning (XEP-0324) [2], to allow for delegation of trust and allowing detailed provisioning of who is allowed to receive what information. Through the use of attributes defined in XEP-0326: Internet of Things - Concentrators (XEP-0326) [3] subscriptions can be extended to underlying nodes controlled by the Thing as well.

Internet of Things contains many different architectures and use cases. For this reason, the IoT standards have been divided into multiple XEPs according to the following table:

Table 1: Internet of Things XEPs

XEP Description
xep-0000-IoT-BatteryPoweredSensors Defines how to handle the peculiars related to battery powered devices, and other devices intermittently available on the network.
xep-0000-IoT-Events This specification. Defines how Things send events, how event subscription, hysteresis levels, etc., are configured.
xep-0000-IoT-Interoperability Defines guidelines for how to achieve interoperability in Internet of Things, publishing interoperability interfaces for different types of devices.
xep-0000-IoT-Multicast Defines how sensor data can be multicast in efficient ways.
xep-0000-IoT-PubSub Defines how efficient publication of sensor data can be made in Internet of Things.
xep-0000-IoT-Chat Defines how human-to-machine interfaces should be constructed using chat messages to be user friendly, automatable and consistent with other IoT extensions and possible underlying architecture.
XEP-0322 Defines how to EXI can be used in XMPP to achieve efficient compression of data. Albeit not an Internet of Things specific XEP, this XEP should be considered in all Internet of Things implementations where memory and packet size is an issue.
XEP-0323 Provides the underlying architecture, basic operations and data structures for sensor data communication over XMPP networks. It includes a hardware abstraction model, removing any technical detail implemented in underlying technologies. This XEP is used by all other Internet of Things XEPs.
XEP-0324 Defines how provisioning, the management of access privileges, etc., can be efficiently and easily implemented.
XEP-0325 Defines how to control actuators and other devices in Internet of Things.
XEP-0326 Defines how to handle architectures containing concentrators or servers handling multiple Things.
XEP-0331 Defines extensions for how color parameters can be handled, based on Data Forms (XEP-0004) [4]
XEP-0336 Defines extensions for how dynamic forms can be created, based on Data Forms (XEP-0004) [5], Data Forms Validation (XEP-0122) [6], Publishing Stream Initiation Requests (XEP-0137) [7] and Data Forms Layout (XEP-0141) [8].
XEP-0347 Defines the peculiars of Thing discovery in Internet of Things. Apart from discovering Things by JID, it also defines how to discover Things based on location, etc.

2. Glossary

The following table lists common terms and corresponding descriptions.

Actuator
Device containing at least one configurable property or output that can and should be controlled by some other entity or device.
Computed Value
A value that is computed instead of measured.
Concentrator
Device managing a set of devices which it publishes on the XMPP network.
Field
One item of sensor data. Contains information about: Node, Field Name, Value, Precision, Unit, Value Type, Status, Timestamp, Localization information, etc. Fields should be unique within the triple (Node ID, Field Name, Timestamp).
Field Name
Name of a field of sensor data. Examples: Energy, Volume, Flow, Power, etc.
Field Type
What type of value the field represents. Examples: Momentary Value, Status Value, Identification Value, Calculated Value, Peak Value, Historical Value, etc.
Historical Value
A value stored in memory from a previous timestamp.
Identification Value
A value that can be used for identification. (Serial numbers, meter IDs, locations, names, etc.)
Localization information
Optional information for a field, allowing the sensor to control how the information should be presented to human viewers.
Meter
A device possible containing multiple sensors, used in metering applications. Examples: Electricity meter, Water Meter, Heat Meter, Cooling Meter, etc.
Momentary Value
A momentary value represents a value measured at the time of the read-out.
Node
Graphs contain nodes and edges between nodes. In Internet of Things, sensors, actuators, meters, devices, gateways, etc., are often depicted as nodes whereas links between sensors (friendships) are depicted as edges. In abstract terms, it's easier to talk about a Node, rather than list different possible node types (sensors, actuators, meters, devices, gateways, etc.). Each Node has a Node ID.
Node ID
An ID uniquely identifying a node within its corresponding context. If a globally unique ID is desired, an architecture should be used using a universally accepted ID scheme.
Parameter
Readable and/or writable property on a node/device. The XEP-0326 Internet of Things - Concentrators (XEP-0326) [9] deals with reading and writing parameters on nodes/devices. Fields are not parameters, and parameters are not fields.
Peak Value
A maximum or minimum value during a given period.
Precision
In physics, precision determines the number of digits of precision. In sensor networks however, this definition is not easily applicable. Instead, precision determines, for example, the number of decimals of precision, or power of precision. Example: 123.200 MWh contains 3 decimals of precision. All entities parsing and delivering field information in sensor networks should always retain the number of decimals in a message.
Sensor
Device measuring at least one digital value (0 or 1) or analog value (value with precision and physical unit). Examples: Temperature sensor, pressure sensor, etc. Sensor values are reported as fields during read-out. Each sensor has a unique Node ID.
SN
Sensor Network. A network consisting, but not limited to sensors, where transport and use of sensor data is of primary concern. A sensor network may contain actuators, network applications, monitors, services, etc.
Status Value
A value displaying status information about something.
Timestamp
Timestamp of value, when the value was sampled or recorded.
Token
A client, device or user can get a token from a provisioning server. These tokens can be included in requests to other entities in the network, so these entities can validate access rights with the provisioning server.
Unit
Physical unit of value. Example: MWh, l/s, etc.
Value
A field value.
Value Status
Status of field value. Contains important status information for Quality of Service purposes. Examples: Ok, Error, Warning, Time Shifted, Missing, Signed, etc.
Value Type
Can be numeric, string, boolean, Date & Time, Time Span or Enumeration.
WSN
Wireless Sensor Network, a sensor network including wireless devices.
XMPP Client
Application connected to an XMPP network, having a JID. Note that sensors, as well as applications requesting sensor data can be XMPP clients.

3. Use Cases

Subscribing to events is performed much the same way as requesting sensor data from a device, as defined in XEP-0323. Instead of requesting the data using the req element of the urn:xmpp:iot:sensordata namespace, it is done using the subscribe element of the urn:xmpp:iot:events namespace. Much of the syntax of this subscribe element coincides with that of the req element, with some differences, as will be described in this document.

Responses and sensor data is then sent from the device to the subscriber, in the same way as defined in XEP-0323, with one notable difference: The sequence number seqnr provided in the request, is not forgotten once a readout has been completed, but will be reused every time the Thing reports data to the subscriber. The subscriber must use this sequence number to correlate incoming sensor data with original request. Furthermore, the subscriber must not reuse the sequence number in other sensor data requests to the Thing, while the subscription is alive.

A subscription is cancelled by the subscriber sending a request with an unsubscribe element in it to the Thing. The Thing can also automatically remove subscriptions if the corresponding friendship ends. Furthermore, event conditions should only be evaluated if the corresponding subscriber is online. This, to avoid offline messages to pile up. Once a friend comes online, any subscription conditions corresponding to that friend should be evaluated to inform it of the current state of the Thing.

3.1 Request Subscription of momentary values

The client that wishes to receive momentary values regularly from the sensor initiates the request using the subscribe element sent to the device. In the following example, a subscription is made to receive momentary values every five minutes (specified by the maxInterval attribute), with no field-specific conditions attached.

Example 1. Subscription request of momentary values from a device

                
   <iq type='get'
       from='client@clayster.com/amr'
       to='device@clayster.com'
       id='S0001'>
      <subscribe xmlns='urn:xmpp:iot:events' seqnr='1' momentary='true' maxInterval='PT5M' req='true'/>
   </iq>
            

When the device has received and accepted the request, it responds as follows, using the accepted element defined in XEP-0323. Sensor data is later reported in a way similar to XEP-0323, with the exception that the seqnr will be reused every time the event occurs. If the event causes multiple messages to be sent, the receiver knows which one is the last message, by looking at the done attribute. Since the req attribute is set to true, an event will be sent back immediately (i.e. emulating a parallel readout request operation).

Example 2. Subscription request accepted by device

                
   <iq type='result'
       from='device@clayster.com'
       to='client@clayster.com/amr'
       id='S0001'>
      <accepted xmlns='urn:xmpp:iot:sensordata' seqnr='1'/>
   </iq>
            

3.2 Subscription rejected

If for some reason, the device rejects the subscription request, the communication sequence might look as follows:

Example 3. Momentary read-out rejected

                
   <iq type='get'
       from='client@clayster.com/amr'
       to='device@clayster.com'
       id='S0002'>
      <subscribe xmlns='urn:xmpp:iot:events' seqnr='1' momentary='true' maxInterval='PT5M'/>
   </iq>
   
   <iq type='error'
       from='device@clayster.com'
       to='client@clayster.com/amr'
       id='S0002'>
      <error type='cancel'>
         <forbidden xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
         <text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>Access denied.</text>
      </error>
   </iq>
            

Depending on the reason for rejecting the request, different XMPP errors can be returned, according to the description in the following table. The table also lists recommended error type for each error. Any custom error message is returned in a text element, as in the example above.

Table 2: XMPP Errors when rejecting a subscription request

Error Type Error Element Namespace Description
cancel forbidden urn:ietf:params:xml:ns:xmpp-stanzas If the caller lacks privileges to perform the action.
cancel item-not-found urn:ietf:params:xml:ns:xmpp-stanzas If an item or data source could not be found.
modify bad-request urn:ietf:params:xml:ns:xmpp-stanzas If the request was malformed. Examples can include trying to subscribe to information from a device behind a concentrator, without including node information.

3.3 Unsubscribing a subscription

To unsubscribe a subscription, send the unsubscribe element in a request to the Thing with the seqnr sequence number corresponding to the subscription. The Thing responds with an empty response to acknowledge the un-subscription, regardless if the subscription existed or not.

Example 4. Unsubscribing a subscription

                
   <iq type='get'
       from='client@clayster.com/amr'
       to='device@clayster.com'
       id='S0003'>
      <unsubscribe xmlns='urn:xmpp:iot:events' seqnr='1'/>
   </iq>
   
   <iq type='result'
       from='device@clayster.com'
       to='client@clayster.com/amr'
       id='S0003'/>
            

3.4 Requesting subscription of changes to fields values

The client that wishes to receive information when a field or a set fields change, can do so by specifying amount of change allowed in the corresponding field elements in the subscription. It can also provide optional current values from which the change is measured. If current values are not provided, the Thing uses its corresponding set of current values at the time it receives the request. Current values use the corresponding unit held by the field. To find out, if unsure, you need to make a sensor data readout first.

In the following example, events are sent when light changes by more than 5 units (of a percent), or if a motion detector changes value. Temperature information at the time of the event is also requested. If the conditions are not met within fifteen minutes, an event is raised anyway (as defined using the maxInterval attribute). The minInterval attribute makes sure events are not sent more often than every five seconds.

Example 5. Requesting subscription of changes to fields values

                
   <iq type='get'
       from='client@clayster.com/amr'
       to='device@clayster.com'
       id='S0004'>
      <subscribe xmlns='urn:xmpp:iot:events' seqnr='1' momentary='true' maxInterval='PT15M' minInterval='PT5S'>
          <field name='Light' changedBy='5'/>
          <field name='Motion' changedBy='1' currentValue='0'/>
          <field name='Temperature'/>
      </subscribe>
   </iq>
            

3.5 Requesting subscription of historical data correlated to events

Any type of sensor data can be included in an event subscription, including historical data. To limit the amount of historical data to return in an event, the maxAge attribute can be used, instead of the absolute from and to attributes available in the corresponding req element. The following example requests the last five minutes of historical temperature and light data as soon as the motion detector detects motion (change upwards of 1).

Example 6. Requesting subscription of historical data correlated to events

                
   <iq type='get'
       from='client@clayster.com/amr'
       to='device@clayster.com'
       id='S0005'>
      <subscribe xmlns='urn:xmpp:iot:events' seqnr='1' all='true' minInterval='PT1M' maxAge='PT5M'>
          <field name='Temperature'/>
          <field name='Light'/>
          <field name='Motion' changedUp='1'/>
      </subscribe>
   </iq>
            

3.6 Requesting subscription of historical data correlated to events

Any type of sensor data can be included in an event subscription, including historical data. To limit the amount of historical data to return in an event, the maxAge attribute can be used, instead of the absolute from and to attributes available in the corresponding req element. The following example requests the last five minutes of historical temperature and light data as soon as the motion detector detects motion (change upwards of 1).

Example 7. Requesting subscription of historical data correlated to events

                
   <iq type='get'
       from='client@clayster.com/amr'
       to='device@clayster.com'
       id='S0006'>
      <subscribe xmlns='urn:xmpp:iot:events' seqnr='1' all='true' minInterval='PT1M' maxAge='PT5M'>
          <field name='Temperature'/>
          <field name='Light'/>
          <field name='Motion' changedUp='1'/>
      </subscribe>
   </iq>
            

3.7 Requesting subscription of nodes behind a concentrator

To subscribe to events from one or more nodes behind a concentrator, the nodes have to be specified using node elements in the subscription request. If more than one node is present, the subscription request is assumed to be made to each node individually. When the subscription conditions are met, the corresponding node sends its sensor data back to the subscriber. Note that only the node where the conditions are met include data in the message sent to the subscriber. Event subscriptions are handled individually for each node.

In the following example, a subscription of any changes to a sequence of digital inputs handled by a PLC is made.

Example 8. Requesting subscription of nodes behind a concentrator

                
   <iq type='get'
       from='client@clayster.com/amr'
       to='plc@clayster.com'
       id='S0007'>
      <subscribe xmlns='urn:xmpp:iot:events' seqnr='1' momentary='true' minInterval='PT5S' maxInternval='PT1H'>
          <node nodeId='DI1'/>
          <node nodeId='DI2'/>
          <node nodeId='DI3'/>
          <node nodeId='DI4'/>
          <field name='State' changeBy='1' currentValue='0'/>
      </subscribe>
   </iq>
            

4. Determining Support

If an entity supports the protocol specified herein, it MUST advertise that fact by returning a feature of "urn:xmpp:iot:events" in response to Service Discovery (XEP-0030) [10] information requests.

Example 9. Service discovery information request

			
<iq type='get'
    from='client@clayster.com/amr'
    to='device@clayster.com'
    id='disco1'>
  <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
		

Example 10. Service discovery information response

			
<iq type='result'
    from='device@clayster.com'
    to='client@clayster.com/amr'
    id='disco1'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    ...
    <feature var='urn:xmpp:iot:events'/>
    ...
  </query>
</iq>
		

In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in Entity Capabilities (XEP-0115) [11]. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.

5. Implementation Notes

5.1 Change conditions

An integral part of conditions, is the measurement of changes of magnitudes of field values. Three attributes available on the field element, can be used to define how to measure changes. The changedUp attribute provides a numerical value limiting the amount of upwards change in the field before an event is triggered. The changedDown attributes provides a similar means to control the amount of downwards change in the field, before an event is triggered. If only one of these are provided, only changes in that direction trigger events. If the changedBy attribute is provided, the other two attributes are ignored, and assumed to be of the same value as the changedBy attribute value. All changes are specified using positive numbers.

The following table shows how magnitudes are calculated for field values of different types:

Table 3: Magnitude of change per field type

Type Magnitude
boolean Magnitude is 0 if false, and 1 if true.
date Number of seconds since an implementation specific point in time. Since only changes are measured, actual point in time is not important.
dateTime Number of seconds since an implementation specific point in time. Since only changes are measured, actual point in time is not important.
duration Corresponding number of seconds.
enum Any change to this value, corresponds to a change by 1. If direction of change is important, values are ordered by lexical order.
int The value itself.
long The value itself.
numeric The value itself, without unit. The magnitude specified in any change attributes is assumed to be specified using the same unit as the corresponding field.
string Any change to this value, corresponds to a change by 1. If direction of change is important, values are ordered by lexical order.
time Corresponding number of seconds.

5.2 When to check event conditions

Event conditions should be checked, if the following conditions are true for the corresponding event:

5.3 Removal of friendships

If a friendship is lost, i.e. presence information from the corresponding contact is unsubscribed, the Thing has to automatically remove any event subscriptions available for that contact. If a new friendship is created with the same contact at a later stage, the contact has to request new subscriptions.

5.4 Power-down and persistence of subscriptions

It is up to the thing, if it wants to persist event subscriptions or not. If not persisting event subscriptions, they will automatically be lost if the Thing rests or restarts for some reason.

If the subscriber considers an event subscription important, and wants to make sure a subscription survives any resets of the thing, the maxInterval attribute should be used when requesting the subscription. If an event is not delivered within this time and a margin, the subscriber can assume the subscription has been lost, and a new subscription can be made.

5.5 Overriding subscriptions

A subscriber can only have one active subscription per node on a Thing. If a Thing does not support nodes, each subscriber can only have one active subscription per corresponding Thing. This means, that a new event subscription automatically overrides (or unsubscribes) any existing subscription on the corresponding node or Thing. This in turn makes it easier for subscribers to handle restarts and avoids multiplicity problems due to lack of synchronization between subscriber and Thing.

6. Security Considerations

6.1 Re-evaluation of subscription contents

If a Thing is connected to a provisioning server, as defined in XEP-324: Internet of Things - Provisioning , it should re-evaluate event subscriptions contents if a clearCache command is received from the provisioning server. To be able to do this properly, the contents of the original event subscription should be remembered. Re-evaluating active event subscriptions after a clearCache command enables the owner of the Thing to modify current access rights in the Thing in real-time, including contents send in events.

Existing event subscriptions that are no longer permitted by the new set of rules in the provisioning server, can be removed from memory, without informing the subscriber about the fact. The subscriber will be informed when re-subscribing, that access rights have been lost.

7. IANA Considerations

This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [12].

8. XMPP Registrar Considerations

The protocol schema needs to be added to the list of XMPP protocol schemas.

9. XML Schema

			
<?xml version='1.0' encoding='UTF-8'?>
<xs:schema
    xmlns:xs='http://www.w3.org/2001/XMLSchema'
    targetNamespace='urn:xmpp:iot:events'
    xmlns='urn:xmpp:iot:events'
    xmlns:sd='urn:xmpp:iot:sensordata'
    elementFormDefault='qualified'>

	<xs:import namespace='urn:xmpp:iot:sensordata'/>
	
	<xs:element name='subscribe'>
		<xs:complexType>
			<xs:choice minOccurs='0' maxOccurs='unbounded'>
				<xs:element name='node'>
					<xs:complexType>
						<xs:attribute name='nodeId' type='xs:string' use='required'/>
						<xs:attribute name='sourceId' type='xs:string' use='optional'/>
						<xs:attribute name='cacheType' type='xs:string' use='optional'/>
					</xs:complexType>
				</xs:element>
				<xs:element name='field'>
					<xs:complexType>
						<xs:attribute name='name' type='xs:string' use='required'/>
						<xs:attribute name='currentValue' type='xs:double' use='optional'/>
						<xs:attribute name='changedBy' type='PositiveDouble' use='optional'/>
						<xs:attribute name='changedUp' type='PositiveDouble' use='optional'/>
						<xs:attribute name='changedDown' type='PositiveDouble' use='optional'/>
					</xs:complexType>
				</xs:element>
			</xs:choice>
			<xs:attribute name='seqnr' type='xs:int' use='required'/>
			<xs:attributeGroup ref='sd:fieldTypes'/>
			<xs:attribute name='all' type='xs:boolean' use='optional' default='false'/>
			<xs:attribute name='historical' type='xs:boolean' use='optional' default='false'/>
			<xs:attribute name='maxAge' type='xs:duration' use='optional'/>
			<xs:attribute name='minInterval' type='xs:duration' use='optional'/>
			<xs:attribute name='maxInterval' type='xs:duration' use='optional'/>
			<xs:attribute name='serviceToken' type='xs:string' use='optional'/>
			<xs:attribute name='deviceToken' type='xs:string' use='optional'/>
			<xs:attribute name='userToken' type='xs:string' use='optional'/>
			<xs:attribute name='req' type='xs:boolean' use='optional' default='false'/>
		</xs:complexType>
	</xs:element>

	<xs:element name='unsubscribe'>
		<xs:complexType>
			<xs:attribute name='seqnr' type='xs:int' use='required'/>
		</xs:complexType>
	</xs:element>

	<xs:simpleType name='PositiveDouble'>
		<xs:restriction base='xs:double'>
			<xs:minExclusive value='0'/>
		</xs:restriction>
	</xs:simpleType>

</xs:schema>
		

10. For more information

For more information, please see the following resources:


Appendices


Appendix A: Document Information

Series: XEP
Number: xxxx
Publisher: XMPP Standards Foundation
Status: ProtoXEP
Type: Standards Track
Version: 0.0.1
Last Updated: 2014-08-13
Approving Body: XMPP Council
Dependencies: XMPP Core, XEP-0001, XEP-0030, XEP-0323, XEP-0324, XEP-0326
Supersedes: None
Superseded By: None
Short Name: iot-events
This document in other formats: XML  PDF


Appendix B: Author Information

Peter Waher

Email: peter.waher@clayster.com
JabberID: peter.waher@jabber.org
URI: http://www.linkedin.com/in/peterwaher


Appendix C: Legal Notices

Copyright

This XMPP Extension Protocol is copyright © 1999 - 2014 by the XMPP Standards Foundation (XSF).

Permissions

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.

Disclaimer of Warranty

## 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. ##

Limitation of Liability

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.

IPR Conformance

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 <http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/> or obtained by writing to XMPP Standards Foundation, 1899 Wynkoop Street, Suite 600, Denver, CO 80202 USA).

Appendix D: Relation to XMPP

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.


Appendix E: Discussion Venue

The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.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 <editor@xmpp.org>.


Appendix F: Requirements Conformance

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".


Appendix G: Notes

1. XEP-0323: Internet of Things - Sensor Data <http://xmpp.org/extensions/xep-0323.html>.

2. XEP-0324: Internet of Things - Provisioning <http://xmpp.org/extensions/xep-0324.html>.

3. XEP-0326: Internet of Things - Concentrators <http://xmpp.org/extensions/xep-0326.html>.

4. XEP-0004: Data Forms <http://xmpp.org/extensions/xep-0004.html>.

5. XEP-0004: Data Forms <http://xmpp.org/extensions/xep-0004.html>.

6. XEP-0122: Data Forms Validation <http://xmpp.org/extensions/xep-0122.html>.

7. XEP-0137: Publishing Stream Initiation Requests <http://xmpp.org/extensions/xep-0137.html>.

8. XEP-0141: Data Forms Layout <http://xmpp.org/extensions/xep-0141.html>.

9. XEP-0326: Internet of Things - Concentrators <http://xmpp.org/extensions/xep-0326.html>.

10. XEP-0030: Service Discovery <http://xmpp.org/extensions/xep-0030.html>.

11. XEP-0115: Entity Capabilities <http://xmpp.org/extensions/xep-0115.html>.

12. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.


Appendix H: Revision History

Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/

Version 0.0.1 (2014-08-13)

First draft.

(pw)

END