Thank you for the reply.
Assignee Name (REQUIRED): Matahari Project
Assignee E-mail (REQUIRED): matahari(a)lists.fedorahosted.org
Please confirm if
http://matahariproject.org/ is the organization's
website.
On Wed Aug 24 06:07:57 2011, zbitter(a)redhat.com wrote:
Assignee Name (REQUIRED): Matahari Project
Assignee E-mail (REQUIRED): matahari(a)lists.fedorahosted.org
> (The Assignee is
the organization, company or individual person
> responsible
> for the initial assignment. )
> Contact Name (REQUIRED): Zane Bitter
> Contact E-mail (REQUIRED): zbitter(a)redhat.com
>
> Transport Protocol(s) (REQUIRED): (Please indicate which protocols are
> currently required.)
> [ X ] TCP [ ] UDP [ ] SCTP [ ] DCCP
>
> Service Code (REQUIRED for DCCP only)
>
> A: ____________________________
>
> Service Name (REQUIRED, 15 character maximum):
>
> A: matahari
>
> Desired Port Number (OPTIONAL, for Port Number only)
>
> A: 49000
> NOTE: It is *inappropriate* to use a port number until your
> application has
> been approved for assignment. Leave it blank if no number preference.
>
> Description (REQUIRED) (For example: Super User Messaging)
>
> A: Matahari Broker
>
> Reference (REQUIRED): Please provide a brief and basic technical
> description
> of the protocol that will use the service name or port number,
> including
> message
> formats, types, sequences, functionalities, of your protocol. In
> addition,
> please address the specific questions included below to the extent
> possible.
>
> A: The Matahari server is an implementation of an Advanced Message
> Queuing Protocol (AMQP) broker. Matahari uses a subset of the Qpid
> Management Framework (QMF), which sits on top of AMQP (Apache Qpid is
> an
> implementation of AMQP). AMQP is an open standard which is documented
> here:
>
http://www.amqp.org/confluence/download/attachments/720900/amqp.0-
> 10.pdf
>
> In short, AMQP is a generic protocol for handling message queues.
> Client
> applications can create and subscribe to queues and publish messages
> to
> them.
>
> Matahari (
http://www.matahariproject.org/) is a service to provide
> remote access to system management APIs over QMF. Existing APIs
> support
> system configuration and querying of system parameters for virtual
> servers, however the protocol is extensible so users can add their own
> custom APIs.
>
> Q: If broadcast/multicast is used, how and what for?
>
> A: Multicast may optionally be used to efficiently combine multiple
> brokers into a high-availability cluster.
>
> Q: If UDP is requested, please explain how traffic is limited, and
> whether the protocol reacts to congestion.
>
> A:
> ___________________________________________________________________________
>
> Q: If UDP is requested, please indicate whether the service is solely
> for the discovery of hosts supporting this protocol.
>
> A:
> ___________________________________________________________________________
>
> Q: Please explain how your protocol supports versioning.
>
> A: All AMQP messages begin with a version field, and AMQP defines a
> method for the client and server to negotiate a mutually compatible
> protocol version. QMF objects have a schema which can be queried over
> the protocol.
>
> Q: If your request is for more than one transport, please explain in
> detail how the protocol differs over each transport.
>
> A:
> __________________________________________________________________________
>
> Q: Please describe how your protocol supports security. Please note
> that
> there is current debate as to whether additional future ports will be
> allocated for newly assigned services that lack security, e.g., solely
> for the addition of a secure variant. Applicants are strongly advised
> to
> address this issue as early as possible in the design of their
> protocols.
>
>
> A: The protocol may optionally be tunnelled over SSL.
>
>
> Q: Please explain the state of development of your protocol.
>
> A: AMQP is a published open standard with four published versions
> since
> 2006 and multiple available implementations. QMF has undergone a major
> revision and is now considered stable.
>
> Q: If SCTP is requested, please describe the following: Is there an
> existing TCP and/or UDP service name or port number assignment?
> If so, please indicate the details below:
>
> Service Name: _______________; Port number: _______________
>
> What specific SCTP capability is used by the application such that a
> user who has the choice of both TCP (and/or UDP) and SCTP ports for
> this application would choose SCTP? See [RFC4960 section 7.1]
> (
http://tools.ietf.org/html/rfc4960#section-7.1)
>
> A:
> _____________________________________________________________________________
>
> ________________________________________________________________________________
>
>
> Please provide any other information that would be helpful in
> understanding how this protocol differs from existing assigned
> services.
>
> A: Matahari differs from a generic AMQP broker in that it requires the
> QMF protocol running on top, so only the Apache Qpid implementation of
> AMQP can be used. Since Matahari is designed for system configuration,
> for security reasons it places a tighter than usual set of
> restrictions
> on how the connection can be used, and thus must be segregated from
> regular applications' AMQP traffic.
>