diff --git a/xep-0167.xml b/xep-0167.xml
index e1362283..7eb1c1ab 100644
--- a/xep-0167.xml
+++ b/xep-0167.xml
@@ -579,7 +579,7 @@ delivery-method=inline; configuration=somebase16string;
   <crypto 
       crypto-suite='AES_CM_128_HMAC_SHA1_80' 
       key-params='inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:32' 
-      session-params='KDR=1;UNENCRYPTED_SRTCP'
+      session-params='KDR=1 UNENCRYPTED_SRTCP'
       tag='1'/>
 </encryption>
   ]]></code>
@@ -587,7 +587,7 @@ delivery-method=inline; configuration=somebase16string;
   <code><![CDATA[
     a=crypto:1 AES_CM_128_HMAC_SHA1_80
     inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:32
-    session-params:KDR=1;UNENCRYPTED_SRTCP
+    KDR=1 UNENCRYPTED_SRTCP
   ]]></code>
   <p>When the responder receives a session-initiate message containing an &lt;encryption/&gt; element with the 'required' attribute set to TRUE, the responder MUST either (1) accept the offer by denoting one of the &lt;crypto/&gt; elements as acceptable (it does this by mirroring that &lt;crypto/&gt; element in its session acceptance) or (2) reject the offer by sending a session-terminate message with a Jingle reason of &lt;security-error/&gt; (typically with an RTP-specific condition of &lt;invalid-crypto/&gt;).</p>
   <p>If the 'required' attribute is set to FALSE (this is the default), depending on personal security policies or client configuration the responder SHOULD accept the offer if possible, but MAY simply proceed without encryption.</p>
@@ -1134,7 +1134,7 @@ Romeo                         Juliet
           <crypto 
               crypto-suite='AES_CM_128_HMAC_SHA1_80' 
               key-params='inline:WVNfX19zZW1jdGwgKCkgewkyMjA7fQp9CnVubGVz|2^20|1:32' 
-              session-params='KDR=1;UNENCRYPTED_SRTCP'
+              session-params='KDR=1 UNENCRYPTED_SRTCP'
               tag='1'/>
         </encryption>
       </description>