Component/s: Charter Clarification
The ballot to approve the clarified charter passed on April 6. See https://www.oasis-open.org/committees/ballot.php?id=3596
Sent request to Jesse:
Load clarified charter for MQTT TC
The MQTT TC voted to approve a charter clarification on April 6, 2021.
Please change the text and charter at https://www.oasis-open.org/committees/mqtt/charter.php to read (note change to the 3rd paragraph on the original charter):
The TC approved a clarified charter on 06 April 2021 (https://www.oasis-open.org/committees/ballot.php?id=3596).
The OASIS Message Queuing Telemetry Transport (MQTT) TC approved a revised charter on 25 April 2016 (https://www.oasis-open.org/committees/ballot.php?id=2925) and began work under its new charter on 16 June 2016.
The original charter can be found in the call for participation at https://lists.oasis-open.org/archives/mqtt/201302/msg00000.html.
1. Name of Technical Committee
OASIS Message Queuing Telemetry Transport Technical Committee
2. Statement of Purpose
The purpose of the Message Queuing Telemetry Transport (MQTT) Technical Committee is to standardize a lightweight publish/subscribe messaging protocol designed to be open, simple, lightweight, and suited for use in constrained networks and multi-platform environments. The TC will accomplish this purpose through the refinement of an input specification.
Background and Opportunity:
Many industries are seeing rapid demand for products and solutions which map physical world events into digital events for applications and large-scale distributed services. These applications and services need to connect and communicate with devices ranging from simple sensors, actuators and complex embedded edge-of-network controllers, to mobile devices, often over wireless networks.
Needs and Requirements:
A simple, predictable, and easy to implement message protocol is needed for connecting embedded and mobile devices such as physical sensors, controllers, and smart phones with servers used in Web, enterprise, and other applications where a lightweight messaging protocol is desired. The protocol must be able to cope with runtime platform constraints, network constraints and various combinations of both. It must support implementations that run on embedded devices with limited power, processor or memory resources. It must connect to a range of web services and enterprise middleware in constrained environments where networks may have any combination of low bandwidth, intermittent connectivity, unpredictable reliability, or high data cost.
Experience with physical world messages and events across many industry domains has identified key requirements for such a message protocol:
• Bi-directional messaging to uniformly handle both signals and commands.
• Determinable delivery of messages to and from sensors and actuators, and other resource constrained devices connected over intermittent, limited bandwidth networks. Basic Quality of Service (QoS) levels are needed to reflect tradeoffs between bandwidth, availability, and delivery guarantees. Always-connected and sometimes-connected models both need to be supported. A message subscriber must be able to set up a quality of service needed that reflects the constraints and characteristics of message source’s network connection.
• Connectivity Awareness. To support intermittent networks, the publish/subscribe infrastructure needs to provide message subscribers, if necessary, a means to determine the likely connected, disconnected or error state of the end devices in the network.
• Loose coupling to support dynamic system environments where high volumes of physical world messages and events need to be made available to enterprise servers and other consumers in ways which may not have been originally anticipated. Time, space, and synchronization decoupling are needed.
• Constrained operations. Instrumentation of the physical world must be supported in a proliferation of platforms, technologies and networks that are driven by very diverse equations of cost, technology and physical constraints.
• Scalability suitable to supporting environments where millions of devices are connected to large scale distributed services.
Value of Standardization:
Although connectivity solutions currently exist to integrate these types of systems, the lack of a standardized messaging protocol to address the inherent constraints and fragmentation has become an inhibitor in growing markets. Standardization of an open protocol that addresses the technical and market requirements can overcome these inhibitors through:
• Choices. With a standard protocol, initial choices in devices, networks and suppliers, will not limit choices and adaptability in the future. A standard protocol that supports current and future device payload formats will support deployment, connectivity, and reconfiguration over a wide range of network and server characteristics.
• Flexible Integration. Even if highly effective, decoupling techniques between internal device infrastructure and external systems will not see widespread adoption without standardization. With devices and device controllers utilizing a standardized message protocol, a basic publish/subscribe model can support integration with a wide range of established messaging and event processing systems, allowing subscribers to effectively decouple from device and network APIs.
• Time to Market. Porting and supporting multiple protocols on multiple platforms tends to inhibit adoption in control and instrumentation systems, which are built using many variations of hardware and software platforms, device types, and networks. Providing an open protocol that scales well from critical embedded systems up to high volume enterprise transaction processing, and one that is data, platform and language independent, will shorten time to market and support new levels of integration.
• Skills. A standard, based on protocol and programming models familiar to both embedded and IT programming communities, will accelerate markets by building on skilled resources that already understand these types of solutions.
3. Scope of Work of the TC
The TC will accept the OASIS Standard MQTT Version 3.1.1 as its input specification. The TC will also accept as input a list of issues and recommended changes from the TC Members, incorporating appropriate additional contributions (such as the MQTT-SN specification) into the TC.
All contributions will be accepted for consideration without any prejudice or restrictions and evaluated based on technical merit in so far as they conform to this charter and its schedule.
The scope of the TC's work is limited to technical refinements of features organized into the following categories:
• Enhancements for Scalability and Large-Scale Systems including the ability to communicate functional levels, define optional functions, and control resource usage.
• Improved Error Reporting allowing error indications to be returned by both MQTT client and MQTT server with the definition of additional return values.
• Formalize commonly observed patterns including, but not limited to capability discovery, request-response, correlation.
• Extensibility Mechanisms enabling the addition of data fields on packets, including application-extensible data whose interpretation is not specified by MQTT.
• Performance Improvements to address constraints and bottlenecks discovered in previous versions.
• Additional support for Resource Constrained MQTT clients. There is growing demand for messaging solutions optimized for extremely constrained devices, often operating within data networks that have very low bandwidth and/or reliability. In some cases, the runtime environment is unable to support a TCP/IP layer. MQTT for Sensor Networks (MQTT-SN) is well suited to this problem space and is conceptually similar to MQTT. The TC will develop MQTT-SN as an OASIS standard work track product in order to extend the reach of MQTT in IoT solutions that include these constrained environments.
It is often expensive or impractical to immediately upgrade mobile and other field equipment in response to protocol updates. There needs to be a careful balance between feature enhancements and potential disruption to existing implementations.
The newer version of the standard will build on the previous version so that it is straightforward for existing implementations to support multiple versions.
This TC may also produce the following non-normative Committee Notes for the MQTT specification:
• A requirements and recommendations document for enhancements or issues deemed within in scope but which could not be included in the next version of the specification. These will be collected for consideration in a future version of the standardized specification.
• Primers or white papers describing usage examples, scenarios and/or best practices.
• Test scenario descriptions.
Out of Scope
Any proposal that does not contribute to one or more of the categories listed in the Scope of Work section is deemed out of scope. Furthermore, any proposal that cannot be completed within the deliverable milestone is deemed out of scope. The following items are specifically out of scope:
• The TC will not specify mappings of MQTT functions described in the specifications, to any programming language or particular messaging middleware.
• The TC will not produce reference implementations of the protocol.
• Except for the values and fields directly related to the MQTT protocol, the TC will not prescribe the payload format of messages that are published according to the specifications.
• The TC will not identify MQTT topics nor prescribe any mechanism or convention for classification of MQTT topics or topic spaces.
• Transport level security is assumed and no mandatory security features will be added.
Contributions to this TC which are out of scope for this charter may be accumulated and taken into consideration for potential development in a future charter.
Once the TC has completed work on a deliverable and it has become an OASIS Standard, the TC will enter "maintenance mode" for that deliverable.
The purpose of maintenance mode is to provide fixes to address ambiguity, inconsistencies and errors. The maintenance mode will not functionally enhance a previously adopted deliverable or extend its functionality.
The TC will collect issues raised against the deliverables and periodically process those issues. Issues that request or require new or enhanced functionality shall be marked as enhancement requests and set aside. Issues that result in the clarification or non-substantive correction of the deliverables shall be processed. The TC shall maintain a list of these adopted clarifications and may periodically create a new maintenance revision of the deliverables including these updates.
The TC will evaluate and review existing work products alongside any new issues raised.
The TC will prepare an initial Committee Specification Draft of MQTT-SN before the end of 2021.
The TC may advance OASIS standard versions of the MQTT protocols to ISO/IEC JTC 1 through the JTC 1 PAS Transposition Process.
5. IPR Mode
The TC shall operate under Non Assertion Terms.
6. Anticipated audience
• IoT developers, architects and designers building solutions, such as devices, edge-of-network servers/controllers, monitoring servers, embedded and control systems, embedded platforms, mobile and web applications, middleware and enterprise applications as well as network providers.
• System integrators at multiple levels, including but not limited to, integration with products and solutions from various wireless network providers and middleware suppliers.
• Companies offering next generation large scale distributed services for IoT scenarios
TC business will be conducted in English.