AMQP Specification Transport

More documents

Recommendations

Info

AMQP Specification. Connection 3 Connection 3.1 Version Negotiation Prior to sending any frames on a connection, each peer MUST start by sending a protocol header that indicates the protocol version used on the connection. The protocol header consists of the upper case ASCII letters "AMQP" followed by 1, 0, 0, and connection flags. This is an 8-octet sequence: 4 OCTETS 1 OCTET 1 OCTET 1 OCTET 1 OCTET +----------+---------+---------+----------+---------+ | "AMQP" | major | minor | revision | flags | +----------+---------+---------+----------+---------+ flags: 0|0|0|0|0|0|R|S R: tls-required -- The peer requires all data following the connection header to be encrypted. If R is set then S MUST also be set. S: tls-supported -- Indicates that the peer supports TLS encryption. If either peer's connection header has the R flag set then all connection data following the connection header will be encrypted, otherwise connection data will be unencrypted. Note: if one protocol header requires TLS, and the other does not support it, then both peers MUST abort the connection. An AMQP client and server agree on a protocol version as follows: • When the client opens a new socket connection to an AMQP server, it MUST send a protocol header with the client's preferred protocol version. • If the requested protocol version is supported, the server MUST send its own protocol header with the requested version to the socket, and then implement the protocol accordingly. • If the requested protocol version is not supported, the server MUST send a protocol header with a supported protocol version and then close the socket. • When choosing a protocol version to respond with, the server SHOULD choose the highest supported version that is less than or equal to the requested version. If no such version exists, the server SHOULD respond with the highest supported version. • If the server can't parse the protocol header, the server MUST send a valid protocol header with a supported protocol version and then close the socket. Based on this behavior a client can discover which protocol versions a server supports by attempting to connect with its highest supported version and reconnecting with a version less than or equal to the version received back from the server. AMQP Transport v. 1-0 Page 6 of 83
AMQP Specification. Connection Version Negotiation Examples TCP Client TCP Server ====================================================== AMQP%d1.0.0.0 ------------->
Page 1 and 2: AMQP Specification. Transport 1 Tra
Page 3 and 4: AMQP Specification. Framing 2 Frami
Page 5: AMQP Specification. Framing 2.3 Fra
Page 9 and 10: AMQP Specification. Connection TCP
Page 11 and 12: AMQP Specification. Connection be i
Page 13 and 14: AMQP Specification. Connection If a
Page 15 and 16: AMQP Specification. Connection inco
Page 17 and 18: AMQP Specification. Connection 3.9.
Page 19 and 20: AMQP Specification. Connection 3.9.
Page 21 and 22: AMQP Specification. Session 4 Sessi
Page 23 and 24: AMQP Specification. Session Endpoin
Page 25 and 26: AMQP Specification. Session Endpoin
Page 27 and 28: AMQP Specification. Session Snapsho
Page 29 and 30: AMQP Specification. Session Upon re
Page 31 and 32: AMQP Specification. Session 4.12.2
Page 41 and 42: AMQP Specification. Link between tw
Page 43 and 44: AMQP Specification. Link +---------
Page 45 and 46: AMQP Specification. Link Peer Partn
Page 47 and 48: AMQP Specification. Link Endpoint I
Page 49 and 50: AMQP Specification. Link 5.12.1 Com
Page 55 and 56: AMQP Specification. Link State Tran
Page 57 and 58:
AMQP Specification. Link header: he
Page 59 and 60:
AMQP Specification. Link 5.14.5 Com
Page 61 and 62:
AMQP Specification. Link 5.14.7 Com
Page 63 and 64:
AMQP Specification. Basic-types 6 B
Page 65 and 66:
AMQP Specification. Basic-types Nam
Page 67 and 68:
AMQP Specification. Basic-types Wir
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83:
AMQP Specification. Derived-types E
show all

AMQP Specification Transport

Create successful ePaper yourself

Delete template?

Save as template?