Difference between revisions of "Interop Event Test Cases"

From XMPP WIKI
Jump to navigation Jump to search
m
 
(2 intermediate revisions by 2 users not shown)
Line 27: Line 27:
== SASL ==
== SASL ==


See [http://www.xmpp.org/specs/rfc3920.html#sasl Section 6] of [http://www.xmpp.org/specs/rfc3920.html RFC 3920]
See [http://www.xmpp.org/specs/rfc3920.html#sasl Section 6] of [http://www.xmpp.org/specs/rfc3920.html RFC 3920] (including authzid)


== Resource Binding ==
== Resource Binding ==
Line 44: Line 44:


See [http://www.xmpp.org/specs/rfc3920.html#rfc.section.3.2 Section 3.2] of [http://www.xmpp.org/specs/rfc3920.html RFC 3920]
See [http://www.xmpp.org/specs/rfc3920.html#rfc.section.3.2 Section 3.2] of [http://www.xmpp.org/specs/rfc3920.html RFC 3920]
[[Category:Interop]]

Latest revision as of 19:22, 5 August 2019

This page lists various test cases that will be addressed at the Interop Event.

XML Streams

See Section 4 of RFC 3920

Should test all stream error conditions, in particular the following for stream setup (i.e., before negotiation of TLS, SASL, etc.):

  • invalid streams namespace
  • unsupported default namespace
  • bad namespace prefix
  • host gone, host unknown, see other host
  • unsupported version

TLS

See Section 5 of RFC 3920

Should test the following:

  • Self-signed certificates
  • Certificates issued by root CA
  • Certificates issued by Intermediate CA

Testing non-cert TLS auth (e.g., IPSec) is probably out of scope for now...

SASL

See Section 6 of RFC 3920 (including authzid)

Resource Binding

See Section 7 of RFC 3920

Address Determination

See Section 3.5 of RFC 3920

Server Dialback

See Section 8 of RFC 3920

Internationalized Domain Names

See Section 3.2 of RFC 3920