ISO/IEC 19464:2014

Information technology - Advanced Message Queuing Protocol (AMQP) v1.0 specification

ISO/IEC 19464:2014 defines the Advanced Message Queuing Protocol (AMQP), an open internet protocol for business messaging. It defines a binary wire-level protocol that allows for the reliable exchange of business messages between two parties. AMQP has a layered architecture and the specification is organized as a set of parts that reflects that architecture. Part 1 defines the AMQP type system and encoding. Part 2 defines the AMQP transport layer, an efficient, binary, peer-to-peer protocol for transporting messages between two processes over a network. Part 3 defines the AMQP message format, with a concrete encoding. Part 4 defines how interactions can be grouped within atomic transactions. Part 5 defines the AMQP security layers.

Technologies de l'information — Spécification du protocole avancé de mise en file d'attente de messages (AMPQ) v1.0

General Information

• Status: Published
• Publication Date: 28-Apr-2014
• ICS: 35.100.70 - Application layer
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9093 - International Standard confirmed
• Start Date: 10-May-2025
• Completion Date: 30-Oct-2025

Relations

• Consolidated By: ISO 13365-2:2020 - Leather - Chemical determination of the preservative (TCMTB, PCMC, OPP, OIT) content in leather by liquid chromatography - Part 2: Artificial perspiration extraction method
• Effective Date: 06-Jun-2022

Overview

ISO/IEC 19464:2014 specifies the Advanced Message Queuing Protocol (AMQP) v1.0 - an open, binary, wire-level internet protocol for reliable business messaging. Published in 2014, the standard defines a layered architecture for exchanging messages between two processes over a network. The ISO publication includes PDF and machine-readable forms (HTML, XML, DTD) of the OASIS AMQP v1.0 specification.

Key topics and requirements

• Layered architecture: The specification is organized into parts that map to protocol layers, enabling modular implementation and interoperability.
• Type system & encoding (Part 1): Defines the AMQP type system and concrete encoding rules for representing data on the wire.
• Transport layer (Part 2): Describes an efficient, binary, peer-to-peer transport for moving messages between processes; focuses on reliability and low-overhead delivery.
• Message format (Part 3): Specifies the structure and concrete encoding of AMQP messages to ensure consistent interpretation across implementations.
• Transactions (Part 4): Defines how interactions can be grouped into atomic transactions for guaranteed message processing semantics.
• Security layers (Part 5): Details security mechanisms and layers applicable to the protocol to protect message integrity, confidentiality, and authentication.
• Interoperability requirement: Emphasizes consistent wire-level behavior so different vendors’ implementations can interoperate.

Applications

ISO/IEC 19464:2014 and AMQP v1.0 are suited for systems requiring robust, interoperable, and standardized message exchange:

• Enterprise messaging and message-oriented middleware (MOM)
• Financial services and trading platforms requiring reliable delivery and transactional semantics
• Distributed systems and microservices communication across heterogeneous environments
• Integration platforms, brokers, and middleware vendors implementing cross-vendor messaging
• IoT gateways and telemetry systems that need a compact, binary protocol with defined type/encoding

Who uses this standard

• Enterprise architects and systems integrators designing messaging infrastructures
• Middleware and broker vendors implementing AMQP-compliant products
• Application developers building interoperable, transactional messaging applications
• Security engineers applying protocol-level security and compliance controls
• QA and interoperability test teams validating conformance to the AMQP wire protocol

Related standards

• The ISO/IEC 19464 package references the OASIS AMQP v1.0 XML and HTML materials included on the CD-ROM.
• Other messaging protocols and standards (for comparison/choice) include MQTT, STOMP, and JMS-based specifications; selection depends on use case, performance, and interoperability needs.

Keywords: ISO/IEC 19464, AMQP v1.0, Advanced Message Queuing Protocol, binary wire-level protocol, message format, transport layer, transactions, security, enterprise messaging.

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 19464
First edition
2014-05-01
Information technology — Advanced
Message Queuing Protocol (AMQP) v1.0
specification
Technologies de l'information — Spécification du protocole avancé de
mise en file d'attente de messages (AMPQ) v1.0

