diff --git a/xep-0167.xml b/xep-0167.xml
index 0dc9d6bb..d02f1455 100644
--- a/xep-0167.xml
+++ b/xep-0167.xml
@@ -7,7 +7,7 @@
 <xep>
 <header>
   <title>Jingle RTP Sessions</title>
-  <abstract>This specification defines a Jingle application type for negotiating a session that uses the Real-time Transport Protocol (RTP) to exchange media such as voice or video. The application type includes a straightforward mapping to Session Description Protocol (SDP) for interworking with SIP media endpoints.</abstract>
+  <abstract>This specification defines a Jingle application type for negotiating one or more sessions that use the Real-time Transport Protocol (RTP) to exchange media such as voice or video. The application type includes a straightforward mapping to Session Description Protocol (SDP) for interworking with SIP media endpoints.</abstract>
   &LEGALNOTICE;
   <number>0167</number>
   <status>Proposed</status>
@@ -25,6 +25,12 @@
   &stpeter;
   &seanegan;
   &robmcqueen;
+  <revision>
+    <version>0.22</version>
+    <date>2008-06-09</date>
+    <initials>psa</initials>
+    <remark><p>Added name attribute to active element to mirror usage for mute element; clarified meaning of session in the context of this specification; recommended that all sessions established via the same Jingle negotiation should be treated as synchronized.</p></remark>
+  </revision>
   <revision>
     <version>0.21</version>
     <date>2008-06-09</date>
@@ -202,7 +208,8 @@
 </section1>
 
 <section1 topic='Application Format' anchor='format'>
-  <p>A Jingle RTP session is described by a content type that contains one application format and one transport method. The application format consists of one or more encodings contained within a wrapper &lt;description/&gt; element qualified by the 'urn:xmpp:tmp:jingle:apps:rtp' namespace &NSNOTE;. In the language of <cite>RFC 4566</cite> each encoding is a payload-type; therefore, each &lt;payload-type/&gt; element specifies an encoding that can be used for the RTP stream, as illustrated in the following example.</p>
+  <p>A Jingle RTP session is described by a content type that contains one application format and one transport method. Each &lt;content/&gt; element defines a single RTP session. A Jingle negotiation MAY result in the establishment of multiple RTP sessions (e.g., one for audio and one for video). An application SHOULD consider all of the RTP sessions that are established via the same Jingle negotiation to be synchronized for purposes of streaming, playback, recording, etc.</p>
+  <p>The application format consists of one or more encodings contained within a wrapper &lt;description/&gt; element qualified by the 'urn:xmpp:tmp:jingle:apps:rtp' namespace &NSNOTE;. In the language of <cite>RFC 4566</cite> each encoding is a payload-type; therefore, each &lt;payload-type/&gt; element specifies an encoding that can be used for the RTP stream, as illustrated in the following example.</p>
   <example caption="RTP description format"><![CDATA[
     <description xmlns='urn:xmpp:tmp:jingle:apps:rtp'>
       <payload-type id='96' name='speex' clockrate='16000'/>
@@ -442,7 +449,7 @@ delivery-method=inline; configuration=somebase16string;
       </tr>
       <tr>
         <td>&lt;active/&gt;</td>
-        <td>The principal or device is again actively participating in the session after having been on hold or on mute.</td>
+        <td>The principal or device is again actively participating in the session after having been on hold or on mute. The &lt;active/&lt; element MAY possess a 'name' attribute whose value specifies a particular session that is again active (e.g., activating the video aspect but not the voice aspect of a voice+video chat). If no 'name' attribute is included, the recipient MUST assume that all sessions are active.</td>
       </tr>
       <tr>
         <td>&lt;hold/&gt;</td>
@@ -450,7 +457,7 @@ delivery-method=inline; configuration=somebase16string;
       </tr>
       <tr>
         <td>&lt;mute/&gt;</td>
-        <td>The principal is temporarily stopping media output but continues to accept media input. The &lt;mute/&lt; element MAY possess a 'name' attribute whose value specifies a particular content-type to be muted (e.g., muting the video aspect but not the voice aspect of a voice+video chat). If no 'name' attribute is included, the recipient MUST assume that all content-types are to be muted.</td>
+        <td>The principal is temporarily stopping media output but continues to accept media input. The &lt;mute/&lt; element MAY possess a 'name' attribute whose value specifies a particular session to be muted (e.g., muting the video aspect but not the voice aspect of a voice+video chat). If no 'name' attribute is included, the recipient MUST assume that all sessions are to be muted.</td>
       </tr>
       <tr>
         <td>&lt;ringing/&gt;</td>
@@ -469,7 +476,7 @@ delivery-method=inline; configuration=somebase16string;
           action='session-info'
           initiator='romeo@montague.net/orchard'
           sid='a73sjjvkla37jfea'>
-    <active xmlns='urn:xmpp:tmp:jingle:apps:rtp:info'/>
+    <active xmlns='urn:xmpp:tmp:jingle:apps:rtp:info' name='webcam'/>
   </jingle>
 </iq>
     ]]></example>
@@ -1388,7 +1395,15 @@ Romeo                         Juliet
     xmlns='urn:xmpp:tmp:jingle:apps:rtp:info'
     elementFormDefault='qualified'>
 
-  <xs:element name='active' type='empty'/>
+  <xs:element name='active'>
+    <xs:complexType>
+      <xs:simpleContent>
+        <xs:extension base='empty'>
+          <xs:attribute name='name' type='xs:string' use='optional'/>
+        </xs:extension>
+      </xs:simpleContent>
+    </xs:complexType>
+  </xs:element>
 
   <xs:element name='hold' type='empty'/>