XEP-0412: XMPP Compliance Suites 2019

Transcription

1 0412: XMPP Compliance Suites 2019 Jonas Schäfer Version Status Type Short Name Proposed Standards Track CS2019 This document defines XMPP protocol compliance levels.

2 Legal Copyright This XMPP Extension Protocol is copyright by XMPP Standards Foundation (XSF). Permissions Permission is hereby granted, free of charge, to any person obtaining a copy of this specification ( Specification ), to make use of Specification without restriction, including without limitation rights to implement Specification in a software program, deploy Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of Specification, and to permit persons to whom Specification is furnished to do so, subject to condition that foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding authors, title, number, or publisher of Specification, and shall not claim endorsement of modified works by authors, any organization or project to which authors belong, or XMPP Standards Foundation. Warranty ## NOTE WELL: This Specification is provided on an AS IS BASIS, WITHOUT WARRANTIES OR CONDI- TIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ## Liability In no event and under no legal ory, wher in tort (including negligence), contract, or orwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall 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 Specification or implementation, deployment, or or use of Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all or commercial damages or losses), even if XMPP Standards Foundation or such author has been advised of possibility of such damages. Conformance This XMPP Extension Protocol has been contributed in full conformance with XSF s Intellectual Property Rights Policy (a copy of which can be found at < or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO USA).

3 Contents 1 Introduction 1 2 Compliance Levels Core Compliance Suite Web Compliance Suite IM Compliance Suite Mobile Compliance Suite Implementation Notes 18 4 Security Considerations 18 5 IANA Considerations 19 6 XMPP Registrar Considerations 19 7 Acknowledgements 19

4 1 Introduction The XMPP Standards Foundation (XSF) 1 defines protocol suites for purpose of compliance testing and software certification. This document specifies compliance levels for XMPP clients and servers; it is hoped that this document will advance state of art, and provide guidance and eventual certification to XMPP client and server authors. Unless explicitly noted, support for listed specifications is REQUIRED for compliance purposes. A feature is considered supported if all comma separated feature providers listed in Providers column are implemented (unless orwise noted). 2 Compliance Levels 2.1 Core Compliance Suite 1 The XMPP Standards Foundation (XSF) is an independent, non-profit membership organization that develops open extensions to IETF s Extensible Messaging and Presence Protocol (XMPP). For furr information, see < 1

5 Core Core Advanced Advanced Providers Core features RFC 6120 RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core < RFC 7622 RFC 7622: Extensible Messaging and Presence Protocol (XMPP): Address Format < is not listed due to unclear interoperability impact of using PRECIS and Stringprep in same ecosystem. 2

6 < ns/x ns/x ns/x Core Core Advanced Advanced Providers TLS RFC 7590 RFC 7590: Use of Transport Layer Security (TLS) in Extensible Messaging and Presence Protocol (XMPP) Direct TLS support of SRV records 0368 for XMPP means over TLS having ability 0368) XEPto accept 0368: SRV direct TLS records connections. for XMPP over TLS discovery 0368.html>. Service Discovery 0030) 0030: Service Discovery broadcasts 0030.html>. Entity Capabilities 0115) 0115: Entity Capabilities 0115.html>. 3

7 ns/x Core Core Advanced Advanced Providers Extensibility N/A N/A Jabber Component Protocol 0114) 0114: Jabber Component Protocol Event publishing While Personal Eventing Protocol 0114.html>. does not require all features of Publish- Subscribe to be available on users JIDs, and nor does this suite, it is desirable for this to be case and it is expected that this will a requirement of future Compliance Suites. Personal Eventing Protocol 0163) 0163: Personal Eventing Protocol ns/x 0163.html>. 4

8 2.2 Web Compliance Suite To be considered XMPP web compliant, all features from core compliance suite must be met, as well as all features in this suite. 5

9 Core Core Advanced Advanced Providers Web Connection Mechanisms Support can be enabled via an external component or an internal server module/- plugin. If claiming compliance using such an addition, necessary compo- nents/- ules/- plugins MUST be detailed. Only one of recommended providers must be implemented for compliance. Support can be enabled via an external component or an internal server module/- plugin. If claiming compliance using such an addition, necessary compo- nents/- ules/- plugins MUST be detailed. Only one of recommended providers must be implemented for compliance. RFC 7395 RFC 7395: An Extensible Messaging and Presence Protocol (XMPP) Subprotocol for Web- Socket < XMPP Over BOSH 0206) 0206: XMPP Over BOSH ns/ 0206.html>. (See also: BOSH 0124) 0124: Bidirectionalstreams Over Synchronous HTTP ns/ 0124.html>.) 6

10 2.3 IM Compliance Suite To be considered XMPP IM compliant, all features from core compliance suite must be met, as well as all features in this suite. < Core Core Advanced AdvancedProviders Core features RFC 6121 RFC 6121: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence User Avatars N/A N/A Not required for command line or terminal based interfaces. User Avatar 0084) 0084: User Avatar 0084.html>. 7

