forked from xsf/xeps
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathxep-0387.xml
413 lines (413 loc) · 15.2 KB
/
xep-0387.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
<!ENTITY component "<note>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.</note>">
<!ENTITY usecases "<note>Support for the Entity Use Cases and Occupant Use Cases is REQUIRED; support for the remaining use cases is RECOMMENDED.</note>">
<!ENTITY onlyone "<note>Only one of the recommended providers must be implemented for compliance.</note>">
<!ENTITY nocli "<note>Not required for command line or terminal based interfaces.</note>">
<!ENTITY avatar "<note>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.</note>">
<!ENTITY pubsubjid "<note>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.</note>">
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
<title>XMPP Compliance Suites 2018</title>
<abstract>
This document defines XMPP protocol compliance levels.
</abstract>
&LEGALNOTICE;
<number>0387</number>
<status>Obsolete</status>
<lastcall>2017-12-21</lastcall>
<lastcall>2017-11-15</lastcall>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
<dependencies>
<spec>RFC 6120</spec>
<spec>RFC 6121</spec>
<spec>RFC 7395</spec>
<spec>RFC 7590</spec>
<spec>RFC 7622</spec>
<spec>XEP-0030</spec>
<spec>XEP-0045</spec>
<spec>XEP-0048</spec>
<spec>XEP-0049</spec>
<spec>XEP-0084</spec>
<spec>XEP-0085</spec>
<spec>XEP-0114</spec>
<spec>XEP-0115</spec>
<spec>XEP-0124</spec>
<spec>XEP-0163</spec>
<spec>XEP-0191</spec>
<spec>XEP-0198</spec>
<spec>XEP-0206</spec>
<spec>XEP-0223</spec>
<spec>XEP-0249</spec>
<spec>XEP-0280</spec>
<spec>XEP-0313</spec>
<spec>XEP-0352</spec>
<spec>XEP-0368</spec>
</dependencies>
<supersedes>
<spec>XEP-0375</spec>
</supersedes>
<supersededby>
<spec>XEP-0412</spec>
</supersededby>
<shortname>CS2018</shortname>
&sam;
&jonaswielicki;
<revision>
<version>1.0.0</version>
<date>2018-01-25</date>
<initials>XEP Editor (jwi)</initials>
<remark><p>Move to Draft as per Council vote on 2018-01-24.</p></remark>
</revision>
<revision>
<version>0.4</version>
<date>2018-01-25</date>
<initials>kis</initials>
<remark><p>Address recent feedback</p></remark>
</revision>
<revision>
<version>0.3.3</version>
<date>2018-01-23</date>
<initials>XEP Editor (jwi)</initials>
<remark><p>Add Jonas as author.</p><p>Move back to experimental.</p></remark>
</revision>
<revision>
<version>0.3.2</version>
<date>2018-01-18</date>
<initials>XEP Editor (ssw, revision added by jwi)</initials>
<remark><p>Rejected by council</p></remark>
</revision>
<revision>
<version>0.3.1</version>
<date>2017-11-04</date>
<initials>ssw</initials>
<remark><p>Update RFC 6122 references to RFC 7622</p></remark>
</revision>
<revision>
<version>0.3.0</version>
<date>2017-11-01</date>
<initials>ssw</initials>
<remark><p>Bump year to 2018</p></remark>
</revision>
<revision>
<version>0.2.0</version>
<date>2017-02-10</date>
<initials>ssw</initials>
<remark>
<ul>
<li>Add XEP-0085: Chat State Notifications</li>
<li>Add XEP-0249: Direct MUC Invitations</li>
<li>Add XEP-0368: SRV records for XMPP over TLS</li>
<li>Typo fixes (thanks to Georg Lucas)</li>
</ul>
</remark>
</revision>
<revision>
<version>0.1.0</version>
<date>2017-02-08</date>
<initials>ssw</initials>
<remark>
<p>First draft updated from XEP-0375 accepted by the council.</p>
</remark>
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
<p>
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).
</p>
</section1>
<section1 topic='Compliance Levels' anchor='levels'>
<section2 topic='Core Compliance Suite' anchor='core'>
<table caption='XMPP Core Compliance Levels'>
<tr>
<th>Feature</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
<th>Providers</th>
</tr>
<tr>
<td><strong>Core features</strong></td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&rfc6120;, &rfc7622;</td>
</tr>
<tr>
<td><strong>TLS</strong></td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&rfc7590;, &xep0368;<note>Server support means having the ability to accept direct TLS connections.</note></td>
</tr>
<tr>
<td><strong>Feature discovery</strong></td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0030;</td>
</tr>
<tr>
<td><strong>Feature broadcasts</strong></td>
<td align='center'>✕</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0115;</td>
</tr>
<tr>
<td><strong>Server Extensibility</strong></td>
<td align='center'>✓</td>
<td align='center'>N/A</td>
<td align='center'>✓</td>
<td align='center'>N/A</td>
<td>&xep0114;</td>
</tr>
<tr>
<td><strong>Event publishing</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓&pubsubjid;</td>
<td align='center'>✓</td>
<td>&xep0163;</td>
</tr>
</table>
</section2>
<section2 topic='Web Compliance Suite' anchor='web'>
<p>
To be considered XMPP web compliant, all features from the core
compliance suite must be met, as well as all features in this suite.
</p>
<table caption='XMPP Web Compliance Levels'>
<tr>
<th>Feature</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
<th>Providers</th>
</tr>
<tr>
<td><strong>Web Connection Mechanisms</strong></td>
<td align='center'>✓&component;</td>
<td align='center'>✓&onlyone;</td>
<td align='center'>✓&component;</td>
<td align='center'>✓&onlyone;</td>
<td>&rfc7395;, &xep0206; (See also: &xep0124;)</td>
</tr>
</table>
</section2>
<section2 topic='IM Compliance Suite' anchor='im'>
<p>
To be considered XMPP IM compliant, all features from the core
compliance suite must be met, as well as all features in this suite.
</p>
<table caption='XMPP IM Compliance Levels'>
<tr>
<th>Feature</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
<th>Providers</th>
</tr>
<tr>
<td><strong>Core features</strong></td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&rfc6121;</td>
</tr>
<tr>
<td><strong>User Avatars</strong></td>
<td align='center'>N/A</td>
<td align='center'>✓&nocli;&avatar;</td>
<td align='center'>N/A</td>
<td align='center'>✓&nocli;&avatar;</td>
<td>&xep0084;&xep0153;</td>
</tr>
<tr>
<td><strong>vcard-temp</strong></td>
<td align='center'>✓</td>
<td align='center'>✓&nocli;</td>
<td align='center'>✓</td>
<td align='center'>✓&nocli;</td>
<td>&xep0054;</td>
</tr>
<tr>
<td><strong>Outbound Message Synchronization</strong></td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0280;</td>
</tr>
<tr>
<td><strong>User Blocking</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0191;</td>
</tr>
<tr>
<td><strong>Group Chat</strong></td>
<td align='center'>✓&component;</td>
<td align='center'>✓&usecases;</td>
<td align='center'>✓&component;</td>
<td align='center'>✓&usecases;</td>
<td>&xep0045;<note>Implementations should take note that future versions of these compliance suites may rely on &xep0369; instead.</note>, &xep0249;</td>
</tr>
<tr>
<td><strong>Bookmarks</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓&component;</td>
<td align='center'>✓</td>
<td>&xep0048;</td>
</tr>
<tr>
<td><strong>Persistent Storage of Private Data via PubSub</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓&component;</td>
<td align='center'>✓</td>
<td>&xep0223;</td>
</tr>
<tr>
<td><strong>Private XML Storage</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓&component;</td>
<td align='center'>✓</td>
<td>&xep0049;</td>
</tr>
<tr>
<td><strong>Session Resumption</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0198;</td>
</tr>
<tr>
<td><strong>Stanza Acknowledgements</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0198;</td>
</tr>
<tr>
<td><strong>History Storage / Retrieval</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0313;</td>
</tr>
<tr>
<td><strong>Chat States</strong></td>
<td align='center'>N/A</td>
<td align='center'>✕</td>
<td align='center'>N/A</td>
<td align='center'>✓</td>
<td>&xep0085;</td>
</tr>
</table>
</section2>
<section2 topic='Mobile Compliance Suite' anchor='mobile'>
<p>
To be considered XMPP mobile compliant, all features from the core
compliance suite must be met, as well as all features in this suite.
</p>
<table caption='XMPP Mobile Compliance Levels'>
<tr>
<th>Feature</th>
<th>Core Server</th>
<th>Core Client</th>
<th>Advanced Server</th>
<th>Advanced Client</th>
<th>Providers</th>
</tr>
<tr>
<td><strong>Session Resumption</strong></td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0198;</td>
</tr>
<tr>
<td><strong>Stanza Acknowledgements</strong></td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0198;</td>
</tr>
<tr>
<td><strong>Client State Indiciation</strong></td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td align='center'>✓</td>
<td>&xep0352;</td>
</tr>
<tr>
<td><strong>Third Party Push Notifications</strong></td>
<td align='center'>✕</td>
<td align='center'>✕</td>
<td align='center'>✓&component;</td>
<td align='center'>✓</td>
<td>&xep0357;</td>
</tr>
</table>
</section2>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>
<p>
Some of the protocol specifications referenced herein have their own
dependencies; developers need to consult the relevant specifications for
further information.
</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>
This document introduces no additional security considerations above and
beyond those defined in the documents on which it depends.
</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<p>This document requires no interaction with the ®ISTRAR;.</p>
</section1>
<section1 topic='Acknowledgements' anchor='ack'>
<p>
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.
</p>
</section1>
</xep>