XEP-xxxx: privileged entity

Abstract:This specification provides a way for XMPP entities to have a privileged access to other entities data
Author:Jérôme Poisson
Copyright:© 1999 - 2014 XMPP Standards Foundation. SEE LEGAL NOTICES.
Status:ProtoXEP
Type:Standards Track
Version:0.0.3
Last Updated:2014-11-13

WARNING: This document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards Foundation, and this document is not yet an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at <http://xmpp.org/extensions/> and announced on the <standards@xmpp.org> mailing list.


Table of Contents


1. Introduction
2. Requirements
3. Glossary
4. Admin Mode Use Cases
    4.1. Permission Request Use Case
       4.1.1. Entity Requests Admin Privilege
       4.1.2. Server Accepts Admin Privilege
       4.1.3. Server Rejects Admin Privilege
    4.2. Privileged Entity Sends <iq/> Stanzas
5. Client Mode Use Cases
    5.1. Permission Request Use Case
    5.2. Privileged Entity Sends <iq/> Stanzas
6. Special permissions
    6.1. Message Permission
    6.2. Managed Entity Presence
    6.3. Roster Presence
7. Configuration
8. Discovering Support
9. Business Rules
10. Implementation Notes
11. Security Considerations
12. IANA Considerations
13. XMPP Registrar Considerations
    13.1. Protocol Namespaces
    13.2. Protocol Versioning
14. XML Schema
15. Acknowledgements

Appendices
    A: Document Information
    B: Author Information
    C: Legal Notices
    D: Relation to XMPP
    E: Discussion Venue
    F: Requirements Conformance
    G: Notes
    H: Revision History


1. Introduction

XMPP components are used for long through Jabber Component Protocol (XEP-0114) [1], but are quite limited: they have a restricted access to other entities data, similar to what a client can do. This is sufficient for components like gateways, but very limiting for more complex components like a PubSub service. The goal of this XEP is to allow a component or any entity to have a "privileged" status, and access an other entity data with the same privileges than the entity itself, that means send and receive <iq/> stanzas on its behalf (and in some cases, send <message/> or receive <presence/> stanzas).

Privileged entities have numerous advantages, including:

2. Requirements

A privileged entity can be used in two modes:

In admin mode, the privileged entity MAY be able to emit <iq/> stanzas in the same way as any entity, including managing roster or accessing persistent storage. The privilege mechanism MUST be totally transparent for the managed entities.

In client mode, a privileged entity MUST have an explicit authorization for any <iq/> namespace he wants to use. Client SHOULD be able to check and revoke granted permissions, and if it's not possible, permissions MUST be revoked after a disconnection.

In addition, some special permissions can permit to send <message/> stanzas on behalf of the server or access <presence/> informations.

3. Glossary

4. Admin Mode Use Cases

4.1 Permission Request Use Case

4.1.1 Entity Requests Admin Privilege

Once an entity is authenticated and stream is started, it can request a privileged status. It does it by sending an <iq/> stanza with 'urn:xmpp:privilege:0' namespace.

The <query/> element MUST have a "request" type and MAY have a 'privilege' attribute with the value "admin". Namespace permissions are asked with a <perm/> element, which MUST contain a 'namespace' attribute set to the requested namespace and a 'type' attribute which can be:

Example 1. Entity asks for admin privilege

<iq from='pubsub.capulet.net' type='get' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0' type='request' privilege='admin'>
        <perm namespace='jabber:iq:roster' type='both'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='both'/>
    </query>
</iq>
            

4.1.2 Server Accepts Admin Privilege

If the server accepts the privileged status (e.g.: admin status specified in configuration), it MUST return an <iq/> result stanza with a <query/> element of type "allowed", and listing the allowed permissions in <perm/> elements:

Example 2. Server accepts admin privilege

<iq from='capulet.net' to='pubsub.capulet.net' type='result' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0'
           type='allowed'>
        <perm namespace='jabber:iq:roster' type='both'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='both'/>
    </query>
</iq>

Note: the granted permissions MAY be different from the requested ones, according to server's configuration.

4.1.3 Server Rejects Admin Privilege

If the server rejects the privileged status, it MUST return a <forbidden/> error:

Example 3. Server rejects admin privilege

