diff --git a/xep-0170.xml b/xep-0170.xml
index 22154ff4..ced79e31 100644
--- a/xep-0170.xml
+++ b/xep-0170.xml
@@ -24,6 +24,12 @@
   <supersededby/>
   <shortname>N/A</shortname>
   &stpeter;
+  <revision>
+    <version>0.5</version>
+    <date>2006-12-06</date>
+    <initials>psa</initials>
+    <remark>Per Council feedback, removed section on deprecated jabber:iq:auth protocol.</remark>
+  </revision>
   <revision>
     <version>0.4</version>
     <date>2006-08-02</date>
@@ -98,23 +104,6 @@
       <li>IM session establishment</li>
     </ol>
   </section2>
-  <section2 topic='Non-SASL Authentication' anchor='c2s-iqauth'>
-    <p>The legacy &xep0078; protocol can be used by clients to log into older (pre-XMPP) servers. In essence the "jabber:iq:auth" protocol is an older way of doing what the XMPP RFCs specify in the SASL, resource binding, and IM session stream features. Therefore the following order is RECOMMENDED:</p>
-    <ol>
-      <li>TLS</li>
-      <li>jabber:iq:auth</li>
-    </ol>
-    <p>If the "jabber:iq:auth" feature is negotiated, then SASL, resource binding, and IM session establishment MUST NOT be negotiated. TLS SHOULD be negotiated, but some older software will instead connect to an SSL-enabled port rather than upgrading port 5222 using TLS.</p>
-    <p>If both stream compression and non-SASL authentication are negotiated, the following order is RECOMMENDED:</p>
-    <ol>
-      <li>TLS</li>
-      <li>jabber:iq:auth</li>
-      <li>Stream compression</li>
-    </ol>
-  </section2>
-  <section2 topic='Advanced Message Processing' anchor='c2s-amp'>
-    <p>Support for the &xep0079; protocol is advertised as a stream feature but its use is not negotiated; therefore no recommendation is needed.</p>
-  </section2>
 </section1>
 <section1 topic='Server-to-Server Recommendations' anchor='s2s'>
   <section2 topic='Standard XMPP Features' anchor='s2s-xmpp'>