XEP-0375: XMPP Compliance Suites 2016

Document Lifecycle Experimental Retracted Proposed Draft Final

The XMPP Standards Foundation (XSF) [1] defines protocol suites for the purpose of compliance testing and software certification. This document specifies the 2016 compliance levels for XMPP clients and servers; it is hoped that this document will advance the state of the art, and provide guidence and eventual certification to XMPP client and server authors. Unless explicitly noted, support for the listed specifications is REQUIRED for compliance purposes.

2. Compliance Levels ¶

2.2 Web Compliance Suite ¶ To be considered XMPP web compliant, all line items from the core compliance suite above must be met, as well as all items in this suite. Table 2: XMPP Web Compliance Levels for 2016 ¶ Feature Core Server Core Client Advanced Server Advanced Client Providers Web Connection Mechanisms ✓† ✓§ ✓† ✓§ RFC 7395 8], BOSH (XEP-0124) 9] and XMPP Over BOSH (XEP-0206) 10]

* Necessary to support Personal Eventing Protocol (PEP).

† Support can be enabled via an external component or an internal server module/plugin.

‡ Support for the Entity Use Cases and Occupant Use Cases is REQUIRED; support for the remaining use cases is RECOMMENDED.

§ Only one of the recommended providers must be implemented for compliance.

3. Implementation Notes ¶

Some of the protocol specifications referenced herein have their own dependencies; developers need to consult the relevant specifications for further information.

4. Security Considerations ¶

This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.

5. IANA Considerations ¶

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

6. XMPP Registrar Considerations ¶

This document requires no interaction with the XMPP Registrar [23].

The author would like to thank Guus der Kinderen, Dele Olajide, Marc Laporte, Dave Cridland and Daniel Gultsch for their suggestions.

Appendices

Appendix A: Document Information ¶

Series XEP Number 0375 Publisher XMPP Standards Foundation Status Retracted Type Standards Track Version 0.3 Last Updated 2016-07-20 Approving Body XMPP Council Dependencies RFC 6120, RFC 6121, RFC 6122, RFC 7395, XEP-0030, XEP-0045, XEP-0084, XEP-0114, XEP-0115, XEP-0124, XEP-0163, XEP-0191, XEP-0198, XEP-0206, XEP-0280, XEP-0313, XEP-0352, XEP-0369 Supersedes XEP-0270 Superseded By XEP-0387 Short Name CS2016 Source Control HTML

This document in other formats: XML PDF

Appendix B: Author Information ¶

Peter Saint-Andre

Sam Whited

Appendix C: Legal Notices ¶

Copyright This XMPP Extension Protocol is copyright © 1999 – 2020 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. ## 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 from, out of, or in connection with the Specification or the implementation, deployment, or other use of 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 can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA). Visual Presentation The HTML representation (you are looking at) is maintained by the XSF. It is based on the YAML CSS Framework, which is licensed under the terms of the CC-BY-SA 2.0 license.

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.

Given that this XMPP Extension Protocol normatively references IETF technologies, discussion on the <xsf-ietf@xmpp.org> list might also be appropriate.

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. The XMPP Standards Foundation (XSF) is an independent, non-profit membership organization that develops open extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP). For further information, see <https://xmpp.org/about/xmpp-standards-foundation>. 2. RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core <http://tools.ietf.org/html/rfc6120>. 3. RFC 6122: Extensible Messaging and Presence Protocol (XMPP): Address Format <http://tools.ietf.org/html/rfc6122>. 4. XEP-0030: Service Discovery <https://xmpp.org/extensions/xep-0030.html>. 5. XEP-0115: Entity Capabilities <https://xmpp.org/extensions/xep-0115.html>. 6. XEP-0114: Jabber Component Protocol <https://xmpp.org/extensions/xep-0114.html>. 7. XEP-0163: Personal Eventing Protocol <https://xmpp.org/extensions/xep-0163.html>. 8. RFC 7395: An Extensible Messaging and Presence Protocol (XMPP) Subprotocol for WebSocket <http://tools.ietf.org/html/rfc7395>. 9. XEP-0124: Bidirectional-streams Over Synchronous HTTP <https://xmpp.org/extensions/xep-0124.html>. 10. XEP-0206: XMPP Over BOSH <https://xmpp.org/extensions/xep-0206.html>. 11. RFC 6121: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence <http://tools.ietf.org/html/rfc6121>. 12. XEP-0084: User Avatar <https://xmpp.org/extensions/xep-0084.html>. 13. XEP-0280: Message Carbons <https://xmpp.org/extensions/xep-0280.html>. 14. XEP-0313: Message Archive Management <https://xmpp.org/extensions/xep-0313.html>. 15. XEP-0191: Blocking Command <https://xmpp.org/extensions/xep-0191.html>. 16. XEP-0045: Multi-User Chat <https://xmpp.org/extensions/xep-0045.html>. 17. XEP-0369: Mediated Information eXchange (MIX) <https://xmpp.org/extensions/xep-0369.html>. 18. XEP-0048: Bookmark Storage <https://xmpp.org/extensions/xep-0048.html>. 19. XEP-0198: Stream Management <https://xmpp.org/extensions/xep-0198.html>. 20. XEP-0352: Client State Indication <https://xmpp.org/extensions/xep-0352.html>. 21. XEP-0357: Push Notifications <https://xmpp.org/extensions/xep-0357.html>. 22. 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/>. 23. 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 <https://xmpp.org/registrar/>.

Appendix H: Revision History ¶

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

Version 0.3 (2016-07-20) ¶ Don't require both BOSH and Websockets. ssw Version 0.2 (2016-07-11) ¶ Add rationale.

Refactor suites to focus less on XEPs and more on features. ssw Version 0.1.1 (2016-05-25) ¶ Add mobile compliance suites. ssw Version 0.1.0 (2016-05-10) ¶ Initial published version approved by the XMPP Council. XEP Editor (ssw) Version 0.0.1 (2015-09-30) ¶ First draft. ssw

END