<iq from='capulet.net' to='pubsub.capulet.net' type='error' id='privilege1'>
    <error type='cancel'>
        <forbidden xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
    </error>
</iq>
            

4.2 Privileged Entity Sends <iq/> Stanzas

Sending an <iq/> stanza is done by sending the stanza the way it would be done by the managed entity, except that its JID is in the 'to' attribute. In the following example, the PubSub service want to know Juliet's roster because she owns a node with access model based on publiser's roster:

Example 4. Privileged Entity Sends A Roster Stanza

<iq id='roster1'
    xmlns='urn:xmpp:privilege:0'
    to='juliet@example.com'
    type='get'
    id='roster1'>
        <query xmlns='jabber:iq:roster'/>
</iq>
            

The server then answers normally, as it would have done to the managed entity:

Example 5. Server Answers To Privileged Entity

<iq id='roster1'
    from='juliet@example.com'
    to='pubsub.capulet.net'
    type='result'>
    <query xmlns='jabber:iq:roster' ver='ver7'>
        <item jid='nurse@example.com'/>
        <item jid='romeo@example.net'/>
    </query>
</iq>
            

In the following example, the sync.capulet.net privileged entity want to access managed entity's bookmarks to synchronize them with an online service. It can request the bookmarks in the following way:

Example 6. Privileged Entity Request Bookmarks

<iq id='bookmark1'
    to='juliet@capulet.lit'
    type='get'>
    <pubsub xmlns='http://jabber.org/protocol/pubsub'>
        <items node='storage:bookmarks'/>
    </pubsub>
</iq>
            

and server answers:

Example 7. Server Returns Bookmarks

<iq id='bookmark1'
    to='sync.capulet.net'
    type='result'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <items node='storage:bookmarks'>
      <item id='current'>
        <storage xmlns='storage:bookmarks'>
          <conference name='The Play&apos;s the Thing'
                      autojoin='true'
                      jid='theplay@conference.shakespeare.lit'>
            <nick>JC</nick>
          </conference>
        </storage>
      </item>
    </items>
  </pubsub>
</iq>
            

5. Client Mode Use Cases

5.1 Permission Request Use Case

In client mode, the privileged entity is not certified by the server administrator, so the permissions MUST be explicitly allowed by the managed entity. This is initiated by the privileged entity (it can be after an interaction with a managed entity, like a subscription). It's done in the same way as for admin mode with the following exceptions:

  1. the privilege type is client instead of admin
  2. the privilege is given per entity, so the managed entity MUST be specified in a 'to' attribute

If an entity want a read/write access to a client's roster (Juliet) and a read only access to her pubsub, it can ask the permission like this:

Example 8. Entity asks for user privilege

<iq from='priv.montaigu.net' to='capulet.net' type='get' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0'
           type='request'
           privilege='client'
           to='juliet@capulet.net'>
        <perm namespace='jabber:iq:roster' type='both'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='get'/>
    </query>
</iq>

Once received the permission request, the server asks the client to grant or deny the requested permission using Data Forms (XEP-0004) [2]. The form SHOULD allow to fine tune the granted permissions. The server uses a challenge which it MUST have generated himself.

Example 9. Server asks user for the permission

<message from='capulet.net' to='juliet@capulet.net'>
    <body>
        priv.montaigu.net wants some privileges.
        Do you you allow him to use the following features?

        Be careful! According permissions to an entity is a serious thing,
        think twice that you can trust the entity before doing this.
    </body>
    <x xmlns='jabber:x:data' type='form'>
        <title>Privileges request</title>
        <instructions>priv.montaigu.net wants to use the following features:
            Do you allow it?</instructions>
        <field type='hidden' var='challenge'><value>5439123</value></field>
        <field type='hidden' var='FORM_TYPE'>
            <value>urn:xmpp:privilege:0</value>
        </field>
        <field type='list-single'
            label='Manage roster (jabber:iq:roster) READ/WRITE'
            var='jabber:iq:roster'>
            <value>0</value>
            <option label='None'><value>none</value></option>
            <option label='Read only (get)'><value>get</value></option>
            <option label='Write only (set)'><value>set</value></option>
            <option label='Read and write (both)'><value>both</value></option>
        </field>
        <field type='list-single'
            label='Manage PubSub (http://jabber.org/protocol/pubsub) READ'
            var='http://jabber.org/protocol/pubsub'>
            <value>0</value>
            <option label='None'><value>none</value></option>
            <option label='Read only (get)'><value>get</value></option>
        </field>
    </x>
