From 5ce429af431ad62d635789c71d21a4d86296222b Mon Sep 17 00:00:00 2001
From: "Matthew A. Miller" <linuxwolf@outer-planes.net>
Date: Thu, 13 Mar 2014 09:13:13 -0600
Subject: [PATCH] xep-0124 v1.11rc3: community feedback

---
 xep-0124.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/xep-0124.xml b/xep-0124.xml
index 9d3556f8..4e1cde27 100644
--- a/xep-0124.xml
+++ b/xep-0124.xml
@@ -6,6 +6,7 @@
 <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
 <xep>
   <header>
+    <interim/>
     <title>Bidirectional-streams Over Synchronous HTTP (BOSH)</title>
     <abstract>This specification defines a transport protocol that emulates the semantics of a long-lived, bidirectional TCP connection between two entities (such as a client and a server) by efficiently using multiple synchronous HTTP request/response pairs without requiring the use of frequent polling or chunked responses.</abstract>
     &LEGALNOTICE;
@@ -585,7 +586,7 @@ Content-Length: 68
     <p>Note: If the connection manager did not specify a 'polling' attribute in the session creation response, then it MUST allow the client to poll as frequently as it chooses.</p>
   </section1>
   <section1 topic='Terminating the BOSH Session' anchor='terminate'>
-    <p>At any time, the client MAY gracefully terminate the session by sending a <body/> element with a 'type' attribute set to "terminate". The termination request MAY include one or more payloads that the connection manager MUST forward to the server to ensure graceful logoff. The payload in the termination request SHOULD NOT need any response from the server.</p>
+    <p>At any time, the client MAY gracefully terminate the session by sending a &lt;body/&gt; element with a 'type' attribute set to "terminate". The termination request MAY include one or more payloads that the connection manager MUST forward to the server to ensure graceful logoff. The payload in the termination request SHOULD NOT need any response from the server.</p>
     <example caption="Session termination by client">
 <![CDATA[POST /webclient HTTP/1.1
 Host: httpcm.example.com
@@ -600,7 +601,7 @@ Content-Length: 153
   <presence type='unavailable'
             xmlns='jabber:client'/>
 </body>]]></example>
-    <p>The connection manager SHOULD respond to this request with an HTTP 200 OK containing an empty &lt;body/&gt; element. The connection manager SHOULD acknowledge the session termination on the oldest connection with a HTTP 200 OK containing a <body/> element of the type 'terminate'. On all other open connections, the connection manager SHOULD respond with an HTTP 200 OK containing an empty <body/> element.</p>
+    <p>The connection manager SHOULD respond to this request with an HTTP 200 OK containing an empty &lt;body/&gt; element. The connection manager SHOULD acknowledge the session termination on the oldest connection with a HTTP 200 OK containing a &lt;body/&gt; element of the type 'terminate'. On all other open connections, the connection manager SHOULD respond with an HTTP 200 OK containing an empty &lt;body/&gt; element.</p>
       <example caption="Connection manager acknowledges termination">
 <![CDATA[HTTP/1.1 200 OK
 Content-Type: text/xml; charset=utf-8