Reference number
©
ISO/IEC 2014
This CD-ROM contains:
1) the publication ISO/IEC 19464:2014 in portable document format (PDF), which can be viewed using
Adobe® Acrobat® Reader;
2) HTML, XML and DTD versions of the OASIS Advanced Message Queuing Protocol (AMQP)
Version 1.0.
Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

©  ISO/IEC 2014
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 2014 – All rights reserved

Installation
If this publication has been packaged as a zipped file, do NOT open the file from the CD-ROM, but co
...

INTERNATIONAL ISO/IEC
STANDARD 19464
First edition
2014-05-01
Information technology — Advanced
Message Queuing Protocol (AMQP) v1.0
specification
Technologies de l'information — Spécification du protocole avancé de
mise en file d'attente de messages (AMPQ) v1.0

Reference number
©
ISO/IEC 2014
©  ISO/IEC 2014
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 2014 – All rights reserved

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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
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.
ISO/IEC 19464 was prepared by the OASIS Advanced Message Queuing Protocol Technical Committee (as
OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0) 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 2014 – All rights reserved iii

OASIS Advanced Message Queuing Protocol
(AMQP) Version 1.0
OASIS Standard
29 October 2012
Specification URIs
This version:
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.html
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-complete-v1.0-os.pdf
Previous version:
http://docs.oasis-open.org/amqp/core/v1.0/csprd01/amqp-core-overview-v1.0-csprd01.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/csprd01/amqp-core-overview-v1.0-csprd01.html
http://docs.oasis-open.org/amqp/core/v1.0/csprd01/amqp-core-complete-v1.0-csprd01.pdf
Latest version:
http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-overview-v1.0.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-overview-v1.0.html
http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf
Technical Committee:
OASIS Advanced Message Queuing Protocol (AMQP) TC
Chairs:
Ram Jeyaraman ([e-mail]), Microsoft
Angus Telfer ([e-mail]), INETCO Systems
Editors:
Robert Godfrey ([e-mail]), JPMorgan Chase & Co.
David Ingham ([e-mail]), Microsoft
Rafael Schloming ([e-mail]), Red Hat
© ISO/IEC 2014 – All rights reserved

Additional artifacts:
This specification consists of the following documents:
 Part 0: Overview - Overview of the AMQP specification
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.html
 Part 1: Types - AMQP type system and encoding
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-types-v1.0-os.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-types-v1.0-os.html
 Part 2: Transport - AMQP transport layer
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html
 Part 3: Messaging - AMQP Messaging Layer
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html
 Part 4: Transactions - AMQP Transactions Layer
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transactions-v1.0-os.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transactions-v1.0-os.html
 Part 5: Security - AMQP Security Layers
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-security-v1.0-os.xml (Authoritative)
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-security-v1.0-os.html
 XML Document Type Definition (DTD)
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp.dtd (Authoritative)
Related work:
This specification replaces or supersedes:
 AMQP v1.0 Final, 07 October 2011. http://www.amqp.org/specification/1.0/amqp-org-download
