ISO/IEC 20922:2016

Information technology — Message Queuing Telemetry Transport (MQTT) v3.1.1

ISO/IEC 20922:2016 is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network 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 payload. Three qualities of service for message delivery: "At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after. "At least once", where messages are assured to arrive but duplicates can occur. "Exactly once", where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.

Technologies de l'information — Transport par télémesure des messages en file d’attente (MQTT) v3.1.1

General Information

• Status: Published
• Publication Date: 07-Jun-2016
• ICS: 35.100.70 - Application layer
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9060 - Close of review
• Start Date: 02-Dec-2026

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 20922
First edition
2016-06-15
Information technology — Message
Queuing Telemetry Transport (MQTT)
v3.1.1
Technologies de l'information — Transport par télémesure des
messages en file d’attente (MQTT) v3.1.1
Reference number
ISO/IEC 20922:2016(E)
©
ISO/IEC 2016

---------------------- Page: 1 ----------------------
ISO/IEC 20922:2016(E)
COPYRIGHT PROTECTED DOCUMENT
©  ISO/IEC 2016
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any
means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2016 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 20922:2016(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of
document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any
patent rights identified during the development of the document will be in the Introduction and/or on the ISO
list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO's adherence to the WTO principles in the Technical Barriers to Trade (TBT),
see the following URL: Foreword — Supplementary information.
ISO/IEC 20922:2016 was prepared by the OASIS Message Queuing Telemetry Transport (MQTT)
Technical Committee and was adopted, under the PAS procedure, by Joint Technical Committee ISO/IEC
JTC 1, Information technology, in parallel with its approval by the national bodies of ISO and IEC.
© ISO/IEC 2016 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 20922:2016(E)

MQTT Version 3.1.1
OASIS Standard
29 October 2014
Specification URIs
This version:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.doc (Authoritative)
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.pdf
Previous version:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/cos01/mqtt-v3.1.1-cos01.doc (Authoritative)
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/cos01/mqtt-v3.1.1-cos01.html
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/cos01/mqtt-v3.1.1-cos01.pdf
Latest version:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.doc (Authoritative)
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.pdf
Technical Committee:
OASIS Message Queuing Telemetry Transport (MQTT) TC
Chairs:
Raphael J Cohn ([e-mail]), Individual
Richard J Coppen ([e-mail]), IBM
Editors:
Andrew Banks ([e-mail]), IBM
Rahul Gupta ([e-mail]), IBM
Related work:
This specification is related to:
MQTT and the NIST Cybersecurity Framework Version 1.0. Edited by Geoff Brown and
Louis-Philippe Lamoureux. Latest version: http://docs.oasis-open.org/mqtt/mqtt-nist-
cybersecurity/v1.0/mqtt-nist-cybersecurity-v1.0.html.
Abstract:
MQTT is a Client Server publish/subscribe messaging transport protocol. It is light weight, open,
simple, and designed so as to be easy to implement. These characteristics make it ideal for use
in many situations, including constrained environments such as for communication in Machine to
Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required
and/or network 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 payload.
Three qualities of service for message delivery:
mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 1 of 81
© ISO/IEC 2016 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 20922:2016(E)
"At most once", where messages are delivered according to the best efforts of the
operating environment. Message loss can occur. This level could be used, for
example, with ambient sensor data where it does not matter if an individual reading is
lost as the next one will be published soon after.
"At least once", where messages are assured to arrive but duplicates can occur.
"Exactly once", where message are assured to arrive exactly once. This level could
be used, for example, with billing systems where duplicate or lost messages could
lead to incorrect charges being applied.
A small transport overhead and protocol exchanges minimized to reduce network traffic.
A mechanism to notify interested parties when an abnormal disconnection occurs.
Status:
This document was last revised or approved by the membership of OASIS on the above date.
The level of approval is also listed above. Check the “Latest version” location noted above for
possible later revisions of this document. Any other numbered Versions and other technical work
produced by the Technical Committee (TC) are listed at https://www.oasis-
open.org/committees/tc_home.php?wg_abbrev=mqtt#technical.
TC members should send comments on this specification to the TC’s email list. Others should
send comments to the TC’s public comment list, after subscribing to it by following the
instructions at the “Send A Comment” button on the TC’s web page at https://www.oasis-
open.org/committees/mqtt/.
For information on whether any patents have been disclosed that may be essential to
implementing this specification, and any offers of patent licensing terms, please refer to the
Intellectual Property Rights section of the Technical Committee web page (https://www.oasis-
open.org/committees/mqtt/ipr.php).
Citation format:
When referencing this specification the following citation format should be used:
[mqtt-v3.1.1]
MQTT Version 3.1.1. Edited by Andrew Banks and Rahul Gupta. 29 October 2014. OASIS
Standard. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html. Latest version:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html.

mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 2 of 81
© ISO/IEC 2016 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 20922:2016(E)
Notices
Copyright © OASIS Open 2014. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual
Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that
comment on or otherwise explain it or assist in its implementation may be prepared, copied, published,
and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice
and this section are included on all such copies and derivative works. However, this document itself may
not be modified in any way, including by removing the copyright notice or references to OASIS, except as
needed for the purpose of developing any document or deliverable produced by an OASIS Technical
Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must
be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors
or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would
necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard,
to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to
such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that
produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of
any patent claims that would necessarily be infringed by implementations of this specification by a patent
holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR
Mode of the OASIS Technical Committee that produced this specification. OASIS may include such
claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that
might be claimed to pertain to the implementation or use of the technology described in this document or
the extent to which any license under such rights might or might not be available; neither does it
represent that it has made any effort to identify any such rights. Information on OASIS' procedures with
respect to rights in any document or deliverable produced by an OASIS Technical Committee can be
found on the OASIS website. Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an attempt made to obtain a general license
or permission for the use of such proprietary rights by implementers or users of this OASIS Committee
Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no
representation that any information or list of intellectual property rights will at any time be complete, or
that any claims in such list are, in fact, Essential Claims.
The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be
used only to refer to the organization and its official outputs. OASIS welcomes reference to, and
implementation and use of, specifications, while reserving the right to enforce its marks against
misleading uses. Please see https://www.oasis-open.org/policies-guidelines/trademark for above
guidance.

mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 3 of 81
© ISO/IEC 2016 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 20922:2016(E)
Table of Contents
1 Introduction . 9
1.1 Organization of MQTT . 9
1.2 Terminology . 9
1.3 Normative references . 10
1.4 Non normative references . 11
1.5 Data representations . 13
1.5.1 Bits . 13
1.5.2 Integer data values . 13
1.5.3 UTF-8 encoded strings . 13
1.6 Editing conventions . 15
2 MQTT Control Packet format . 16
2.1 Structure of an MQTT Control Packet . 16
2.2 Fixed header . 16
2.2.1 MQTT Control Packet type . 16
2.2.2 Flags . 17
2.2.3 Remaining Length . 18
2.3 Variable header . 19
2.3.1 Packet Identifier . 20
2.4 Payload . 21
3 MQTT Control Packets . 23
3.1 CONNECT – Client requests a connection to a Server . 23
3.1.1 Fixed header. 23
3.1.2 Variable header . 23
3.1.3 Payload . 29
3.1.4 Response . 30
3.2 CONNACK – Acknowledge connection request . 31
3.2.1 Fixed header. 31
3.2.2 Variable header . 31
3.2.3 Payload . 33
3.3 PUBLISH – Publish message . 33
3.3.1 Fixed header. 33
3.3.2 Variable header . 35
3.3.3 Payload . 36
3.3.4 Response . 36
3.3.5 Actions . 36
3.4 PUBACK – Publish acknowledgement . 37
3.4.1 Fixed header. 37
3.4.2 Variable header . 37
3.4.3 Payload . 37
3.4.4 Actions . 37
3.5 PUBREC – Publish received (QoS 2 publish received, part 1) . 37
3.5.1 Fixed header. 38
3.5.2 Variable header . 38
mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 4 of 81
© ISO/IEC 2016 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 20922:2016(E)
3.5.3 Payload . 38
3.5.4 Actions . 38
3.6 PUBREL – Publish release (QoS 2 publish received, part 2). 38
3.6.1 Fixed header. 38
3.6.2 Variable header . 39
3.6.3 Payload . 39
3.6.4 Actions . 39
3.7 PUBCOMP – Publish complete (QoS 2 publish received, part 3) . 39
3.7.1 Fixed header. 39
3.7.2 Variable header . 40
3.7.3 Payload . 40
3.7.4 Actions . 40
3.8 SUBSCRIBE - Subscribe to topics . 40
3.8.1 Fixed header. 40
3.8.2 Variable header . 40
3.8.3 Payload . 41
3.8.4 Response . 42
3.9 SUBACK – Subscribe acknowledgement . 43
3.9.1 Fixed header. 44
3.9.2 Variable header . 44
3.9.3 Payload . 44
3.10 UNSUBSCRIBE – Unsubscribe from topics . 45
3.10.1 Fixed header. 45
3.10.2 Variable header . 45
3.10.3 Payload . 46
3.10.4 Response . 46
3.11 UNSUBACK – Unsubscribe acknowledgement. 47
3.11.1 Fixed header. 47
3.11.2 Variable header . 47
3.11.3 Payload . 48
3.12 PINGREQ – PING request . 48
3.12.1 Fixed header. 48
3.12.2 Variable header . 48
3.12.3 Payload . 48
3.12.4 Response . 48
3.13 PINGRESP – PING response . 48
3.13.1 Fixed header. 48
3.13.2 Variable header . 49
3.13.3 Payload . 49
3.14 DISCONNECT – Disconnect notification . 49
3.14.1 Fixed header. 49
3.14.2 Variable header . 49
3.14.3 Payload . 49
3.14.4 Response . 49
4 Operational behavior . 51
mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 5 of 81
© ISO/IEC 2016 – All rights reserved

---------------------- Page: 8 ----------------------
ISO/IEC 20922:2016(E)
4.1 Storing state . 51
4.1.1 Non normative example . 51
4.2 Network Connections . 52
4.3 Quality of Service levels and protocol flows . 52
4.3.1 QoS 0: At most once delivery . 52
4.3.2 QoS 1: At least once delivery . 53
4.3.3 QoS 2: Exactly once delivery . 54
4.4 Message delivery retry . 55
4.5 Message receipt . 56
4.6 Message ordering . 56
4.7 Topic Names and Topic Filters . 57
4.7.1 Topic wildcards . 57
4.7.2 Topics beginning with $ . 58
4.7.3 Topic semantic and usage . 58
4.8 Handling errors . 59
5 Security . 60
5.1 Introduction . 60
5.2 MQTT solutions: security and certification . 60
5.3 Lightweight cryptography and constrained devices . 61
5.4 Implementation notes . 61
5.4.1 Authentication of Clients by the Server . 61
5.4.2 Authorization of Clients by the Server . 61
5.4.3 Authentication of the Server by the Client . 61
5.4.4 Integrity of Application Messages and Control Packets . 62
5.4.5 Privacy of Application Messages and Control Packets . 62
5.4.6 Non-repudiation of message transmission . 62
5.4.7 Detecting compromise of Clients and Servers . 62
5.4.8 Detecting abnormal behaviors. 63
5.4.9 Other security considerations .
...

DRAFT INTERNATIONAL STANDARD ISO/IEC 20922
Attributed to ISO/IEC JTC 1 by the Central Secretariat (see page iii)

Voting begins on Voting terminates on
2015-10-07 2016-01-07
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION  МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ  ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION  МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОММИСИЯ  COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE


PUBLICLY AVAILABLE SPECIFICATION PROCEDURE
Information technology — Message Queuing Telemetry
Transport (MQTT) v3.1.1

ICS 35.100.70


This Publicly Available Specification (PAS) is being submitted for Fast-track processing in
accordance with the provisions of ISO/IEC JTC 1 Directives.


THIS DOCUMENT IS A DRAFT CIRCULATED FOR COMMENT AND APPROVAL. IT IS THEREFORE SUBJECT TO CHANGE AND MAY NOT BE
REFERRED TO AS AN INTERNATIONAL STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL, TECHNOLOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME
STANDARDS TO WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS.
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT, WITH THEIR COMMENTS, NOTIFICATION OF ANY RELEVANT PATENT RIGHTS OF WHICH
THEY ARE AWARE AND TO PROVIDE SUPPORTING DOCUMENTATION.
International Organization for Standardization, 2015
©
International Electrotechnical Commission, 2015

---------------------- Page: 1 ----------------------
ISO/IEC DIS 20922

COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2015
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any
means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2015 — All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC DIS 20922
NOTE FROM ITTF
The ballot on the transposition of a PAS into an International Standard follows the JTC 1 PAS procedures
contained in the JTC 1 Supplement, F.3.
Reflecting the importance of the PAS process, the JTC 1 secretariat shall also inform JTC 1 national bodies
and Liaison Organisations, and those organisations authorized to be PAS submitters, of the initiation of any
PAS ballot, the results of the ballot, and the identity of the JTC 1 subcommittee which will be responsible for
any future work.
For ballot, JTC 1 National Bodies and the PAS Submitter shall receive both the PAS to be transposed and the
accompanying Explanatory Report. During the ballot JTC 1 members may propose changes to the PAS.
These can be resolved with the PAS Submitter after completion of the ballot.
The period for combined DIS voting shall be five months. In order to be accepted the DIS must be supported
by 75 % of the votes cast (abstention is not counted as a vote) and by two-thirds of the P-members voting of
JTC 1.
In the case of a failure of the ballot, JTC 1 shall make known to the Submitter the reasons which have led to
the negative result. Based on this information, the Submitter may choose to re-submit a modified specification
as a new PAS submission.
Once the Draft International Standard has been approved by JTC 1, it shall progress to the approval stage
(FDIS).

© ISO/IEC 2015 — All rights reserved iii

---------------------- Page: 3 ----------------------
MQTT Version 3.1.1
OASIS Standard
29 October 2014
Specification URIs
This version:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.doc (Authoritative)
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.pdf
Previous version:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/cos01/mqtt-v3.1.1-cos01.doc (Authoritative)
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/cos01/mqtt-v3.1.1-cos01.html
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/cos01/mqtt-v3.1.1-cos01.pdf
Latest version:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.doc (Authoritative)
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.pdf
Technical Committee:
OASIS Message Queuing Telemetry Transport (MQTT) TC
Chairs:
Raphael J Cohn ([e-mail]), Individual
Richard J Coppen ([e-mail]), IBM
Editors:
Andrew Banks ([e-mail]), IBM
Rahul Gupta ([e-mail]), IBM
Related work:
This specification is related to:
MQTT and the NIST Cybersecurity Framework Version 1.0. Edited by Geoff Brown and
Louis-Philippe Lamoureux. Latest version: http://docs.oasis-open.org/mqtt/mqtt-nist-
cybersecurity/v1.0/mqtt-nist-cybersecurity-v1.0.html.
Abstract:
MQTT is a Client Server publish/subscribe messaging transport protocol. It is light weight, open,
simple, and designed so as to be easy to implement. These characteristics make it ideal for use
in many situations, including constrained environments such as for communication in Machine to
Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required
and/or network 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 payload.
Three qualities of service for message delivery:
mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 1 of 81

---------------------- Page: 4 ----------------------
"At most once", where messages are delivered according to the best efforts of the
operating environment. Message loss can occur. This level could be used, for
example, with ambient sensor data where it does not matter if an individual reading is
lost as the next one will be published soon after.
"At least once", where messages are assured to arrive but duplicates can occur.
"Exactly once", where message are assured to arrive exactly once. This level could
be used, for example, with billing systems where duplicate or lost messages could
lead to incorrect charges being applied.
A small transport overhead and protocol exchanges minimized to reduce network traffic.
A mechanism to notify interested parties when an abnormal disconnection occurs.
Status:
This document was last revised or approved by the membership of OASIS on the above date.
The level of approval is also listed above. Check the “Latest version” location noted above for
possible later revisions of this document. Any other numbered Versions and other technical work
produced by the Technical Committee (TC) are listed at https://www.oasis-
open.org/committees/tc_home.php?wg_abbrev=mqtt#technical.
TC members should send comments on this specification to the TC’s email list. Others should
send comments to the TC’s public comment list, after subscribing to it by following the
instructions at the “Send A Comment” button on the TC’s web page at https://www.oasis-
open.org/committees/mqtt/.
For information on whether any patents have been disclosed that may be essential to
implementing this specification, and any offers of patent licensing terms, please refer to the
Intellectual Property Rights section of the Technical Committee web page (https://www.oasis-
open.org/committees/mqtt/ipr.php).
Citation format:
When referencing this specification the following citation format should be used:
[mqtt-v3.1.1]
MQTT Version 3.1.1. Edited by Andrew Banks and Rahul Gupta. 29 October 2014. OASIS
Standard. http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html. Latest version:
http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html.

mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 2 of 81

---------------------- Page: 5 ----------------------
Notices
Copyright © OASIS Open 2014. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual
Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that
comment on or otherwise explain it or assist in its implementation may be prepared, copied, published,
and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice
and this section are included on all such copies and derivative works. However, this document itself may
not be modified in any way, including by removing the copyright notice or references to OASIS, except as
needed for the purpose of developing any document or deliverable produced by an OASIS Technical
Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must
be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors
or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would
necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard,
to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to
such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that
produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of
any patent claims that would necessarily be infringed by implementations of this specification by a patent
holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR
Mode of the OASIS Technical Committee that produced this specification. OASIS may include such
claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that
might be claimed to pertain to the implementation or use of the technology described in this document or
the extent to which any license under such rights might or might not be available; neither does it
represent that it has made any effort to identify any such rights. Information on OASIS' procedures with
respect to rights in any document or deliverable produced by an OASIS Technical Committee can be
found on the OASIS website. Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an attempt made to obtain a general license
or permission for the use of such proprietary rights by implementers or users of this OASIS Committee
Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no
representation that any information or list of intellectual property rights will at any time be complete, or
that any claims in such list are, in fact, Essential Claims.
The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be
used only to refer to the organization and its official outputs. OASIS welcomes reference to, and
implementation and use of, specifications, while reserving the right to enforce its marks against
misleading uses. Please see https://www.oasis-open.org/policies-guidelines/trademark for above
guidance.

mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 3 of 81

---------------------- Page: 6 ----------------------
Table of Contents
1 Introduction . 9
1.1 Organization of MQTT . 9
1.2 Terminology . 9
1.3 Normative references . 10
1.4 Non normative references . 11
1.5 Data representations . 13
1.5.1 Bits . 13
1.5.2 Integer data values . 13
1.5.3 UTF-8 encoded strings . 13
1.6 Editing conventions . 15
2 MQTT Control Packet format . 16
2.1 Structure of an MQTT Control Packet . 16
2.2 Fixed header . 16
2.2.1 MQTT Control Packet type . 16
2.2.2 Flags . 17
2.2.3 Remaining Length . 18
2.3 Variable header . 19
2.3.1 Packet Identifier . 20
2.4 Payload . 21
3 MQTT Control Packets . 23
3.1 CONNECT – Client requests a connection to a Server . 23
3.1.1 Fixed header. 23
3.1.2 Variable header . 23
3.1.3 Payload . 29
3.1.4 Response . 30
3.2 CONNACK – Acknowledge connection request . 31
3.2.1 Fixed header. 31
3.2.2 Variable header . 31
3.2.3 Payload . 33
3.3 PUBLISH – Publish message . 33
3.3.1 Fixed header. 33
3.3.2 Variable header . 35
3.3.3 Payload . 36
3.3.4 Response . 36
3.3.5 Actions . 36
3.4 PUBACK – Publish acknowledgement . 37
3.4.1 Fixed header. 37
3.4.2 Variable header . 37
3.4.3 Payload . 37
3.4.4 Actions . 37
3.5 PUBREC – Publish received (QoS 2 publish received, part 1) . 37
3.5.1 Fixed header. 38
3.5.2 Variable header . 38
mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 4 of 81

---------------------- Page: 7 ----------------------
3.5.3 Payload . 38
3.5.4 Actions . 38
3.6 PUBREL – Publish release (QoS 2 publish received, part 2). 38
3.6.1 Fixed header. 38
3.6.2 Variable header . 39
3.6.3 Payload . 39
3.6.4 Actions . 39
3.7 PUBCOMP – Publish complete (QoS 2 publish received, part 3) . 39
3.7.1 Fixed header. 39
3.7.2 Variable header . 40
3.7.3 Payload . 40
3.7.4 Actions . 40
3.8 SUBSCRIBE - Subscribe to topics . 40
3.8.1 Fixed header. 40
3.8.2 Variable header . 40
3.8.3 Payload . 41
3.8.4 Response . 42
3.9 SUBACK – Subscribe acknowledgement . 43
3.9.1 Fixed header. 44
3.9.2 Variable header . 44
3.9.3 Payload . 44
3.10 UNSUBSCRIBE – Unsubscribe from topics . 45
3.10.1 Fixed header. 45
3.10.2 Variable header . 45
3.10.3 Payload . 46
3.10.4 Response . 46
3.11 UNSUBACK – Unsubscribe acknowledgement. 47
3.11.1 Fixed header. 47
3.11.2 Variable header . 47
3.11.3 Payload . 48
3.12 PINGREQ – PING request . 48
3.12.1 Fixed header. 48
3.12.2 Variable header . 48
3.12.3 Payload . 48
3.12.4 Response . 48
3.13 PINGRESP – PING response . 48
3.13.1 Fixed header. 48
3.13.2 Variable header . 49
3.13.3 Payload . 49
3.14 DISCONNECT – Disconnect notification . 49
3.14.1 Fixed header. 49
3.14.2 Variable header . 49
3.14.3 Payload . 49
3.14.4 Response . 49
4 Operational behavior . 51
mqtt-v3.1.1-os 29 October 2014
Standards Track Work Product Copyright © OASIS Open 2014. All Rights Reserved. Page 5 of 81

---------------------- Page: 8 ----------------------
4.1 Storing state . 51
4.1.1 Non normative example . 51
4.2 Network Connections . 52
4.3 Quality of Service levels and protocol flows . 52
4.3.1 QoS 0: At most once delivery . 52
4.3.2 QoS 1: At least once delivery . 53
4.3.3 QoS 2: Exactly once delivery . 54
4.4 Message delivery retry . 55
4.5 Message receipt . 56
4.6 Message ordering . 56
4.7 Topic Names and Topic Filters . 57
4.7.1 Topic wildcards . 57
4.7.2 Topics beginning with $ . 58
4.7.3 Topic semantic and usage . 58
4.8 Handling errors . 59
5 Security . 60
5.1 Introduction . 60
5.2 MQTT solutions: security and certification . 60
5.3 Lightweight cryptography and constrained devices . 61
5.4 Implementation notes . 61
5.4.1 Authentication of Clients by the Server . 61
5.4.2 Authorization of Clients by the Server . 61
5.4.3 Authentication of the Server by the Client . 61
5.4.4 Integrity of Application Messages and Control Packets . 62
5.4.5 Privacy of Application Messages and Control Packets . 62
5.4.6 Non-repudiation of message transmission . 62
5.4.7 Detecting compromise of Clients and Servers . 62
5.4.8 Detecting abnormal behaviors. 63
5.4.9 Other secur
...