From 667871628b56d6dfb188a74e4705e02b432b139c Mon Sep 17 00:00:00 2001
From: stpeter <stpeter@stpeter.im>
Date: Wed, 25 May 2011 09:17:35 -0600
Subject: [PATCH] 1.1

---
 xep-0178.xml | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/xep-0178.xml b/xep-0178.xml
index d39fd9b7..63942a03 100644
--- a/xep-0178.xml
+++ b/xep-0178.xml
@@ -11,7 +11,6 @@
   &LEGALNOTICE;
   <number>0178</number>
   <status>Active</status>
-  <interim/>
   <type>Informational</type>
   <sig>Standards</sig>
   <approver>Council</approver>
@@ -24,8 +23,8 @@
   &stpeter;
   &pgmillard;
   <revision>
-    <version>1.1rc7</version>
-    <date>in progress, last updated 2011-05-11</date>
+    <version>1.1</version>
+    <date>2011-05-25</date>
     <initials>psa</initials>
     <remark><p>Updated text and examples to be consistent with RFC 6120 and RFC 6125.</p></remark>
   </revision>
@@ -211,7 +210,7 @@
           ]]></example>
         </li>
         <li>
-          <p>If the client certificate does not contain a JID, then the client MAY include an authorization identity, but only if it desires to be authorized as a JID other than the address in the client certificate; else it MUST NOT include an authorization identity (this is shown in the following example by setting the XML character data of the &lt;auth/&gt; element to "=").</p>
+          <p>If the client certificate does not contain a JID, then the client MAY include an authorization identity, but only if it desires to be authorized as a JID other than the address specified during SASL negotiation; else it MUST NOT include an authorization identity (this is shown in the following example by setting the XML character data of the &lt;auth/&gt; element to "=").</p>
           <example><![CDATA[
 <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' 
       mechanism='EXTERNAL'>=</auth>