Abstract:
The Advanced Message Queuing Protocol (AMQP) is an open internet protocol for business messaging. It defines a binary
wire-level protocol that allows for the reliable exchange of business messages between two parties. AMQP has a layered
architecture and the specification is organized as a set of parts that reflects that architecture. Part 1 defines the AMQP type
system and encoding. Part 2 defines the AMQP transport layer, an efficient, binary, peer-to-peer protocol for transporting
messages between two processes over a network. Part 3 defines the AMQP message format, with a concrete encoding. Part
4 defines how interactions can be grouped within atomic transactions. Part 5 defines the AMQP security layers.
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.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others
should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web
page at http://www.oasis-open.org/committees/amqp/.
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
(http://www.oasis-open.org/committees/amqp/ipr.php).
Citation format:
When referencing this specification the following citation format should be used:
[amqp-core-complete-v1.0]
OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0. 29 October 2012. OASIS Standard.
http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-complete-v1.0-os.pdf.
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 1 of 124
© ISO/IEC 2014 – All rights reserved

Notices:
c
Copyright
OASIS Open 2012. 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 WAR-
RANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFOR-
MATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABIL-
ITY 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, specifi-
cations, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/
policies-guidelines/trademark for above guidance.
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 2 of 124
© ISO/IEC 2014 – All rights reserved

Contents
0 Overview 7
0.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
0.1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
0.1.2 Normative References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
0.1.3 Non-normative References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
0.2 Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
0.3 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
0.4 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1 Types 16
1.1 Type System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.1.1 Primitive Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.1.2 Described Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.1.3 Composite Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.1.4 Restricted Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2 Type Encodings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.1 Fixed Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.2.2 Variable Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.2.3 Compound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.2.4 Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.3 Type Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.3.1 Primitive Type Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.3.2 Composite Type Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.3.3 Descriptor Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.3.4 Field Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.3.5 Restricted Type Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.4 Composite Type Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.5 Descriptor Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.6 Primitive Type Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.6.1 null . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.6.2 boolean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.6.3 ubyte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.6.4 ushort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.6.5 uint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.6.6 ulong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.6.7 byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.6.8 short . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.6.9 int . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.6.10 long . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.6.11 float . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.6.12 double . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.6.13 decimal32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.6.14 decimal64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.6.15 decimal128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.6.16 char . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.6.17 timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.6.18 uuid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.6.19 binary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.6.20 string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 3 of 124
© ISO/IEC 2014 – All rights reserved

1.6.21 symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.6.22 list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.6.23 map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.6.24 array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2 Transport 31
2.1 Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.1.1 Conceptual Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.1.2 Communication Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.1.3 Protocol Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.2 Version Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.3 Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.3.1 Frame Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.3.2 AMQP Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.4 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.4.1 Opening A Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.4.2 Pipelined Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.4.3 Closing A Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.4.4 Simultaneous Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.4.5 Idle Timeout Of A Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.4.6 Connection States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.4.7 Connection State Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.5 Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.5.1 Establishing A Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5.2 Ending A Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5.3 Simultaneous End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.4 Session Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.5 Session States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.5.6 Session Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.6 Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.6.1 Naming A Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.6.2 Link Handles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.6.3 Establishing Or Resuming A Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.6.4 Detaching And Reattaching A Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.6.5 Link Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.6.6 Closing A Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.6.7 Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.6.8 Synchronous Get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.6.9 Asynchronous Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.6.10 Stopping A Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.6.11 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.6.12 Transferring A Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.6.13 Resuming Deliveries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.6.14 Transferring Large Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.7 Performatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.7.1 Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.7.2 Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.7.3 Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.7.4 Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.7.5 Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.7.6 Disposition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.7.7 Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.7.8 End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.7.9 Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.8 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 4 of 124
© ISO/IEC 2014 – All rights reserved

2.8.1 Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.8.2 Sender Settle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.8.3 Receiver Settle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.8.4 Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.8.5 Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.8.6 Milliseconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.8.7 Delivery Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.8.8 Delivery Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.8.9 Transfer Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.8.10 Sequence No . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.8.11 Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.8.12 IETF Language Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.8.13 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.8.14 Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
2.8.15 AMQP Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
2.8.16 Connection Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.8.17 Session Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2.8.18 Link Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2.8.19 Constant Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3 Messaging 81
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.2 Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.2.1 Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
3.2.2 Delivery Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
3.2.3 Message Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.2.4 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.2.5 Application Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.2.6 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.2.7 AMQP Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.2.8 AMQP Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.2.9 Footer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.2.10 Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.2.11 Message ID ULong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.2.12 Message ID UUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.2.13 Message ID Binary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.2.14 Message ID String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.2.15 Address String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.2.16 Constant Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.3 Distribution Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.4 Delivery State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.4.1 Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
3.4.2 Accepted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
3.4.3 Rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.4.4 Released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.4.5 Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.4.6 Resuming Deliveries Using Delivery States . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
3.5 Sources and Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.5.1 Filtering Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.5.2 Distribution Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.5.3 Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
3.5.4 Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.5.5 Terminus Durability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.5.6 Terminus Expiry Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.5.7 Standard Distribution Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 5 of 124
© ISO/IEC 2014 – All rights reserved

3.5.8 Filter Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.5.9 Node Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.5.10 Delete On Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.5.11 Delete On No Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.5.12 Delete On No Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.5.13 Delete On No Links Or Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4 Transactions 102
4.1 Transactional Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.2 Declaring a Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.3 Discharging a Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.4 Transactional Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4.4.1 Transactional Posting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4.4.2 Transactional Retirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4.4.3 Transactional Acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.4.4 Interaction Of Settlement With Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.4.4.1 Transactional Posting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.4.4.2 Transactional Retirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.4.4.3 Transactional Acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.5 Coordination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.5.1 Coordinator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.5.2 Declare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.5.3 Discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.5.4 Transaction ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.5.5 Declared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.5.6 Transactional State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.5.7 Transaction Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.5.8 Transaction Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5 Security 112
5.1 Security Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.2 TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.2.1 Alternative Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.2.2 Constant Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.3 SASL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.3.1 SASL Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.3.2 SASL Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.3.3 Security Frame Bodies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.3.3.1 SASL Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.3.3.2 SASL Init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.3.3.3 SASL Challenge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.3.3.4 SASL Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.3.3.5 SASL Outcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.3.3.6 SASL Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.3.4 Constant Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
XML Document Type Definition (DTD) 119
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 6 of 124
© ISO/IEC 2014 – All rights reserved

PART 0. OVERVIEW
Part 0: Overview
0.1 Introduction
The Advanced Message Queuing Protocol is an open internet protocol for business messaging.
AMQP is comprised of several layers. The lowest level defines an efficient, binary, peer-to-peer protocol for
transporting messages between two processes over a network. Above this, the messaging layer defines an
abstract message format, with concrete standard encoding. Every compliant AMQP process MUST be able to
send and receive messages in this standard encoding.
0.1.1 Terminology
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
“RECOMMENDED”, “MAY”, and “OPTIONAL” in this specification are to be interpreted as described in IETF
RFC 2119 [RFC2119].
The authoritative form of the AMQP specification consists of a set of XML source documents. These documents
are transformed into PDF and HTML representations for readability. The machine readable version of the AMQP
DTD describes the XML used for the authoritative source documents. This DTD includes the definition of the
syntax used in the excerpts of XML presented in the PDF and HTML representations.
0.1.2 Normative References
[ASCII]
American National Standards Institute, Inc., American National Standard for Information Systems, Coded Char-
acter Sets - 7-Bit American National Standard Code for Information Interchange (7-Bit ASCII), ANSI X3.4-1986,
March 26, 1986.
[BCP47]
A. Phillips, Ed., M. Davis, Ed., Tags for Identifying Languages. IETF BCP: 47, September 2009.
http://www.ietf.org/rfc/bcp/bcp47.txt
[IANAHTTPPARAMS]
IANA (Internet Assigned Numbers Authority), Hypertext Transfer Protocol (HTTP) Parameters.
http://www.iana.org/assignments/http-parameters/http-parameters.xml
[IANAPEN]
IANA (Internet Assigned Numbers Authority), Private Enterprise Numbers.
http://www.iana.org/assignments/enterprise-numbers
[IANASUBTAG]
IANA (Internet Assigned Numbers Authority), Language Subtag Registry.
http://www.iana.org/assignments/language-subtag-registry
[IEEE754]
Standard for Floating-Point Arithmetic. IEEE 754-2008, August 2008.
http://ieeexplore.ieee.org/servlet/opac?punumber=4610933
[IEEE1003]
The Single UNIX Specification, Version 4. IEEE Std 1003.1-2008, December 2008.
http://www.unix.org/version4/
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 7 of 124
© ISO/IEC 2014 – All rights reserved

PART 0. OVERVIEW 0.1 Introduction
[RFC1982]
R. Elz, R. Bush, Serial Number Arithmetic. IETF RFC 1982, August 1996.
http://www.ietf.org/rfc/rfc1982.txt
[RFC2046]
N. Freed, N. Borenstein, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types. IETF RFC 2046,
November 1996.
http://www.ietf.org/rfc/rfc2046.txt
[RFC2119]
S. Bradner, Key words for use in RFCs to Indicate Requirement Levels. IETF RFC 2119, March 1997.
http://www.ietf.org/rfc/rfc2119.txt
[RFC2234]
D. Crocker, Ed., P. Overell, Augmented BNF for Syntax Specifications: ABNF. IETF RFC 2234, November 1997.
http://www.ietf.org/rfc/rfc2234.txt
[RFC2616]
R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, Hypertext Transfer Protocol –
HTTP/1.1. IETF RFC 2616, June 1999.
http://www.ietf.org/rfc/rfc2616.txt
[RFC4122]
P. Leach, M. Mealling, R. Salz, A Universally Unique IDentifier (UUID) URN Namespace. IETF RFC 4122, July
2005.
http://www.ietf.org/rfc/rfc4122.txt
[RFC4366]
S. Blake-Wilson, M. Nystrom, D. Hopwood, J. Mikkelsen, T. Wright, Transport Layer Security (TLS) Extensions.
IETF RFC 4366, April 2006.
http://www.ietf.org/rfc/rfc4366.txt
[RFC4422]
A. Melnikov, Ed., K. Zeilenga, Ed., Simple Authentication and Security Layer (SASL). IETF RFC 4422, June 2006.
http://www.ietf.org/rfc/rfc4422.txt
[RFC4616]
K. Zeilenga, Ed., The PLAIN Simple Authentication and Security Layer (SASL) Mechanism. IETF RFC 4616,
August 2006.
http://www.ietf.org/rfc/rfc4616.txt
[RFC5246]
T. Dierks, E. Rescorla., The Transport Layer Security (TLS) Protocol Version 1.2. IETF RFC 5246, August 2008.
http://www.ietf.org/rfc/rfc5246.txt
[RFC5646]
A. Phillips, Ed., M. Davis, Ed., Tags for Identifying Languages. IETF RFC 5646, September 2009.
http://www.ietf.org/rfc/rfc5646.txt
[RFC5802]
C. Newman, A. Menon-Sen, A. Melnikov, N. Williams, Salted Challenge Response Authentication Mechanism
(SCRAM) SASL and GSS-API Mechanisms. IETF RFC 5802, July 2010.
http://www.ietf.org/rfc/rfc5802.txt
[UNICODE6]
The Unicode Consortium. The Unicode Standard, Version 6.0.0, (Mountain View, CA: The Unicode Consortium,
2011. ISBN 978-1-936213-01-6)
http://www.unicode.org/versions/Unicode6.0.0/
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 8 of 124
© ISO/IEC 2014 – All rights reserved

PART 0. OVERVIEW 0.1 Introduction
0.1.3 Non-normative References
[AMQPCONNCAP]
AMQP Capabilities Registry: Connection Capabilities
http://www.amqp.org/specification/1.0/connection-capabilities
[AMQPCONNPROP]
AMQP Capabilities Registry: Connection Properties
http://www.amqp.org/specification/1.0/connection-properties
[AMQPDELANN]
AMQP Capabilities Registry: Delivery Annotations
http://www.amqp.org/specification/1.0/delivery-annotations
[AMQPDISTMODE]
AMQP Capabilities Registry: Distribution Modes
http://www.amqp.org/specification/1.0/distribution-modes
[AMQPFILTERS]
AMQP Capabilities Registry: Filters
http://www.amqp.org/specification/1.0/filters
[AMQPFOOTER]
AMQP Capabilities Registry: Footer
http://www.amqp.org/specification/1.0/footer
[AMQPLINKCAP]
AMQP Capabilities Registry: Link Capabilities
http://www.amqp.org/specification/1.0/link-capabilities
[AMQPLINKPROP]
AMQP Capabilities Registry: Link Properties
http://www.amqp.org/specification/1.0/link-properties
[AMQPLINKSTATEPROP]
AMQP Capabilities Registry: Link State Properties
http://www.amqp.org/specification/1.0/link-state-properties
[AMQPMESSANN]
AMQP Capabilities Registry: Message Annotations
http://www.amqp.org/specification/1.0/message-annotations
[AMQPNODEPROP]
AMQP Capabilities Registry: Node Properties
http://www.amqp.org/specification/1.0/node-properties
[AMQPSESSCAP]
AMQP Capabilities Registry: Session Capabilities
http://www.amqp.org/specification/1.0/session-capabilities
[AMQPSESSPROP]
AMQP Capabilities Registry: Session Properties
http://www.amqp.org/specification/1.0/session-properties
[AMQPSOURCECAP]
AMQP Capabilities Registry: Source Capabilities
http://www.amqp.org/specification/1.0/source-capabilities
[AMQPTARGETCAP]
AMQP Capabilities Registry: Target Capabilities
http://www.amqp.org/specification/1.0/target-capabilities
amqp-core-complete-v1.0-os 29 October 2012
Standards Track Work Product Copyright
c OASIS Open 2012. All Rights Reserved. Page 9 of 124
© ISO/IEC 2014 – All rights reserved

PART 0. OVERVIEW 0.2 Conformance
0.2 Conformance
AMQP defines a wire level protocol for business messaging. The definition allows for all common business mes-
saging behaviors. AMQP does not define a wire-level distinction between “clients” and “brokers”, the protocol is
symmetric. It is expected and encouraged that implementations of AMQP will have different capabilities. Expec-
tations of the capabilities of a “client library” are different from expectations of a “broker” which are themselves
different from the capabilities of a “router”. As relevant profiles emerge (where appropriate and applicable) these
will be formalised.
A conformant implementation MUST perform protocol negotiation (see Part 2: section 2.2), and then parse,
process, and produce frames in accordance with the format and semantics defined in parts 1 through 5 of this
specification.
Conformant implementations MUST NOT require the use of any extensions defined outside this document in order
to interoperate with any other conformant implementation.
Part 1 of this document defines the type system and type encodings that every conformant implementation MUST
implement.
Part 2 defines the peer-to-peer transport protocol which operates over TCP. Every conformant implementation of
AMQP over TCP MUST implement Part 2. Future standards mapping AMQP to protocols other than TCP MAY
modify or replace Part 2 when AMQP is being used over that protocol. A conformant implementation MUST
implement Part 2 or a mapping of AMQP to some non-TCP protocol.
Part 2 admits behaviors that might not be appropriate for every implementation. For example a “client library” might
not allow for its communication partner to spontaneously attempt to initiate a connection and request messages.
Where an implementation does not allow for a behavior the implementation MUST respond according to the rules
defined within Part 2 of the specification.
Part 3 of this document defines the AMQP Messaging Layer. Every conformant implementation which processes
messages MUST implement this part of the specification.
Some implementations might not process messages (for example, an implementation acting as a “router” which
looks only at the routing information carried by the AMQP Transport layer). Such implementations do not actively
implement Part 3, but MUST NOT act in ways which violate the rules of this part of the specification.
The Messaging layer admits behaviors that might not be appropriate for all implementations (and within an im-
plementation all behaviors might not be available for all configurations). Where a behavior is not admitted, the
implementation MUST respond according to the rules defined within this specification.
Part 4 defines the requirements for transactional messaging. Transactional messaging defines two roles, that
of the transactional resource and th
...