A Jabber travels further into the Jabber-as-Middleware world, it needs a protocol to determine "who can do what to whom". This proposal defines a protocol that enables any Jabber entity to determine the permissions of another Jabber entity, whether the context is a user JID querying a component for access, a client-to-client conversation, or a component asking another component about a request from a user.

All access control lists (ACLs) boil down to three aspects: Actor, Operation, and Target/Sink. With this in mind it becomes almost trivial to implement the basic query/response mechanism.

Here we have the inventory.capulet.com component querying the security component as to whether juliet@ may obtain the requested poison.

Unfortunately, the response is in the affirmative and the romantic tragedy follows.

The <acl> element provides the container for the query. It MUST have the three attributes: actor, oper, and target.

The actor attribute is set to the Jabber ID which is attempting to perform an operation. This need not be the JID sending the acl, although it may be. Remember this is to allow for the question, "Can X do Y to Z?", which is a question anyone can ask.

The oper attribute is application-specific and refers to the operation for which a permission check is required (e.g., read/write operations). This also defines the scope of the ACL check, so the implementation is responsible for interpreting the actor and target values based on the value of the 'oper' attribute.

The target is the object which the actor is trying to perform the operation on. This MUST be a node queryable via &jep0030;.

Requests MUST be in the form of an empty <acl/> element with ALL the attributes specified. If not all attributes are specified, the request is incomplete and ambiguities arise; therefore the entity receving the request MUST return a "bad request" error to the sender.

Responses MUST be in one of three forms: allowed, denied, error.

The response is inserted into the <acl/> as a child element. If the response is allowed, then <allowed/> is inserted. If the JID is denied then <denied/> is returned. If there is inadequate information then <error/> is used following the standard Jabber error scheme.

To obtain a list of acl operations that a jid supports, you must send an empty <query/>

The to jid must then respond with a list of operations, if the jid supports SAC.

To follow.

To follow.

This JEP requires no interaction with &IANA;.

As a result of this JEP, the ®ISTRAR; will need to register the 'http://jabber.org/protocol/sac' namespace.

1. Add disco integration section.
2. Fill out error codes.
3. Add DTD and Schema.
4. Allow for query of all allowable operations for actor in relation to a target.
5. Investigate possible integration with pubsub.