Frequently Asked Questions

Answer: The Baggage Test Broker can be accessed using an MQTT message client. The detailed connection details are provided when your request for access to the broker is approved. The Baggage Test broker is secured through use of digital certificates to authenticate and authorize MQTT connections. The security certificate must be signed by IATA.
Answer: The Testbed Broker can be accessed by registered users, including Airlines (IATA members), Airports (ACI members) and other interested aviation parties. Please see the Registration page of this website and contact IATA (baggageservices@iata.org) if you would like to request access.
Answer: The Baggage Test Broker accepts communications using the MQTT protocol (v3.1.1). Please check that your broker client is MQTT compatible. The MQTT broker software examples above are all expected to be compatible with the Baggage Test Broker.
Answer: The IATA Certification Service can sign a digital certificate that you have already generated. Please contact IATA (baggageservices@iata.org) and submit a certificate signing request to IATA.
Answer: Yes. IATA can sign an existing digital certificate to enable you to connect to the Baggage Testbed.
Answer: The Baggage Test Broker publishes sample Bag Logistics And Conformance Event Service messages compliant with the two most recently published message schemas (XSDs). The sample messages provide content based on a range of baggage scenarios such as passengers flying on direct or transfer flights to and from a variety of airports. Registered users of the Baggage Test Broker can subscribe to a range of message topics so that these sample messages can be downloaded or viewed.
Answer: Registered users of the Baggage Test Broker must make a successful SSL connection in order to subscribe to topics on the broker and retrieve messages. The SSL encryption uses the SSL certificate keys to secure the content of the message in transport as a standard feature of the MQTT protocol.
Answer: IATA currently expects to release updated Baggage Event Notification XML Schemas (XSDs) on a quarterly basis. Registered users of the Baggage Test Broker can subscribe to topics containing messages compliant with the most recent schema release as well as the prior schema release. Please contact IATA (baggageservices@iata.org) if you have any questions relating to the current schema version.
Answer: Over time, messages compliant with IATA Recommended Practice 1755 will replace those of IATA Recommended Practice 1745. There are equivalent messages types in RP1755 corresponding to RP1745 BSMs/BPMs, however, directly converting from one message format to the other is not always possible. IATA provide guidance in the RP1755 Implementation Guide on the topic of message conversion.
Answer: The Baggage Test Broker provides sample message content that can be viewed by any registered user. The Baggage Test Broker uses the SSL certificate identity to authenticate connecting clients. The SSL certificate identity is also used to authorize access to specific message topics by use of an Access Control List (ACL). Security considerations for individual broker implementations are discussed in the RP1755 Implementation Guide.
Answer: The Baggage Test Broker uses the topic naming convention as outlined in the RP1755 Implementation Guide.
Answer: The Baggage Test Broker is provided as a central platform against which to test baggage information exchange with broker clients. There are several airline, airport and other third parties with live MQTT message brokers that exchange baggage XML messages. IATA provide a Directory Services Node in which registered users can lookup the connection details for other live message brokers. Please contact IATA (baggageservices@iata.org) if you wish to request access to the IATA Directory Services node.
Answer: IATA/ACI jointly developed the new message standard to support the aviation industry, now published as IATA Recommended Practice 1755. Please contact IATA (baggageservices@iata.org) if you have any questions relating to the current messaging standard.