</message>

The server SHOULD include a warning message, SHOULD translate the namespace to human friendly names (and MAY keep the original namespace in addition) and MUST set the default value to "none" (permission refused). The server SHOULD use namespace as field var, so a client can use it to have a customized display.

The client can then answer to the form:

Example 10. Client Answer To The Form

<message from='juliet@capulet.net' to='capulet.net'>
  <x xmlns='jabber:x:data' type='submit'>
    <field var='FORM_TYPE'>
      <value></value>
    </field>
    <field var='challenge'><value>5439123</value></field>
    <field var='jabber:iq:roster'><value>both</value></field>
    <field var='http://jabber.org/protocol/pubsub'><value>none</value></field>
  </x>
</message>

Here Juliet allows priv.montaigu.net to use 'set' and 'get' in order to manage her roster, but doesn't want it to do any 'get' on her pubsub nodes.

Finaly, the server notify the entity of the granted permissions. For this it uses a <query/> element with the 'allowed' type, and puts the client JID in a 'from' attribute:

Example 11. Server notify accepted permissions

<iq from='capulet.net' to='priv.montaigu.net' type='set' id='privilege2'>
    <query xmlns='urn:xmpp:privilege:0'
        type='allowed'
        from='juliet@capulet.net'>
        <perm namespace='jabber:iq:roster' type='both'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='none'/>
    </query>
</iq>

The privileged entity can now act according to permission granted to him.

5.2 Privileged Entity Sends <iq/> Stanzas

Sending <iq/> stanzas is done in the exact same way as for admin mode. If an entity wants to sent a non authorized <iq/>, it will get a <forbidden/> error:

Example 12. Entity Request bookmarks

<iq to='juliet@capulet.lit' type='get' id='bookmark1'>
    <pubsub xmlns='http://jabber.org/protocol/pubsub'>
        <items node='storage:bookmarks'/>
    </pubsub>
</iq>

Example 13. The Stanza Is Not Autorized !

<iq from='capulet.net' to='priv.montaigu.net' type='error' id='bookmark1'>
    <error type='cancel'>
        <forbidden xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
    </error>
</iq>
            

6. Special permissions

In some cases, an entity may need extra permission beyond what <iq/> stanzas can do. An entity may want to send <message/> stanzas on behalf of the server, or get <presence/> informations. The special permissions manage these cases with some restrictions.

6.1 Message Permission

With some namespaces it can be desirable to send notifications (e.g. PEP service), so the privileged entity must be able to send <message/> stanzas. To do this, it MUST request it by using a <perm/> element with the special "message" namespace attribute and a 'type' attribute with the value "outgoing" (any other type MUST be rejected with a <forbidden/> error).

A privileged entity can then send message on the behalf either of the server or of a bare JID of the server, using Message Forwarding (XEP-0297) [3], with the following restrictions:

  1. forwarded <message/> 'type' attribute has the value of "headline"
  2. forwarded <message/> 'from' attribute MUST be a bare JID from the server, no resource is allowed
  3. in client mode, the forwarded <message/> 'from' attribute can only be one of a managed entity which has explicitly accepted the delegation

If any of this rules is violated, the server MUST return a <not-authorized/> stream error and close the connection, as explained in RFC 6120 [4] section 4.9.3.12.

In the following example, pubsub.capulet.lit asks for pubsub and outgoing messages permission

Example 14. entity asks for outgoing messages permission

<iq from='pubsub.capulet.net' type='get' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0' type='request' privilege='admin'>
        <perm namespace='message' type='outgoing'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='both'/>
    </query>
</iq>
            

Example 15. server accepts permission

<iq from='capulet.net' to='pubsub.capulet.net' type='result' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0' type='allowed'>
        <perm namespace='message' type='outgoing'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='both'/>
    </query>
</iq>
        

Now that pubsub.capulet.lit is allowed, it can send messages using <forwarded/> elements.

Example 16. privileged entity send a notificaction message