11 Core Core Advanced AdvancedProviders User Avatar Compatibility Not required for command line or terminal based interfaces. User Avatar to vcard- Based Avatars Conversion 0398) 0398: User Avatar to vcard- Based Avatars Conversion 0398.html>., vcard- Based Avatars 0153) 0153: vcard- Based Avatars 0153.html>. 8

12 Core Core Advanced AdvancedProviders vcard-temp vcardtemp 0054) 0054: vcardtemp Outbound Message Synchronization 0054.html>. Message Carbons 0280) 0280: Message Carbons User Blocking 0280.html>. Blocking Command 0191) 0191: Blocking Command 0191.html>. 9

13 Core Core Advanced Advanced Providers Group Chat Support can be enabled via an external component or an internal server ule/- plugin. If claiming compliance using such an addition, necessary components/- ules/- plugins MUST be detailed. Support for Entity Use Cases and Occupant Use Cases is RE- QUIRED; support for remaining use cases is REC- OM- MENDED. Support can be enabled via an external component or an internal server ule/- plugin. If claiming compliance using such an addition, necessary components/- ules/- plugins MUST be detailed. Support for Entity Use Cases and Occupant Use Cases is RE- QUIRED; support for remaining use cases is REC- OM- MENDED. Multi- User Chat 0045) 0045: Multi- User Chat 0045.html>.Implementation should take note that future versions of se compliance suites may rely on Mediated Information exchange (MIX) 0369) 0369: Mediated Information exchange (MIX) 0369.html>. instead., Direct MUC 10

14 Core Core Advanced AdvancedProviders Bookmarks Support Bookmark can be enabled via an external component or an internal server ule/- plugin. If claiming compliance using such an addition, necessary components/- ules/- plugins MUST be detailed. Storage 0048) 0048: Bookmark Storage 0048.html>. 11

15 Core Core Advanced AdvancedProviders Persistent Storage of Private Data via PubSub Support Best can be enabled via an external component or an internal server ule/- plugin. If claiming compliance using such an addition, necessary components/- ules/- plugins MUST be detailed. Practices for Persistent Storage of Private Data via Publish- Subscribe 0223) 0223: Best Practices for Persistent Storage of Private Data via Publish- Subscribe 0223.html>. 12

16 Core Core Advanced AdvancedProviders Private XML Storage Support Private can be enabled via an external component or an internal server ule/- plugin. If claiming compliance using such an addition, necessary components/- ules/- plugins MUST be detailed. XML Storage 0049) 0049: Private XML Storage 0049.html>. 13

17 Core Core Advanced AdvancedProviders Session Resumption Stream Management 0198) 0198: Stream Management Stanza Acknowledgements 0198.html>. Stream Management 0198) 0198: Stream Management 0198.html>. 14

18 Core Core Advanced AdvancedProviders Message Acknowledgements N/A N/A Message Delivery Receipts 0184) 0184: Message Delivery Receipts History Storage / Retrieval 0184.html>. Message Archive Management 0313) 0313: Message Archive Management 0313.html>. 15

19 Core Core Advanced AdvancedProviders Chat States N/A N/A Chat State Notifications 0085) 0085: Chat State Notifications Message Correction N/A N/A 0085.html>. Last Message Correction 0308) 0308: Last Message Correction 0308.html>. 2.4 Mobile Compliance Suite To be considered XMPP mobile compliant, all features from core compliance suite must be met, as well as all features in this suite. 16

20 ns ns ns Core Core Advanced Advanced Providers Session Resumption Stream Management 0198) 0198: Stream Management Stanza Acknowledgements 0198.html>. Stream Management 0198) 0198: Stream Management State Indication 0198.html>. State Indication 0352) 0352: State Indication 0352.html>. 17

21 4 SECURITY CONSIDERATIONS Core Core Advanced Third Party Push Notifications Support can be enabled via an external component or an internal server module/plugin. If claiming compliance using such an addition, necessary compo- nents/- ules/- plugins MUST be detailed. Advanced Providers Push Notifications 0357) 0357: Push Notifications ns 0357.html>. 3 Implementation Notes Some of protocol specifications referenced herein have ir own dependencies; developers need to consult relevant specifications for furr information. 4 Security Considerations This document introduces no additional security considerations above and beyond those defined in documents on which it depends. 18

22 7 ACKNOWLEDGEMENTS 5 IANA Considerations This document requires no interaction with Internet Assigned Numbers Authority (IANA) 2. 6 XMPP Registrar Considerations This document requires no interaction with XMPP Registrar 3. 7 Acknowledgements The author would like to thank Guus der Kinderen, Dele Olajide, Marc Laporte, Dave Cridland, Daniel Gultsch, Florian Schmaus, Tobias Markmann, and Georg Lukas for ir suggestions. 2 The Internet Assigned Numbers Authority (IANA) is central coordinator for assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For furr information, see < 3 The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in context of XMPP extension protocols approved by XMPP Standards Foundation. For furr information, see < 19