diff options
authorFlorian Schmaus <flo@geekplace.eu>2017-10-06 16:18:06 +0200
committerSam Whited <sam@samwhited.com>2017-10-06 09:24:33 -0500
commit83624c9f94da430eb800ed8b37a78587ccdc0a86 (patch)
parent0071bdd205f37fca1df7f9760bc2dded1c6ed99d (diff)
XEP-0388 SASL2: Avoid superfluous whitespaces in Example 1-3
1 files changed, 3 insertions, 6 deletions
diff --git a/xep-0388.xml b/xep-0388.xml
index e81944a..9943186 100644
--- a/xep-0388.xml
+++ b/xep-0388.xml
@@ -104,8 +104,7 @@
<authenticate xmlns='urn:xmpp:sasl:1' mechanism="BLURDLYBLOOP">
- </example>
<p>In order to provide support for other desired stream states beyond authentication, additional child elements are used. For example, a hypothetical XEP-0198 session resumption element might be included, and/or Resource Binding requests.</p>
<example caption="An authentication request with a (hypothetical) bind request"><![CDATA[
<authenticate xmlns='urn:xmpp:sasl:1' mechanism='BLURDYBLOOP'>
@@ -114,8 +113,7 @@
<bind xmlns='urn:xmpp:bind:example'/>
- </example>
<section2 topic="Challenges and Responses" anchor="challenge">
<p>Server Challenges MAY then be sent. Each Challenge MUST be responded to by a Client in a Client Response. These are not extensible, and contain the corresponding base64 encoded SASL data:</p>
@@ -129,8 +127,7 @@
<response xmlns='urn:xmpp:sasl:1'>
- </example>
<section2 topic="During Authentication">
<p>At any time while authentication is in progress, neither Client nor Server sends any element (including stanzas) or other data except the top-level elements defined herein. Clients MUST NOT send whitespace, and MUST send only &lt;response/> elements as appropriate or an &lt;abort/> element to immediately cause an error. Servers MUST disconnect Clients immediately if any other traffic is received. Servers are similarly REQUIRED to send no whitespace, and only the &lt;response/> and completion elements from the section below.</p>