<message from='pubsub.capulet.lit' to='capulet.lit' id='notif1'>
    <forwarded xmlns='urn:xmpp:forward:0'>
        <message from='juliet@capulet.lit'
            id='foo'
            to='romeo@montague.lit/orchard'
            type='headline'
            xmlns='jabber:client'>
            <event xmlns='http://jabber.org/protocol/pubsub#event'>
                <items node='http://jabber.org/protocol/tune'>
                    <item>
                        <tune xmlns='http://jabber.org/protocol/tune'>
                            <artist>Gerald Finzi</artist>
                            <length>255</length>
                            <source>Music for "Love's Labors Lost" (Suite for small orchestra)</source>
                            <title>Introduction (Allegro vigoroso)</title>
                            <track>1</track>
                        </tune>
                    </item>
                </items>
            </event>
            <delay xmlns='urn:xmpp:delay' stamp='2014-11-25T14:34:32Z'/>
        </message>
    </forwarded>
</message>
        

The server sees that forwarded message type is 'headline', that juliet@capulet.lit is a bare JID of the server, and that outgoing message permission was granted in admin mode (so all bare JIDs from server are allowed); it can now send the notification:

Example 17. server sends the notification as if it was originating from him

<message from='juliet@capulet.lit'
    id='bar'
    to='romeo@montague.lit/orchard'
    type='headline'>
    <event xmlns='http://jabber.org/protocol/pubsub#event'>
        <items node='http://jabber.org/protocol/tune'>
            <item>
                <tune xmlns='http://jabber.org/protocol/tune'>
                    <artist>Gerald Finzi</artist>
                    <length>255</length>
                    <source>Music for "Love's Labors Lost" (Suite for small orchestra)</source>
                    <title>Introduction (Allegro vigoroso)</title>
                    <track>1</track>
                </tune>
            </item>
        </items>
    </event>
    <delay xmlns='urn:xmpp:delay' stamp='2014-11-25T14:34:32Z'/>
</message>
    

6.2 Managed Entity Presence

It can be often desirable for a privileged entity to have presence information of the managed entities (e.g. to know when to send it notificiations). As privileges must be transparent for the managed entity (in admin mode), this presence has to be sent by the server without modifying managed entity roster.

To do this, the privileged entity MUST ask for presence information when requesting privileges, using a special "presence" namespace attribute and a 'type' attribute with the value "managed_entity".

If the delegation is granted, the server MUST use a directed presence, as specified in RFC 6121 [5] section 4.6 on the behalf of managed entity each time its presence information change.

This privilege MUST NOT be requested in client mode, if so the server MUST reject the request by setting the allowed type to "none". If an entity needs presence information in client mode, it SHOULD request it using the normal <presence/> subscription mechanism.

Example 18. privileged entity asks for pusub privilege with presence

<iq from='pubsub.capulet.net' type='get' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0' type='request' privilege='admin'>
        <perm namespace='presence' type='managed_entity'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='both'/>
    </query>
</iq>

Example 19. server accepts privileges

<iq from='capulet.net' to='pubsub.capulet.net' type='result' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0' type='allowed'>
        <perm namespace='presence' type='managed_entity'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='both'/>
    </query>
</iq>

Example 20. server receives new presence from Juliet

<presence from='juliet@capulet.lit/balcony'
          id='presence1'
          xml:lang='en'>
    <show>chat</show>
    <status>Staying on the balcony</status>
</presence>

Example 21. server redirects presence to privileged entity

<presence from='juliet@capulet.lit/balcony'
          to='pubsub.capulet.lit'
          id='presence1'
          xml:lang='en'>
    <show>chat</show>
    <status>Staying on the balcony</status>
</presence>

6.3 Roster Presence

