diff --git a/inbox/cs2017.xml b/inbox/cs2017.xml new file mode 100644 index 00000000..e8548cdb --- /dev/null +++ b/inbox/cs2017.xml @@ -0,0 +1,318 @@ + + +%ents; +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."> +Not required for command line or terminal based interfaces."> +]> + + +
+ XMPP Compliance Suites 2017 + + This document defines XMPP protocol compliance levels for 2017. + + &LEGALNOTICE; + 0375 + Experimental + Standards Track + Standards + + RFC 6120 + RFC 6121 + RFC 6122 + RFC 7395 + RFC 7590 + 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-0375 + + + CS2017 + &sam; + + 0.0.1 + 2015-09-30 + ssw +

First draft updated from XEP-0375.

 + +
+ +

+ The &XSF; defines protocol suites for the purpose of compliance testing + and software certification. + This document specifies the 2017 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. + A feature is considered supported if all comma separated feature providers + listed in the "Providers" column are implemented (unless otherwise noted). +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureCore ServerCore ClientAdvanced ServerAdvanced ClientProviders
Core features✓✓✓✓&rfc6120;, &rfc6122;
TLS✓✓✓✓&rfc7590;
Feature discovery✓✓✓✓&xep0030;
Feature broadcasts✕✓✓&forpep;✓&xep0115;
Server Extensibility✓N/A✓N/A&xep0114;
Event publishing✕✕✓✓&xep0163;
+ + +

+ To be considered XMPP web compliant, all features from the core + compliance suite must be met, as well as all features in this suite. +

+ + + + + + + + + + + + + + + + + +
FeatureCore ServerCore ClientAdvanced ServerAdvanced ClientProviders
Web Connection Mechanisms✓&component;✓&onlyone;✓&component;✓&onlyone;&rfc7395;, &xep0206; (See also: &xep0124;)
+ + +

+ To be considered XMPP IM compliant, all features from the core + compliance suite must be met, as well as all features in this suite. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureCore ServerCore ClientAdvanced ServerAdvanced ClientProviders
Core features✓✓✓✓&rfc6121;
User AvatarsN/A✓&nocli;N/A✓&nocli;&xep0084;
Outbound Message Synchronization✓✓✓✓&xep0280;
User Blocking✕✕✓✓&xep0191;
Group Chat✓&component;✓&usecases;✓&component;✓&usecases;&xep0045;Implementations should take note that future versions of these compliance suites may rely on &xep0369; instead.
Bookmarks✕✕✓&component;✓&xep0048;
Session Resumption✕✕✓✓&xep0198;
Stanza Acknowledgements✕✕✓✓&xep0198;
History Storage / Retrieval✕✕✓✓&xep0313;
+ + +

+ To be considered XMPP mobile compliant, all features from the core + compliance suite must be met, as well as all features in this suite. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureCore ServerCore ClientAdvanced ServerAdvanced ClientProviders
Session Resumption✓✓✓✓&xep0198;
Stanza Acknowledgements✓✓✓✓&xep0198;
Client State Indiciation✓✓✓✓&xep0352;
Third Party Push Notifications✕✕✓&component;✓&xep0357;
+ + + +

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

+ + +

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

+ + +

This document requires no interaction with &IANA;.

+ + +

This document requires no interaction with the ®ISTRAR;.

+ + +

+ 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 their suggestions. +

+ +