OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Form submission from: Request a Special Majority Vote to proceed to Candidate OASIS Standard

Submitted on Wednesday, October 24, 2018 - 13:49
Submitted by user:
Submitted values are:

Your name: Richard Coppen
TC name: Message Queuing Telemetry Transport (MQTT)
TC email address: mqtt@lists.oasis-open.org
Title: MQTT Version 5.0 Committee Specification 02
Committee Specification URI:
Committee Specification editable source URI(s):
Certification by the TC that all schema and XML instances are well-formed and
that expressions are valid: We so certify
Clear English-language summary of the specification:
MQTT is a Client Server publish/subscribe messaging transport protocol. It is
light weight, open, simple, and designed to be easy to implement. These
characteristics make it ideal for use in many situations, including
environments such as for communication in Machine to Machine (M2M) and
of Things (IoT) contexts where a small code footprint is required and/or
bandwidth is at a premium.
The protocol runs over TCP/IP, or over other network protocols that provide
ordered, lossless, bi-directional connections. Its features include:
         Use of the publish/subscribe message pattern which provides
one-to-many message distribution and decoupling of applications.
         A messaging transport that is agnostic to the content of the
         Three qualities of service for message delivery:
o    "At most once", where messages are delivered according to the best
of the operating environment. Message loss can occur. This level could be
for example, with ambient sensor data where it does not matter if an
reading is lost as the next one will be published soon after.
o    "At least once", where messages are assured to arrive but duplicates can
o    "Exactly once", where messages are assured to arrive exactly once. This
level could be used, for example, with billing systems where duplicate or
messages could lead to incorrect charges being applied.
         A small transport overhead and protocol exchanges minimized to
network traffic.
         A mechanism to notify interested parties when an abnormal
disconnection occurs.
Relationship of this specification to similar work:
This specification replaces or supersedes:
         MQTT Version 3.1.1. Edited by Andrew Banks and Rahul Gupta. 29
October 2014. OASIS Standard.
This specification is related to:
         MQTT and the NIST Cybersecurity Framework Version 1.0. Edited by
Geoff Brown and Louis-Philippe Lamoureux. Latest version:
     --Statements of Use--
       Link to Statement of Use #1:

       Link to Statement of Use #2:

       Link to Statement of Use #3:
       Additional Statements of Use:

     --Public Reviews--
       First public review announcement URI:

       Comment resolution log:

       Additional public review announcement URIs:
       Additional comment resolution log URIs: http://

Approval link:
Earlier attempts to standardize: No
Sources of explanatory information:

The results of this submission may be viewed at:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]