In addition to "managed entity presence", a privileged entity may need to know when a contact in managed entity roster is online (for example, it's necessary for a PEP service because of the presence default access model).

In this case, privileged entity MUST ask for presence information when requesting privileges, using a special "presence" namespace attribute (as in previous section) and a 'type' attribute with the value "roster". Furthermore, the privileged entity MUST have read permission on roster namespace (i.e. 'type' attribute in allowed <perm> of namespace jabber:iq:roster MUST have a value of either get or both).

If the delegation is granted, the server MUST send to the privileged entity every presence information that the managing entity is receiving.

The server MUST reject the permission if the privileged entity doesn't have read permission on roster namespace.

Note: this permission should be given carefully, as it gives access to presence of potentially a lot of entities to the privileged entity (see security considerations). If allowed in client mode, server SHOULD display an extra warning when requesting permissions to the managed entity.

Example 22. privileged entity asks for pusub privilege with presence roster

<iq from='pubsub.capulet.net' type='get' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0' type='request' privilege='admin'>
        <perm namespace='presence' type='roster'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='both'/>
        <perm namespace='jabber:iq:roster' type='get'/>
    </query>
</iq>

Note the presence of jabber:iq:roster permission request.

Example 23. server accepts privileges

<iq from='capulet.net' to='pubsub.capulet.net' type='result' id='privilege1'>
    <query xmlns='urn:xmpp:privilege:0' type='allowed'>
        <perm namespace='presence' type='roster'/>
        <perm namespace='http://jabber.org/protocol/pubsub' type='both'/>
        <perm namespace='jabber:iq:roster' type='get'/>
    </query>
</iq>

Example 24. server receives new presence from Romeo, which is in Juliet's roster

<presence from='romeo@montaigu.lit/orchard'/>

Example 25. server sends the presence as usually, but also to the privileged entity

<presence from='romeo@montaigu.lit/orchard'
          to='juliet@capulet.lit'/>
<presence from='romeo@montaigu.lit/orchard'
          to='pubsub.capulet.lit'/>

7. Configuration

Server SHOULD provide a way for clients to check already granted permission, and revoke them by using Ad-Hoc Commands (XEP-0050) [6] on the well-defined command node 'urn:xmpp:privilege:0#configure'.

If present, the configuration commands MUST allow at least to check permissions granted to a privileged entity, and to revoke them. A server MAY offer an option to keep permission from one session to an other (see business rules).

8. Discovering Support

If a server or an entity supports the privileged entity protocol, it MUST report that fact by including a service discovery feature of "urn:xmpp:privilege:0" in response to a Service Discovery (XEP-0030) [7] information request:

Example 26. Service Discovery information request

<iq from='pubsub.capulet.net'
    id='disco1'
    to='capulet.net'
    type='get'>
  <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
  

Example 27. Service Discovery information response

<iq from='capulet.net'
    id='disco1'
    to='pubsub.capulet.net'
    type='result'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    ...
    <feature var='urn:xmpp:privilege:0'/>
    ...
  </query>
</iq>
  

9. Business Rules

  1. In client mode, server MAY keep permission granted to an entity by a client from one session to an other, but if it do so, it MUST provide configuration like explained in the suitable section. If server offers this feature, it SHOULD add a field directly in configuration commands.
  2. If a client can't check or revoke permission (i.e. it doesn't support Ad-Hoc Commands (XEP-0050) [8]) when granting permissions, the server MUST NOT keep granted permissions from one session to an other, and permissions will be asked on each new session.
  3. If permissions are changed during a session, server MUST notify privileged entity of the new permissions, like in permission request use case.
  4. A server MUST NOT grant permission for this XEP namespace ('urn:xmpp:privilege:0').

10. Implementation Notes

As admin mode is far more easy to implement than client mode, a server MAY choose to only implement the former.

11. Security Considerations

  1. Privileged entity nearly have the same possibility as the server itself, admin permission should be granted carefuly, only if you absolutely trust the entity.
  2. A server MAY choose to filter allowed namespaces, to avoid giving dangerous permissions. In this case, it MUST always set the allowed type of filtered namespaces to "none"
  3. Roster presence is particulary sensitive, because if an entity accept this permission, it shares presence information of its whole roster. For this reason, a server MAY choose to forbid its use in client mode (by always setting the allowed type to "none"). A server SHOULD at least disallow it in default configuration.
  4. In case of filtering, a whitelist system is more secure and SHOULD be prefered to a blacklist (idealy, configuration would allow no filtering, whitelist filtering and blacklist filtering).

12. IANA Considerations

This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [9].

13. XMPP Registrar Considerations

13.1 Protocol Namespaces

