oasis-tcs/amqp-specs

OASIS Advanced Message Queuing Protocol (AMQP) TC: OASIS AMQP TC specification and document repository. AMQP is a secure, reliable and open internet protocol for handling business messaging. https://github.com/oasis-tcs/amqp-specs

README

Members of the OASIS Advanced Message Queuing Protocol (AMQP) TC create and manage technical content in this TC GitHub repository ( https://github.com/oasis-tcs/amqp-specs ) as part of the TC's chartered work (the program of work and deliverables described in its charter.

OASIS TC GitHub repositories, as described in GitHub Repositories for OASIS TC Members' Chartered Work, are governed by the OASIS TC Process, IPR Policy, and other policies, similar to TC Wikis, TC JIRA issues tracking instances, TC SVN/Subversion repositories, etc. While they make use of public GitHub repositories, these TC GitHub repositories are distinct from OASIS Open Repositories, which are used for development of open source licensed content.

Description

The purpose of this repository is support development of OASIS AMQP TC specifications and documents. AMQP is a secure, reliable and open internet protocol for handling business messaging.

Contributions

As stated in this repository's CONTRIBUTING file, contributors to this repository are expected to be Members of the OASIS AMQP TC for any substantive change requests. Anyone wishing to contribute to this GitHub project and participate in the TC's technical activity is invited to join as an OASIS TC Member. Public feedback is also accepted, subject to the terms of the OASIS Feedback License.

Licensing

Please see the LICENSE file for description of the license terms and OASIS policies applicable to the TC's work in this GitHub project. Content in this repository is intended to be part of the AMQP TC's permanent record of activity, visible and freely available for all to use, subject to applicable OASIS policies, as presented in the repository LICENSE file.

Further Description of this Repository

[TC may provide any additional narrative content here. For example, the Members may wish to provide an extended statement of purpose.]

Contact

Please send questions or comments about OASIS TC GitHub repositories to the OASIS TC Administrator. For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the the AMQP TC's home page.

amqp-specs's Issues

[Event Streams] Multiple partitions on link for consumer group

Talking about consumer groups, the section 4.5.1 says:

The event log node MAY also attach consumer group links without binding them to a specific partition, allowing for multiple partitions to be associated with a link and for those binding to change dynamically without having to reestablish the link.

So AFAIU the link is not bounded to any partition but anyway the consumer can get messages from more than one partition and it knows about that only in the event-streams-source-partition during message transfer.
Is that right?

Thinking about a possible Kafka implementation of this, a Kafka consumer knows about the assigned partitions since the beginning (and even the revoked ones) during a rebalance; it doesn't get the information only when a message is consumed.
I was wondering if we could provide the list of assigned partitions (as we have with event-streams-partition in section 4.3).
The problem could be about as mentioned above ... "change dynamically without having to reestablish the link" ... so how to update the consumer with the new partitions if they changed.

[Event Streams] Mentioning AMQP_EVENT_STREAMS_V1_0 as "desired-capabilities"

In the section "3.1 Connection and Link Capabilities" we, somehow, mention the "offered-capabilities" that the event log node MUST fill with AMQP_EVENT_STREAMS_V1_0 for announcing that it supports the event streams specification.
Should we also mention that a sender/receiver can specify the same in the open frame in the "desired-capabilities" so that if the AMQP node can just shutdowns the connection if it doesn't support that?