OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

amqp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Call for Participation: OASIS Advanced Message Queuing Protocol (AMQP) Technical Committee

OASIS members & interested parties,

A new OASIS technical committee is being formed. The OASIS Advanced Message Queuing Protocol (AMQP) Technical Committee has been proposed by the members of OASIS listed in section 2.d of the charter below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode and language specified in the proposal will constitute the TC's official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's first meeting.

The eligibility requirements for becoming a participant in the TC at the first meeting are:

(a) you must be an employee of an OASIS member organization or an individual member of OASIS, and
(b) you must join the Technical Committee, which you may do by using the "Join this TC" button on the TC's home page at http://www.oasis-open.org/committees/amqp/.

To be considered a voting member at the first meeting, you must:

(a) join the Technical Committee at least 7 days prior to the first meeting
(by 7 October 2011); and
(b) you must attend the first meeting of the TC, at the time and date fixed below
(14 October 2011).

Participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties.

Non-OASIS members who wish to participate may contact us about joining OASIS. See http://www.oasis-open.org/join/. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC's public home page at http://www.oasis-open.org/committees/amqp/.

Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation.


(1) Charter of the Technical Committee

(a) Name of the TC

OASIS Advanced Message Queuing Protocol (AMQP) Technical Committee (TC).

(b) Statement of Purpose

The purpose of the Advanced Message Queuing Protocol (AMQP) Technical Committee (TC) is to define an open internet protocol for business messaging. Salient business messaging requirements are:

- Ubiquity
- Open internet protocol standard supporting unencumbered (a) use, (b) implementation, and (c) extension.
- Clear and unambiguous core functionality for business message routing and delivery within internet infrastructure - so that business messaging is provided by infrastructure and not by integration experts.
- Low barrier to understand, use and implement.
- Fits into existing enterprise messaging applications environments in a practical way.

- Safety
- Infrastructure for a secure and trusted global transaction network.
- Consisting of business messages that are tamper-proof.
- Supporting message durability independent of receivers being connected, and
- Message delivery is resilient to technical failure.
- Supports business requirements to transport business transactions of any financial value.
- Sender and receiver roles are mutually agreed upon by counter parties - no possibility for injection of spam.

- Fidelity
- Well-stated message queuing and delivery semantics covering: at-most-once; at-least-once; and once-and-only-once aka 'reliable'.
- Well-stated message ordering semantics describing what a sender can expect (a) a receiver to observe and (b) a queue manager to observe.
- Well-stated reliable failure semantics so all exceptions can be managed.

- Applicability
- As TCP subsumed all technical features of networking, we aspire for AMQP to be the prevalent business messaging technology (tool) for organizations so that with increased use, ROI increases and TCO decreases.
- Any AMQP client can initiate communication with, and then communicate with, any AMQP broker over TCP.
- Any AMQP client can request communication with, and if supported, negotiate the use of alternate transport protocols (e.g. SCTP, UDP/multicast), from any AMQP broker.
- Provides the core set of messaging patterns via a single manageable protocol: asynchronous directed messaging, request/reply, publish/subscribe, store and forward.
- Supports hub and spoke messaging topology within and across business boundaries.
- Supports hub to hub message relay across business boundaries through enactment of explicit agreements between broker authorities.
- Supports Peer to Peer messaging across any network.

- Interoperability
- Stable core (client-broker) wire protocol so that brokers do not require upgrade during 1.x feature evolution: Any 1.x client will work with any 1.y broker if y >= x.
- Stable extended (broker-broker) wire protocol so that brokers do not require upgrade during 1.x feature evolution: Any two broker versions 1.x, 1.y can communicate using protocol 1.x if x

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]