The XMPP Registrar [10] includes 'urn:xmpp:privilege:0' in its registry of protocol namespaces (see <http://xmpp.org/registrar/namespaces.html>).

13.2 Protocol Versioning

If the protocol defined in this specification undergoes a revision that is not fully backwards-compatible with an older version, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.

14. XML Schema

<?xml version='1.0' encoding='UTF-8'?>

<xs:schema
    xmlns:xs='http://www.w3.org/2001/XMLSchema'
    targetNamespace='urn:xmpp:privilege:0'
    xmlns='urn:xmpp:privilege:0'
    elementFormDefault='qualified'>

  <xs:element name='query'>
      <xs:complexType>
          <xs:attribute name='type' use='required'>
              <xs:simpleType base='xs:NMTOKEN'>
                  <xs:enumeration value='request'/>
                  <xs:enumeration value='allowed'/>
              </xs:simpleType>
          </xs:attribute>
          <xs:attribute name='privilege' use='optional'>
              <xs:simpleType base='xs:NMTOKEN'>
                  <xs:enumeration value='admin'/>
                  <xs:enumeration value='client'/>
              </xs:simpleType>
          </xs:attribute>
          <xs:attribute name='to' use='optional' type='xs:string'/>
          </xs:attribute>
          <xs:element name='perm'
                      maxOccurs='unbounded'>
              <xs:complexType>
                  <xs:attribute name='namespace' use='required' type='xs:string'/>
                  <xs:attribute name='type' use='required'>
                      <xs:simpleType base='xs:NMTOKEN'>
                          <xs:enumeration value='none'/>
                          <xs:enumeration value='get'/>
                          <xs:enumeration value='set'/>
                          <xs:enumeration value='both'/>
                      </xs:simpleType>
                  </xs:attribute>
              </xs:complexType>
          </xs:element>
      </xs:complexType>
  </xs:element>

</xs:schema>
    

15. Acknowledgements

Thanks to Sergey Dobrov, Dave Cridland, Steven Lloyd Watkin, Lance Stout and Johannes Hund for their feedbacks. Thanks to Adrien Cossa for his typos/style corrections.

The client mode permission mechanism is inspired from Remote Roster Management (XEP-0321) [11] permission request.


Appendices


Appendix A: Document Information

Series: XEP
Number: xxxx
Publisher: XMPP Standards Foundation
Status: ProtoXEP
Type: Standards Track
Version: 0.0.3
Last Updated: 2014-11-13
Approving Body: XMPP Council
Dependencies: XMPP Core, XEP-0114, XEP-0004
Supersedes: None
Superseded By: None
Short Name: NOT_YET_ASSIGNED
This document in other formats: XML  PDF


Appendix B: Author Information

Jérôme Poisson

Email: goffi@goffi.org
JabberID: goffi@jabber.fr


Appendix C: Legal Notices

Copyright

This XMPP Extension Protocol is copyright (c) 1999 - 2014 by the XMPP Standards Foundation (XSF).

Permissions

Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.

Disclaimer of Warranty

## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##

Limitation of Liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

IPR Conformance

This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at <http://xmpp.org/extensions/ipr-policy.shtml> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).

Appendix D: Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.


Appendix E: Discussion Venue

The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.

Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.

Errata can be sent to <editor@xmpp.org>.


Appendix F: Requirements Conformance

The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".


Appendix G: Notes

1. XEP-0114: Jabber Component Protocol <http://xmpp.org/extensions/xep-0114.html>.

2. XEP-0004: Data Forms <http://xmpp.org/extensions/xep-0004.html>.

3. XEP-0297: Message Forwarding <http://xmpp.org/extensions/xep-0297.html>.

4. RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core <http://tools.ietf.org/html/rfc6120>.

5. RFC 6121: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence <http://tools.ietf.org/html/rfc6121>.

6. XEP-0050: Ad-Hoc Commands <http://xmpp.org/extensions/xep-0050.html>.

7. XEP-0030: Service Discovery <http://xmpp.org/extensions/xep-0030.html>.

8. XEP-0050: Ad-Hoc Commands <http://xmpp.org/extensions/xep-0050.html>.

9. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.

10. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <http://xmpp.org/registrar/>.

11. XEP-0321: Remote Roster Management <http://xmpp.org/extensions/xep-0321.html>.


Appendix H: Revision History

Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/

Version 0.0.3 (2014-11-13)

(jp)

Version 0.0.2 (2014-09-17)

(jp)

Version 0.0.1 (2014-05-09)

First draft.

(jp)

END