AMQP Technical Committee reboot meeting summary
Participants:
- Clemens Vasters (Microsoft) - Chair
- Rob Godfrey (IBM) - Chair
- Richard Coppen (IBM)
- Eldert Grootenboer (Microsoft)
- Ashish Chhabria (Microsoft)
- Matthew Leming (IBM)
- David Ansari (Broadcom)
- Vasily Shcherbinin (IBM)
- Karl Nilsson (Broadcom)
- Selvam, Vignesh (AWS)
- Moser, Stefan (AWS)
- Kevin Lam (Microsoft)
- Robbie Gemmell (IBM)
- Ted Ross (IBM)
Key outcomes
1. AMQP Technical Committee formally reactivated
- The meeting primarily served to restart the OASIS AMQP Technical Committee after a long period of inactivity.
- Committee participation and voting rights were effectively re-established for attendees.
- OASIS participation, IPR, and committee process rules were reviewed at the beginning of the meeting.
2. Chairs re-elected
- Clemens Vasters and Rob Godfrey were nominated and approved as co-chairs.
- No objections were raised.
- The committee agreed to continue with the previous co-chair model.
Charter status
- The existing AMQP charter was reviewed.
- Consensus was that the current charter is broad enough to allow the intended work, including MCP-related activities.
- The committee provisionally accepted the current charter.
- Future amendments may be proposed, but no immediate charter rewrite is required.
Primary work item: MCP over AMQP
The committee agreed that the first major focus will be work around:
MCP (Model Context Protocol) over AMQP 1.0
Discussion centered around an existing Amazon MQ implementation and GitHub repository presented by Stefan Moser.
Key decisions:
- Stefan's work will be contributed into the TC process.
-
The contribution should be expressed as a specification proposal, not as code.
-
The work must eventually be described at the AMQP protocol level rather than in terms of specific client APIs or broker libraries, but the initial submission can be expressed in API terms.
- Stefan agreed to act as editor for the initial proposal, with guidance from the committee.
Relationship with MQTT work
Clemens brought back feedback from the MQTT TC.
Main points:
- There is growing interest in AI-related messaging workloads.
- MQTT and AMQP likely address complementary parts of future AI architectures.
- The groups should avoid duplicating work.
- A liaison or joint working model between the AMQP and MQTT committees should be explored.
- Particular interest exists around:
- AI messaging architectures
- metadata handling
- interoperability
- device and edge integration
Richard and Clemens will develop a proposal for cross-TC collaboration.
Additional specification work
Several possible future work items were discussed:
- Potential consolidation/update of older AMQP committee specifications.
- Possible advancement of previous committee drafts to higher status.
- Existing unfinished work from the 2019-2021 period may be revisited.
- An HTTP-over-AMQP specification was mentioned as an example of unfinished work.
No decisions were made beyond acknowledging these as backlog candidates.
New proposal discussed
David Ansari raised a possible extension proposal:
- Introduce a new AMQP delivery state such as "processing".
- Intended for scenarios where work is ongoing and lock renewal semantics are needed.
Response:
- The committee encouraged creation of a formal proposal/specification draft.
- Rob noted that existing AMQP semantics should be reviewed carefully before introducing protocol changes.
Operating model
The committee agreed to:
- Continue using OASIS mailing lists for official committee business.
- Continue using the AMQP TC GitHub repository for specification development.
- Accept Markdown-based specification authoring.
Cadence
The committee agreed on:
- Meetings every two weeks.
- Initial work will focus on iterating on the MCP-over-AMQP proposal once the first draft is submitted.
Action items
| Owner | Action |
| Stefan Moser / Vignesh Selvam | Produce an initial MCP-over-AMQP specification draft for TC contribution |
| Clemens Vasters & Richard Coppen | Develop proposal for AMQP/MQTT collaboration mechanism |
| David Ansari | Prepare proposal for a new AMQP delivery state |
| Clemens Vasters | Schedule recurring bi-weekly meetings and maintain consistent Teams meeting links |
Best Regards
Clemens