diff --git a/xep-0412.xml b/xep-0412.xml index d3d49c79..0fbf7df1 100644 --- a/xep-0412.xml +++ b/xep-0412.xml @@ -1,384 +1,31 @@ + %ents; -Support can be enabled via an external component or an internal server module/plugin. If claiming compliance using such an addition, the necessary components/modules/plugins MUST be detailed."> -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."> -While 'User Avatars' is more modern, 'vCard-Based Avatars' is more widely deployed. Although it is suggested that to maximise interoperability with existing software a client fully supports both it is sufficient to claim compliance with this suite if the support for 'vCard-Based Avatars' is read-only."> -While 'Personal Eventing Protocol' does not require all the features of 'Publish-Subscribe' to be available on the users' JIDs, and nor does this suite, it is desirable for this to be the case and it is expected that this will a requirement of future Compliance Suites."> ]> -
- XMPP Compliance Suites 2019 - - This document defines XMPP protocol compliance levels. - - &LEGALNOTICE; - 0412 - Experimental - Standards Track - Standards - - RFC 6120 - RFC 6121 - RFC 7395 - RFC 7590 - RFC 7622 - XEP-0030 - XEP-0045 - XEP-0048 - XEP-0049 - XEP-0084 - XEP-0085 - XEP-0114 - XEP-0115 - XEP-0124 - XEP-0163 - XEP-0191 - XEP-0198 - XEP-0206 - XEP-0223 - XEP-0249 - XEP-0280 - XEP-0313 - XEP-0352 - XEP-0368 - - - XEP-0378 - - - CS2019 - &jonaswielicki; +
+ No Such XEP + This document is a tombstone for a XEP which was prematurely published (i.e. before the council vote was completed). + &LEGALNOTICE; + 0412 + Retracted + Informational + Standards + + + + N/A + &jonaswielicki; - 0.1.0 - 2018-12-16 - XEP Editor (jsc) - Accepted by vote of Council on 2018-12-19. + 0.1 + 2018-12-20 + none +

No such specification.

 - - 0.0.1 - 2018-12-08 - jsc - -

First draft based on XEP-0378. Non-editorial Changes:

-
    -
  • Prefer XEP-0084 for Avatars, use XEP-0398 for compat.
    • -
  • Add XEP-0184
    • -
- - -
- -

- The &XSF; defines protocol suites for the 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 the state of the art, and provide - guidance 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;, &rfc7622;
TLS✓Server support of XEP-0368 means having the ability to accept direct TLS connections.✓✓✓&rfc7590;, &xep0368;
Feature discovery✓✓✓✓&xep0030;
Feature broadcasts✕✓✓✓&xep0115;
Server Extensibility✓N/A✓N/A&xep0114;
Event publishing✕✕✓&pubsubjid;✓&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;
User Avatar Compatibility✕✓&nocli;✓✓&nocli;&xep0398;, &xep0153;
vcard-temp✓✓✓✓&xep0054;
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., &xep0249;
Bookmarks✕✕✓&component;✓&xep0048;
Persistent Storage of Private Data via PubSub✕✕✓&component;✓&xep0223;
Private XML Storage✕✕✓&component;✓&xep0049;
Session Resumption✕✕✓✓&xep0198;
Stanza Acknowledgements✕✕✓✓&xep0198;
Message Acknowledgements✕✕✓✓&xep0184;
History Storage / Retrieval✕✕✓✓&xep0313;
Chat StatesN/A✕N/A✓&xep0085;
- - -

- 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 Indication✓✓✓✓&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. -

+
+ +

This document is a tombstone for a XEP which was prematurely published (i.e. before the council vote was completed)..